Ghiyath al-Din Muhammad
Sultan of Ghurid Empire
Ghiyath al-Din Muhammad (Persian: غیاث الدین محمد بن سام), also known as Ghiyath al-Din Ghori or Ghiyassuddin Ghori (c. 1140 – 13 March 1203), was the Sultan of the Ghurid dynasty from 1163 until his death in 1203. During the diarchy of Ghiyath and his younger brother Muhammad of Ghor, who governed the eastern realm of the Ghurid Empire, the Ghurids emerged as one of the greatest powers of the eastern Islamic world.
During his early reign, he defeated the Ghurid claimants to the throne and fought with the Khwarazmian Empire over the lordship of Khorasan. He occupied Ghazna and Herat by 1175 and went on to establish control over most of what is now Afghanistan and the surrounding areas by 1200, and as far west as Bastam and Gurgan. His brother, Mu'izz al-Din, helped manage and expand the eastern part of the empire (as far as Bengal) and served Ghiyath with utmost loyalty and deference. Ghiyath died in 1203 and was succeeded by Mu'izz al-Din.
Early life
Ghiyath was born in 1140, as the son of Baha al-Din Sam I, who briefly reigned as king of the Ghurid dynasty in 1149. According to the Tabaqat-i-Nasiri by Minhaj al-Siraj, his birth name like his younger sibling Muhammad of Ghor was "Muhammad". During the tender years of Ghiyath al-Din, his mother used to call him "Habshi" due to his dark complexion. His title as a prince was "Shamsuddin" and after ascending the throne, he styled himself as "Ghiyasuddin or "Ghiyath al-Din.
This brief starts where responsible research should: with the source description of “Ghiyath al-Din Muhammad” as sultan of Ghurid Empire. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the history & society register because the source frames it as sultan of Ghurid Empire. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Contemporary correspondence, administrative files and participant testimony can test how later narratives organized the event or institution. The source revision retrieved here is dated Jun 10, 2026. The linked authority identifier is Q3918363. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1140, 1203, 1163 and 1175.
Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Ghiyath al-Din Muhammad”, its source revision and the description used here.
- Expand the search: follow Ghiyath al-Din Muhammad primary sources, Ghiyath al-Din Muhammad archive and Ghiyath 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 “Ghiyath al-Din Muhammad”?
- What chronology connects this entry to wider political or social change?
- Who created the surviving record, and for what administrative purpose?
Search terms from this dossier
This entry incorporates text from “Ghiyath al-Din Muhammad” 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.