Triple
T17080586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reactor No. 4 |
E414457
|
entity |
| Predicate | coolantSystem |
P90828
|
FINISHED |
| Object | boiling light-water channels |
—
|
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: boiling light-water channels | Statement: [Reactor No. 4, coolantSystem, boiling light-water channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coolantSystem Context triple: [Reactor No. 4, coolantSystem, boiling light-water channels]
-
A.
coolant
Indicates that one entity functions as a coolant for another, serving to absorb and remove heat from it.
-
B.
coolantPressure
Indicates the pressure level exerted by a coolant within a cooling system or component.
-
C.
coolantBoilingLocation
Indicates the place or environment where a coolant reaches its boiling point or undergoes boiling.
-
D.
coolantLossOccurred
Indicates that a loss of coolant has taken place in the system or component in question.
-
E.
hasReactorCoolantSystem
chosen
Indicates that an entity is equipped with or includes a reactor coolant system used to remove heat from a reactor.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe2fe7c819099ab0586b1a119f6 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.