Kaikhosro of Kartli
Georgian titular king of Kartli (1674–1711)

Kaikhosro (Georgian: ქაიხოსრო; 15 April 1674 – 27 September 1711), of the Bagrationi dynasty, was a titular king (a Persian-appointed wali) of Kartli, eastern Georgia, from 1709 to 1711. He reigned in absentia since he served during the whole of this period as a Persian commander-in-chief in what is now Afghanistan.
Biography
Kaikhosro was born on 15 April 1674. He was the eldest son of Prince Levan, and accompanied his father during the service in the Safavid Empire. Since 1703, Kaikhosro himself served on high posts in the Persian administration, including being a darougha (prefect) of the capital city of Isfahan and a naib (deputy) to the divanbeg (chief justice). On the death of his uncle, George XI, in 1709, he was confirmed as a wali/king of Kartli and a sipah-salar (commander-in-chief) of the Persian armies in what is now Afghanistan, and granted Tabriz and Barda in possession. He spent the whole of this period in the field, and Kartli was administered by his brother Vakhtang.
In November 1709, Kaikhosro led a new Persian–Georgian army, supported by contingents from Khorasan, Herat, and Kerman, against the Afghans after Gurgin Khan was assassinated by Mir Wais Hotak, a rebel chieftain of the Ghilzai tribe. Kaikhosro's efforts to take Kandahar, however, were in vain. A fragile truce ensued, but in the summer of 1711 the hostilities resumed.
Begin with the source’s own compact description: “Kaikhosro of Kartli” is georgian titular king of Kartli (1674–1711). The dossier treats that line as a proposition to test through Kaikhosro, Kartli and Georgian, not as a finished interpretation.
Why this record matters
The phrase “georgian titular king of Kartli (1674–1711)” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
The entry’s evidential value lies in the named roles, institutions and publications that can be tested against primary documentation. The source revision retrieved here is dated Aug 27, 2026. The linked authority identifier is Q2702817. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1674, 1711, 1709 and 1703.
Public reputation and documentary evidence do not always develop together; absence from a summary is not evidence of historical absence. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Read biographical claims against dates, named institutions and the cited references. Distinguish a subject’s later reputation from evidence produced during their lifetime.
- Establishing names and roles
- Building a first chronology
- Locating cited institutions
Personal papers, civil or court records, institutional files and the scholarship cited by the source.
Three-step research path
- Establish the record: confirm the title “Kaikhosro of Kartli”, its source revision and the description used here.
- Expand the search: follow Kaikhosro of Kartli primary sources, Kaikhosro of Kartli archive and Kaikhosro research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Kaikhosro of Kartli”?
- How has the subject’s reputation changed across later accounts?
- Which primary records establish identity, chronology and institutional ties?
Search terms from this dossier
This entry incorporates text from “Kaikhosro of Kartli” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.