Triple
T14991018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Booster Neutrino Beam |
E373833
|
entity |
| Predicate | neutrinoMode |
P27468
|
FINISHED |
| Object | neutrino mode |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: neutrino mode | Statement: [Booster Neutrino Beam, neutrinoMode, neutrino mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neutrinoMode Context triple: [Booster Neutrino Beam, neutrinoMode, neutrino mode]
-
A.
neutrinoBurstDetected
Indicates that a sudden, significant increase in neutrino emissions has been observed or recorded.
-
B.
neutrinoFlavorAtSource
Indicates the specific neutrino flavor (e.g., electron, muon, tau) that a neutrino possesses at its point of origin or production.
-
C.
neutrinoBeamDestination
Indicates the target location or object toward which a neutrino beam is directed or intended to travel.
-
D.
decayMode
Indicates the specific process or pathway by which an unstable entity transforms or decays into other products.
-
E.
modeType
chosen
Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
- F. None of above.
Provenance (3 batches)
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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded715db408190b44e8a8452c79764 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:53 a.m.