CACrown ArchivesThe cinema collection
Menu
Research dossier · Places & Architecture

Pirdeh, Tehran

village in Firuzkuh County, Tehran Province, Iran

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 revisionJul 3, 2026
Entity authorityQ5855623 ↗
Source-derived summary

Pirdeh (Persian: پيرده) is a village in Poshtkuh Rural District of the Central District in Firuzkuh County, Tehran province, Iran.

Demographics

Population

At the time of the 2006 National Census, the village's population was 272 in 59 households. The following census in 2011 counted 473 people in 149 households. The 2016 census measured the population of the village as 280 people in 94 households.

Editorial summary

Begin with the source’s own compact description: “Pirdeh, Tehran” is village in Firuzkuh County, Tehran Province, Iran. The dossier treats that line as a proposition to test through Pirdeh, Tehran and village, not as a finished interpretation.

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—2006, 2011, 2016—that can be checked directly. The selected authority fields contribute no independent date. For this dossier, Pirdeh, Tehran and village is the immediate research focus.
Editorial analysis

Why this record matters

The phrase “village in Firuzkuh County, Tehran Province, Iran” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.

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 Jul 3, 2026. The linked authority identifier is Q5855623. Authority coordinates are 35.663, 52.794. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2006, 2011 and 2016.

Critical limits

Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. 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 “Pirdeh, Tehran”, its source revision and the description used here.
  2. Expand the search: follow Pirdeh, Tehran primary sources, Pirdeh, Tehran archive and Pirdeh 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 “Pirdeh, Tehran”?
  2. Which earlier names or jurisdictions may reveal additional records?
  3. Which authority defined the place, boundary or structure at the relevant date?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “Pirdeh, Tehran” 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.