Triple

T14180691
Position Surface form Disambiguated ID Type / Status
Subject Babur’s Indian campaigns E351443 entity
Predicate instanceOf P0 FINISHED
Object early 16th-century conflict C14531 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: early 16th-century conflict
Context triple: [Babur’s Indian campaigns, instanceOf, early 16th-century conflict]
  • A. 16th-century conflict chosen
    A 16th-century conflict is a historically documented military, political, or religious struggle that occurred between 1501 and 1600, involving organized groups or states and significantly influencing the social and geopolitical landscape of the early modern period.
  • B. 13th-century conflict
    A 13th-century conflict is a military or political struggle that occurred between 1201 and 1300, shaped by medieval feudal structures, religious motivations, and emerging state powers.
  • 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. 7th-century conflict
    A 7th-century conflict is a military or political struggle that occurred between 600 and 699 CE, typically involving early medieval states, empires, or tribes and shaped by the religious, cultural, and territorial dynamics of that era.
  • E. 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.
  • 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_69d8278834a08190b0f1784e58d7b99c completed April 9, 2026, 10:26 p.m.
Created at: April 10, 2026, 1:02 a.m.