Triple
T22823654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sindlingen |
E565292
|
entity |
| Predicate | locatedNear |
P294
|
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: [Sindlingen, locatedNear, Zeilsheim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zeilsheim Context triple: [Sindlingen, locatedNear, 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.
Siezenheim
Siezenheim is a village and cadastral community in the municipality of Wals-Siezenheim near Salzburg, Austria.
-
E.
Diedelsheim
Diedelsheim is a district of the town of Bretten in the state of Baden-Württemberg in southwestern Germany.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dd2005081909baef070124eb839 |
completed | April 29, 2026, 3:41 a.m. |
Created at: April 17, 2026, 3:34 p.m.