Triple

T20206354
Position Surface form Disambiguated ID Type / Status
Subject Bodenseekreis E493361 entity
Predicate hasTown P847 FINISHED
Object Tettnang 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: Tettnang | Statement: [Bodenseekreis, hasTown, Tettnang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tettnang
Context triple: [Bodenseekreis, hasTown, Tettnang]
  • A. Tettnang chosen
    Tettnang is a small town in southern Germany’s Baden-Württemberg region, known for its hop cultivation and proximity to Lake Constance.
  • B. Obertraun
    Obertraun is a small Austrian village in the Salzkammergut region, known for its alpine scenery and proximity to the Dachstein mountains and Hallstatt.
  • C. Seßlach
    Seßlach is a small, well-preserved medieval town in northern Bavaria, Germany, known for its intact city walls and historic half-timbered houses.
  • D. Reichenau an der Rax
    Reichenau an der Rax is a market town in Lower Austria known as a historic summer resort and gateway to the Rax mountain region.
  • E. Maroldsweisach
    Maroldsweisach is a municipality in the Haßberge district of northern Bavaria, Germany, known for its rural setting and historic Franconian character.
  • 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.