Triple
T19478043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unternehmen Wintergewitter |
E487302
|
entity |
| Predicate | SovietUnitInvolved |
P40398
|
FINISHED |
| Object | 2nd Guards 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: 2nd Guards Army Context triple: [Unternehmen Wintergewitter, SovietUnitInvolved, 2nd Guards Army]
-
A.
3rd Guards Army
The 3rd Guards Army was a distinguished Soviet Red Army formation in World War II, noted for its key role in major Eastern Front offensives against Nazi Germany.
-
B.
1st Guards Army
The 1st Guards Army was an elite Soviet Red Army formation that played a key role on the Eastern Front of World War II, participating in major offensives against Nazi Germany.
-
C.
10th Guards Army
The 10th Guards Army was an elite Soviet Red Army formation that fought on the Eastern Front during World War II, distinguished by its "Guards" status for exceptional combat performance.
-
D.
Soviet 2nd Guards Army
chosen
The Soviet 2nd Guards Army was an elite Red Army formation that played a key role on the Eastern Front in World War II, particularly in major offensives against German forces in East Prussia and beyond.
-
E.
7th Guards Army
The 7th Guards Army was a distinguished Soviet Red Army formation in World War II, noted for its elite status and key role in major Eastern Front operations.
- 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.