Triple
T32959776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Gas-cooled Reactor |
E843202
|
entity |
| Predicate | typicalOutletCoolantTemperature |
P164009
|
FINISHED |
| Object | about 640 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: about 640 degrees Celsius | Statement: [Advanced Gas-cooled Reactor, typicalOutletCoolantTemperature, about 640 degrees Celsius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOutletCoolantTemperature Context triple: [Advanced Gas-cooled Reactor, typicalOutletCoolantTemperature, about 640 degrees Celsius]
-
A.
coolantOutletTemperature
chosen
Indicates the temperature of the coolant as it exits a system, component, or process.
-
B.
coolantInletTemperature
Indicates the temperature of the coolant as it enters a specified component or system.
-
C.
coolantPressure
Indicates the pressure level exerted by a coolant within a cooling system or component.
-
D.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
E.
exhaustGasTemperature
Indicates the temperature of the exhaust gases produced by an engine or combustion process.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:21 a.m.