mirror of
https://github.com/explosion/spaCy.git
synced 2025-06-28 17:03:04 +03:00
Fix entity_id refactoring problems in docstrings.
This commit is contained in:
parent
c61654eef8
commit
6fc7997c06
|
@ -1,14 +1,11 @@
|
||||||
# cython: infer_types=True, profile=True
|
# cython: infer_types=True, profile=True
|
||||||
|
|
||||||
from ..typedefs cimport hash_t
|
|
||||||
|
|
||||||
from .kb cimport KnowledgeBase
|
|
||||||
from .kb_in_memory cimport InMemoryLookupKB
|
from .kb_in_memory cimport InMemoryLookupKB
|
||||||
from ..errors import Errors
|
from ..errors import Errors
|
||||||
|
|
||||||
cdef class Candidate:
|
cdef class Candidate:
|
||||||
"""A `Candidate` object refers to a textual mention that may or may not be resolved
|
"""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.
|
algorithm which will disambiguate the various candidates to the correct one.
|
||||||
Each candidate (mention, entity_id) pair is assigned a certain prior probability.
|
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.
|
entity_vector (List[float]): Entity embedding.
|
||||||
mention_hash (int): Mention hash.
|
mention_hash (int): Mention hash.
|
||||||
prior_prob (float): Prior probability of entity for this mention - i.e. the probability that, independent of
|
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
|
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.
|
doesn't) it might be better to eschew this information and always supply the same value.
|
||||||
"""
|
"""
|
||||||
|
|
Loading…
Reference in New Issue
Block a user