Triple
T2254436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eocene–Oligocene climate transition |
E49688
|
entity |
| Predicate | occursAtTime |
P24433
|
FINISHED |
| Object | Eocene–Oligocene boundary |
—
|
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: Eocene–Oligocene boundary | Statement: [Eocene–Oligocene climate transition, occursAtTime, Eocene–Oligocene boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursAtTime Context triple: [Eocene–Oligocene climate transition, occursAtTime, Eocene–Oligocene boundary]
-
A.
occursAt
chosen
Indicates that an event or action takes place at a specific time or location.
-
B.
occursWhen
Indicates that one event or condition happens at the same time or is triggered under the circumstances defined by another event or condition.
-
C.
presentedAtTime
Indicates that an event, action, or item was presented or occurred at a specific point in time.
-
D.
occurredDuring
Indicates that one event or action took place within the temporal span of another event or time period.
-
E.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc121af78819085b2e601d2f9bcdf |
completed | March 7, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.