Triple
T1996445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silurian |
E43370
|
entity |
| Predicate | startBoundaryEvent |
P3589
|
FINISHED |
| Object | end-Ordovician mass extinction |
—
|
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: end-Ordovician mass extinction | Statement: [Silurian, startBoundaryEvent, end-Ordovician mass extinction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startBoundaryEvent Context triple: [Silurian, startBoundaryEvent, end-Ordovician mass extinction]
-
A.
hasBoundaryEvent
chosen
Indicates that an event occurs at or defines the boundary or limit of another entity or process.
-
B.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
C.
setsBoundary
Indicates that one entity defines or forms the limiting edge or border of another entity.
-
D.
startPoint
Indicates the initial location or position from which an object, path, or action begins.
-
E.
startOfRule
Indicates that one element marks the beginning boundary or initial segment of a specified rule.
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb91055d88190a980e7b42e5895d4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb79c97d48190b3147430ed39faa9 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.