Triple

T14135886
Position Surface form Disambiguated ID Type / Status
Subject Mongol invasion of 1306 E350293 entity
Predicate instanceOf P0 FINISHED
Object Mongol invasion of the Indian subcontinent C17523 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: Mongol invasion of the Indian subcontinent
Context triple: [Mongol invasion of 1306, instanceOf, Mongol invasion of the Indian subcontinent]
  • A. Mongol invasion chosen
    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.
  • B. Mongol invasion of the Middle East
    The Mongol invasion of the Middle East was a series of 13th- and 14th-century military campaigns by the Mongol Empire that devastated major Islamic centers, reshaped regional political structures, and facilitated new patterns of trade and cultural exchange across Eurasia.
  • C. Mughal campaign
    A Mughal campaign is a military expedition undertaken by the Mughal Empire to expand, consolidate, or defend its territories through organized warfare and strategic operations.
  • D. Mongol invasion of Europe battle
    A Mongol invasion of Europe battle is a military engagement in which Mongol forces confront European armies during their 13th-century westward campaigns, characterized by highly mobile cavalry tactics, psychological warfare, and often decisive Mongol victories.
  • E. Javanese military campaign
    A Javanese military campaign is a coordinated series of armed operations conducted by Javanese polities or forces to achieve specific political, territorial, or strategic objectives.
  • 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_69d827865f608190b311820428ae027b completed April 9, 2026, 10:26 p.m.
Created at: April 10, 2026, 12:13 a.m.