Triple
T1889248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALPHA experiment |
E41831
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | antimatter experiment |
C3060
|
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: antimatter experiment Context triple: [ALPHA experiment, instanceOf, antimatter experiment]
-
A.
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.
-
B.
kaon decay experiment
A kaon decay experiment is a particle physics study that produces and observes kaons to measure their decay modes, lifetimes, and symmetry-violating processes, testing the predictions of the Standard Model.
-
C.
forward physics experiment
A forward physics experiment is a particle physics setup designed to study particles produced at very small angles relative to the beam direction, typically far from the interaction point, to probe phenomena such as diffraction, elastic scattering, and very low–momentum-transfer processes.
-
D.
physics experiment
chosen
A physics experiment is a controlled procedure designed to test hypotheses, observe phenomena, and measure physical quantities to understand the laws governing the natural world.
-
E.
particle accelerator upgrade project
A particle accelerator upgrade project is a coordinated engineering and scientific effort to enhance an existing accelerator’s performance, capabilities, or reliability through targeted hardware, software, and infrastructure improvements.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:34 p.m.