Triple
T38278734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sayf al-Dawla |
E1022029
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hamdanid emir |
C26187
|
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: Hamdanid emir Context triple: [Sayf al-Dawla, instanceOf, Hamdanid emir]
-
A.
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.
-
B.
Ghaznavid sultan
A Ghaznavid sultan is the sovereign ruler of the medieval Ghaznavid dynasty, governing its territories, directing military campaigns, and overseeing political, economic, and religious affairs of the state.
-
C.
Aghlabid ruler
An Aghlabid ruler is a sovereign from the Aghlabid dynasty who governed the semi-autonomous emirate of Ifriqiya under nominal Abbasid suzerainty, overseeing military expansion, economic development, and cultural patronage in North Africa and the central Mediterranean between the 9th and early 10th centuries.
-
D.
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.
-
E.
Emir
chosen
Emir is a noble title denoting a ruler, commander, or high-ranking leader in various Islamic societies, often governing a territory or holding significant political and military authority.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.