Triple
T13917564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saray Mulk Khanum |
E334661
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Timurid royal consort |
C34369
|
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: Timurid royal consort Context triple: [Saray Mulk Khanum, instanceOf, Timurid royal consort]
-
A.
Timurid princess
A Timurid princess is a noblewoman of the Timurid dynasty, typically involved in dynastic politics, cultural patronage, and the consolidation of power across Central and South Asia between the 14th and 16th centuries.
-
B.
Ottoman consort
An Ottoman consort was a woman in the Ottoman imperial harem who, as a wife or favored companion of the sultan, held varying degrees of social, political, and ceremonial influence within the court.
-
C.
Abbasid royal consort
An Abbasid royal consort is a spouse or favored partner of an Abbasid caliph who held recognized status within the caliphal household and often wielded social, cultural, or political influence at court.
-
D.
Ottoman princess
An Ottoman princess is a female member of the Ottoman dynasty, typically the daughter, sister, or close female relative of a sultan, who held significant social status, political influence, and cultural patronage within the imperial court.
-
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. 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.