Triple
T27687254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | schwere Panzerjäger-Abteilung 653 |
E698064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Panzerjäger unit |
C53168
|
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: Panzerjäger unit Context triple: [schwere Panzerjäger-Abteilung 653, instanceOf, Panzerjäger unit]
-
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.
Panzergrenadier regiment
A Panzergrenadier regiment is a mechanized infantry formation, typically integrated with armored units, designed to conduct rapid, combined-arms operations alongside tanks.
-
C.
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.
-
D.
Waffen-SS battle group
A Waffen-SS battle group was an ad hoc, mixed-arms combat formation of the Nazi SS, assembled from available units and resources for specific tactical operations during World War II.
-
E.
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.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:50 p.m.