Triple
T12283596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New World monkeys |
E292771
|
entity |
| Predicate | approximateDivergenceTime |
P63017
|
FINISHED |
| Object | 35–40 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: 35–40 million years ago | Statement: [New World monkeys, approximateDivergenceTime, 35–40 million years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDivergenceTime Context triple: [New World monkeys, approximateDivergenceTime, 35–40 million years ago]
-
A.
divergenceTime
chosen
Indicates the point in time at which two entities, lineages, or states split from a common origin or began to differ from each other.
-
B.
ancestralRange
Indicates the geographic area or region that a lineage or taxon historically occupied in its evolutionary past.
-
C.
approximateAgeBeforePresent
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
D.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
-
E.
hasApproximateDipOfOlderRocks
Indicates that the dip (inclination) of older rock layers is approximately equal to a specified dip value or orientation.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9261e1570819084bb4fdb44aa6aea |
completed | April 10, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69d91c4d9a9c8190aeb7beaf9792d8f0 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.