Triple
T20755009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barun Goyot Formation |
E510821
|
entity |
| Predicate | ageInMa |
P114406
|
FINISHED |
| Object | approximately 80–72 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: approximately 80–72 million years ago | Statement: [Barun Goyot Formation, ageInMa, approximately 80–72 million years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageInMa Context triple: [Barun Goyot Formation, ageInMa, approximately 80–72 million years ago]
-
A.
age_Ma
chosen
Indicates the age of something measured in millions of years (mega-annum).
-
B.
endAgeMa
Indicates the age (in years) at which a marriage or marital relationship ends.
-
C.
minimumAgeMa
Indicates that there is a specified minimum age requirement associated with an entity, below which the related action, status, or relationship is not permitted.
-
D.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
E.
maximumAgeMa
Indicates that there is a specified maximum age limit applicable to an entity or relationship.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c22e0d288190ba924423af59d70d |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:34 p.m.