Zhu Shizhen
father of Hongwu Emperor

Zhu Shizhen (1281–1344), born Zhu Wusi, was the father of Zhu Yuanzhang, the Hongwu Emperor, the founding emperor of the Ming dynasty of China.
Zhu Shizhen was a native of Jurong. His father, Zhu Chuyi, later relocated the family to Xuyi in Si Prefecture, and in subsequent years Zhu Shizhen moved to Zhongli in Hao Prefecture with his wife of the Chen clan and their children. In 1344, when a severe drought devastated the lands north of the Huai River, Zhu Shizhen, Lady Chen, and their eldest son succumbed one after another. After founding the Ming dynasty in 1368, Zhu Yuanzhang posthumously elevated his father as Emperor Chun, with the temple name Renzu, while his mausoleum was established at Fengyang as the Imperial Mausoleum.
Early life
Zhu Wusi was born in 1281 at Zhujiaxiang, Tongde Township, Jurong County, Jiangsu, China. His father, Zhu Chuyi, was registered as a "gold-washing household" (taojin hu) under the Yuan dynasty, which required him to deliver a fixed amount of gold annually to the authorities. As there were no gold mines in Jurong, Zhu Chuyi was forced to sell agricultural products for cash and then purchase gold to meet the quota—an arduous and costly burden. Unable to withstand the continued pressure from officials, in 1289, when Zhu Wusi was eight years old, Zhu Chuyi moved the family to Sunjiagang, located thirteen li north of Si Prefecture (in modern Xuyi County, Huai'an, Jiangsu).
Zhu Wusi married a woman of the Chen family, who bore him a son, Zhu Chongsi, and a daughter while they resided in Xuyi.
This brief starts where responsible research should: with the source description of “Zhu Shizhen” as father of Hongwu Emperor. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as father of Hongwu Emperor. Its deeper value depends on whether names, dates, institutions and citations support that framing.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Sep 22, 2026. The linked authority identifier is Q6121440. None of the 1 selected statements returned an explicit reference. The first chronological checks are 1281, 1344, 1368 and 1289.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. 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
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 “Zhu Shizhen”, its source revision and the description used here.
- Expand the search: follow Zhu Shizhen primary sources, Zhu Shizhen archive and Shizhen 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 “Zhu Shizhen”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Zhu Shizhen” 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.