Triple
T14969731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Württemberg-Baden |
E373284
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Allied-occupied territory |
C9943
|
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: Allied-occupied territory Context triple: [Württemberg-Baden, instanceOf, Allied-occupied territory]
-
A.
Allied occupation body
An Allied occupation body is an administrative authority established by victorious Allied powers to govern, oversee reconstruction, and implement political, economic, and legal reforms in a defeated or occupied territory following conflict.
-
B.
Allied military authority
chosen
An Allied military authority is a governing body established by cooperating allied nations' armed forces to administer, control, and coordinate military and sometimes civil affairs in occupied or liberated territories during and immediately after conflict.
-
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.
military occupation
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.
-
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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:49 a.m.