Triple
T33629221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K2K experiment |
E861502
|
entity |
| Predicate | beamTargetLocation |
P24989
|
FINISHED |
| Object | Super-Kamiokande |
—
|
NE NERFINISHED |
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: Super-Kamiokande | Statement: [K2K experiment, beamTargetLocation, Super-Kamiokande]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beamTargetLocation Context triple: [K2K experiment, beamTargetLocation, Super-Kamiokande]
-
A.
targetLocation
Indicates the specific place or destination toward which an action, movement, or effect is directed.
-
B.
plannedLocationRelativeToLHC
Indicates that an entity’s intended or proposed location is specified in relation to the Large Hadron Collider (LHC), such as its position, proximity, or orientation with respect to the LHC.
-
C.
targetedPosition
Indicates a relationship where an action, influence, or focus is specifically directed toward a particular position, role, or location.
-
D.
detectorPosition
Indicates the spatial location or placement of a detector relative to a reference frame or system.
-
E.
neutrinoBeamDestination
chosen
Indicates the target location or object toward which a neutrino beam is directed or intended to travel.
- 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_69f6f859cf8c8190a2a0d3d31e4392e7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:41 a.m.