Triple
T10182727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strepsirrhini |
E236826
|
entity |
| Predicate | isAncestrallyRelatedTo |
P34787
|
FINISHED |
| Object | early primate lineages |
—
|
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: early primate lineages | Statement: [Strepsirrhini, isAncestrallyRelatedTo, early primate lineages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAncestrallyRelatedTo Context triple: [Strepsirrhini, isAncestrallyRelatedTo, early primate lineages]
-
A.
relationToAncestors
Indicates a familial relationship that connects an entity to one or more of its ancestors in a lineage or hierarchy.
-
B.
hasGenealogicalRelation
Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
-
C.
hasAncestralRoots
chosen
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
D.
isParentsFamilyOf
Indicates that one entity is the family (collective relatives) of another entity’s parents.
-
E.
isCrossoverOf
Indicates that one entity is a crossover derived from, combining elements of, or intersecting the domains of the referenced entities.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded3408b88190a7d981a6dcea48d9 |
completed | April 2, 2026, 4:14 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.