Triple

T18501409
Position Surface form Disambiguated ID Type / Status
Subject Köniz stop E452076 entity
Predicate municipality P852 FINISHED
Object Köniz 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: Köniz | Statement: [Köniz stop, municipality, Köniz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Köniz
Context triple: [Köniz stop, municipality, Köniz]
  • A. Köniz chosen
    Köniz is a large suburban municipality in the canton of Bern, Switzerland, known for its proximity to the city of Bern and its mix of urban and rural landscapes.
  • B. Konina
    Konina is a village in southern Poland situated in the Gorce Mountains region near the peak of Turbacz.
  • C. Könnern
    Könnern is a small town in the German state of Saxony-Anhalt, known for its rural character and location near the Saale River.
  • D. Zwenkau
    Zwenkau is a small town in the Free State of Saxony in eastern Germany, situated near Leipzig and known for its proximity to former lignite mining areas now being transformed into lake landscapes.
  • E. Zollikofen
    Zollikofen is a municipality in the canton of Bern in Switzerland, functioning as a suburban community within the greater Bern metropolitan 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_69d8d3855d50819097fc8561b0299dd9 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e532c43de48190b49b87c1bb591016 completed April 19, 2026, 7:53 p.m.
Created at: April 10, 2026, 11:36 a.m.