Could not find any data to train the Entity Linker on. #10704
-
Hi!I have been trying to build an Entity Linker model. I have been following the demo project along with the video. I have annotated my data and created my training and dev set in spacy format as well. When I try to train the EntityLinker, I get an error saying that there is no training data.
Which is absurd because I have followed the format of scripts as given for spacy's v3 config system. The only difference is I have multiple entities for each |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
It looks like that warning can only be issued in v1 of the EntityLinker, and it only comes up if you have a batch with no annotations. This could happen if some of the docs in your training set happen to not have any entities in them, or the entites present have no entries in your knowledge base. If it is happening only sometimes it is not necessarily a problem, and could be caused by an unlucky batch. (Do note that unlike some other components, the EntityLinker isn't really helped by data that correctly has no annotations.) If you can share an example document / knowledge base that by themselves have this problem we could look at it more. Alternately, you could upgrade to v2 of the EntityLinker architecture - you should just need to change the version in your config if you're using a recent enough version of spaCy. |
Beta Was this translation helpful? Give feedback.
It looks like that warning can only be issued in v1 of the EntityLinker, and it only comes up if you have a batch with no annotations. This could happen if some of the docs in your training set happen to not have any entities in them, or the entites present have no entries in your knowledge base. If it is happening only sometimes it is not necessarily a problem, and could be caused by an unlucky batch. (Do note that unlike some other components, the EntityLinker isn't really helped by data that correctly has no annotations.)
If you can share an example document / knowledge base that by themselves have this problem we could look at it more. Alternately, you could upgrade to v2 of the Entit…