Triple

T22319314
Position Surface form Disambiguated ID Type / Status
Subject Obergerlafingen E551738 entity
Predicate hasNeighboringMunicipality P224 FINISHED
Object Koppigen 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: Koppigen | Statement: [Obergerlafingen, hasNeighboringMunicipality, Koppigen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koppigen
Context triple: [Obergerlafingen, hasNeighboringMunicipality, Koppigen]
  • A. Koppigen chosen
    Koppigen is a municipality in the canton of Bern in Switzerland, situated in the Emmental region.
  • B. Kiental
    Kiental is a picturesque alpine valley and village in the Bernese Oberland region of Switzerland, known for its dramatic mountain scenery and hiking opportunities.
  • C. Buochs
    Buochs is a Swiss lakeside municipality known for its scenic setting on Lake Lucerne and proximity to the Alps in central Switzerland.
  • D. Tobel
    Tobel is a small settlement within the municipality of Lutzenberg in the canton of Appenzell Ausserrhoden, Switzerland.
  • E. Disentis
    Disentis is a Swiss Alpine village in the canton of Graubünden known for its Benedictine monastery and access to extensive skiing and mountain sports.
  • 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_69e11e4776588190abb21e5cea79973f completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15762fac08190a6a514baffbbbca1 completed April 29, 2026, 12:57 a.m.
Created at: April 16, 2026, 8:42 p.m.