Sea monster
mythical or legendary creature, believed to dwell in the sea and often imagined to be of immense size
Sea monsters are beings from folklore believed to dwell in the sea and are often imagined to be of immense size. Marine monsters can take many forms, including sea dragons, sea serpents, or tentacled beasts. They can be slimy and scaly and are often pictured threatening ships or spouting jets of water. The definition of a "monster" is subjective; further, some sea monsters may have been based on scientifically accepted creatures, such as whales and types of giant and colossal squid.
Sightings and legends
Sea monster accounts are found in virtually all cultures that have contact with the sea. For example, Avienius relates of Carthaginian explorer Himilco's voyage "...there monsters of the deep, and beasts swim amid the slow and sluggishly crawling ships." (lines 117–29 of Ora Maritima). Sir Humphrey Gilbert claimed to have encountered a lion-like monster with "glaring eyes" on his return voyage after formally claiming St. John's, Newfoundland (1583) for England. Another account of an encounter with a sea monster comes from July 1734. Hans Egede, a Dano-Norwegian missionary, reported that on a voyage to Godthåb on the western coast of Greenland he observed:
a most terrible creature, resembling nothing they saw before.
The public source identifies “Sea monster” as mythical or legendary creature, believed to dwell in the sea and often imagined to be of immense size. This brief keeps that definition visible, then builds a research path around monster, mythical and legendary.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Sea monster”, the useful work is to connect “mythical or legendary creature, believed to dwell in the sea and often imagined to be of immense size” to the records capable of establishing context and consequence.
Maps, plans, fabric surveys and administrative records can establish how the site’s name, extent and function changed over time. The source revision retrieved here is dated Sep 6, 2026. The linked authority identifier is Q920028. The Library of Congress control number is sh85119234. 1 of 1 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 1583 and 1734.
Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. 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
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Sea monster”, its source revision and the description used here.
- Expand the search: follow Sea monster primary sources, Sea monster archive and monster 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 “Sea monster”?
- What physical evidence or contemporary plan supports the description?
- Which earlier names or jurisdictions may reveal additional records?
Search terms from this dossier
This entry incorporates text from “Sea monster” 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.