Triple
T6010083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T2K |
E133809
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neutrino oscillation experiment |
C13496
|
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 oscillation experiment Context triple: [T2K, instanceOf, neutrino oscillation experiment]
-
A.
neutrino experiment
A neutrino experiment is a scientific investigation designed to detect, measure, and analyze neutrinos and their interactions to study fundamental properties of matter and the universe.
-
B.
long-baseline neutrino experiment
chosen
A long-baseline neutrino experiment is a particle physics setup in which a beam of neutrinos is produced at one location and detected hundreds to thousands of kilometers away to study neutrino oscillations and fundamental properties.
-
C.
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.
-
D.
Fermilab experiment
A Fermilab experiment is a high-energy physics research project conducted at the Fermi National Accelerator Laboratory to investigate fundamental particles, forces, and the structure of matter using particle accelerators and detectors.
-
E.
muon magnetic moment experiment
A muon magnetic moment experiment precisely measures how the muon's intrinsic magnetic dipole deviates from the value predicted by the Standard Model, providing a sensitive test for new 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:06 p.m.