Triple
T21112564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saalian glaciation |
E520209
|
entity |
| Predicate | timeStartApproximate |
P48368
|
FINISHED |
| Object | about 0.3 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: about 0.3 million years ago | Statement: [Saalian glaciation, timeStartApproximate, about 0.3 million years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeStartApproximate Context triple: [Saalian glaciation, timeStartApproximate, about 0.3 million years ago]
-
A.
timeStartApprox
chosen
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
B.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
C.
timeframeApproximate
Indicates that the time period associated with an event or relation is not exact but only roughly or loosely specified.
-
D.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
E.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
- 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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72103b3888190a19e9a40f01fb439 |
completed | April 21, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:54 p.m.