Triple
T15064456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS-Schwere Panzerabteilung 101 |
E379718
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Waffen-SS heavy tank battalion |
C35397
|
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 heavy tank battalion Context triple: [SS-Schwere Panzerabteilung 101, instanceOf, Waffen-SS heavy tank battalion]
-
A.
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.
-
B.
Waffen-SS armoured division
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.
-
C.
Wehrmacht armoured division
A Wehrmacht armoured division was a World War II German military formation combining tanks, mechanized infantry, artillery, and support units to conduct fast, coordinated offensive operations.
-
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 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.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:02 a.m.