Triple

T8875340
Position Surface form Disambiguated ID Type / Status
Subject Allschwil E211264 entity
Predicate borderWith P224 FINISHED
Object Basel-Stadt E22322 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: Basel-Stadt | Statement: [Allschwil, borderWith, Basel-Stadt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Basel-Stadt
Context triple: [Allschwil, borderWith, Basel-Stadt]
  • A. Basel-Stadt chosen
    Basel-Stadt is a small, urban Swiss canton centered on the city of Basel, a major cultural and economic hub in northwestern Switzerland.
  • 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. 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.
  • D. Kloten
    Kloten is a town in the canton of Zurich in northern Switzerland, best known as the home of Zurich Airport.
  • E. Stettlen
    Stettlen is a municipality in the canton of Bern in Switzerland, situated just east of the city of Bern and functioning largely as a residential and commuter community.
  • 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_69ca838e78748190934d82db3104f855 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc614565788190aa14535760df88c8 completed April 1, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69cffd78f35881909c15249b58a1ce03 completed April 3, 2026, 5:48 p.m.
Created at: March 30, 2026, 6:52 p.m.