Triple
T28019672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wangen (Göppingen district) |
E707651
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipality of Baden-Württemberg |
C53676
|
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: municipality of Baden-Württemberg Context triple: [Wangen (Göppingen district), instanceOf, municipality of Baden-Württemberg]
-
A.
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.
-
B.
district of Karlsruhe
A district of Karlsruhe is an administrative subdivision within the city or surrounding region of Karlsruhe, responsible for local governance, services, and community organization in its designated area.
-
C.
borough of Stuttgart
A borough of Stuttgart is an administrative subdivision of the city that encompasses specific neighborhoods and local governance functions within Stuttgart’s municipal structure.
-
D.
district of Ludwigshafen am Rhein
A district of Ludwigshafen am Rhein is an administrative subdivision of the city that encompasses specific residential, commercial, and infrastructural areas governed under the municipal authority of Ludwigshafen am Rhein, Germany.
-
E.
district of North Rhine-Westphalia
A district of North Rhine-Westphalia is an administrative territorial unit within the German federal state of North Rhine-Westphalia, responsible for regional governance, public services, and local coordination among its municipalities.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 8:09 p.m.