Triple

T21573237
Position Surface form Disambiguated ID Type / Status
Subject mansabdars E532334 entity
Predicate instanceOf P0 FINISHED
Object Mughal administrative rank-holder 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 administrative rank-holder
Context triple: [mansabdars, instanceOf, Mughal administrative rank-holder]
  • 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. member of the Mughal dynasty
    A member of the Mughal dynasty is an individual belonging by birth or marriage to the imperial Timurid-origin ruling family that governed large parts of the Indian subcontinent from the early 16th to the mid-19th century.
  • C. Persian court official
    A Persian court official is a high-ranking administrator or advisor serving the royal court of ancient or medieval Persia, responsible for managing state affairs, protocol, and governance on behalf of the monarch.
  • D. British East India Company officer
    A British East India Company officer was a commissioned military or administrative official serving under the Company’s authority in India and other colonial territories, responsible for enforcing its policies, protecting its commercial interests, and often exercising significant political and military power.
  • E. Indian princely ruler
    An Indian princely ruler is a hereditary monarch or sovereign of a semi-autonomous princely state in the Indian subcontinent who exercised varying degrees of internal authority under overarching imperial or colonial powers.
  • 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_69e0c4618bec8190bcb0feb74568cbb1 completed April 16, 2026, 11:13 a.m.
Created at: April 16, 2026, 6:30 p.m.