Triple
T27281401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo antecessor |
E688340
|
entity |
| Predicate | possibleCommonAncestorOf |
P133657
|
FINISHED |
| Object | Neanderthals and modern humans |
—
|
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: Neanderthals and modern humans | Statement: [Homo antecessor, possibleCommonAncestorOf, Neanderthals and modern humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleCommonAncestorOf Context triple: [Homo antecessor, possibleCommonAncestorOf, Neanderthals and modern humans]
-
A.
sharesCommonAncestorWith
Indicates that two entities have at least one ancestor in common in their lineage or hierarchy.
-
B.
hasCommonRepresentative
Indicates that two or more entities share the same person or organization acting as their representative.
-
C.
commonBasis
Indicates that two or more entities share an underlying foundation, principle, or set of assumptions that supports or explains their relationship.
-
D.
hasCommonAncestryGroup
Indicates that the related entities share membership in the same ancestral or lineage-based group.
-
E.
proposesAncestor
chosen
Indicates that one entity puts forward or suggests another entity as a possible ancestor in a lineage or hierarchy.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 11:07 a.m.