Triple
T6010318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LHC insertion region for CMS |
E133814
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | LHC insertion region |
C1695
|
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: LHC insertion region Context triple: [LHC insertion region for CMS, instanceOf, LHC insertion region]
-
A.
LHC run
An LHC run is a defined operational period of the Large Hadron Collider during which proton or ion beams are circulated and collided under specific energy and luminosity conditions to collect experimental data.
-
B.
CERN experiment
A CERN experiment is a large-scale, collaborative scientific investigation conducted at CERN’s particle physics facilities to study fundamental particles and forces using high-energy collisions and advanced detectors.
-
C.
CERN accelerator complex component
chosen
A CERN accelerator complex component is a specialized physical or control-system element—such as magnets, RF cavities, beamlines, detectors, or power and cooling infrastructure—that collectively enables the production, acceleration, steering, and monitoring of particle beams for experimental research.
-
D.
hadron collider
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.
-
E.
Tevatron experiment
A Tevatron experiment is a high-energy particle physics investigation conducted using the Tevatron proton–antiproton collider at Fermilab to study fundamental particles and forces.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:06 p.m.