Triple
T19478046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unternehmen Wintergewitter |
E487302
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | German Sixth 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: German Sixth Army Context triple: [Unternehmen Wintergewitter, relatedTo, German Sixth Army]
-
A.
German 6th Army
chosen
The German 6th Army was a major Wehrmacht field army best known for its encirclement and catastrophic defeat at Stalingrad, a turning point on the Eastern Front in World War II.
-
B.
German 6th Army
The German 6th Army was a major field formation of the Imperial German Army in World War I, noted for its role on the Western Front in key battles such as those around Arras and in the early stages of the war.
-
C.
German 7th Army
The German 7th Army was a major field army of the Imperial German Army in World War I, active on the Western Front and involved in several key battles against French and Allied forces.
-
D.
German 7th Army
The German 7th Army was a major field army of the Wehrmacht that fought primarily on the Western Front during World War II, notably in the Normandy campaign and subsequent retreat across France.
-
E.
German 6th SS Panzer Army
The German 6th SS Panzer Army was a Waffen-SS armoured formation of Nazi Germany that fought on both the Western and Eastern Fronts in the final years of World War II, notably during the Battle of the Bulge and the defense of Hungary and Austria.
- 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.