Triple
T33588550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MSW effect |
E860355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neutrino oscillation phenomenon |
C27977
|
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 phenomenon Context triple: [MSW effect, instanceOf, neutrino oscillation phenomenon]
-
A.
flavor oscillation system
A flavor oscillation system is a physical framework in which particles can change their type (or "flavor") over time or distance due to quantum mechanical mixing of their underlying states.
-
B.
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.
-
C.
neutrino physics process
chosen
A neutrino physics process is an interaction or transformation involving neutrinos—such as their production, propagation, oscillation, or detection—governed by the weak force and described within the framework of particle physics.
-
D.
long-baseline neutrino experiment
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.
-
E.
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.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:40 a.m.