Triple
T8070275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin Defense Area |
E188352
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German military district |
C23498
|
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: German military district Context triple: [Berlin Defense Area, instanceOf, German military district]
-
A.
military district of the Holy Roman Empire
A military district of the Holy Roman Empire was an administrative and territorial unit organized primarily for defense and military command, grouping various imperial estates under a regional military structure.
-
B.
Reichskommissariat
A Reichskommissariat was a type of civilian administrative territory established and governed by Nazi Germany in occupied regions during World War II, intended to facilitate political control, economic exploitation, and eventual Germanization.
-
C.
German army detachment
A German army detachment is a temporary, task-organized military formation separated from a larger parent unit to conduct specific operations under its own command structure.
-
D.
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.
-
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. 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:27 p.m.