Triple
T35056430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wirtschafts- und Verwaltungshauptamt |
E1011478
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | SS-Hauptamt |
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: SS-Hauptamt Context triple: [Wirtschafts- und Verwaltungshauptamt, instanceOf, SS-Hauptamt]
-
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.
Führer Headquarters
The Führer Headquarters were a series of heavily fortified command complexes used by Adolf Hitler and the Nazi leadership during World War II to plan and direct military operations.
-
C.
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.
-
D.
KGB division
A KGB division is an organizational unit within the Soviet Union’s state security agency responsible for specialized functions such as intelligence, counterintelligence, surveillance, or internal security operations.
-
E.
Wehrmacht signals unit
A Wehrmacht signals unit was a specialized German military formation responsible for establishing, operating, and maintaining communications networks—such as radio, telephone, and telegraph—between command elements and combat units during World War II.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.