Triple

T790608
Position Surface form Disambiguated ID Type / Status
Subject Jura E16904 entity
Predicate bordersCanton P224 FINISHED
Object Solothurn E22880 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: Solothurn | Statement: [Jura, bordersCanton, Solothurn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Solothurn
Context triple: [Jura, bordersCanton, Solothurn]
  • A. Solothurn chosen
    Solothurn is a canton in northwestern Switzerland known for its historic baroque town of the same name and its location along the Aare River.
  • B. 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.
  • C. Neuchâtel
    Neuchâtel is a French-speaking canton in western Switzerland known for its lakeside capital, watchmaking industry, and historic architecture.
  • D. Olten
    Olten is a town in the canton of Solothurn in northwestern Switzerland, known as an important railway junction and regional economic center.
  • E. Fribourg
    Fribourg is a bilingual Swiss canton in western Switzerland known for its medieval capital city and location at the cultural boundary between French- and German-speaking regions.
  • 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_69a4936cb7448190914f5fe4b8d81607 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a79754988190ab494b1c54d6a2a4 completed March 1, 2026, 8:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad7957d7048190b7fe9a79543931b2 completed March 8, 2026, 1:27 p.m.
Created at: March 1, 2026, 7:38 p.m.