Triple

T22550090
Position Surface form Disambiguated ID Type / Status
Subject Lebern electoral district E557534 entity
Predicate hasMunicipality P847 FINISHED
Object Hüniken 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: Hüniken | Statement: [Lebern electoral district, hasMunicipality, Hüniken]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hüniken
Context triple: [Lebern electoral district, hasMunicipality, Hüniken]
  • A. Hüniken chosen
    Hüniken is a small rural municipality in the canton of Solothurn in northern Switzerland.
  • B. Hintonburg
    Hintonburg is a historic, arts-oriented urban neighbourhood in west-central Ottawa, known for its mix of residential streets, independent shops, and cultural venues.
  • C. Waasmunster
    Waasmunster is a municipality in East Flanders, Belgium, known for its green, semi-rural character and location between Ghent and Antwerp.
  • D. Frontenhausen
    Frontenhausen is a market town in Lower Bavaria, Germany, known for its rural character and location within the Landshut district.
  • E. Kostheim
    Kostheim is a district of the city of Wiesbaden in the German state of Hesse, located on the right bank of the Rhine opposite Mainz.
  • 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_69e11e59db848190b4272ecd2b690ffd completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15f74512c8190b5369e19a4bc6325 completed April 29, 2026, 1:31 a.m.
Created at: April 16, 2026, 8:52 p.m.