-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Effect of the different possible parameter combinations for ‘mentions’ in the REST API #124
Comments
Thanks for reporting this @aa303554. This seems indeed a bug as the order of the processes on which mentions are extracted should not change the results. |
mmm it's not a bug, it depends on the order, and it's the expected result. Actually it has to consider the order. The This is probably easier to understand when using a specialized mention recognizer like a module to recognize the species name. It has to be applied first because it's the most specific (it already disambiguate the species name, so wikipedia is not as precise). However, the tool has no way to know in advance which one is the most specific, so the order is used. Ok we need to update the documentation to clarify that. |
The following observations come from the online API
1/When you reverse the order between ‘wikipedia’ and ‘ner’ in the mentions parameter, the result is different. Namely, when ‘ner’ comes second, NER isn’t performed at all. The documentation doesn’t cover this particular constraint.
For the order Wikipedia/ner:
Result with ner first and wikipedia second :
The text was updated successfully, but these errors were encountered: