Triple
T17319220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waipapa Power Station |
E420510
|
entity |
| Predicate | hasAnnualGeneration |
P113164
|
FINISHED |
| Object | approximately 330 GWh |
—
|
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: approximately 330 GWh | Statement: [Waipapa Power Station, hasAnnualGeneration, approximately 330 GWh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnnualGeneration Context triple: [Waipapa Power Station, hasAnnualGeneration, approximately 330 GWh]
-
A.
recordAnnualGenerationYear
Indicates the year in which an entity’s annual generation (e.g., production or output) is recorded.
-
B.
averageAnnualGeneration
Indicates the typical amount of something produced or generated per year, averaged over a specified multi-year period.
-
C.
expectedAnnualGeneration
Indicates the amount of output (typically energy or production) that a system or asset is expected to generate over the course of a year.
-
D.
plantAnnualGeneration
chosen
Indicates the amount of electricity a plant generates over the course of a year.
-
E.
hasAnnualList
Indicates that an entity maintains or is associated with a list that is updated or issued on an annual basis.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399f84a881908dd99ecd7cc02708 |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.