Triple

T17147944
Position Surface form Disambiguated ID Type / Status
Subject Aulendorf–Kißlegg railway E416142 entity
Predicate serves P98 FINISHED
Object Bad Waldsee NE ONNED1

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 Waldsee | Statement: [Aulendorf–Kißlegg railway, serves, Bad Waldsee]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bad Waldsee
Context triple: [Aulendorf–Kißlegg railway, serves, Bad Waldsee]
  • A. Bad Waldsee chosen
    Bad Waldsee is a historic spa town in the German state of Baden-Württemberg, known for its thermal baths and picturesque old town.
  • B. Bad Wiessee
    Bad Wiessee is a Bavarian spa town in southern Germany, known for its therapeutic iodine-sulfur springs and scenic location on the shores of Lake Tegernsee.
  • C. Riegsee
    Riegsee is a picturesque lake in Bavaria, Germany, known for its clear waters and scenic Alpine surroundings.
  • D. Schottensee
    Schottensee is a picturesque alpine lake in the Pizol region of the Swiss Alps, popular with hikers for its clear blue waters and scenic mountain backdrop.
  • E. Hopfensee
    Hopfensee is a picturesque lake in the Allgäu region of Bavaria, Germany, known for its scenic mountain views and popular recreational activities.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d886d15af4819092f92f8a129763e6 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3f404f0e88190b7ac9ac523fdc7da completed April 18, 2026, 9:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0195428c6c8190a11e3f7c8f6796fe in_progress May 11, 2026, 8:37 a.m.
Created at: April 10, 2026, 5:36 a.m.