Triple
T5399443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Relativistic Heavy Ion Collider |
E120736
|
entity |
| Predicate | maximumCenterOfMassEnergyProtonProton |
P24995
|
FINISHED |
| Object | 500 GeV |
—
|
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: 500 GeV | Statement: [Relativistic Heavy Ion Collider, maximumCenterOfMassEnergyProtonProton, 500 GeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumCenterOfMassEnergyProtonProton Context triple: [Relativistic Heavy Ion Collider, maximumCenterOfMassEnergyProtonProton, 500 GeV]
-
A.
maximumProtonProtonCentreOfMassEnergy
chosen
Indicates the highest center-of-mass energy achievable in proton–proton collisions for a given experimental or physical setup.
-
B.
centerOfMassEnergy
Indicates the total energy available in the center-of-mass frame when two or more particles interact or collide.
-
C.
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.
-
D.
maximumProtonEnergy
Indicates the highest energy value that protons can attain in a given system, process, or context.
-
E.
beamEnergy
Indicates the amount of energy carried by or assigned to a beam in a physical or engineered system.
- 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_69bd4637b92c8190b815b6443ae4b323 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.