Triple
T15658817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vermont Yankee Nuclear Power Corporation |
E376516
|
entity |
| Predicate | powerPlantFuel |
P119629
|
FINISHED |
| Object | uranium |
—
|
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: uranium | Statement: [Vermont Yankee Nuclear Power Corporation, powerPlantFuel, uranium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerPlantFuel Context triple: [Vermont Yankee Nuclear Power Corporation, powerPlantFuel, uranium]
-
A.
powerplantType
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
-
B.
powerplant
Indicates that an entity functions as a facility or installation where energy sources are converted into usable power, typically electricity.
-
C.
powerplantPower
Indicates that a power plant provides or generates a specified amount of electrical power.
-
D.
fuelTypeProduced
Indicates the type of fuel that is generated or produced by a given source, process, or facility.
-
E.
powerplantOutput
Indicates the amount of energy or power produced by a power plant over a given period or at a specific moment.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef3cb8c8190a10815b675b341c1 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:15 a.m.