Hryhoriy Chorny
Ukrainian hetman
Hryhoriy Savych Chorny (Ukrainian: Григорій (Грицько) Савич Чорний, Polish: Hryćko Czarny), died 1630, was a Hetman of the Dnieper Cossacks from 1628 to 1630 who represented the registered Cossacks while the larger bulk of unregistered ones elected Taras Fedorovych (Triasylo) as their popular leader.
In 1628 Chorny along with Mykhailo Doroshenko took part in the Crimean campaign against the Crimean Tatars. Following Doroshenko's death both Fedorovych and Chorny laid their claim to Hetmanship while only the latter's claim was recognized by the Polish Crown despite Fedorovych's unquestionably larger popular support.
As a Hetman, Chorny conducted pro-Polish policies, particularly aimed at suppression and control of the rank and file of the unregistered Cossacks.
During the popular Fedorovych Uprising of unregistered Cossacks and peasants Chorny was captured by the rebels and had to stand trial before a Cossack military tribunal. He was found guilty and sentenced to death for the support of the Polish policies and the Union of Brest, a subtle attempt of Catholicization of unwilling traditionally Orthodox Ukrainians. Chorny was beheaded in Borovytsi, currently a village in Chyhyrynskyi Raion (district) of Cherkasy Oblast (province).
References
Ihor Pidkova (editor), Roman Shust (editor), "Dovidnyk z istorii Ukrainy Archived 2009-04-10 at the Wayback Machine", 3 Volumes, "(t. 3) Archived 2012-01-21 at the Wayback Machine, Kyiv, 1993-1999, ISBN 5-7707-5190-8 (t. 1), ISBN 5-7707-8552-7 (t.
“Hryhoriy Chorny” enters the record as ukrainian hetman. Crown Archives preserves that source wording while asking what Hryhoriy, Chorny and Ukrainian can confirm, complicate or overturn.
Why this record matters
“Hryhoriy Chorny” is worth following because a concise public description often conceals a longer documentary argument. Here, Hryhoriy, Chorny and Ukrainian provides the most credible route into that argument.
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 Nov 8, 2025. The linked authority identifier is Q4517229. 1 of 1 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 1630, 1628, 2009 and 2012.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. 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 “Hryhoriy Chorny”, its source revision and the description used here.
- Expand the search: follow Hryhoriy Chorny primary sources, Hryhoriy Chorny archive and Hryhoriy 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 “Hryhoriy Chorny”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Hryhoriy Chorny” 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.