Triple

T17403622
Position Surface form Disambiguated ID Type / Status
Subject Ostermundigen E423156 entity
Predicate hasNeighboringMunicipality P224 FINISHED
Object Bolligen 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: Bolligen | Statement: [Ostermundigen, hasNeighboringMunicipality, Bolligen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bolligen
Context triple: [Ostermundigen, hasNeighboringMunicipality, Bolligen]
  • A. Bolligen chosen
    Bolligen is a Swiss municipality in the canton of Bern, known as a residential community on the outskirts of the city of Bern.
  • B. Bollingen
    Bollingen is a small Swiss locality on the shores of Lake Zurich, known for its rural character and scenic lakeside setting.
  • C. Ullensvang
    Ullensvang is a scenic municipality in Vestland county, Norway, known for its fruit orchards, fjord landscapes, and location along the Hardangerfjord.
  • D. Bisingen
    Bisingen is a municipality in the Zollernalb district of Baden-Württemberg, Germany, known for its proximity to the historic Hohenzollern Castle.
  • E. Nydalen
    Nydalen is a modern riverside neighborhood in Oslo, Norway, known for its business district, educational institutions, and redeveloped industrial areas.
  • 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_69d889d7d27c819088486ce3f0627fa1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43b051cc48190872278ee0b52240d completed April 19, 2026, 2:16 a.m.
Created at: April 10, 2026, 5:45 a.m.