Triple

T19564684
Position Surface form Disambiguated ID Type / Status
Subject Kinzigtal E489547 entity
Predicate hasTown P847 FINISHED
Object Hausach 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: Hausach | Statement: [Kinzigtal, hasTown, Hausach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hausach
Context triple: [Kinzigtal, hasTown, Hausach]
  • A. Hausach chosen
    Hausach is a small town in Germany’s Black Forest region, known for its scenic valley setting along the Kinzig River and its traditional timber-framed architecture.
  • B. Miesbach
    Miesbach is a historic town in southern Germany known for its traditional Bavarian culture and picturesque Alpine foothill setting.
  • C. Biberach an der Riß
    Biberach an der Riß is a historic town in the German state of Baden-Württemberg, known for its well-preserved medieval old town and traditional Swabian culture.
  • D. Gerlachsheim
    Gerlachsheim is a district of the town Lauda-Königshofen in the Main-Tauber-Kreis region of Baden-Württemberg, Germany.
  • E. Wolpertshausen
    Wolpertshausen is a small rural municipality in the German state of Baden-Württemberg, known for its agricultural character and location within the Hohenlohe region.
  • 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63f76b220819096e668534c6bac67 completed April 20, 2026, 3 p.m.
Created at: April 10, 2026, 1:42 p.m.