Triple
T4179325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotorua geothermal area |
E86553
|
entity |
| Predicate | hasEnergyUse |
P5332
|
FINISHED |
| Object | direct-use geothermal heating |
—
|
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: direct-use geothermal heating | Statement: [Rotorua geothermal area, hasEnergyUse, direct-use geothermal heating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnergyUse Context triple: [Rotorua geothermal area, hasEnergyUse, direct-use geothermal heating]
-
A.
energyUse
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
B.
electricityUse
Indicates the amount or pattern of electrical energy consumed by an entity during a specified period or activity.
-
C.
hasEnergyManagement
Indicates that an entity possesses or is associated with a system, capability, or function for monitoring, controlling, or optimizing energy use.
-
D.
energyType
chosen
Indicates the kind or category of energy associated with an entity or process.
-
E.
hasEnergyRole
Indicates that one entity plays a specific functional role in the production, distribution, management, or use of energy in relation 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_69aed93de98c8190ad838ce507b77c8a |
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.