Triple

T22435813
Position Surface form Disambiguated ID Type / Status
Subject Unterliederbach E554619 entity
Predicate borderedBy P224 FINISHED
Object Zeilsheim 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: Zeilsheim | Statement: [Unterliederbach, borderedBy, Zeilsheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zeilsheim
Context triple: [Unterliederbach, borderedBy, Zeilsheim]
  • A. Zeilsheim chosen
    Zeilsheim is a western district of Frankfurt am Main, Germany, known for its residential character and post-war history, including a former displaced persons camp.
  • B. Sulzheim
    Sulzheim is a small municipality in the Schweinfurt district of Lower Franconia in northern Bavaria, Germany.
  • C. Külsheim
    Külsheim is a small town in the Main-Tauber district of Baden-Württemberg in southwestern Germany, known for its historic center and surrounding rural landscape.
  • D. Diedelsheim
    Diedelsheim is a district of the town of Bretten in the state of Baden-Württemberg in southwestern Germany.
  • E. Germersheim
    Germersheim is a town in the Rhineland-Palatinate region of southwestern Germany, situated on the Rhine River and known for its historic fortress and role as a local administrative and transport hub.
  • 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_69e11e5010e48190ae1e9c9db9697637 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15ade60508190b0100d5c2843b920 completed April 29, 2026, 1:11 a.m.
Created at: April 16, 2026, 8:47 p.m.