Triple
T27107166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westinghouse 3-loop PWR |
E686612
|
entity |
| Predicate | typicalThermalPowerRange |
P200141
|
FINISHED |
| Object | 2400–3000 MWt |
—
|
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: 2400–3000 MWt | Statement: [Westinghouse 3-loop PWR, typicalThermalPowerRange, 2400–3000 MWt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalThermalPowerRange Context triple: [Westinghouse 3-loop PWR, typicalThermalPowerRange, 2400–3000 MWt]
-
A.
thermalPower
Indicates the amount of heat energy per unit time that a system, device, or process generates, transfers, or consumes.
-
B.
typicalElectricalOutputRange
Indicates the usual range of electrical power or energy output that an entity is expected to produce under normal operating conditions.
-
C.
electricalCapacityPerReactor_MWe
Indicates the electrical power output capacity, measured in megawatts electric (MWe), that is provided by each individual reactor.
-
D.
powerplantType
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
-
E.
powerplantPower
Indicates that a power plant provides or generates a specified amount of electrical power.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69ff779d3d788190af5a2dbc4d7ca3c8 |
completed | May 9, 2026, 6:06 p.m. |
Created at: April 27, 2026, 8:51 a.m.