Triple
T23269502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRESST |
E588248
|
entity |
| Predicate | discriminatesEventsBy |
P151610
|
FINISHED |
| Object | simultaneous phonon and light readout |
—
|
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: simultaneous phonon and light readout | Statement: [CRESST, discriminatesEventsBy, simultaneous phonon and light readout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discriminatesEventsBy Context triple: [CRESST, discriminatesEventsBy, simultaneous phonon and light readout]
-
A.
treatsEventsAs
Indicates that one entity regards, handles, or interprets certain occurrences or inputs specifically as events, typically for the purpose of processing, categorization, or response.
-
B.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
C.
interpretsEvent
Indicates that an entity analyzes and assigns meaning or significance to an event.
-
D.
accessibleForEventType
Indicates that something can be used, reached, or is available in the context of a specified type or category of event.
-
E.
selectedEvent
Indicates that a particular event has been chosen or designated from a set of possible events.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:45 p.m.