Triple
T30667918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Vöslau |
E780712
|
entity |
| Predicate | mineralSpringTemperature |
P123862
|
FINISHED |
| Object | about 26 °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: about 26 °C | Statement: [Bad Vöslau, mineralSpringTemperature, about 26 °C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mineralSpringTemperature Context triple: [Bad Vöslau, mineralSpringTemperature, about 26 °C]
-
A.
hasMineralSpringsTemperatureRange
Indicates the range of temperatures characteristic of the mineral springs associated with an entity.
-
B.
hasMineralSprings
Indicates that a place or entity possesses or is characterized by the presence of mineral springs.
-
C.
hasMineralSpringsType
Indicates that an entity is associated with or characterized by a specific type or category of mineral springs.
-
D.
waterTemperatureAtSource
chosen
Indicates the temperature of water measured at its point of origin or source location.
-
E.
hasHighestSpringTemperatureApprox
Indicates that an entity’s highest spring temperature is approximately equal to a specified value or that another entity’s highest spring temperature.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68ae5dfc08190af9d7f937b674f47 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:31 p.m.