Triple
T23269481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRESST |
E588248
|
entity |
| Predicate | usesDetectionMedium |
P25632
|
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: [CRESST, usesDetectionMedium, scintillating crystals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDetectionMedium Context triple: [CRESST, usesDetectionMedium, scintillating crystals]
-
A.
usesActiveMedium
Indicates that an entity performs an action or operates by employing an active medium as the means or channel for that action or process.
-
B.
mainDetector
Indicates that an entity serves as the primary or principal detector in relation to another entity or system.
-
C.
requiresDetectionOf
Indicates that one entity can only occur, be valid, or proceed if another entity has first been detected or identified.
-
D.
usedInDetector
chosen
Indicates that something (e.g., a component, material, or method) is employed as part of a detector or detection system.
-
E.
detected
Indicates that an entity has observed, identified, or discovered the presence or occurrence of another entity or event.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957219188190b30bceffad1542da |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:45 p.m.