Triple
T8174850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamiokande experiment |
E190915
|
entity |
| Predicate | usedPhotodetectors |
P25632
|
FINISHED |
| Object | photomultiplier tubes |
—
|
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: photomultiplier tubes | Statement: [Kamiokande experiment, usedPhotodetectors, photomultiplier tubes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPhotodetectors Context triple: [Kamiokande experiment, usedPhotodetectors, photomultiplier tubes]
-
A.
numberOfDetectors
Indicates the quantity of detectors associated with or involved in a given entity or system.
-
B.
usedInDetector
chosen
Indicates that something (e.g., a component, material, or method) is employed as part of a detector or detection system.
-
C.
numberOfMainDetectors
Indicates the quantity of primary detectors associated with or used in a given context or system.
-
D.
vertexDetectorTechnology
Indicates the specific detection technology or method used in the vertex detector component of a particle physics or tracking system.
-
E.
detectorType
Indicates the specific kind or category of detector associated with an entity or measurement.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb480a7ac4819088fabd5bec6ba2e5 |
completed | March 31, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.