Triple
T11194935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ziyad ibn Salih |
E264897
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Abbasid military commander |
C26121
|
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 military commander Context triple: [Ziyad ibn Salih, instanceOf, Abbasid military commander]
-
A.
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.
-
B.
Islamic-era military person
chosen
An Islamic-era military person is an individual who served in the armed forces of a Muslim-ruled polity during the historical periods of Islamic governance, participating in warfare, defense, or military administration.
-
C.
Umayyad governor
An Umayyad governor was a provincial administrator appointed by the Umayyad caliphs to oversee local governance, tax collection, security, and implementation of central policies within a designated region of the caliphate.
-
D.
Ottoman general
An Ottoman general is a high-ranking military commander in the Ottoman Empire responsible for planning, leading, and overseeing major military campaigns and the administration of troops.
-
E.
Arab general
An Arab general is a high-ranking military leader of Arab origin responsible for planning, directing, and overseeing large-scale armed forces operations and strategy.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:29 p.m.