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
Added configuration option to resolve within a given ontology #290
Conversation
…side a given ontology.
@MFSY this is ready to be reviewed |
Codecov Report
@@ Coverage Diff @@
## master #290 +/- ##
==========================================
+ Coverage 72.68% 72.85% +0.17%
==========================================
Files 86 88 +2
Lines 5499 5574 +75
==========================================
+ Hits 3997 4061 +64
- Misses 1502 1513 +11
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
I proposed to use the existing resolving 'target' as a way to specify the ontology to resolve to. |
kgforge/specializations/resolvers/entity_linking/service/entity_linking_elastic_service.py
Outdated
Show resolved
Hide resolved
@MFSY Done, now it uses a dictionary. I also changed |
The option to search within an ontology was added inside the configuration file, and the parameter to trigger this is
resolving_context
which should match one of thecontexts
names provided in the configuration.Done: