Ivan Gannibal
Russian general (1735–1801)
Ivan Abramovich Gannibal (Russian: Ива́н Абра́мович Ганниба́л; 5 June 1735 – 12 October 1801) was a Russian military leader. He was the son of military commander, general and engineer Abram Petrovich Gannibal, as well as the great-uncle of Russia's most famous poet, Alexander Pushkin.
Gannibal led a detachment of the Imperial Black Sea Fleet, which besieged and captured the Turkish fortress of Navarin during the Russo-Turkish War of 1768–1774, and took part in the founding of the city of Kherson. Gannibal's ultimate military rank was Général en Chef.
Early life
Gannibal was the oldest of 10 children born to Abram Gannibal and his Swedish-German wife Christina Regina Siöberg in Karjaküla, Reval Governorate, Russian Empire (presently in Estonia). Gannibal was destined for a military career from an early age, entering the Naval Artillery School in the imperial capital at the age of 9. He would eventually graduate from the Naval Academy and join the Imperial Russian Navy as an officer.
Russo-Turkish War
At the height of the Russo-Turkish War of 1768-1774, the 34-year-old Gannibal, in the rank of Brigadier, took a leading role in the siege and capture of the Ottoman fortress of Navarino in the Peloponnese.
The Russian Mediterranean Expeditionary Force under the command of Count Alexey Grigoryevich Orlov sent a squadron of ships toward Navarino in April 1770. Three of the vessels were sent toward shore with a forward force of 300 men and a number of artillery pieces, under Gannibal's command.
This brief starts where responsible research should: with the source description of “Ivan Gannibal” as russian general (1735–1801). 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 russian general (1735–1801). 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 Jul 9, 2026. The linked authority identifier is Q4133331. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1735, 1801, 1768 and 1774.
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 “Ivan Gannibal”, its source revision and the description used here.
- Expand the search: follow Ivan Gannibal primary sources, Ivan Gannibal archive and Ivan 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 “Ivan Gannibal”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Ivan Gannibal” 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.