Triple
T19478040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unternehmen Wintergewitter |
E487302
|
entity |
| Predicate | GermanUnitInvolved |
P25051
|
FINISHED |
| Object | 4th Panzer Army |
—
|
NE GENERATED |
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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 4th Panzer Army Context triple: [Unternehmen Wintergewitter, GermanUnitInvolved, 4th Panzer Army]
-
A.
5th Panzer Army
The 5th Panzer Army was a German World War II armored field army that played major roles in campaigns in North Africa and on the Western Front, including the Battle of the Bulge.
-
B.
3rd Panzer Army
The 3rd Panzer Army was a German Wehrmacht armored field army of World War II that played a major role on the Eastern Front, particularly in large-scale offensives and defensive operations against the Soviet Union.
-
C.
6th Panzer Army
The 6th Panzer Army was a major German armoured formation of the Waffen-SS that played a central role in late World War II offensives on the Western and Eastern Fronts, including the Battle of the Bulge.
-
D.
2nd Panzer Army
The 2nd Panzer Army was a major German Wehrmacht armored formation in World War II, noted for its leading role in early Eastern Front offensives and subsequent operations across the Soviet Union and the Balkans.
-
E.
German 4th Panzer Army
chosen
The German 4th Panzer Army was a major Wehrmacht armored formation on the Eastern Front in World War II, playing a central role in key operations including the drive toward Stalingrad and later defensive battles against the Red Army.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:39 p.m.