Triple

T20206353
Position Surface form Disambiguated ID Type / Status
Subject Bodenseekreis E493361 entity
Predicate hasTown P847 FINISHED
Object Überlingen 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: Überlingen | Statement: [Bodenseekreis, hasTown, Überlingen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Überlingen
Context triple: [Bodenseekreis, hasTown, Überlingen]
  • A. Überlingen chosen
    Überlingen is a historic lakeside town in the German state of Baden-Württemberg, situated on the northern shore of Lake Constance and known for its medieval architecture and tourism.
  • B. Bochingen
    Bochingen is a village and district of the town Oberndorf am Neckar in the state of Baden-Württemberg in southwestern Germany.
  • C. Vaterstetten
    Vaterstetten is a municipality in the district of Ebersberg near Munich in Bavaria, Germany, known as a residential suburb with strong transport links to the Bavarian capital.
  • D. Riehe
    Riehe is a small river in Lower Saxony, Germany, known as one of the tributaries feeding into the Innerste.
  • E. Obersulm
    Obersulm is a municipality in the German state of Baden-Württemberg, known for its wine-growing areas and location near the city of Heilbronn.
  • 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_69da6269614c8190bb40475d9d477358 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66d922ebc8190ae012da8ceba74dd completed April 20, 2026, 6:16 p.m.
Created at: April 11, 2026, 11:38 p.m.