Triple
T20853734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danishmend Emirate |
E513426
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Turkish beylik |
C18272
|
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 Context triple: [Danishmend Emirate, instanceOf, Turkish beylik]
-
A.
Turkish principality
chosen
A Turkish principality is a semi-independent, territorially defined political entity ruled by a Turkish dynastic leader, typically emerging in the medieval or early modern period within the broader context of Turkic state formation and regional power dynamics.
-
B.
Oghuz Turkic polity
An Oghuz Turkic polity is a socio-political entity formed by Oghuz Turkic groups, typically characterized by tribal confederation structures, nomadic or semi-nomadic lifeways, and rule by military-elite lineages asserting authority over diverse subject populations.
-
C.
Ottoman order
An Ottoman order is a formal honor or decoration bestowed by the Ottoman Empire to recognize distinguished service, loyalty, or achievement in military, civil, or diplomatic fields.
-
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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:44 p.m.