Triple

T3842063
Position Surface form Disambiguated ID Type / Status
Subject Bairam Khan E93473 entity
Predicate instanceOf P0 FINISHED
Object Mughal statesman C13577 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: Mughal statesman
Context triple: [Bairam Khan, instanceOf, Mughal statesman]
  • A. Mughal official chosen
    A Mughal official was an appointed administrator or noble in the Mughal Empire responsible for governing territories, collecting revenue, maintaining law and order, and implementing imperial policies on behalf of the emperor.
  • B. Governor-General of Bengal
    The Governor-General of Bengal was the chief British official in colonial Bengal, later evolving into the de facto head of British administration in India, responsible for overseeing governance, revenue, and foreign affairs in the region.
  • C. subah of the Mughal Empire
    A subah of the Mughal Empire was a major provincial administrative division governed by a subahdar, responsible for local governance, revenue collection, and military control within its territory.
  • D. Hindu ruler
    A Hindu ruler is a sovereign or monarch who governs a territory while adhering to, promoting, or being culturally shaped by Hindu religious, social, and philosophical traditions.
  • E. Mughal noblewoman
    A Mughal noblewoman is an elite female member of the Mughal courtly aristocracy, distinguished by her lineage, wealth, political influence, and participation in the cultural and social life of the empire.
  • 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_69aed96ce578819084ab16e3439976c9 completed March 9, 2026, 2:30 p.m.
Created at: March 9, 2026, 3:18 p.m.