Triple
T3631644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DØ detector |
E76967
|
entity |
| Predicate | successorExperimentAtSite |
P49682
|
FINISHED |
| Object | none (Tevatron shut down) |
—
|
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: none (Tevatron shut down) | Statement: [DØ detector, successorExperimentAtSite, none (Tevatron shut down)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorExperimentAtSite Context triple: [DØ detector, successorExperimentAtSite, none (Tevatron shut down)]
-
A.
successorStateSite
Indicates that one site or state of a site directly follows another as its immediate successor in a sequence or process.
-
B.
successorUseOfSite
Indicates that one use or function of a site directly follows and replaces a previous use of that same site in time.
-
C.
successorBuildingOnSite
Indicates that one building directly replaces another on the same physical site or location.
-
D.
successorState
Indicates that one state directly follows another as the immediate next state in a sequence or process.
-
E.
successorConfiguration
Indicates that one configuration directly follows another as its immediate next state in a sequence or process.
- F. None of above. chosen
Provenance (4 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc30251d881908284edeb7fe69ad8 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb842be7c8190b7dfdb7c906f294c |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:23 p.m.