Triple
T32894308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Generalleutnant of the Waffen-SS |
E841423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Waffen-SS rank |
C14128
|
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: Waffen-SS rank Context triple: [Generalleutnant of the Waffen-SS, instanceOf, Waffen-SS rank]
-
A.
Waffen-SS officer
chosen
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.
-
B.
Sturmabteilung rank
A Sturmabteilung rank represents a specific hierarchical position and level of authority within the paramilitary wing of the Nazi Party in Germany.
-
C.
Waffen-SS regiment
A Waffen-SS regiment is a military unit of the Nazi Party’s armed wing, typically composed of several battalions, that served as a frontline combat formation during World War II and was often involved in both conventional warfare and war crimes.
-
D.
Waffen-SS special operations unit
A Waffen-SS special operations unit is a historically specific, elite paramilitary formation of Nazi Germany’s SS tasked with conducting high-risk, often clandestine or irregular military missions during World War II.
-
E.
Waffen-SS armoured corps
The Waffen-SS armoured corps was the armoured warfare branch of Nazi Germany’s Waffen-SS, comprising elite but ideologically driven tank and mechanized formations that fought alongside the regular army on multiple fronts 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:18 a.m.