Triple
T33753972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermann Göring Panzer Division |
E864922
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German armoured division |
C10086
|
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: German armoured division Context triple: [Hermann Göring Panzer Division, instanceOf, German armoured division]
-
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 armoured division
chosen
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.
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.
German armoured formation
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.
Waffen-SS armoured division
A Waffen-SS armoured division was a large, elite German World War II combat formation combining tanks, mechanized infantry, artillery, and support units under the Nazi Party’s SS organization.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.