Triple

T23282975
Position Surface form Disambiguated ID Type / Status
Subject Stans E588915 entity
Predicate hasNeighboringMunicipality P224 FINISHED
Object Buochs 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: Buochs | Statement: [Stans, hasNeighboringMunicipality, Buochs]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Buochs
Context triple: [Stans, hasNeighboringMunicipality, Buochs]
  • A. Buochs chosen
    Buochs is a Swiss lakeside municipality known for its scenic setting on Lake Lucerne and proximity to the Alps in central Switzerland.
  • B. Saanen
    Saanen is a picturesque Swiss village in the Bernese Oberland known for its traditional chalets, alpine scenery, and proximity to the upscale resort town of Gstaad.
  • C. Koppigen
    Koppigen is a municipality in the canton of Bern in Switzerland, situated in the Emmental region.
  • D. Axalp
    Axalp is a small Swiss alpine village and ski area in the Bernese Oberland, known for its scenic views over Lake Brienz and its annual Swiss Air Force flight demonstrations.
  • E. Oberegg
    Oberegg is a Swiss municipality in the canton of Appenzell Innerrhoden, known for its rural landscape and location in the Appenzell 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_69e25d16e2c08190a291de254703129e completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f196447a748190bd797ec9baa63fc3 completed April 29, 2026, 5:25 a.m.
Created at: April 17, 2026, 4:58 p.m.