Triple
T10923768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Higher SS and Police Leader East |
E258011
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi SS and police command |
C14185
|
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 SS and police command Context triple: [Higher SS and Police Leader East, instanceOf, Nazi SS and police command]
-
A.
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.
-
B.
Waffen-SS field army
A Waffen-SS field army was a large, front-line combat formation of Nazi Germany’s Waffen-SS, composed of multiple corps and divisions and employed in major operational campaigns during World War II.
-
C.
Waffen-SS corps
The Waffen-SS corps was the combat branch of Nazi Germany’s SS organization, comprising ideologically driven, militarized units that fought alongside the regular army and were heavily involved in war crimes and atrocities during World War II.
-
D.
Nazi paramilitary unit
chosen
A Nazi paramilitary unit is an organized, militarized group aligned with the National Socialist regime that used violence, intimidation, and coercion to enforce its ideology, suppress opposition, and support its political and military objectives.
-
E.
Waffen-SS officer
A Waffen-SS officer was a commissioned leader within Nazi Germany’s Waffen-SS, responsible for commanding combat units of this paramilitary organization that was deeply involved in war crimes and atrocities 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:22 p.m.