CACrown ArchivesThe cinema collection
EN/FR
Search
Menu
Research dossier · Places & Architecture

Peebles Castle

castle in Scottish Borders, Scotland, UK

Architectural plans, a scale model, maps and brass measuring instruments
Places and architectureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionOct 2, 2025
Entity authorityQ7160134 ↗
Source-derived summary

Peebles Castle was a 12th-century castle built near Peebles, Scotland. Peebles was created a royal burgh by King David I of Scotland in the 12th century. The castle, once a royal castle, was built as a motte-and-bailey castle. Nothing remains above ground.

Citations

References

This article incorporates text from a publication now in the public domain: Chisholm, Hugh, ed. (1911). "Peebles". Encyclopædia Britannica (11th ed.). Cambridge University Press.

Editorial summary

This brief starts where responsible research should: with the source description of “Peebles Castle” as castle in Scottish Borders, Scotland, UK. Everything that follows is an evidence route, not borrowed authority.

Editorial reviewA strong orientation record where physical form, institutional use and historical geography need to be read together. The current lead gives the account dated anchors—1911—that can be checked directly. The selected authority fields contribute no independent date. The account is most persuasive where Peebles, Castle and castle can be independently traced.
Editorial analysis

Why this record matters

The subject matters to the places & architecture register because the source frames it as castle in Scottish Borders, Scotland, UK. Its deeper value depends on whether names, dates, institutions and citations support that framing.

Evidence profile

Place names and jurisdictional language are key evidence: both can reveal earlier catalogue descriptions and overlooked record series. The source revision retrieved here is dated Oct 2, 2025. The linked authority identifier is Q7160134. Authority coordinates are 55.651, -3.193. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1911.

Critical limits

Modern boundaries and familiar names can conceal earlier jurisdictions or structures that do not align with the present site. 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

Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.

Best used for
  • Historic place names
  • Jurisdictional context
  • Routes into maps and plans
Verify next

Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.

Three-step research path

  1. Establish the record: confirm the title “Peebles Castle”, its source revision and the description used here.
  2. Expand the search: follow Peebles Castle primary sources, Peebles Castle archive and Peebles research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Peebles Castle”?
  2. Which authority defined the place, boundary or structure at the relevant date?
  3. What physical evidence or contemporary plan supports the description?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “Peebles Castle” 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.