Triple
T22384323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Süleyman Shah of Germiyan |
E553355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anatolian bey |
C40025
|
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: Anatolian bey Context triple: [Süleyman Shah of Germiyan, instanceOf, Anatolian bey]
-
A.
Turkic bey
chosen
A Turkic bey is a tribal or regional chieftain who held military, administrative, and political authority within Turkic societies, often serving as a vassal or subordinate ruler under a greater sovereign.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Crimean khan
A Crimean khan was the sovereign ruler of the Crimean Khanate, a Turkic-Mongol state that existed from the 15th to the 18th century under the suzerainty of the Ottoman Empire.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.