Triple
T25371796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hesperocyoninae |
E632949
|
entity |
| Predicate | earliestFossilAge |
P18580
|
FINISHED |
| Object | late Eocene |
—
|
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: late Eocene | Statement: [Hesperocyoninae, earliestFossilAge, late Eocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestFossilAge Context triple: [Hesperocyoninae, earliestFossilAge, late Eocene]
-
A.
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.
-
B.
earliestKnownAncestor
Indicates that one entity is the most distant (oldest) known ancestor in the lineage of another entity.
-
C.
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.
-
D.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
-
E.
fossilRangeQualifier
Indicates how the temporal range of a fossil (e.g., its first or last appearance in the geologic record) should be interpreted, refined, or qualified.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4a11323e08190a8ec4687f8fefe7f |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:38 p.m.