Triple
T1184025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CNGS |
E25204
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neutrino beam facility |
C4317
|
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: neutrino beam facility Context triple: [CNGS, instanceOf, neutrino beam facility]
-
A.
neutrino detector
A neutrino detector is a highly sensitive instrument or facility designed to observe and measure elusive neutrinos by capturing their rare interactions with matter, often deep underground or underwater to shield from background radiation.
-
B.
particle accelerator complex
chosen
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.
CERN accelerator complex component
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.
-
E.
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.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:45 p.m.