Duke Kangyang
Goryeo royal
Duke Kangyang or Prince Kangyang (Korean: 강양공; Hanja: 江陽公; died 1308), born Wang Cha, was a Goryeo royal prince as the first and oldest son of King Chungnyeol and Princess Jeongsin, also great-grandfather of its last monarch, King Gongyang.
Biography
Palace life
As the oldest son and since his mother was King Chungnyeol's first wife, Wang Cha was the one who should become the crown prince. Yet, due to Yuan dynasty influence on Goryeo after the king's marriage with Kublai Khan's daughter–Qutugh Kelmysh, Wang Cha must give up the crown prince position to his half younger brother.
In 1279 (5th years reign of his father), Wang Cha had to go to the temple Dongsimsa (동심사) in Aju, Chungcheong Province (now Asan, South Chungcheong Province) to avoid conflict with the crown prince. Four years later in 1283, Wang Cha was able to back to Gaegyeong and received his royal title–Duke Kangyang (강양공; 江陽公).
Death and afterlife
Duke Kangyang died in 1308 (24th years reign of his father) and received his posthumous name, Chŏnggang (정강; 靖康) along with his honorary title, Duke Chŏnggang (정강공; 靖康公) given by his great-grandson–King Gongyang in 1391.
Although his wife is unknown, according to the remaining historical sources, Duke Kangyang had 3 sons: Wang Hu the Grand Prince Danyang (단양대군 왕후) who served in Yuan dynasty, Wang Ko the Prince Yeonan (연안군 왕고) who was King Chungseon's trusted official, and Wang Hun the Prince Yeondeok (연덕군 왕훈) who would become the grandfather of King Gongyang.
Notes
References
External links
Duke Kangyang on the Encyclopedia of Korean Culture (in Korean).
강양공 on Doosan Encyclopedia (in Korean).
This brief starts where responsible research should: with the source description of “Duke Kangyang” as goryeo royal. 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 goryeo royal. Its deeper value depends on whether names, dates, institutions and citations support that framing.
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 Aug 30, 2026. The linked authority identifier is Q12582969. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1308, 1279, 1283 and 1391.
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 “Duke Kangyang”, its source revision and the description used here.
- Expand the search: follow Duke Kangyang primary sources, Duke Kangyang archive and Duke 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 “Duke Kangyang”?
- 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 “Duke Kangyang” 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.