-
Notifications
You must be signed in to change notification settings - Fork 57
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
Adding OpenTapioca to the available annotators #316
Comments
Added OpenTapioca However, the benchmark results are currently not correct, e.g., the two results of the annotator are counted as fp and fn although they are overlapping the expected set of URIs.
|
Many thanks, that is wonderful! And I am very interested in the scoring issues of course, since it could potentially increase the scores I reported in the paper :) (By the way it looks like we both used "Tapioca" to name our projects - sorry about this conflict, if I knew I would have picked another name!) |
The issue is pretty easy 😄 Since http://dbpedia.org/resource/Sydney links to (@wetneb no problem. I am happy that you named it "OpenTapioca" which makes it easier to distinguish them 😉 ) |
A run without cached data, without the DBpedia index and with HTTP-based retrieval enabled solves the problem. So the index is simply outdated. |
If there is anything I can help with to move forward on this, let me know :) From my understanding it is simply a matter of merging 93c00d0 and updating the index, which I cannot do on your instance. |
Please excuse the long delay. We had some issues to update the indexes. http://gerbil.aksw.org/gerbil/experiment?id=201908220000 |
Thanks a lot! I will add a PR to enable it for A2KB too. |
Hi!
First, thanks for maintaining GERBIL, it is a very useful tool!
If you are interested, I am running an entity linker for Wikidata at https://opentapioca.org/ which exposes a NIF endpoint at https://opentapioca.org/api/nif. It could be nice to add it to the list of available annotators, although it is already possible to add it manually as a webservice.
The text was updated successfully, but these errors were encountered: