Triple
T12760951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office Group W |
E304992
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subdivision of the SS Main Economic and Administrative Office |
C23961
|
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: subdivision of the SS Main Economic and Administrative Office Context triple: [Office Group W, instanceOf, subdivision of the SS Main Economic and Administrative Office]
-
A.
Nazi SS office
chosen
A Nazi SS office was an administrative and operational unit of the Schutzstaffel responsible for planning, coordinating, and executing the regime’s ideological, security, and genocidal policies.
-
B.
Wehrmacht headquarters
The Wehrmacht headquarters was the central command authority of Nazi Germany's unified armed forces, responsible for strategic planning, coordination, and direction of military operations during World War II.
-
C.
Waffen-SS division
A Waffen-SS division was a large, front-line combat formation of Nazi Germany’s Waffen-SS, combining infantry, armor, and support units under a unified command and ideologically aligned with the SS.
-
D.
Gulag administrative body
The Gulag administrative body is the centralized state organization responsible for planning, managing, and overseeing the operation of forced labor camps within the Soviet penal system.
-
E.
Nazi economic authority
A Nazi economic authority is a state-controlled institution or official body within Nazi Germany responsible for directing, regulating, and coordinating economic activity in line with the regime’s ideological, militaristic, and autarkic goals.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:28 p.m.