Triple
T7668402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | proton–antiproton collider at CERN |
E173682
|
entity |
| Predicate | laterUpgradedEnergy |
P24216
|
FINISHED |
| Object | 630 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: 630 GeV | Statement: [proton–antiproton collider at CERN, laterUpgradedEnergy, 630 GeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterUpgradedEnergy Context triple: [proton–antiproton collider at CERN, laterUpgradedEnergy, 630 GeV]
-
A.
postUpgradeInjectionEnergy
Indicates the energy level associated with an injection process after an upgrade has been applied.
-
B.
energyBeforeUpgrade
Indicates the amount or state of energy associated with an entity prior to a specified upgrade or improvement action.
-
C.
beamEnergyAfterUpgrade
chosen
Indicates the energy level of a beam following an upgrade or enhancement to the system that produces or accelerates it.
-
D.
upgradedBy
Indicates that an entity has been improved, enhanced, or moved to a higher version or level as a result of actions performed by another entity.
-
E.
successorEnergy
Indicates that one energy state, configuration, or value directly follows another in a defined sequence or progression.
- 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_69c699562484819086752091e3164a27 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7063dab1881909598b04999b8b690 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015f7430819099d3ea2781b7cee2 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4 p.m.