Triple

T32919273
Position Surface form Disambiguated ID Type / Status
Subject Yudenich’s forces E842100 entity
Predicate instanceOf P0 FINISHED
Object White Army contingent C59522 CONCEPT FINISHED

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: White Army contingent
Context triple: [Yudenich’s forces, instanceOf, White Army contingent]
  • A. Polish military contingent
    A Polish military contingent is a temporary, organized group of Polish Armed Forces personnel and resources deployed for specific missions, operations, or international commitments.
  • B. Soviet field army
    A Soviet field army was a large, operational-level military formation of the Soviet Armed Forces, typically comprising multiple corps or divisions, support units, and command structures, organized to conduct sustained offensive or defensive campaigns in a designated theater of operations.
  • C. Mexican field army
    A Mexican field army is a large, operational-level military formation of the Mexican Armed Forces, composed of multiple divisions, brigades, and support units organized to conduct sustained combat and security operations within a designated theater.
  • D. Turkmen troops
    Turkmen troops are military forces composed primarily of ethnic Turkmen soldiers, historically serving in various regional armies and contemporary national armed forces, often reflecting Turkmen cultural, political, and strategic interests.
  • E. Arab volunteer force
    The Arab volunteer force is a loosely organized group of individuals from various Arab countries who voluntarily join military or paramilitary efforts, often motivated by shared political, religious, or ideological goals rather than formal state directives.
  • F. None of above. chosen

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_69f3494779388190a5d3e97f92278be2 completed April 30, 2026, 12:21 p.m.
Created at: May 1, 2026, 1:19 a.m.