Triple
T28033075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Terraces |
E708323
|
entity |
| Predicate | geothermalProcess |
P33784
|
FINISHED |
| Object | hot water circulation through limestone |
—
|
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: hot water circulation through limestone | Statement: [Lower Terraces, geothermalProcess, hot water circulation through limestone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geothermalProcess Context triple: [Lower Terraces, geothermalProcess, hot water circulation through limestone]
-
A.
geologicalFormationProcess
chosen
Indicates the natural geological process or set of processes by which a particular geological formation came into existence.
-
B.
isGeothermalFieldType
Indicates that one entity is classified as a specific type or category of geothermal field in relation to another entity.
-
C.
causesGeologicalProcess
Indicates that one entity brings about, initiates, or is responsible for a geological process occurring in another or in the environment.
-
D.
hasGeothermalPotential
Indicates that an entity possesses conditions suitable for generating or exploiting geothermal energy.
-
E.
heatSource
Indicates that one entity serves as a source of heat or heating for 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:18 p.m.