Skip to content
Discussion options

You must be logged in to vote

Hi!

Because the Knowledge Base can potentially grow quite big, we've opted to make it as efficient as possible for the retrieval task required by the Entity Linker - which is retrieving possible KB ID's, given a certain alias/mention. Unfortunately this also means that querying the other way around (ID -> set of aliases) will be inefficient in the current implementation. To add insult to injury, the description is never stored in its original string form, only the vectorized form of it. Again, because of efficiency reasons in the core implementation.

One solution for your use-case could be to create a subclass of KnowledgeBase that reimplements the add_entity, set_entities, add_alias and a…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by svlandeg
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat / nel Feature: Named Entity linking
2 participants
Converted from issue

This discussion was converted from issue #6778 on January 20, 2021 21:15.