Triple

T12055352
Position Surface form Disambiguated ID Type / Status
Subject district of Toggenburg E287026 entity
Predicate contains P35 FINISHED
Object Lichtensteig E767210 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: Lichtensteig | Statement: [district of Toggenburg, contains, Lichtensteig]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lichtensteig
Context triple: [district of Toggenburg, contains, Lichtensteig]
  • A. Lichtensteig chosen
    Lichtensteig is a small historic town in the canton of St. Gallen in northeastern Switzerland, known for its well-preserved old town and picturesque setting in the Toggenburg region.
  • B. Bettlach
    Bettlach is a Swiss municipality located in the canton of Solothurn.
  • C. Waldegg
    Waldegg is a locality in Switzerland situated along the route of the A3 motorway.
  • D. Steißlingen
    Steißlingen is a municipality in the district of Konstanz in the state of Baden-Württemberg in southern Germany.
  • E. Untereggen
    Untereggen is a small Swiss municipality in the canton of St. Gallen, known for its rural character and location in the country’s northeastern region.
  • 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_69d6ab4780948190bdb9f7620c2ac27e completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90425258c8190ba7b3b837c439253 completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f69b78f55c81908c41bccdcecf2d22 completed May 3, 2026, 12:48 a.m.
Created at: April 8, 2026, 9:47 p.m.