Triple
T19609640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5. SS-Panzer-Division „Wiking“ |
E470694
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Waffen-SS Panzer division |
C16370
|
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 Panzer division Context triple: [5. SS-Panzer-Division „Wiking“, instanceOf, Waffen-SS Panzer division]
-
A.
Waffen-SS armoured division
chosen
A Waffen-SS armoured division was a large, elite German World War II combat formation combining tanks, mechanized infantry, artillery, and support units under the Nazi Party’s SS organization.
-
B.
Waffen-SS division
A Waffen-SS division was a large, front-line combat formation of Nazi Germany’s Waffen-SS, combining infantry, armor, and support units under a unified command and ideologically aligned with the SS.
-
C.
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.
-
D.
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.
-
E.
Waffen-SS heavy tank battalion
A Waffen-SS heavy tank battalion was a specialized World War II German armored unit equipped primarily with heavy tanks like the Tiger, organized to deliver concentrated breakthrough and counterattack power in support of SS corps and army operations.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:43 p.m.