Triple
T14991505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDF Collaboration |
E373844
|
entity |
| Predicate | colliderEnergy |
P23072
|
FINISHED |
| Object | 1.8 TeV |
—
|
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: 1.8 TeV | Statement: [CDF Collaboration, colliderEnergy, 1.8 TeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colliderEnergy Context triple: [CDF Collaboration, colliderEnergy, 1.8 TeV]
-
A.
maximumProtonProtonCentreOfMassEnergy
Indicates the highest center-of-mass energy achievable in proton–proton collisions for a given experimental or physical setup.
-
B.
designedCenterOfMassEnergy
Indicates that one entity specifies the intended or planned center-of-mass energy at which another entity (such as an experiment, collider, or process) is meant to operate.
-
C.
beamEnergy
Indicates the amount of energy carried by or assigned to a beam in a physical or engineered system.
-
D.
centerOfMassEnergy
chosen
Indicates the total energy available in the center-of-mass frame when two or more particles interact or collide.
-
E.
wasWorldsHighestEnergyCollider
Indicates that a collider held the status of having the highest collision energy in the world at a given time.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded715db408190b44e8a8452c79764 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:53 a.m.