Triple

T18868024
Position Surface form Disambiguated ID Type / Status
Subject Żeligowski's Mutiny E461491 entity
Predicate instanceOf P0 FINISHED
Object Polish–Lithuanian War event C6009 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: Polish–Lithuanian War event
Context triple: [Żeligowski's Mutiny, instanceOf, Polish–Lithuanian War event]
  • A. battle of the Polish–Ukrainian War
    A battle of the Polish–Ukrainian War is a specific military engagement between Polish and Ukrainian forces during the 1918–1919 conflict over territorial control and national sovereignty in Eastern Europe.
  • B. Polish–Russian war
    The Polish–Russian war refers to a series of historical military conflicts between Poland (or the Polish–Lithuanian Commonwealth) and Russia (including Muscovy and later the Russian Empire) over territorial control, political influence, and regional dominance in Eastern Europe.
  • C. Polish military history event chosen
    A Polish military history event is a significant occurrence involving Poland’s armed forces—such as battles, campaigns, uprisings, operations, or strategic decisions—that influenced the course of Poland’s national or military development.
  • D. Polish–Teutonic War
    The Polish–Teutonic War was a series of late medieval and early modern conflicts between the Kingdom of Poland (often allied with Lithuania) and the Teutonic Order over territorial control and regional dominance in the Baltic region.
  • E. conflict in the Polish–Lithuanian Commonwealth
    Conflict in the Polish–Lithuanian Commonwealth encompasses the political, social, religious, and military disputes that arose within and around the dual state, shaping its internal dynamics and external relations from its formation to its partitions.
  • F. None of above.

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_69d8dcfb7b9c8190854e7b171b98ea2e completed April 10, 2026, 11:20 a.m.
Created at: April 10, 2026, 11:57 a.m.