Triple
T19033462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kampfgruppe Peiper |
E465803
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | armored Kampfgruppe |
C32525
|
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: armored Kampfgruppe Context triple: [Kampfgruppe Peiper, instanceOf, armored Kampfgruppe]
-
A.
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.
-
B.
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.
-
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.
German armoured formation
chosen
A German armoured formation is a military unit or grouping, typically at battalion, regiment, brigade, or division level, built around tanks and other armored fighting vehicles to conduct rapid, mechanized offensive and defensive operations.
-
E.
Panzergrenadier regiment
A Panzergrenadier regiment is a mechanized infantry formation, typically integrated with armored units, designed to conduct rapid, combined-arms operations alongside tanks.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:02 p.m.