Triple
T4184136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taupō geothermal area |
E88268
|
entity |
| Predicate | hasEnergyType |
P5332
|
FINISHED |
| Object | renewable energy |
—
|
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: renewable energy | Statement: [Taupō geothermal area, hasEnergyType, renewable energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnergyType Context triple: [Taupō geothermal area, hasEnergyType, renewable energy]
-
A.
hasEnergyRole
Indicates that one entity plays a specific functional role in the production, distribution, management, or use of energy in relation to another entity.
-
B.
energyType
chosen
Indicates the kind or category of energy associated with an entity or process.
-
C.
hasEnergyFunction
Indicates that an entity is associated with, governed by, or characterized through a specific energy function.
-
D.
usesPowerType
Indicates that one entity operates or functions by means of a specified type or source of power.
-
E.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.