Triple
T23110667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand electricity grid |
E576308
|
entity |
| Predicate | energySourcesTransmitted |
P5332
|
FINISHED |
| Object | hydroelectric power |
—
|
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: hydroelectric power | Statement: [New Zealand electricity grid, energySourcesTransmitted, hydroelectric power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energySourcesTransmitted Context triple: [New Zealand electricity grid, energySourcesTransmitted, hydroelectric power]
-
A.
isMajorSourceOfElectricityFor
Indicates that one entity provides the primary or dominant share of electrical power used by another entity.
-
B.
energyType
chosen
Indicates the kind or category of energy associated with an entity or process.
-
C.
energyThroughputCategory
Indicates the classification of an entity based on the amount or level of energy it processes or transfers over a given period.
-
D.
energyTransferMethod
Indicates the process or mechanism by which energy is transferred from one entity or system to another.
-
E.
transferredPowerTo
Indicates that one entity has passed control, authority, or energy to another entity.
- 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_69e245f4af548190898d434a64a1e774 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e0e58308190a355de3ae81dd510 |
completed | April 29, 2026, 4:50 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:58 p.m.