Triple
T12496100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tithonian |
E298687
|
entity |
| Predicate | boundaryEvent |
P3589
|
FINISHED |
| Object | ends at the Jurassic–Cretaceous 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: ends at the Jurassic–Cretaceous boundary | Statement: [Tithonian, boundaryEvent, ends at the Jurassic–Cretaceous boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundaryEvent Context triple: [Tithonian, boundaryEvent, ends at the Jurassic–Cretaceous boundary]
-
A.
hasBoundaryEvent
chosen
Indicates that an event occurs at or defines the boundary or limit of another entity or process.
-
B.
boundaryReviewEvent
Indicates an event in which the boundaries or limits of something are formally examined, evaluated, or adjusted.
-
C.
closureEvent
Indicates an event or action in which something is formally brought to an end, completed, or shut down.
-
D.
parallelEvent
Indicates that two or more events occur at the same time or overlap in time without a required order between them.
-
E.
backgroundEvent
Indicates that one event occurs in the background relative to another primary or foreground event.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:57 p.m.