4 ms·

The dependency parse in the demo for "my dog also likes eating sausage" has "eating" as an adjective modifying "sausage". It's as if "eating sausage" were a kin

The dependency parse in the demo for "my dog also likes eating sausage" has "eating" as an adjective modifying "sausage". It's as if "eating sausage" were a kind of sausage. 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/ http://nlp.stanford.edu:8080/parser/ doesn't make this mistake!

nl 11y ago
Yes, I missed that. Good pickup. Weirdly, the demo of the same software at http://nlp.stanford.edu:8080/parser/ 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 https://news.ycombinator.com/item?id=10350090
- gangeli 11y ago
  These are likely using different parsers. Namely, the (faster) neural net dependency parser running at corenlp.run -- which gets thrown off by the POS tag error -- versus the constituency parser you linked to. 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?
  - nl 11y ago
    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. [1] http://nlp.stanford.edu/software/sutime.shtml http://nlp.stanford.edu/software/sutime.shtml
    - gangeli 11y ago
      This should be able to read rules from the filesystem as well (if not, it's a bug and we should fix it!). The reason all of the examples are classpath examples is just because we distribute our models as a jar by default. The SUTime rules could be thought of more as a "model" for the rule-based system rather than a configuration file.

nl 11y ago

Yes, I missed that. Good pickup. Weirdly, the demo of the same software at http://nlp.stanford.edu:8080/parser/ 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 https://news.ycombinator.com/item?id=10350090

gangeli 11y ago
These are likely using different parsers. Namely, the (faster) neural net dependency parser running at corenlp.run -- which gets thrown off by the POS tag error -- versus the constituency parser you linked to. 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?
- nl 11y ago
  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. [1] http://nlp.stanford.edu/software/sutime.shtml http://nlp.stanford.edu/software/sutime.shtml
  - gangeli 11y ago
    This should be able to read rules from the filesystem as well (if not, it's a bug and we should fix it!). The reason all of the examples are classpath examples is just because we distribute our models as a jar by default. The SUTime rules could be thought of more as a "model" for the rule-based system rather than a configuration file.