Triple
T5647857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Akutan |
E124426
|
entity |
| Predicate | geothermalPotentialUse |
P15520
|
FINISHED |
| Object | geothermal energy development |
—
|
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: geothermal energy development | Statement: [Mount Akutan, geothermalPotentialUse, geothermal energy development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geothermalPotentialUse Context triple: [Mount Akutan, geothermalPotentialUse, geothermal energy development]
-
A.
hasGeothermalPotential
chosen
Indicates that an entity possesses conditions suitable for generating or exploiting geothermal energy.
-
B.
hasGeothermalField
Indicates that an entity possesses, contains, or is associated with a geothermal field.
-
C.
hasThermalWaterUse
Indicates that something makes use of thermal water, typically for purposes such as heating, bathing, energy production, or therapeutic applications.
-
D.
hydropowerPotential
Indicates the amount of energy that could be generated from water resources at a given site or region under specified conditions.
-
E.
reservoirUse
Indicates the way a reservoir is utilized or the purpose for which its stored water is used.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022d1534c8190ac4828e44300fb91 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:42 p.m.