Triple
T29992342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRYSTAL BARREL |
E761914
|
entity |
| Predicate | hasDetectorTechnology |
P7243
|
FINISHED |
| Object | scintillating crystals |
—
|
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: scintillating crystals | Statement: [CRYSTAL BARREL, hasDetectorTechnology, scintillating crystals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDetectorTechnology Context triple: [CRYSTAL BARREL, hasDetectorTechnology, scintillating crystals]
-
A.
hasModeOfDetection
Indicates that one entity is identified, measured, or observed using a specified method or technique of detection.
-
B.
isDetector
Indicates that one entity functions as a detector for, or is responsible for detecting, another entity or phenomenon.
-
C.
detectorCapability
Indicates that one entity has the ability or functional capacity to detect, sense, or identify another entity or phenomenon.
-
D.
detectorType
chosen
Indicates the specific kind or category of detector associated with an entity or measurement.
-
E.
trackingDetectorTechnology
Indicates that an entity uses or is associated with a specific technology for tracking detectors (devices that measure and reconstruct particle trajectories).
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 29, 2026, 6:39 p.m.