Halicarnassus
ancient Greek city in Caria, present day Bodrum in Turkey
Halicarnassus was an ancient city in Caria, in Anatolia. It was located in southwest Caria, on an advantageous site on the Gulf of Gökova, which is now in Bodrum, Turkey. The city was famous for the Mausoleum of Halicarnassus, also known simply as the Tomb of Mausolus, whose name provided the origin of the word "mausoleum". The mausoleum, built from 353 to 350 BC, ranked as one of the seven wonders of the ancient world.
Halicarnassus' history was unique on two interlinked issues. Halicarnassus retained a monarchical system of government at a time when most other Greek city states had long since rid themselves of their kings. Secondly, while their Ionian neighbours rebelled against Persian rule, Halicarnassus remained loyal to them. It formed part of the Persian Empire until Alexander the Great captured it at the siege of Halicarnassus in 333 BC.
Zephyria was the original name of the settlement, and the present site of the great Castle of St. Peter built by the Knights of Rhodes in 1404 AD. It was built on what was originally an island, which gradually expanded to include several Carian settlements on the mainland. However, in the course of time, the island topographically united with the mainland, and the city was extended to combine with the existing Salmacis, an older town of the native Leleges and Carians, and site of the later citadel.
“Halicarnassus” enters the record as ancient Greek city in Caria, present day Bodrum in Turkey. Crown Archives preserves that source wording while asking what Halicarnassus, ancient and Greek can confirm, complicate or overturn.
Why this record matters
“Halicarnassus” is worth following because a concise public description often conceals a longer documentary argument. Here, Halicarnassus, ancient and Greek provides the most credible route into that argument.
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 20, 2026. The linked authority identifier is Q5843680. VIAF identifies the subject as 239465532. Authority coordinates are 37.038, 27.424. 2 of 4 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1404.
Modern boundaries and familiar names can conceal earlier jurisdictions or structures that do not align with the present site. 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 “Halicarnassus”, its source revision and the description used here.
- Expand the search: follow Halicarnassus primary sources, Halicarnassus archive and Halicarnassus 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 “Halicarnassus”?
- Which authority defined the place, boundary or structure at the relevant date?
- Which earlier names or jurisdictions may reveal additional records?
Search terms from this dossier
This entry incorporates text from “Halicarnassus” 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.