Triple
T11294436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Besættelsen |
E267414
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German occupation of Denmark |
C18793
|
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 occupation of Denmark Context triple: [Besættelsen, instanceOf, German occupation of Denmark]
-
A.
German-Danish War
The German-Danish War was a mid-19th-century conflict (1864) between Denmark and the German states of Prussia and Austria over control of the duchies of Schleswig and Holstein, leading to Danish defeat and significant territorial loss.
-
B.
Reichskommissariat
chosen
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.
postwar occupation
Postwar occupation is the temporary control and administration of a defeated state’s territory by foreign military or allied authorities to manage security, political transition, and reconstruction after armed conflict.
-
D.
German military administration
The German military administration is the organizational structure and governing authority through which Germany’s armed forces plan, manage, and execute military policies, logistics, personnel, and operations.
-
E.
Nazi Germany expansion
Nazi Germany expansion refers to the aggressive territorial and political enlargement of Germany under Adolf Hitler from 1938 to 1941 through annexations, invasions, and occupations that precipitated and escalated World War II in Europe.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:32 p.m.