Triple
T15897538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS and Police Leadership in occupied territories |
E385499
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi command structure |
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: Nazi command structure Context triple: [SS and Police Leadership in occupied territories, instanceOf, Nazi command structure]
-
A.
Wehrmacht organization
The Wehrmacht organization is a structured representation of the hierarchical, functional, and administrative components of Nazi Germany’s unified armed forces, including their command chains, unit types, and operational relationships.
-
B.
Wehrmacht high command
The Wehrmacht high command was the central military leadership of Nazi Germany responsible for planning, directing, and coordinating the operations of the German armed forces during the Second World War.
-
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.
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.
-
E.
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.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:51 a.m.