Triple
T27687252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | schwere Panzerjäger-Abteilung 653 |
E698064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wehrmacht Heer unit |
C53167
|
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: Wehrmacht Heer unit Context triple: [schwere Panzerjäger-Abteilung 653, instanceOf, Wehrmacht Heer unit]
-
A.
Wehrmacht regiment
A Wehrmacht regiment was a mid-level military unit of Nazi Germany’s armed forces, typically composed of several battalions and supporting elements, responsible for tactical operations within a division.
-
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 army detachment
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.
-
D.
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.
-
E.
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.
- 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.