Triple

T16894300
Position Surface form Disambiguated ID Type / Status
Subject Interlaken-Oberhasli administrative district E424257 entity
Predicate contains P35 FINISHED
Object Bönigen NE ONNED1

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: Bönigen | Statement: [Interlaken-Oberhasli administrative district, contains, Bönigen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bönigen
Context triple: [Interlaken-Oberhasli administrative district, contains, Bönigen]
  • A. Bönigen chosen
    Bönigen is a Swiss village in the canton of Bern, known for its scenic location on the shore of Lake Brienz near Interlaken.
  • B. Bremgarten
    Bremgarten is a historic Swiss town in the canton of Aargau, known for its well-preserved medieval old town and scenic riverside setting.
  • C. Villigen
    Villigen is a municipality in the canton of Aargau, Switzerland, known for hosting major scientific research facilities.
  • D. Kesswil
    Kesswil is a small Swiss village on the shores of Lake Constance, best known as the birthplace of the influential psychiatrist and psychoanalyst Carl Gustav Jung.
  • E. Göschenen
    Göschenen is a Swiss mountain village and railway junction in the canton of Uri, known as a gateway to the Gotthard region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d889da3e8c8190a2b118f383f0beac completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e3c8d6bfc88190b6b47b89c1135871 completed April 18, 2026, 6:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a01954069e0819087fab0a782a83f39 finalizing May 11, 2026, 8:37 a.m.
Created at: April 10, 2026, 5:29 a.m.