Triple
T36309785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichsführer-SS command system |
E894036
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi security apparatus |
C56837
|
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: Nazi security apparatus Context triple: [Reichsführer-SS command system, instanceOf, Nazi security apparatus]
-
A.
Nazi paramilitary command structure
chosen
A Nazi paramilitary command structure is the hierarchical, militarized chain of authority through which Nazi Party-aligned armed organizations (such as the SA and SS) organized, directed, and enforced ideological, political, and military objectives.
-
B.
Nazi SS office
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.
-
C.
Stasi official
A Stasi official is a government functionary of East Germany’s Ministry for State Security responsible for overseeing surveillance, intelligence gathering, and political repression to maintain state control.
-
D.
Nazi report
A Nazi report is an official document produced by Nazi authorities or affiliated organizations that records observations, decisions, policies, or activities in line with the regime’s ideological, political, or military objectives.
-
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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.