Triple
T3694665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Wittmann |
E78427
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Waffen-SS officer |
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 officer Context triple: [Michael Wittmann, instanceOf, Waffen-SS officer]
-
A.
Nazi official
A Nazi official is a person who held an administrative, political, or military position within the National Socialist (Nazi) regime in Germany, responsible for implementing and enforcing its totalitarian, racist, and genocidal policies.
-
B.
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.
-
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.
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.
-
E.
Nazi Germany military rank
A Nazi Germany military rank represents a specific hierarchical position within the armed forces of the Third Reich, defining an individual's authority, responsibilities, and status in the military structure.
- F. None of above. chosen
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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:26 p.m.