Triple
T10359063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neustadt (Dresden) |
E244083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Dresden |
C24004
|
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 Dresden Context triple: [Neustadt (Dresden), instanceOf, district of Dresden]
-
A.
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.
-
B.
borough of Dresden
chosen
A borough of Dresden is an administrative subdivision of the city of Dresden that encompasses several neighborhoods and is responsible for local governance and public services within its defined area.
-
C.
administrative district of East Germany
An administrative district of East Germany was a mid-level territorial unit (Bezirk) established by the German Democratic Republic to organize regional governance, planning, and administration between the central government and local municipalities.
-
D.
Stadtbezirk of Hanover
A Stadtbezirk of Hanover is an administrative borough within the city that groups several neighborhoods for local governance, planning, and public services.
-
E.
rural district of Germany
A rural district of Germany is an administrative subdivision, typically encompassing several towns and municipalities, that manages regional services such as infrastructure, education, and public welfare in predominantly non-urban areas.
- F. None of above.
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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:59 a.m.