Triple
T27107171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westinghouse 3-loop PWR |
E686612
|
entity |
| Predicate | reactorCoolantPumpsTotal |
P5505
|
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, reactorCoolantPumpsTotal, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactorCoolantPumpsTotal Context triple: [Westinghouse 3-loop PWR, reactorCoolantPumpsTotal, 3]
-
A.
numberOfReactors
Indicates the quantity of reactors associated with or contained by a given entity.
-
B.
hasReactorCoolantSystem
Indicates that an entity is equipped with or includes a reactor coolant system used to remove heat from a reactor.
-
C.
plannedNumberOfReactors
Indicates the total number of reactors that are intended or scheduled to be built, installed, or operated for a given facility or project.
-
D.
numberOfPumps
chosen
Indicates the quantity of pumps associated with or required by an entity or system.
-
E.
electricalCapacityPerReactor_MWe
Indicates the electrical power output capacity, measured in megawatts electric (MWe), that is provided by each individual 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623fef610819086a38b74d8c934b3 |
completed | May 2, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:51 a.m.