Triple
T10612301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saadat Ali Khan I |
E276034
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal noble |
C4231
|
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 noble Context triple: [Saadat Ali Khan I, instanceOf, Mughal noble]
-
A.
Mughal official
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.
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.
-
C.
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.
-
D.
Mughal princess
A Mughal princess is a royal woman of the Mughal Empire, typically involved in courtly politics, patronage of arts and architecture, and the preservation and exercise of dynastic power and cultural influence.
-
E.
Nawab
chosen
Nawab: A Nawab is a historical title for a Muslim noble or provincial governor in South Asia, often associated with regional power, landownership, and a refined courtly lifestyle under larger empires such as the Mughals or the British Raj.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 7:33 p.m.