Triple

T19478037
Position Surface form Disambiguated ID Type / Status
Subject Unternehmen Wintergewitter E487302 entity
Predicate opposingForce P4567 FINISHED
Object Soviet 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: Soviet 2nd Guards Army
Context triple: [Unternehmen Wintergewitter, opposingForce, Soviet 2nd Guards Army]
  • A. 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.
  • B. Soviet 3rd Guards Army
    The Soviet 3rd Guards Army was an elite Red Army field formation that played a key role on the Eastern Front in World War II, particularly in major offensives to liberate occupied Soviet territory from Nazi Germany.
  • C. Soviet 5th Guards Army
    The Soviet 5th Guards Army was an elite Red Army formation that played a key role on the Eastern Front in World War II, participating in major offensives during the final push into Germany.
  • D. Soviet 11th Guards Army
    The Soviet 11th Guards Army was an elite Red Army formation that played a key role on the Eastern Front in World War II, particularly in the final offensives against Nazi Germany in East Prussia.
  • E. Soviet 62nd Army
    The Soviet 62nd Army was a Red Army field formation renowned for its pivotal and stubborn defense of Stalingrad during World War II, which played a crucial role in turning the tide on the Eastern Front.
  • 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.