Triple
T33629217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K2K experiment |
E861502
|
entity |
| Predicate | producedNeutrinoBeamType |
P149334
|
FINISHED |
| Object | muon neutrino beam |
—
|
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: muon neutrino beam | Statement: [K2K experiment, producedNeutrinoBeamType, muon neutrino beam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedNeutrinoBeamType Context triple: [K2K experiment, producedNeutrinoBeamType, muon neutrino beam]
-
A.
neutrinoBeamType
chosen
Indicates the specific type or classification of a neutrino beam used or produced in an experimental or observational context.
-
B.
neutrinoProductionMethod
Indicates the process or mechanism by which neutrinos are generated or produced.
-
C.
neutrinoBeamDestination
Indicates the target location or object toward which a neutrino beam is directed or intended to travel.
-
D.
neutronFluxType
Indicates the specific classification or category of neutron flux characterizing how neutrons are distributed or behave in a given context.
-
E.
beamEnergyType
Indicates the type or category of energy used or produced by a beam in a given context.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 1, 2026, 1:41 a.m.