Triple
T25442565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramazanid beylik |
E637545
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Turkmen beylik |
C25982
|
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: Turkmen beylik Context triple: [Ramazanid beylik, instanceOf, Turkmen beylik]
-
A.
Oghuz Turkic polity
chosen
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.
-
B.
Oghuz Turk
An Oghuz Turk is a member of a historical western Turkic tribal confederation whose descendants include many modern Turkic peoples such as Turks of Turkey, Azerbaijanis, and Turkmen.
-
C.
Uzbek ruling house
The Uzbek ruling house is the dynastic lineage that held political authority and sovereignty over Uzbek territories, shaping the region’s governance, culture, and historical development.
-
D.
Turkish principality
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.
-
E.
Barmakid
A Barmakid is a member of a powerful Persian family of viziers and administrators who served the early Abbasid caliphs, renowned for their influence, wealth, and patronage of culture before their sudden downfall.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2 p.m.