Triple
T24966127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diedesfeld |
E624748
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Stadtteil von Neustadt an der Weinstraße |
C49350
|
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: Stadtteil von Neustadt an der Weinstraße Context triple: [Diedesfeld, instanceOf, Stadtteil von Neustadt an der Weinstraße]
-
A.
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.
-
B.
Stadtteil of Cologne
A Stadtteil of Cologne is an official urban district within the city’s administrative structure, typically characterized by its own local identity, infrastructure, and residential and commercial areas.
-
C.
Stadtteil von Krefeld
Ein Stadtteil von Krefeld ist eine klar abgegrenzte, verwaltungstechnisch definierte Teilfläche des Stadtgebiets von Krefeld mit eigener Infrastruktur, Bebauungsstruktur und teils eigenständiger Identität.
-
D.
district of Mannheim
A district of Mannheim is an administrative subdivision of the city of Mannheim, Germany, characterized by its own local neighborhoods, infrastructure, and community services within the broader urban area.
-
E.
district of Wuppertal
A district of Wuppertal is an administrative subdivision of the German city of Wuppertal, encompassing specific neighborhoods, local governance functions, and community services within its defined area.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6 a.m.