Triple

T1059879
Position Surface form Disambiguated ID Type / Status
Subject Solothurn E22880 entity
Predicate hasHistoricTown P847 FINISHED
Object Solothurn (town) 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 (town) | Statement: [Solothurn, hasHistoricTown, Solothurn (town)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Solothurn (town)
Context triple: [Solothurn, hasHistoricTown, Solothurn (town)]
  • 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. Porrentruy
    Porrentruy is a historic town in northwestern Switzerland known for its medieval castle and role as a regional center in the canton of Jura.
  • C. Hermance
    Hermance is a small lakeside municipality on the shores of Lake Geneva in southwestern Switzerland.
  • D. Yverdon-les-Bains
    Yverdon-les-Bains is a historic spa town in western Switzerland known for its thermal baths, medieval castle, and location at the southern end of Lake Neuchâtel.
  • E. Aubonne
    Aubonne is a river in western Switzerland that flows through the canton of Vaud before emptying into Lake Geneva.
  • 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_69a4b8f3f98c819096338198d9f30491 completed March 1, 2026, 10:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac4c1d82c88190b418e2e2f050b563 completed March 7, 2026, 4:02 p.m.
Created at: March 1, 2026, 7:42 p.m.