Triple
T22006779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakup I of Germiyan |
E543466
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Turkish beylik ruler |
C45657
|
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: Turkish beylik ruler Context triple: [Yakup I of Germiyan, instanceOf, Turkish beylik ruler]
-
A.
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.
-
B.
Seljuk sultan of Rum
A Seljuk sultan of Rum was the Muslim Turkic ruler of the Sultanate of Rum in Anatolia, governing a medieval state that emerged from the Great Seljuk Empire and served as a political and cultural bridge between the Islamic world and Byzantine-influenced Asia Minor.
-
C.
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.
-
D.
Aq Qoyunlu ruler
An Aq Qoyunlu ruler is a sovereign leader of the Aq Qoyunlu tribal confederation who exercised political, military, and administrative authority over its territories in Anatolia, Iran, and surrounding regions during the 14th–16th centuries.
-
E.
ruler of Karaman
The ruler of Karaman is the sovereign authority governing the historical Anatolian beylik of Karaman, responsible for its political leadership, military command, and administration of justice and resources.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:21 p.m.