What is it getting wrong?
The correct parse has "eating" as an xcomp of "likes", and "sausage" as a dobj of "eating". You can see the correct parse for this structure if you plug "I like eating sausage" into the demo.
EDIT: Weirdly, the demo of the same software at http://nlp.stanford.edu:8080/parser/ doesn't make this mistake!
Weirdly, the demo of the same software at http://nlp.stanford.edu:8080/parser/ doesn't make this mistake!
See my rant about the config of CoreNLP: https://news.ycombinator.com/item?id=10350090
You're right that the configuration is confusing for new users. But, you have to remember that this is first and foremost research code intended to be flexible enough for the Stanford NLP group's research needs. In terms of particular configuration sources, nearly everything should be configurable from properties passed in as a properties file. Are there exceptions to this rule?
SUTime is documented to accept a property to a file that is read to obtain other properties. Quote:
sutime.rules = [path to rules file][1]
I'm unclear if that works - looking at our code it appears the properties files need to be in the classpath under a package that is defined by the sutime.rules property.
I don't remember how other packages worked.