Triple

T5772856
Position Surface form Disambiguated ID Type / Status
Subject The Deluge (Swedish invasion of the Polish–Lithuanian Commonwealth) E127368 entity
Predicate instanceOf P0 FINISHED
Object Swedish invasion C18789 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: Swedish invasion
Context triple: [The Deluge (Swedish invasion of the Polish–Lithuanian Commonwealth), instanceOf, Swedish invasion]
  • A. Viking raid
    A Viking raid is a swift, seaborne assault by Norse warriors on coastal or riverside settlements, aimed at plunder, captives, and territorial influence.
  • B. Mongol invasion
    The Mongol invasion refers to the series of 13th- and 14th-century military campaigns by the Mongol Empire that rapidly expanded its control across Eurasia through highly mobile warfare, psychological tactics, and widespread destruction.
  • C. invasion of Russia
    Invasion of Russia is a large-scale military campaign in which foreign forces attempt to penetrate, occupy, or subdue Russian territory, often facing vast distances, harsh climate, and strong defensive resistance.
  • D. Soviet–Finnish War
    The Soviet–Finnish War, also known as the Winter War (1939–1940), was a conflict in which the Soviet Union invaded Finland to secure territory and strategic depth, facing unexpectedly strong Finnish resistance in harsh winter conditions.
  • E. 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.
  • 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_69c00834f6308190851b0abeddd8ed7e completed March 22, 2026, 3:18 p.m.
Created at: March 22, 2026, 3:50 p.m.