Triple
T9756956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NPF-57 |
E236576
|
entity |
| Predicate | thermalPowerLimit |
P18504
|
FINISHED |
| Object | licensed maximum reactor thermal power for Hope Creek |
—
|
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: licensed maximum reactor thermal power for Hope Creek | Statement: [NPF-57, thermalPowerLimit, licensed maximum reactor thermal power for Hope Creek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thermalPowerLimit Context triple: [NPF-57, thermalPowerLimit, licensed maximum reactor thermal power for Hope Creek]
-
A.
thermalPower
Indicates the amount of heat energy per unit time that a system, device, or process generates, transfers, or consumes.
-
B.
powerplantPower
Indicates that a power plant provides or generates a specified amount of electrical power.
-
C.
restrictsPowerOf
Indicates that one entity limits, constrains, or reduces the authority, control, or influence that another entity can exercise.
-
D.
powerplantOutput
Indicates the amount of energy or power produced by a power plant over a given period or at a specific moment.
-
E.
maximumPowerDuringOperation
chosen
Indicates the highest level of power that occurs while the system or component is operating.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9fb2889481908fba4a449d5007fe |
completed | April 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:24 p.m.