explosion/spaCy
1
1
Fork 0
mirror of https://github.com/explosion/spaCy.git synced 2025-04-22 10:02:01 +03:00
Code Issues Packages Projects Releases Wiki Activity

Fix entity_id refactoring problems in docstrings.

Browse Source
This commit is contained in:
Raphael Mitsch 2023-03-10 08:55:32 +01:00
parent c61654eef8
commit 6fc7997c06
1 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
spacy/kb/candidate.pyx
View File

@ -1,14 +1,11 @@
# cython: infer_types=True, profile=True
from ..typedefs cimport hash_t
from .kb cimport KnowledgeBase
from .kb_in_memory cimport InMemoryLookupKB
from ..errors import Errors
cdef class Candidate:
"""A `Candidate` object refers to a textual mention that may or may not be resolved
to a specific `entity_id` from a Knowledge Base. This will be used as input for the entity_id linking
to a specific entity from a Knowledge Base. This will be used as input for the entity linking
algorithm which will disambiguate the various candidates to the correct one.
Each candidate (mention, entity_id) pair is assigned a certain prior probability.
@ -87,7 +84,7 @@ cdef class InMemoryCandidate(Candidate):
entity_vector (List[float]): Entity embedding.
mention_hash (int): Mention hash.
prior_prob (float): Prior probability of entity for this mention - i.e. the probability that, independent of
the context, this mention resolves to this entity_id in the corpus used to build the knowledge base. In
the context, this mention resolves to this entity in the corpus used to build the knowledge base. In
cases in which this isn't always possible (e.g.: the corpus to analyse contains mentions that the KB corpus
doesn't) it might be better to eschew this information and always supply the same value.
"""