Triple
T11832880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Occupied Enemy Territory East |
E281437
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military occupation zone |
C833
|
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: military occupation zone Context triple: [Occupied Enemy Territory East, instanceOf, military occupation zone]
-
A.
military occupation
chosen
A military occupation is the effective control and administration of a territory by foreign armed forces without the sovereign consent of the territory’s recognized government.
-
B.
military-controlled zone
A military-controlled zone is a designated geographic area where military authorities exercise primary control over security, movement, and activities, often restricting civilian access and enforcing special regulations.
-
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 district
A German military district is a regional administrative and organizational unit of the German armed forces responsible for local command, logistics, personnel management, and military infrastructure within its designated area.
-
E.
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.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:43 p.m.