Chinese Text Project Data wiki |
Data wiki -> 驃騎將軍
驃騎將軍[View] [Edit] [History]ctext:851682
Relation | Target | Textual basis |
---|---|---|
type | office | |
name | 驃騎將軍 | |
authority-wikidata | Q1051272 | |
link-wikipedia_zh | 骠骑将军 | |
link-wikipedia_en | General_of_Agile_Cavalry |
General of Agile Cavalry was a military rank in Imperial China. The title was introduced during the reign of Emperor Wu of Han. The title was used in subsequent dynasties, sometimes as the General-in-Chief of Agile Cavalry.
The text above has been excerpted automatically from Wikipedia - please correct any errors in the original article.
驃騎將軍,中國古代高級武官職。
漢武帝元狩二年起開始設置驃騎將軍。元狩四年,令官階、俸祿與大將軍等同。東漢以後,各代都有延設,有時加 「驃騎大將軍」 。隋朝和唐朝初年,改為府兵制下基層軍府主官,秩正四品。唐顯慶元年改為武散官名「驃騎大將軍」,宋初延之,政和年間廢,明武散階正二品初授「驃騎將軍」。
Read more...: 各朝代政權的驃騎將軍 西漢 東漢 魏晉 蜀漢 孫吳
The text above has been excerpted automatically from Wikipedia - please correct any errors in the original article.
Source | Relation | from-date |
---|---|---|
劉放 | held-office | 245/10/23正始六年八月癸巳 |
孫資 | held-office | 250/11/12 - 250/12/10嘉平二年十月 |
蕭宏 | held-office | 512/12/16天監十一年十一月己酉 |
王茂 | held-office | 513/10/21天監十二年九月戊午 |
廬陵王續 | held-office | 539/2/4大同五年正月乙卯 |
蕭循 | held-office | 552/12/14承聖元年十一月丁丑 |
王僧辯 | held-office | 555/3/10承聖四年二月癸丑 |
蕭勃 | held-office | 557/1/17太平元年十二月壬申 |
陳宣帝 | held-office | 562/8/3天嘉三年六月丙辰 |
陳叔堅 | held-office | 582/2/26太建十四年正月癸亥 |
Text | Count |
---|---|
北史 | 15 |
陳書 | 18 |
新唐書 | 5 |
全上古三代秦漢三國六朝文 | 8 |
周書 | 10 |
三國志 | 48 |
隋書 | 14 |
明史 | 3 |
舊唐書 | 3 |
漢書 | 4 |
文獻通考 | 4 |
北齊書 | 3 |
梁書 | 18 |
資治通鑑 | 16 |
南史 | 25 |
通志 | 4 |
後漢書 | 8 |
晉書 | 63 |
魏書 | 30 |
南齊書 | 12 |
宋書 | 18 |
明史紀事本末 | 1 |
通典 | 3 |
十六國春秋 | 3 |
Enjoy this site? Please help. | Site design and content copyright 2006-2024. When quoting or citing information from this site, please link to the corresponding page or to https://ctext.org. Please note that the use of automatic download software on this site is strictly prohibited, and that users of such software are automatically banned without warning to save bandwidth. 沪ICP备09015720号-3 | Comments? Suggestions? Please raise them here. |