Triple

T9321833
Position Surface form Disambiguated ID Type / Status
Subject Sindelfingen E224283 entity
Predicate hasTwinTown P919 FINISHED
Object Schaffhausen E183831 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: Schaffhausen | Statement: [Sindelfingen, hasTwinTown, Schaffhausen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schaffhausen
Context triple: [Sindelfingen, hasTwinTown, Schaffhausen]
  • A. Schaffhausen chosen
    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.
  • B. Schafhausen
    Schafhausen is a village and district of the town Weil der Stadt in the German state of Baden-Württemberg.
  • C. 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.
  • D. Grenchen
    Grenchen is a Swiss town in the canton of Solothurn known for its watchmaking industry and location at the foot of the Jura Mountains.
  • E. Türnich
    Türnich is a district of the town of Kerpen in North Rhine-Westphalia, Germany, known as a residential area within the Cologne metropolitan 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_69ca8426d48481909596360f7791c7dd completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd36f2bd288190bb1556a88d9e90f3 completed April 1, 2026, 3:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1af2542c48190b481dcd08187dabd completed April 5, 2026, 12:39 a.m.
Created at: March 30, 2026, 7:38 p.m.