Triple
T22520969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yūsuf (son of al-Ḥāfiẓ li-Dīn Allāh) |
E556772
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 12th-century Egyptian noble |
C45068
|
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: 12th-century Egyptian noble Context triple: [Yūsuf (son of al-Ḥāfiẓ li-Dīn Allāh), instanceOf, 12th-century Egyptian noble]
-
A.
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.
-
B.
Ayyubid prince
An Ayyubid prince is a male member of the ruling family of the medieval Ayyubid dynasty, typically holding territorial authority, military command, or administrative responsibilities within the dynasty’s fragmented domains in the Middle East.
-
C.
Wāli of Egypt
The Wāli of Egypt was the Ottoman-appointed governor who administered Egypt on behalf of the sultan, overseeing its military, fiscal, and civil affairs.
-
D.
Fatimid official
chosen
A Fatimid official was an administrative or military functionary serving the Fatimid Caliphate, responsible for implementing state policy, managing governance, and upholding the interests of the Isma'ili Shi'a regime across its territories.
-
E.
Fatimid chief qadi
The Fatimid chief qadi was the highest judicial authority in the Fatimid Caliphate, overseeing the application of Islamic law, supervising judges and courts, and advising the caliph on legal and religious matters.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.