Triple
T18402754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngawha geothermal field |
E450036
|
entity |
| Predicate | geothermalType |
P94841
|
FINISHED |
| Object | low-enthalpy system |
—
|
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: low-enthalpy system | Statement: [Ngawha geothermal field, geothermalType, low-enthalpy system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geothermalType Context triple: [Ngawha geothermal field, geothermalType, low-enthalpy system]
-
A.
isGeothermalFieldType
chosen
Indicates that one entity is classified as a specific type or category of geothermal field in relation to another entity.
-
B.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
-
C.
hasGeothermalPotential
Indicates that an entity possesses conditions suitable for generating or exploiting geothermal energy.
-
D.
hasGeothermalField
Indicates that an entity possesses, contains, or is associated with a geothermal field.
-
E.
typeOfVolcanicFeature
Indicates that one entity is classified as a specific kind or category of volcanic feature represented by the other 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e519537eb88190bc85d21471e27c26 |
completed | April 19, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:46 a.m.