Triple
T21614245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sitt al-Mulk |
E533392
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Fatimid princess |
C35519
|
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: Fatimid princess Context triple: [Sitt al-Mulk, instanceOf, Fatimid princess]
-
A.
Fatimid noblewoman
chosen
A Fatimid noblewoman is an elite female member of the Fatimid Caliphate’s ruling or aristocratic families, distinguished by her political influence, wealth, education, and participation in courtly, religious, and cultural life.
-
B.
Abbasid princess
An Abbasid princess is a female member of the Abbasid dynasty’s royal family, typically involved in the political, cultural, and social life of the Islamic caliphate through courtly influence, patronage, and dynastic alliances.
-
C.
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.
-
D.
Arab noblewoman
An Arab noblewoman is a high-status woman of Arab heritage, often belonging to a historically influential family or lineage, who embodies cultural refinement, social responsibility, and traditional or contemporary forms of leadership within her community.
-
E.
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.
- 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_69e0c46411108190bba0d4176dffc9f3 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:33 p.m.