Triple

T1059844
Position Surface form Disambiguated ID Type / Status
Subject Solothurn E22880 entity
Predicate hasMunicipality P847 FINISHED
Object Olten E182060 NE FINISHED

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: Olten | Statement: [Solothurn, hasMunicipality, Olten]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Olten
Context triple: [Solothurn, hasMunicipality, Olten]
  • A. Olten chosen
    Olten is a town in the canton of Solothurn in northwestern Switzerland, known as an important railway junction and regional economic center.
  • B. Solothurn
    Solothurn is a canton in northwestern Switzerland known for its historic baroque town of the same name and its location along the Aare River.
  • C. Schaffhausen
    Schaffhausen is a historic town and capital of the canton of the same name in northern Switzerland, known for its well-preserved medieval old town and proximity to the Rhine Falls.
  • D. St. Gallen
    St. Gallen is a historic city in northeastern Switzerland renowned for its UNESCO-listed Abbey of Saint Gall and rich textile heritage.
  • E. Biel/Bienne
    Biel/Bienne is a bilingual (German-French) Swiss city in the canton of Bern, known for its watchmaking industry and location at the eastern end of Lake Biel.
  • 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_69a493dada0481909c43649f9843ea91 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b8f28c7c8190b9ca3749666bcbf3 completed March 1, 2026, 10:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69ae1f9fcac481909cb3f6c6dc681e60 completed March 9, 2026, 1:17 a.m.
Created at: March 1, 2026, 7:42 p.m.