Triple
T14579772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German 2nd Panzer Group |
E342158
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Panzergruppe |
C25499
|
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: Panzergruppe Context triple: [German 2nd Panzer Group, instanceOf, Panzergruppe]
-
A.
German Army panzer division
A German Army panzer division is a World War II-era combined-arms military formation centered on tanks, supported by mechanized infantry, artillery, and reconnaissance units, designed for rapid, offensive armored warfare.
-
B.
Wehrmacht corps
A Wehrmacht corps was a mid-level German Army formation in World War II, typically commanding several divisions and supporting units to conduct coordinated operations within a larger army structure.
-
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 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.
-
E.
Wehrmacht army detachment
chosen
A Wehrmacht army detachment was a flexible, temporary German World War II field formation, typically larger than a corps but smaller than a full army, created to control specific operational sectors or ad hoc groupings of units.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:24 a.m.