Triple
T16516637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miette Hot Springs |
E401200
|
entity |
| Predicate | waterTemperatureAtSource |
P123862
|
FINISHED |
| Object | approximately 54 °C |
—
|
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: approximately 54 °C | Statement: [Miette Hot Springs, waterTemperatureAtSource, approximately 54 °C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterTemperatureAtSource Context triple: [Miette Hot Springs, waterTemperatureAtSource, approximately 54 °C]
-
A.
waterTemperatureType
Indicates the classification or category of a water body’s temperature (e.g., cold, warm, hot) associated with an entity or context.
-
B.
waterTemperatureComparedTo
Indicates how the temperature of one body or sample of water compares to the temperature of another.
-
C.
waterTemperatureForSpawning
Indicates the specific water temperature conditions required or suitable for an organism to begin or successfully carry out spawning.
-
D.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
E.
waterOrigin
Indicates the source or starting location from which the water originates or is supplied.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7c7e588190acbcc2b807a98909 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:14 a.m.