Triple
T21036653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kreis Röbel/Müritz |
E518207
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 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: district of East Germany Context triple: [Kreis Röbel/Müritz, instanceOf, district of East Germany]
-
A.
administrative district of East Germany
chosen
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.
-
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 Leipzig
A district of Leipzig is an administrative subdivision of the city that encompasses specific neighborhoods, local infrastructure, and community services within defined geographic boundaries.
-
D.
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.
-
E.
organization of the German Democratic Republic
The organization of the German Democratic Republic was a centrally planned, socialist state structure characterized by the dominant role of the Socialist Unity Party (SED), extensive state control over political, economic, and social institutions, and a pervasive security apparatus.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:02 p.m.