Triple
T31494742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrison Hot Springs |
E803503
|
entity |
| Predicate | waterSourceForHotSprings |
P4102
|
FINISHED |
| Object | geothermal aquifer |
—
|
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 aquifer | Statement: [Harrison Hot Springs, waterSourceForHotSprings, geothermal aquifer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterSourceForHotSprings Context triple: [Harrison Hot Springs, waterSourceForHotSprings, geothermal aquifer]
-
A.
waterSource
chosen
Indicates that one entity serves as the source or provider of water for another entity.
-
B.
thermalWaterType
Indicates the specific classification or type of thermal water associated with an entity.
-
C.
thermalWaterDiscovered
Indicates that a source of thermal water has been found or identified, typically as a result of exploration or investigation.
-
D.
waterOrigin
Indicates the source or starting location from which the water originates or is supplied.
-
E.
waterSourceType
Indicates the kind or category of source from which water is obtained.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 30, 2026, 9:40 p.m.