Triple
T14569510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Südoststadt, Nuremberg |
E341872
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Nuremberg |
C34959
|
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: district of Nuremberg Context triple: [Südoststadt, Nuremberg, instanceOf, district of Nuremberg]
-
A.
borough of Munich
A borough of Munich is an administrative subdivision of the city that encompasses specific neighborhoods and local governance functions within Munich’s overall municipal structure.
-
B.
district of Saxony
A district of Saxony is an administrative subdivision within the federal state of Saxony in Germany, responsible for local governance, public services, and regional planning across multiple municipalities.
-
C.
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.
-
D.
region of Bavaria
A region of Bavaria is a geographically and administratively defined area within the German federal state of Bavaria, characterized by shared cultural, historical, and economic features.
-
E.
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.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:23 a.m.