Triple
T7668375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | proton–antiproton collider at CERN |
E173682
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proton–antiproton collider |
C1693
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: proton–antiproton collider Context triple: [proton–antiproton collider at CERN, instanceOf, proton–antiproton collider]
-
A.
hadron collider
chosen
A hadron collider is a type of particle accelerator that propels hadrons, such as protons or heavy ions, to extremely high energies and smashes them together to study fundamental particles and forces.
-
B.
particle accelerator complex
A particle accelerator complex is an integrated facility comprising accelerators, beamlines, detectors, and support infrastructure designed to accelerate charged particles to high energies for research, medical, or industrial applications.
-
C.
particle accelerator
A particle accelerator is a machine that uses electromagnetic fields to propel charged particles to high speeds and direct them into beams for research, medical, or industrial applications.
-
D.
antiproton decelerator ring
An antiproton decelerator ring is a circular accelerator facility designed to slow down high-energy antiprotons to low energies suitable for precision experiments in antimatter physics.
-
E.
circular particle accelerator
A circular particle accelerator is a device that uses magnetic fields to guide charged particles around a closed loop while electric fields repeatedly increase their energy for high-speed collisions or experiments.
- F. None of above.
Provenance (1 batch)
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. |
Created at: March 27, 2026, 4 p.m.