Triple
T10836274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Khayzuran |
E255764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Abbasid royal consort |
C28866
|
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: Abbasid royal consort Context triple: [al-Khayzuran, instanceOf, Abbasid royal consort]
-
A.
concubine of Muhammad
A concubine of Muhammad is a woman who, under the social and legal norms of 7th-century Arabia, was held in a status of enslaved or captive partner and maintained an intimate, non-marital relationship with the Prophet Muhammad.
-
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 official
An Abbasid official was a bureaucrat or administrator serving the Abbasid Caliphate, responsible for managing state affairs such as taxation, justice, military logistics, and provincial governance within the empire’s centralized administrative system.
-
D.
Salian dynasty consort
A Salian dynasty consort is the spouse of a reigning monarch from the Salian (Frankish and later Holy Roman) ruling house, holding a supportive and often influential role in court and dynastic affairs.
-
E.
Shahbanu of Iran
The Shahbanu of Iran was the title given to the empress consort of the Shah, serving as the highest-ranking woman in the Iranian monarchy with ceremonial, cultural, and sometimes philanthropic roles.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:19 p.m.