Triple
T28016077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VVER-1000 |
E707547
|
entity |
| Predicate | coolantInletTemperature |
P163627
|
FINISHED |
| Object | about 290 °C |
—
|
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 290 °C | Statement: [VVER-1000, coolantInletTemperature, about 290 °C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coolantInletTemperature Context triple: [VVER-1000, coolantInletTemperature, about 290 °C]
-
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.
coolantFlowConfiguration
Indicates how coolant is routed or arranged to flow through a system or component.
-
D.
coolantBoilingLocation
Indicates the place or environment where a coolant reaches its boiling point or undergoes boiling.
-
E.
hasCoolingFlow
Indicates that an entity is equipped with or utilizes a system or mechanism to remove heat or maintain a lower temperature through the flow of a cooling medium.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c0796288190a5936b67d90abd00 |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 8:06 p.m.