Triple

T8790030
Position Surface form Disambiguated ID Type / Status
Subject Oberndorf am Neckar E209138 entity
Predicate hasCityHall P796 FINISHED
Object Rathaus Oberndorf am Neckar E209138 NE 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: Rathaus Oberndorf am Neckar | Statement: [Oberndorf am Neckar, hasCityHall, Rathaus Oberndorf am Neckar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rathaus Oberndorf am Neckar
Context triple: [Oberndorf am Neckar, hasCityHall, Rathaus Oberndorf am Neckar]
  • A. Oberndorf am Neckar chosen
    Oberndorf am Neckar is a small town in the German state of Baden-Württemberg, historically known for its arms manufacturing industry.
  • B. Oberdorf
    Oberdorf is a Swiss municipality situated in the central alpine canton of Nidwalden.
  • C. Oberdorf
    Oberdorf is a locality within the Austrian municipality of Wolfurt in the state of Vorarlberg.
  • D. Oberaudorf
    Oberaudorf is a small Bavarian town in southern Germany near the Austrian border, known for its alpine scenery and ski tourism.
  • E. Oberdorf (SO)
    Oberdorf (SO) is a municipality in the canton of Solothurn in northwestern Switzerland, situated in a hilly area near the Jura Mountains.
  • 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_69ca836168108190bb43d3dc235c1f55 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5f8d25f881908863d636fa57a8a2 completed March 31, 2026, 11:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf5210454c8190aa83d941893a4bc5 completed April 3, 2026, 5:37 a.m.
Created at: March 30, 2026, 6:43 p.m.