Triple
T29692445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D4500 |
E751246
|
entity |
| Predicate | approximateAgeYearsBP |
P52881
|
FINISHED |
| Object | 1.8 million years |
—
|
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: 1.8 million years | Statement: [D4500, approximateAgeYearsBP, 1.8 million years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateAgeYearsBP Context triple: [D4500, approximateAgeYearsBP, 1.8 million years]
-
A.
approximateAgeBeforePresent
chosen
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
B.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
-
C.
estimatedAgeYears
Indicates the approximate number of years assigned as an entity’s age based on estimation rather than exact measurement.
-
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.
ageAtDeposition
Indicates the age an entity had at the time a statement, record, or sample was formally deposited or submitted.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: April 28, 2026, 7:17 p.m.