Triple
T15786350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkana Boy |
E382746
|
entity |
| Predicate | approximateYearBP |
P52881
|
FINISHED |
| Object | about 1,600,000 years before present |
—
|
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,600,000 years before present | Statement: [Turkana Boy, approximateYearBP, about 1,600,000 years before present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateYearBP Context triple: [Turkana Boy, approximateYearBP, about 1,600,000 years before present]
-
A.
approximateAgeBeforePresent
chosen
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
B.
approximateStartCenturyBC
Indicates that an entity’s starting time or occurrence is approximately located within a specified century before the Common Era (BC).
-
C.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
-
D.
approximateUseEndCenturyBC
Indicates an estimated century BCE by which the use or activity associated with the subject is believed to have ended.
-
E.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0540380448190a025338f0e62e6d1 |
completed | April 16, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.