Triple

T19564686
Position Surface form Disambiguated ID Type / Status
Subject Kinzigtal E489547 entity
Predicate hasTown P847 FINISHED
Object Schiltach 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: Schiltach | Statement: [Kinzigtal, hasTown, Schiltach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schiltach
Context triple: [Kinzigtal, hasTown, Schiltach]
  • A. Schiltach chosen
    Schiltach is a small historic town in Germany’s Black Forest region, known for its well-preserved half-timbered houses and picturesque riverside setting.
  • B. Steinlach
    Steinlach is a small river in the German state of Baden-Württemberg that flows through the city of Tübingen before joining the Neckar.
  • C. Kirchlindach
    Kirchlindach is a Swiss municipality in the canton of Bern, known for its rural character and proximity to the city of Bern.
  • D. Herrischried
    Herrischried is a small municipality in the southern Black Forest region of Baden-Württemberg, Germany, known for its scenic landscapes and outdoor recreation opportunities.
  • E. 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.
  • 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.