Triple
T7370311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3rd Panzergrenadier Division |
E169982
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Panzergrenadier division |
C16076
|
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: Panzergrenadier division Context triple: [3rd Panzergrenadier Division, instanceOf, Panzergrenadier division]
-
A.
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.
-
B.
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.
-
C.
Wehrmacht infantry division
A Wehrmacht infantry division was a World War II-era German Army formation composed primarily of foot soldiers, supported by artillery, engineers, and logistical units, organized for sustained ground combat operations.
-
D.
armored infantry division
chosen
An armored infantry division is a large, combined-arms military formation that integrates mechanized infantry, tanks, artillery, and support units to conduct sustained offensive and defensive ground operations.
-
E.
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.
- 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:07 p.m.