Triple
T8322050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanagridae sensu lato |
E194855
|
entity |
| Predicate | taxonomicConcept |
P53195
|
FINISHED |
| Object | sensu lato |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: sensu lato | Statement: [Tanagridae sensu lato, taxonomicConcept, sensu lato]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxonomicConcept Context triple: [Tanagridae sensu lato, taxonomicConcept, sensu lato]
-
A.
speciesConcept
Indicates a conceptual or taxonomic relationship in which an entity is classified as a particular biological species or is associated with a specific species definition.
-
B.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
C.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
D.
taxonCircumscription
chosen
Indicates the taxonomic scope or boundary within which a particular taxon is defined or delimited in a classification.
-
E.
taxonomicStatus
Indicates the formal classification status of a taxon within a taxonomic system, such as whether it is accepted, synonymized, provisional, or invalid.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f693ad08190ad4ce6269a61eb3f |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:55 p.m.