Taghachar (d. 1221)
borjigid Prince

Taghachar (died 1221), also known as Toqučar or Toquchar, was a Mongol military commander, involved in the Mongol campaigns in Central Asia. A son-in-law of Genghis Khan, he most notably took part in the invasion of the Khwarezmian Empire in 1219.
Background
Chroniclers Juvayni and al-Nasawi, both writing in the 13th century, state that Taghachar had been Genghis Khan's son-in-law. Historian Anne Broadbridge identifies his wife as having been a junior princess, rejecting an earlier hypothesis by John Andrew Boyle that she had been Tümelün, daughter of Genghis Khan's chief empress Börte.
Taghachar's own background is vague in Mongol works, with no contemporary source mentioning the name of his father. The 15th-century Timurid chronicler Yazdi writes that Taghachar belonged to the Barlas tribe and had been the son of Suqu Sechen and the younger brother of Qarachar Noyan, the ancestors of Timur. However, historian İlker Evrim Binbaş suggests that this relationship was invented due to the marital link Taghachar provides for the Timurid dynasty with Genghis Khan. Writing later still, the 19th century historian Shir Muhammad Munis states that Taghachar was the son of the Khongirad chief Dei Sechen, and therefore the brother of the empress Börte. Both Anne Broadbridge and John Andrew Boyle also identify Taghachar as a Khongirad, though Broadbridge specifies that he was of a junior line to Börte.
Military career
During the campaign against the Jin, Taghachar remained in Mongolia with 20,000 soldiers, guarding the western border while the main army was absent.
Begin with the source’s own compact description: “Taghachar (d. 1221)” is borjigid Prince. The dossier treats that line as a proposition to test through Taghachar, borjigid and Prince, not as a finished interpretation.
Why this record matters
The phrase “borjigid Prince” 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.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jun 25, 2026. The linked authority identifier is Q115965546. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1221 and 1219.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. 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
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Taghachar (d. 1221)”, its source revision and the description used here.
- Expand the search: follow Taghachar (d. 1221) primary sources, Taghachar (d. 1221) archive and Taghachar 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 “Taghachar (d. 1221)”?
- Which cited source is closest to the event, object or claim?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Taghachar (d. 1221)” 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.