Triple
T6227234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bezirk Berlin |
E139264
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative district of East Germany |
C19442
|
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: administrative district of East Germany Context triple: [Bezirk Berlin, instanceOf, administrative district of East Germany]
-
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.
administrative region of Germany
An administrative region of Germany is a territorial unit within a federal state (Land) that serves as an intermediate level of government for coordinating regional administration, planning, and public services.
-
C.
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.
-
D.
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.
-
E.
region of Germany
A region of Germany is a geographically and culturally distinct area within the country, often defined by historical boundaries, administrative divisions, or shared economic and social characteristics.
- 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:22 p.m.