Triple

T21748587
Position Surface form Disambiguated ID Type / Status
Subject District of Coburg E536850 entity
Predicate hasMunicipality P847 FINISHED
Object Itzgrund 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: Itzgrund | Statement: [District of Coburg, hasMunicipality, Itzgrund]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Itzgrund
Context triple: [District of Coburg, hasMunicipality, Itzgrund]
  • A. Itzgrund chosen
    Itzgrund is a small municipality in the Bavarian region of Germany, known for its rural character and location in the valley of the Itz River.
  • B. Ittigen
    Ittigen is a municipality in the canton of Bern in Switzerland that functions largely as a suburban community within the greater Bern urban region.
  • C. Witellikon
    Witellikon is a small settlement within the municipality of Küsnacht in the canton of Zürich, Switzerland, situated along the shores of Lake Zurich.
  • D. Zihl
    Zihl is a river in Switzerland that serves as a key tributary within the Aare river system.
  • E. Taborio
    Taborio is a village settlement located on the island of Nonouti in the Republic of Kiribati.
  • 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_69e0c46eab808190b848242d63a17c47 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f01a77e19c81909bf26f96aa41a7ce completed April 28, 2026, 2:24 a.m.
Created at: April 16, 2026, 6:50 p.m.