Triple
T18308522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orakei Korako geothermal field |
E438552
|
entity |
| Predicate | Ruatapu CavePoolType |
P131279
|
FINISHED |
| Object | acidic hot pool |
—
|
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: acidic hot pool | Statement: [Orakei Korako geothermal field, Ruatapu CavePoolType, acidic hot pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Ruatapu CavePoolType Context triple: [Orakei Korako geothermal field, Ruatapu CavePoolType, acidic hot pool]
-
A.
caveType
Indicates the specific classification or kind of cave associated with an entity.
-
B.
karstFeature
Indicates a relationship where a geographic entity is identified as, or associated with, a karst-related landform or feature formed by the dissolution of soluble rocks.
-
C.
isKarstCave
Indicates that a cave is formed primarily through the dissolution of soluble rocks (such as limestone), characterizing it as a karst-type cave.
-
D.
hasNearbyCave
Indicates that one entity is located close to or in the vicinity of a cave associated with another entity.
-
E.
caveNumber
Indicates a relationship where an entity is assigned or associated with a specific cave identifier or number.
- F. None of above. chosen
Provenance (4 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50215e0c48190a4679d432b6ee596 |
completed | April 19, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:35 a.m.