Triple
T7668400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | proton–antiproton collider at CERN |
E173682
|
entity |
| Predicate | collisionEnergyType |
P23072
|
FINISHED |
| Object | center-of-mass energy |
—
|
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: center-of-mass energy | Statement: [proton–antiproton collider at CERN, collisionEnergyType, center-of-mass energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collisionEnergyType Context triple: [proton–antiproton collider at CERN, collisionEnergyType, center-of-mass energy]
-
A.
collisionType
Indicates the specific kind or category of collision that occurs between two or more entities.
-
B.
collisionEventAgeApproximate
Indicates an estimated or approximate age associated with a collision event.
-
C.
wasWorldsHighestEnergyCollider
Indicates that a collider held the status of having the highest collision energy in the world at a given time.
-
D.
centerOfMassEnergy
chosen
Indicates the total energy available in the center-of-mass frame when two or more particles interact or collide.
-
E.
finalKineticEnergy
Indicates the amount of kinetic energy an entity possesses at the end of a specified process or time interval.
- 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.