Triple
T3615978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tevatron |
E76600
|
entity |
| Predicate | maximumBeamEnergy |
P5351
|
FINISHED |
| Object | 1 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 TeV | Statement: [Tevatron, maximumBeamEnergy, 1 TeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumBeamEnergy Context triple: [Tevatron, maximumBeamEnergy, 1 TeV]
-
A.
maximumProtonEnergy
Indicates the highest energy value that protons can attain in a given system, process, or context.
-
B.
maximumProtonProtonCentreOfMassEnergy
Indicates the highest center-of-mass energy achievable in proton–proton collisions for a given experimental or physical setup.
-
C.
beamEnergy
chosen
Indicates the amount of energy carried by or assigned to a beam in a physical or engineered system.
-
D.
beamEnergyAfterUpgrade
Indicates the energy level of a beam following an upgrade or enhancement to the system that produces or accelerates it.
-
E.
beamEnergyUnit
Indicates the unit of measurement used to express the energy of a beam.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27c98088190a493c9eddf6b206a |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.