Triple

T20098953
Position Surface form Disambiguated ID Type / Status
Subject Zollernalbkreis E496480 entity
Predicate contains P35 FINISHED
Object Burladingen 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: Burladingen | Statement: [Zollernalbkreis, contains, Burladingen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burladingen
Context triple: [Zollernalbkreis, contains, Burladingen]
  • A. Burladingen chosen
    Burladingen is a small town in the Zollernalb district of Baden-Württemberg in southwestern Germany, known for its location on the Swabian Jura.
  • B. Burglengenfeld
    Burglengenfeld is a historic town in the Upper Palatinate region of Bavaria, Germany, known for its medieval castle and picturesque setting along the Naab River.
  • C. Bleidenstadt
    Bleidenstadt is a district of the town of Taunusstein in the Rheingau-Taunus region of Hesse, Germany, known for its historic church and small-town character.
  • D. Siegsdorf
    Siegsdorf is a Bavarian town in southeastern Germany known for its scenic Alpine surroundings and proximity to the Chiemsee lake.
  • E. Bollodingen
    Bollodingen is a small village in the canton of Bern, Switzerland, situated in the Oberaargau 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_69da626eee3881909f3454986d4a6511 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6666e306c81909c0ef617e0f6fccf completed April 20, 2026, 5:46 p.m.
Created at: April 11, 2026, 11:26 p.m.