Triple

T14731256
Position Surface form Disambiguated ID Type / Status
Subject canton of Solothurn E346078 entity
Predicate contains P35 FINISHED
Object Bettlach E145555 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: Bettlach | Statement: [canton of Solothurn, contains, Bettlach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bettlach
Context triple: [canton of Solothurn, contains, Bettlach]
  • A. Bettlach chosen
    Bettlach is a Swiss municipality located in the canton of Solothurn.
  • B. Sachseln
    Sachseln is a municipality in the Swiss canton of Obwalden, known as the home and pilgrimage site associated with the Swiss patron saint Nicholas of Flüe.
  • C. Waltershof
    Waltershof is an industrial and port district of Hamburg, Germany, located within the borough of Hamburg-Mitte.
  • D. Kiental
    Kiental is a picturesque alpine valley and village in the Bernese Oberland region of Switzerland, known for its dramatic mountain scenery and hiking opportunities.
  • E. Vitznau
    Vitznau is a picturesque Swiss lakeside village in the canton of Lucerne, known as a gateway to Mount Rigi and a popular destination for scenic tourism on Lake Lucerne.
  • 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_69d822e5911c8190ba589f957dbd9ba7 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec26311c8819093a81ff0fa43b33b completed April 14, 2026, 10:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe7e79997c8190bb6f158d50603066 completed May 9, 2026, 12:23 a.m.
Created at: April 10, 2026, 1:29 a.m.