Triple
T15639430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D0 |
E376027
|
entity |
| Predicate | dataTakingEndedWith |
P9293
|
FINISHED |
| Object | shutdown of the Tevatron collider |
—
|
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: shutdown of the Tevatron collider | Statement: [D0, dataTakingEndedWith, shutdown of the Tevatron collider]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTakingEndedWith Context triple: [D0, dataTakingEndedWith, shutdown of the Tevatron collider]
-
A.
useEnded
Indicates that an entity’s period of using or employing another entity has come to an end.
-
B.
alsoEnded
Indicates that one event or state concluded in addition to another already mentioned event or state.
-
C.
stoppedAt
Indicates that an entity has come to a halt or pause at a specific location or point in time.
-
D.
statusEndsWhen
Indicates that a particular status or condition ceases to hold when a specified event, time, or state occurs.
-
E.
endOfExperiment
chosen
Indicates that a specific point in time or condition marks the completion or termination of an experiment.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed06b388190bfebb77fe70e7df1 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.