Triple
T37051468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitanian age |
E917059
|
entity |
| Predicate | timeEndUncertainty |
P35787
|
FINISHED |
| Object | about 0.5 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: about 0.5 million years | Statement: [Capitanian age, timeEndUncertainty, about 0.5 million years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeEndUncertainty Context triple: [Capitanian age, timeEndUncertainty, about 0.5 million years]
-
A.
timeStartUncertaintyMa
Indicates that there is uncertainty or imprecision regarding the starting time of an event or state, measured in millions of years ago (Ma).
-
B.
timeIntervalEndDefined
Indicates that the end point of a time interval is explicitly specified or determined.
-
C.
endTimeApproximate
chosen
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
D.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
E.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.