Triple
T8848439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schorndorf |
E210568
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object |
Miedelsbach
Miedelsbach is a village and district of the town of Schorndorf in the Rems-Murr district of Baden-Württemberg, Germany.
|
E776942
|
NE FINISHED |
How this triple was built (4 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: Miedelsbach | Statement: [Schorndorf, hasSubdivision, Miedelsbach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Miedelsbach Context triple: [Schorndorf, hasSubdivision, Miedelsbach]
-
A.
Luterbach
Luterbach is a municipality in the canton of Solothurn in northwestern Switzerland, known for its residential character and proximity to the Aare River.
-
B.
Hammersbach
Hammersbach is a village in the Bavarian Alps of Germany that serves as a popular gateway for hiking and mountaineering routes into the nearby mountains, including the Höllental valley.
-
C.
Lüßbach
Lüßbach is a small river in Bavaria, Germany, that serves as one of the tributaries feeding into Lake Starnberg.
-
D.
Königsbach
Königsbach is a village and wine-growing district that forms part of the town of Neustadt an der Weinstraße in Rhineland-Palatinate, Germany.
-
E.
Eschbach
Eschbach is a village and district of the town of Usingen in the Hochtaunus region of Hesse, Germany.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Miedelsbach Triple: [Schorndorf, hasSubdivision, Miedelsbach]
Generated description
Miedelsbach is a village and district of the town of Schorndorf in the Rems-Murr district of Baden-Württemberg, Germany.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Miedelsbach Target entity description: Miedelsbach is a village and district of the town of Schorndorf in the Rems-Murr district of Baden-Württemberg, Germany.
-
A.
Luterbach
Luterbach is a municipality in the canton of Solothurn in northwestern Switzerland, known for its residential character and proximity to the Aare River.
-
B.
Hammersbach
Hammersbach is a village in the Bavarian Alps of Germany that serves as a popular gateway for hiking and mountaineering routes into the nearby mountains, including the Höllental valley.
-
C.
Lüßbach
Lüßbach is a small river in Bavaria, Germany, that serves as one of the tributaries feeding into Lake Starnberg.
-
D.
Königsbach
Königsbach is a village and wine-growing district that forms part of the town of Neustadt an der Weinstraße in Rhineland-Palatinate, Germany.
-
E.
Eschbach
Eschbach is a village and district of the town of Usingen in the Hochtaunus region of Hesse, Germany.
- F. None of above. chosen
Provenance (5 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60aa6db0819097c3257499200afc |
completed | April 1, 2026, 12:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0171e98a081909875c96defaf9bfa |
completed | April 3, 2026, 7:38 p.m. |
| NEDg | Description generation | batch_69d019059e8481909a696575366aa0b6 |
completed | April 3, 2026, 7:46 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d019a2736c8190880c8f3786cf353b |
completed | April 3, 2026, 7:48 p.m. |
Created at: March 30, 2026, 6:49 p.m.