Triple
T13214151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Büchenbach |
E314566
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ortsteil von Erlangen |
C32658
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Ortsteil von Erlangen Context triple: [Büchenbach, instanceOf, Ortsteil von Erlangen]
-
A.
Ortsteil von Wolfsburg
An "Ortsteil von Wolfsburg" is a designated local subdivision or district that forms part of the city of Wolfsburg, typically with its own name, identity, and sometimes local administrative functions.
-
B.
administrative region of Bavaria
An administrative region of Bavaria is a territorial subdivision within the German state of Bavaria that serves as an intermediate level of government, coordinating regional administration, planning, and public services across its constituent districts and municipalities.
-
C.
Stadtbezirk 1 of Munich
Stadtbezirk 1 of Munich is the central borough of the city, encompassing the historic old town and key cultural, commercial, and administrative areas.
-
D.
Stadtteil von Frankfurt am Main
Ein Stadtteil von Frankfurt am Main ist eine klar abgegrenzte, verwaltungstechnisch definierte Gebietseinheit innerhalb des Frankfurter Stadtgebiets mit eigener Infrastruktur, Bebauungsstruktur und teils ausgeprägter lokaler Identität.
-
E.
Ortsteil von Mönchengladbach
An "Ortsteil von Mönchengladbach" is a local district or neighborhood that forms part of the city of Mönchengladbach in Germany, typically with its own distinct identity and administrative recognition within the municipality.
- F. None of above. chosen
Provenance (1 batch)
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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:17 p.m.