Triple
T23269506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRESST |
E588248
|
entity |
| Predicate | usesOperatingTemperature |
P3958
|
FINISHED |
| Object | millikelvin temperatures |
—
|
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: millikelvin temperatures | Statement: [CRESST, usesOperatingTemperature, millikelvin temperatures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesOperatingTemperature Context triple: [CRESST, usesOperatingTemperature, millikelvin temperatures]
-
A.
operatingTemperature
chosen
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
B.
operatingTemperatureCategory
Indicates the temperature range classification within which an entity is designed or expected to operate.
-
C.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
D.
hasTemperatureRegime
Indicates that an entity is characterized by or associated with a particular pattern or regime of temperature conditions.
-
E.
hasTemperatureCategory
Indicates that an entity is associated with a specific qualitative temperature classification (e.g., hot, cold, warm).
- 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.