Triple

T29618287
Position Surface form Disambiguated ID Type / Status
Subject Bad Füssing E754922 entity
Predicate hasThermalWaterTemperature P4459 FINISHED
Object approximately 56 °C at the spring 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 56 °C at the spring | Statement: [Bad Füssing, hasThermalWaterTemperature, approximately 56 °C at the spring]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasThermalWaterTemperature
Context triple: [Bad Füssing, hasThermalWaterTemperature, approximately 56 °C at the spring]
  • A. hasThermalWaterUse
    Indicates that something makes use of thermal water, typically for purposes such as heating, bathing, energy production, or therapeutic applications.
  • B. hasTemperature chosen
    Indicates that an entity possesses or is characterized by a specific temperature value.
  • C. hasThermalCharacteristic
    Indicates that an entity possesses a specific thermal property or behavior, such as conductivity, capacity, or response to temperature.
  • D. hasThermalResource
    Indicates that an entity possesses, provides, or is associated with a source of thermal energy or heat-related capability.
  • E. thermalWaterType
    Indicates the specific classification or type of thermal water associated with an 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_69f0ef86b6ec8190a87fff07fd983b1e completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f6b2a65c7c8190ac40f1466ceadefc completed May 3, 2026, 2:27 a.m.
PD Predicate disambiguation batch_69f6b14d7d508190bc7d4c89dfba4a32 completed May 3, 2026, 2:22 a.m.
Created at: April 28, 2026, 6:33 p.m.