Triple
T27107160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westinghouse 3-loop PWR |
E686612
|
entity |
| Predicate | primaryCoolantLoops |
P122285
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Westinghouse 3-loop PWR, primaryCoolantLoops, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCoolantLoops Context triple: [Westinghouse 3-loop PWR, primaryCoolantLoops, 3]
-
A.
hasReactorCoolantSystem
Indicates that an entity is equipped with or includes a reactor coolant system used to remove heat from a reactor.
-
B.
usesBoronInCoolant
Indicates that boron is employed as a component or additive in the coolant used in a system or process.
-
C.
primaryLoops
chosen
Indicates that the subject entity has one or more main or fundamental loop structures directly associated with it.
-
D.
hasCoolingTowers
Indicates that an entity possesses or is equipped with one or more cooling towers as part of its infrastructure or system.
-
E.
thermalNeutronReactor
Indicates that the subject is a nuclear reactor that operates using thermal (low-energy) neutrons to sustain its fission chain reaction.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: April 27, 2026, 8:51 a.m.