Triple
T33629256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K2K experiment |
E861502
|
entity |
| Predicate | neutrinoBeamDirection |
P24989
|
FINISHED |
| Object | from KEK to Super-Kamiokande |
—
|
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: from KEK to Super-Kamiokande | Statement: [K2K experiment, neutrinoBeamDirection, from KEK to Super-Kamiokande]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neutrinoBeamDirection Context triple: [K2K experiment, neutrinoBeamDirection, from KEK to Super-Kamiokande]
-
A.
neutrinoBeamType
Indicates the specific type or classification of a neutrino beam used or produced in an experimental or observational context.
-
B.
neutrinoBeamDestination
chosen
Indicates the target location or object toward which a neutrino beam is directed or intended to travel.
-
C.
detectedNeutrinoSource
Indicates that a particular source has been observed and identified as emitting detectable neutrinos.
-
D.
receivesAntineutrinosFrom
Indicates that one entity is the source from which another entity detects or is exposed to antineutrinos.
-
E.
neutrinoProductionMethod
Indicates the process or mechanism by which neutrinos are generated or produced.
- 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_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:41 a.m.