Triple
T18127320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITER |
E433908
|
entity |
| Predicate | designedPlasmaTemperature |
P3958
|
FINISHED |
| Object | over 150 million degrees Celsius |
—
|
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: over 150 million degrees Celsius | Statement: [ITER, designedPlasmaTemperature, over 150 million degrees Celsius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedPlasmaTemperature Context triple: [ITER, designedPlasmaTemperature, over 150 million degrees Celsius]
-
A.
maxSurfaceTemperature
Indicates the highest temperature that the surface of an entity can reach or sustain under specified conditions.
-
B.
surfaceTemperature_K
Indicates the temperature of a surface expressed in kelvins.
-
C.
hasEffectiveTemperature
Indicates that an entity (typically a star or other astronomical object) possesses a specific effective surface temperature characterizing its emitted radiation.
-
D.
firingTemperature
Indicates the temperature at which a material or object is heated during a firing process (such as in a kiln or furnace).
-
E.
operatingTemperature
chosen
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddef4cd88190b16ef0d6ed3968c6 |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.