Triple

T21748581
Position Surface form Disambiguated ID Type / Status
Subject District of Coburg E536850 entity
Predicate hasCity P316 FINISHED
Object Bad Rodach NE NERFINISHED

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: Bad Rodach | Statement: [District of Coburg, hasCity, Bad Rodach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bad Rodach
Context triple: [District of Coburg, hasCity, Bad Rodach]
  • A. Bad Rodach chosen
    Bad Rodach is a small spa town in northern Bavaria, Germany, known for its thermal baths and historic Franconian charm.
  • B. Bad Grönenbach
    Bad Grönenbach is a spa town in the Bavarian Allgäu region of southern Germany, known for its health resorts and picturesque rural surroundings.
  • C. Bad Ragaz
    Bad Ragaz is a Swiss spa and resort town in the canton of St. Gallen, renowned for its thermal baths and alpine setting.
  • D. Bad Breisig
    Bad Breisig is a small spa town on the Rhine River in western Germany, known for its thermal baths and scenic riverside setting.
  • E. Bad Nauheim
    Bad Nauheim is a spa town in the German state of Hesse, historically known for its therapeutic mineral springs and health resorts.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c46eab808190b848242d63a17c47 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f01a77e19c81909bf26f96aa41a7ce completed April 28, 2026, 2:24 a.m.
Created at: April 16, 2026, 6:50 p.m.