Triple
T19478045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unternehmen Wintergewitter |
E487302
|
entity |
| Predicate | followedBy |
P78
|
FINISHED |
| Object | Operation Little Saturn |
—
|
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: Operation Little Saturn Context triple: [Unternehmen Wintergewitter, followedBy, Operation Little Saturn]
-
A.
Operation Little Saturn
chosen
Operation Little Saturn was a major Soviet offensive in December 1942 aimed at exploiting the encirclement of German forces near Stalingrad by striking deeper into Axis rear areas and collapsing their southern front.
-
B.
Operation Suvorov
Operation Suvorov was a major 1943 Soviet offensive during World War II aimed at recapturing the city of Smolensk from German forces and weakening the German Army Group Center.
-
C.
Operation Bagration
Operation Bagration was a massive 1944 Soviet offensive on the Eastern Front that destroyed much of Germany’s Army Group Centre and marked a decisive turning point in World War II.
-
D.
Operation Uranus
Operation Uranus was the major Soviet counteroffensive launched in November 1942 that encircled German forces at Stalingrad, marking a decisive turning point on the Eastern Front in World War II.
-
E.
Operation Rumyantsev
Operation Rumyantsev was a major Soviet offensive in August 1943 aimed at recapturing Belgorod and Kharkov from German forces following the Battle of Kursk.
- 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.