Triple

T38666656
Position Surface form Disambiguated ID Type / Status
Subject Sack of Surat (1664) E940471 entity
Predicate instanceOf P0 FINISHED
Object event in the Maratha–Mughal Wars C65520 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: event in the Maratha–Mughal Wars
Context triple: [Sack of Surat (1664), instanceOf, event in the Maratha–Mughal Wars]
  • A. event in the Third Anglo-Mysore War
    An event in the Third Anglo-Mysore War is a specific military, political, or diplomatic occurrence between 1789 and 1792 that significantly influenced the course or outcome of the conflict between the Kingdom of Mysore and the British East India Company and its allies.
  • B. Anglo-Maratha War
    The Anglo-Maratha War refers to a series of three late 18th- and early 19th-century conflicts between the British East India Company and the Maratha Empire that ultimately led to British dominance over most of India.
  • C. office in the Maratha Empire
    An office in the Maratha Empire was an administrative or military position within the Maratha governance structure, responsible for managing specific territorial, fiscal, or command duties under the authority of the Maratha rulers.
  • D. event in the Seven Years' War
    An event in the Seven Years' War is a specific historical occurrence—such as a battle, treaty, campaign, or political decision—that took place between 1756 and 1763 and significantly influenced the course or outcome of the global conflict.
  • E. event in the Kurukshetra War
    An event in the Kurukshetra War is a distinct occurrence or incident—such as a battle, duel, divine intervention, or strategic decision—that takes place within the narrative timeline of the Kurukshetra conflict and influences its progression or outcome.
  • 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_69f76edfde348190bf6529d9f49ecd62 completed May 3, 2026, 3:50 p.m.
Created at: May 3, 2026, 4:33 p.m.