Triple

T19484189
Position Surface form Disambiguated ID Type / Status
Subject Heidenheim district E487465 entity
Predicate containsMunicipality P852 FINISHED
Object Nattheim 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: Nattheim | Statement: [Heidenheim district, containsMunicipality, Nattheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nattheim
Context triple: [Heidenheim district, containsMunicipality, Nattheim]
  • A. Nattheim chosen
    Nattheim is a municipality in the Heidenheim district of Baden-Württemberg in southern Germany.
  • B. Veltheim
    Veltheim is a former municipality in North Rhine-Westphalia, Germany, that became part of the town of Porta Westfalica through a local government merger.
  • C. Stockheim
    Stockheim is a village and district of the town of Brackenheim in the Heilbronn district of Baden-Württemberg, Germany.
  • D. Thalheim
    Thalheim is a town in the German state of Saxony-Anhalt that was incorporated into the larger city of Bitterfeld-Wolfen.
  • E. Gemmenich
    Gemmenich is a village in eastern Belgium near the borders with Germany and the Netherlands, known for its scenic countryside and proximity to the Vaalserberg tripoint.
  • 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_69d8e8d924388190b847cb15bb3d0aff completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6343dcc748190b0df816e6ab4cafb completed April 20, 2026, 2:12 p.m.
Created at: April 10, 2026, 1:39 p.m.