Triple
T20725293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mehmed Bey of Karaman |
E509418
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Karamanid ruler |
C43501
|
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: Karamanid ruler Context triple: [Mehmed Bey of Karaman, instanceOf, Karamanid 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.
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.
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.
-
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.
Ottoman sultan
An Ottoman sultan is the supreme ruler of the Ottoman Empire, combining political, military, and religious authority as the head of state and caliph of the Muslim world.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:29 p.m.