Triple
T35227000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simav |
E1017124
|
entity |
| Predicate | geothermalFieldType |
P94841
|
FINISHED |
| Object | low- to medium-enthalpy geothermal field |
—
|
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- to medium-enthalpy geothermal field | Statement: [Simav, geothermalFieldType, low- to medium-enthalpy geothermal field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geothermalFieldType Context triple: [Simav, geothermalFieldType, low- to medium-enthalpy geothermal field]
-
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.
hasGeothermalField
Indicates that an entity possesses, contains, or is associated with a geothermal field.
-
D.
thermalWaterType
Indicates the specific classification or type of thermal water associated with an entity.
-
E.
hasGeothermalPotential
Indicates that an entity possesses conditions suitable for generating or exploiting geothermal energy.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.