Triple
T13136100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panzergruppe Eberbach |
E312087
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German armoured formation |
C32525
|
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 formation Context triple: [Panzergruppe Eberbach, instanceOf, German armoured formation]
-
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.
German army detachment
A German army detachment is a temporary, task-organized military formation separated from a larger parent unit to conduct specific operations under its own command structure.
-
D.
German field army
A German field army is a large, operational-level military formation of the German armed forces, typically composed of multiple corps and supporting units, organized to conduct sustained land campaigns in a defined theater of war.
-
E.
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.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:08 p.m.