Triple
T36287572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shujāʿ |
E893131
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Abbasid noblewoman |
C37594
|
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 noblewoman Context triple: [Shujāʿ, instanceOf, Abbasid noblewoman]
-
A.
Abbasid princess
chosen
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.
-
B.
Fatimid noblewoman
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.
-
C.
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.
-
D.
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.
-
E.
Safavid noblewoman
A Safavid noblewoman is an elite female member of Safavid Iran’s ruling or aristocratic families, whose status, wealth, and influence were shaped by court politics, kinship ties, and the cultural and religious norms of the Safavid dynasty.
- 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_69f76e4955c08190b8cfddca34fc0242 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.