Triple
T22475526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ziyadat Allah III |
E555619
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Aghlabid ruler |
C46358
|
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: Aghlabid ruler Context triple: [Ziyadat Allah III, instanceOf, Aghlabid ruler]
-
A.
Alaouite ruler
An Alaouite ruler is a sovereign from the Alaouite dynasty of Morocco, which has governed the country since the 17th century, combining religious legitimacy as sharifs (descendants of the Prophet Muhammad) with political authority over the Moroccan state.
-
B.
Zengid ruler
A Zengid ruler is a sovereign or governor from the Zengid dynasty, a 12th–13th century Muslim Turkic ruling house that controlled parts of Syria and northern Iraq, known for its military campaigns against Crusader states and efforts to unify Muslim territories.
-
C.
Umayyad emir of Córdoba
An Umayyad emir of Córdoba was a ruler from the Umayyad dynasty who governed the Emirate of Córdoba in al-Andalus, overseeing its political, military, and administrative affairs between the mid-8th and early 10th centuries.
-
D.
Artuqid ruler
An Artuqid ruler is a sovereign or governor from the Artuqid dynasty, a Turkoman ruling family that controlled various principalities in Upper Mesopotamia and Anatolia between the late 11th and early 15th centuries.
-
E.
Bey of Tunis
The Bey of Tunis was the hereditary ruler of the Regency of Tunis under Ottoman suzerainty, functioning as both political leader and symbolic sovereign until the monarchy’s abolition in 1957.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:49 p.m.