Triple
T33400341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaykh Uways Jalayir |
E855278
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jalayirid ruler |
C58258
|
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: Jalayirid ruler Context triple: [Shaykh Uways Jalayir, instanceOf, Jalayirid ruler]
-
A.
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.
-
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.
Afsharid ruler
An Afsharid ruler is a sovereign belonging to the Afsharid dynasty that governed Iran and surrounding regions in the 18th century, exercising political, military, and administrative authority over its territories.
-
D.
Turkish beylik ruler
A Turkish beylik ruler is the sovereign leader of a small, often semi-independent principality (beylik) in medieval Anatolia, exercising military, political, and administrative authority over their territory and subjects.
-
E.
Karamanid ruler
A Karamanid ruler is the sovereign leader of the medieval Anatolian Turkish beylik of Karaman, responsible for governing its territories, directing military campaigns, and managing political and diplomatic relations with neighboring powers.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:35 a.m.