Triple
T33629257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K2K experiment |
E861502
|
entity |
| Predicate | usedDetectorTechnology |
P76504
|
FINISHED |
| Object | water Cherenkov detection at far site |
—
|
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: water Cherenkov detection at far site | Statement: [K2K experiment, usedDetectorTechnology, water Cherenkov detection at far site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedDetectorTechnology Context triple: [K2K experiment, usedDetectorTechnology, water Cherenkov detection at far site]
-
A.
trackingDetectorTechnology
Indicates that an entity uses or is associated with a specific technology for tracking detectors (devices that measure and reconstruct particle trajectories).
-
B.
usedInDetector
Indicates that something (e.g., a component, material, or method) is employed as part of a detector or detection system.
-
C.
usesSearchTechnologyFrom
Indicates that one entity employs or relies on the search technology developed or provided by another entity.
-
D.
technologyUsedBy
chosen
Indicates that a particular technology is employed or utilized by a specified entity.
-
E.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
- 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.