Triple

T3479624
Position Surface form Disambiguated ID Type / Status
Subject Mongol invasion of Poland E73458 entity
Predicate instanceOf P0 FINISHED
Object 13th-century conflict C12823 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: 13th-century conflict
Context triple: [Mongol invasion of Poland, instanceOf, 13th-century conflict]
  • A. 4th-century conflict
    A 4th-century conflict is a historical dispute, war, or series of hostilities that occurred between 300 and 399 CE, shaped by the political, religious, and social dynamics of late antiquity.
  • B. 19th-century conflict
    A 19th-century conflict is a large-scale military or political struggle occurring between 1800 and 1899, typically involving nation-states or empires and shaped by industrialization, nationalism, and shifting imperial ambitions.
  • C. early 18th-century conflict
    An early 18th-century conflict is a historically situated armed struggle or war occurring roughly between 1700 and 1750, shaped by emerging nation-states, dynastic rivalries, and evolving military technologies and tactics.
  • D. 15th-century event
    A 15th-century event is a historically significant occurrence that took place between 1401 and 1500, shaped by and contributing to the political, social, cultural, or technological transformations of that period.
  • E. 20th-century conflict
    20th-century conflict encompasses the major wars, revolutions, and geopolitical struggles between 1900 and 1999 that reshaped global power structures, societies, and ideologies.
  • 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_69ad85b3c9b08190857cae74c7f36da9 completed March 8, 2026, 2:20 p.m.
Created at: March 8, 2026, 3:17 p.m.