Triple
T15257392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sher Afgan Khan |
E364682
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal nobleman |
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 nobleman Context triple: [Sher Afgan Khan, instanceOf, Mughal nobleman]
-
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.
Timurid noble
A Timurid noble is a high-ranking aristocrat within the Timurid Empire, typically of Turco-Mongol lineage, who held land, military command, and administrative authority under the dynasty founded by Timur (Tamerlane).
-
D.
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.
-
E.
crown prince of the Mughal Empire
The crown prince of the Mughal Empire was the designated heir apparent, usually the emperor’s eldest surviving son, who held significant political influence and military command while awaiting succession to the throne.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:13 a.m.