Triple

T21659985
Position Surface form Disambiguated ID Type / Status
Subject canton of Guebwiller E534568 entity
Predicate contains P35 FINISHED
Object Raedersheim NE NERFINISHED

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: Raedersheim | Statement: [canton of Guebwiller, contains, Raedersheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Raedersheim
Context triple: [canton of Guebwiller, contains, Raedersheim]
  • A. Raedersheim chosen
    Raedersheim is a small commune in the Haut-Rhin department of the Grand Est region in northeastern France.
  • B. Riedisheim
    Riedisheim is a commune in northeastern France’s Grand Est region, situated near the city of Mulhouse in the Haut-Rhin department.
  • C. Seinsheim
    Seinsheim is a small municipality in the Kitzingen district of Bavaria, Germany, known for its rural character and Franconian wine-growing tradition.
  • D. Marlenheim
    Marlenheim is a commune in northeastern France’s Alsace region, known as a historic wine-producing village and gateway to the area’s renowned vineyards and scenic countryside.
  • E. Schwanstetten
    Schwanstetten is a municipality in the Roth district of Bavaria, Germany, known for its residential character and proximity to the city of Nuremberg.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c467e1f48190af2650b19175abc4 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef6c06844c81909b9c91e02fa4e6e1 completed April 27, 2026, 2 p.m.
Created at: April 16, 2026, 6:36 p.m.