Triple
T14753852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pressurised water reactor |
E346679
|
entity |
| Predicate | coolantOutletTemperatureTypical |
P19296
|
FINISHED |
| Object | Around 300 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: Around 300 degrees Celsius | Statement: [Pressurised water reactor, coolantOutletTemperatureTypical, Around 300 degrees Celsius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coolantOutletTemperatureTypical Context triple: [Pressurised water reactor, coolantOutletTemperatureTypical, Around 300 degrees Celsius]
-
A.
coolantPressure
Indicates the pressure level exerted by a coolant within a cooling system or component.
-
B.
coolant
Indicates that one entity functions as a coolant for another, serving to absorb and remove heat from it.
-
C.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
D.
exhaustGasTemperature
Indicates the temperature of the exhaust gases produced by an engine or combustion process.
-
E.
typicalTemperature
chosen
Indicates the usual or characteristic temperature associated with an entity under normal conditions.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d59df08190a86da5048358bd6e |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.