Triple
T27281392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo antecessor |
E688340
|
entity |
| Predicate | earliestFossilsAge |
P18580
|
FINISHED |
| Object | about 1.2 million years ago |
—
|
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: about 1.2 million years ago | Statement: [Homo antecessor, earliestFossilsAge, about 1.2 million years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestFossilsAge Context triple: [Homo antecessor, earliestFossilsAge, about 1.2 million years ago]
-
A.
latestFossilsAge
Indicates the age of the most recently formed fossils associated with an entity or location.
-
B.
fossilRecordExtendsBackTo
chosen
Indicates that the existence or presence of something is documented in the fossil record as originating from a specified time or geological period.
-
C.
earliestKnownAncestor
Indicates that one entity is the most distant (oldest) known ancestor in the lineage of another entity.
-
D.
geologicalAge
Indicates the time period in Earth's geological history during which an entity (such as a rock, fossil, or formation) originated or was formed.
-
E.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
- 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_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 11:07 a.m.