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

Trinity Episcopal Church (Columbus, Georgia)

church building in Columbus, United States of America

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 revisionSep 6, 2026
Entity authorityQ7842742 ↗
Source-derived summary

Trinity Episcopal Church is an Episcopal church located in Columbus, Georgia.

History

The church was founded in 1834 and was the fifth Episcopal church in the state of Georgia. The first church building was completed in 1837. The current building was built in 1890-91 and formally consecrated in 1892.

Editorial summary

Begin with the source’s own compact description: “Trinity Episcopal Church (Columbus, Georgia)” is church building in Columbus, United States of America. The dossier treats that line as a proposition to test through Trinity, Episcopal and Church, 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—1834, 1837, 1890, 1892—that can be checked directly. The selected authority fields contribute no independent date. For this dossier, Trinity, Episcopal and Church is the immediate research focus.
Editorial analysis

Why this record matters

The phrase “church building in Columbus, United States of America” 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 Sep 6, 2026. The linked authority identifier is Q7842742. The first chronological checks are 1834, 1837, 1890 and 1892.

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 “Trinity Episcopal Church (Columbus, Georgia)”, its source revision and the description used here.
  2. Expand the search: follow Trinity Episcopal Church (Columbus, Georgia) primary sources, Trinity Episcopal Church (Columbus, Georgia) archive and Trinity 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 “Trinity Episcopal Church (Columbus, Georgia)”?
  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 “Trinity Episcopal Church (Columbus, Georgia)” 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.