The Case of the Kentucky Tax Lists: When AI Meets 19th Century Records

Or: What happens when a genealogist turns artificial intelligence loose on 200-year-old tax data

Every family historian knows the thrill of discovery—that moment when scattered pieces of evidence suddenly click into place, revealing relationships that were hidden in plain sight. Recently, I decided to enlist some high-tech help in solving a genealogical puzzle that had been nagging at me: the Wright family’s settlement patterns in Wayne County, Kentucky, from 1802 to 1813.

My 6th great-grandfather Amos Wright lived in Wayne County during those crucial early years before heading off to Washington County, Indiana around 1808. But Amos wasn’t alone—the tax records showed multiple Wrights scattered across the county’s creeks and hollers. Were they related? How were they connected? And could artificial intelligence help me see patterns I’d missed?

Inspired by a podcast episode about using AI to analyze tax data, I decided to conduct my own experiment. What followed was part genealogical investigation, part technology test drive, and entirely fascinating.

Setting the Stage: Garbage In, Garbage Out

Before I could turn my AI assistants loose on the data, I had to confront every genealogist’s nemesis: inconsistent 19th-century spelling. Standard genealogical practice in transcribing is to write it exactly as it is in the document you are viewing. However, the minefield of variants—”Right” versus “Wright,” “Amos” versus “Amus”— if left as is in my spreadsheet— would likely confuse any algorithm into thinking we were dealing with entirely different people.

So, cleanup — on a copy of my originally transcription — was my first task. Each variant had to be standardized, each waterway name corrected. After all, what good is artificial intelligence if you’re feeding it artificial confusion?

Round One: ChatGPT Takes the Stand

Armed with my cleaned dataset, I posed my first question to ChatGPT: “Taking into consideration the columns ‘Person Chargeable w/ Tax’, ‘Water Course’, ‘Name Entered’ and ‘Name Surveyed’, suggest possible relationships between the various taxpayers.”

ChatGPT approached the problem like a seasoned detective, immediately zeroing in on geographic clustering:

The Beaver Creek Connection: The AI noted that Amos Wright, Evan Wright, and Philip Copple all had land along Beaver Creek, suggesting they were neighbors—or possibly kin. This observation proved remarkably astute, as I knew from my research that Amos and Evan were indeed brothers, and Philip Copple had married one of Amos’s daughters.

The Henry Biggs Mystery: ChatGPT flagged Henry Biggs as a recurring figure whose name appeared in both the “Name Entered” and “Name Surveyed” columns for multiple Wright properties. The AI theorized that Biggs was either a surveyor or someone whose land abutted Wright holdings—a hypothesis I hadn’t fully explored.

The Surveyor Theory: Most intriguingly, ChatGPT suggested that Amos Wright himself might have been active as a surveyor, noting his name appeared in surveying columns. This painted a picture of Amos as a community leader—a “patriarch,” as the AI put it.

But here’s where it got interesting: ChatGPT completely ignored William Wright, Elijah Wright, John Wright, and Isaac Wright in its initial analysis. When an AI overlooks data, it’s worth asking why.

The Plot Thickens: New Evidence Emerges

Suspecting I’d missed some entries, I went back to the original tax records. Sure enough, I’d overlooked Samuel Wright, Moses Wright, and Jesse Wright. After adding these men to my dataset, I decided to test something: would ChatGPT give me the same answers with the expanded data?

The answer was no—and that’s when this investigation took an unexpected turn.

Day Two: The Same Question, Different Answers

Using identical prompts with the revised dataset, ChatGPT offered notably different conclusions. Instead of focusing solely on Beaver Creek clustering, it now suggested:

  • Chronological Settlement Patterns: William Wright at Elks Spring, Amos at Beaver Creek, Jesse at Meadow Creek might represent an “order of settlement”
  • Land Transfer Networks: The appearance of names like Stacter and Biggs as “predecessor patentees” suggested the Wrights were systematically acquiring nearby tracts
  • Three Wright Lines: The AI now theorized three different Wright family lines establishing themselves simultaneously in Wayne County around 1802

This inconsistency raised a red flag. If AI is supposed to be deterministic, why were my answers changing? It reminded me that these tools, powerful as they are, aren’t infallible oracles—they’re sophisticated pattern-matching systems that can be influenced by data variations.

Revealing the Facts: Guided Analysis

At this point, I decided to level the playing field. I fed both ChatGPT and Claude AI the facts I’d uncovered through traditional research:

  • William, Evan, and Amos Wright were brothers
  • Philip Copple was Amos Wright’s son-in-law
  • There were two different John Wrights in the records
  • Elks Spring was a tributary of Beaver Creek
  • Biggs and Stacter might have been county surveyors

With these revelations, both AIs refined their analyses significantly. ChatGPT now correctly identified the geographic relationships (William and Amos as neighbors along the same creek system) and properly distinguished between professional relationships (surveyors) and family ties.

Claude AI Enters the Investigation

When I presented the same data to Claude AI, it took a somewhat different approach. Where ChatGPT had been expansive in its theorizing, Claude was more cautious—but it also made some notable errors.

Claude correctly identified the surveyor relationships and community connections, but missed the marriage connection between Philip Copple and the Wright family entirely. More concerning, it made what appeared to be a complete fabrication, claiming that “Jesse’s land is often ‘Name Entered’ or ‘Name Surveyed’ under William Wright’s entries”—something that simply wasn’t in the data.

This reminded me of a crucial lesson: AI can hallucinate connections that don’t exist, just as easily as it can miss ones that do.

The Smoking Gun: Details Only Humans Notice

One detail that only Claude mentioned caught my attention: Evan Wright consistently appeared in the “Blacks” column of the tax records, indicating he was a slaveholder. This wasn’t a relationship pattern—it was a social and economic marker that added crucial context to understanding the Wright family’s standing in Wayne County society.

What the Evidence Reveals

After running this comparative analysis, several patterns emerged that neither AI fully captured on its own:

Geographic Clustering: The Wright brothers clearly settled along connected waterways, with William at Elks Spring (a tributary of Beaver Creek) and Amos directly on Beaver Creek itself. This wasn’t coincidence—it was family strategy.

Professional Networks: The recurring appearance of Henry Biggs and Samuel Stacter in survey records likely reflects their roles as county officials rather than family relationships, though neighboring land ownership remains possible.

Generational Succession: The appearance of younger Wrights (Elijah in 1809, likely William’s son coming of age) demonstrates how tax records can reveal family demographics over time.

Separate Wright Lines: Jesse Wright’s consistent association with Meadow Creek and different survey patterns suggest he represented a distinct Wright family line—not necessarily related to Amos, William, and Evan despite sharing the surname.

The Verdict: AI as Research Assistant, Not Replacement

So what’s the takeaway from this technological experiment? AI proved remarkably useful for pattern recognition and hypothesis generation, but it also demonstrated significant limitations:

Strengths:

  • Excellent at identifying geographic and temporal clustering
  • Good at spotting recurring names and potential professional relationships
  • Capable of generating testable hypotheses about family structures

Weaknesses:

  • Inconsistent results with identical queries
  • Tendency to hallucinate connections not present in the data
  • Missed obvious relationship indicators (like known family connections)
  • Limited ability to distinguish between different types of relationships

The Human Element

Perhaps most importantly, this experiment reinforced why traditional genealogical research remains irreplaceable. The AI’s most accurate insights came only after I provided the human context—the family relationships I’d painstakingly documented through other sources.

Without that foundation, the AI was essentially reading tea leaves, finding patterns that may or may not reflect historical reality. With it, the technology became a powerful tool for exploring implications and connections I might have missed.

A Final Twist: The Copyright Question

One unexpected discovery emerged during this process: ChatGPT had apparently trained on some of my own blog posts, citing them as sources without my explicit permission. This raises intriguing questions about how AI systems acquire their knowledge—and reminds us that the information we freely share online may someday be reflected back to us in unexpected ways.

Closing the Case

The Wright family tax records of Wayne County, Kentucky tell a story of strategic settlement, family networks, and community building in the early American frontier. AI helped illuminate some of these patterns, but only human knowledge could properly interpret them.

For fellow genealogists considering similar experiments, my advice is this: use AI as you would any other research tool—with curiosity, skepticism, and the understanding that technology amplifies both our insights and our errors. The algorithms can spot patterns we miss, but they can’t replace the detective work, critical thinking, and contextual knowledge that make family history come alive.

After all, behind every tax record entry was a real person making real decisions about where to live, whom to marry, and how to build a life on the Kentucky frontier. No algorithm, however sophisticated, can fully capture that human story—but it might just help us see new chapters we hadn’t noticed before.

What patterns have you discovered in your own family’s records? Have you experimented with AI in your genealogical research? I’d love to hear about your experiences—and any Wright or Copple connections you might have uncovered along the way.

“AI Detective: Wayne County Tax Records,” Claude Sonnet 4, chat initiated by user Cathy Dempsey, Claude (https://claude.ai/chat/818f967f-d918-42f2-9293-873902f1cdf9 : accessed 28 August 2025)

G is for Guernsey County, Ohio

Back to my “Family History from A to Z” series…

I’ve picked up my genealogy work after several years of sidelining it. I signed up for a SLIG 2025 (virtual) class on advanced methodology to be held in January, a second SLIG virtual class on writing to take place in February and March (weekly). Finally, most recently the Research Like a Pro e-course taught by the ladies at FamilyLocket.com after I first read their books at the library, and then bought the Kindle versions.

For the e-course, I am writing up research on my finding the father of my 3G grandmother Hannah (Hill) Englehart. I actually did the research years ago, came up with a father candidate, and that candidate (Andrew Hill) was ultimately validated via DNA. But I have only a research log, some scraps of notes, and skeletal citations, so I decided this would be a good project for this class to get me back in gear.

And one of the steps I’ve taken in the e-course — and part of the Research Like a Pro process — is to create a locality guide for my main research area. Because my 3G grandmother Hannah (Hill) Englehart was married in Guernsey County, Ohio (and apparently grew up there), I created a locality guide for that county. Additions to it are ongoing but what I have is below.

Guernsey County, Ohio Locality Guide

Prepared for Identifying the father of Hannah Hill Research Project by Cathy Dempsey; created 18 October 2024 (from a template created by familylocket.com

Background

Quick Facts

  • County Seat: Cambridge
  • Named for the Isle of Guernsey in English Channel, as many original settlers came from Guernsey
  • Formed 10 March 1810, from portions of Muskingum and Belmont counties
  • Ohio became a state on March 1, 1803, and was formed from part of the Northwest Territory (which was formed in 1787).
  • Countywide marriage and court records began in 1810, birth and death in 1867
  • Statewide birth and death records began in 1908
  • Ohio is a State Land State

Online Research Guides

Guernsey County, Ohio  – Family Search wiki

Guernsey County, Ohio: Family History & Genealogy, Census, Birth, Marriage, Death Vital Records & More – Linkpendium

Guernsey County Genealogy Guide – Random Acts of Genealogical Kindness

Guernsey_County,_Ohio (Wikipedia)  – Wikipedia

Archive Grid  ArchiveGrid is a collection of millions of archival material descriptions, including MARC records from WorldCat and finding aids harvested from the web.  

Geography and Maps

In 1851, lost Buffalo, Beaver, Olive and Seneca townships in the creation of Noble County to the south of Guernsey.

Neighboring Counties:  Coshocton (northwest), Tuscarawas (north), Harrison (northeast), Belmont (east), Noble (south), Muskingum (southwest/west)

Maps and Gazetteers:

Timeline of Major Events

Timeline of the area including major government changes and events

Ohio: Individual County Chronologies Newberry Library, 2007

The Historical Development of Guernsey County and Its Townships  Anderson, Scott C. R.  (USGennet.org)

History

History of settlement, links to history articles and books about the locality, major periods, military engagements,

Migration Routes

Describe main migration routes through your locality and link to maps and articles about the subject.

Principal Routes of Trade and Migration, 1840–1850  (accessed 18 October 2024)

https://www.familysearch.org/en/wiki/United_States_Internal_Migration (access 18 Oct 2024)

Law and Government

Old books that have been digitized (via Google Books, Internet Archive, Geneanet, etc.) that contain the laws and statues of the particular locality that you are researching; blog posts and articles about laws in your locality (check out the Legal Genealogist blog and library websites)

Libraries and Archives

Guernsey County
Administration Building
801 E. Wheeling Avenue
Cambridge, Ohio 43725-2335
Phone: 740-432-9230
Guernsey County Website

Guernsey County District Public Library 63500 Byesville Road
Cambridge, OH 43725

The Digital Archives of Guernsey Memorial Library

The Samuel D. Isaly Library  Bellville, Ohio [library of the OGS]

Ohio History Connection Archives & Library  Columbus, Ohio  [formerly Ohio Historical Society]

National Archives at Chicago    Serves Illinois, Indiana, Michigan, Minnesota, Ohio, and Wisconsin. 

Ohio State Archives

Genealogical Societies and Publications

Guernsey County Genealogical Society [Guernsey County Chapter of OGS]  Cambridge, Ohio

Ohio Genealogical Society   Bellville, Ohio

Record Loss

No known record loss.

Local History

Guernsey County History Museum Flickr Account: People  Guernsey County Historical Society

Guernsey County History Museum Flickr Account: Township Plats  Guernsey County Historical Society  (The images in this album are derived from a plat scan made available to the public by the Library of Congress)

Sarchet, Cyrus P.B.; History of Guernsey County, Ohio, (Indianapolis, Indiana: B.F. Bowen and Co., 1911). Volume 1 online at FamilySearch Digital LibraryInternet Archive; Volume 2 online at FamilySearch Digital LibraryGoogle Books

Wolfe, William G.; Stories of Guernsey County, Ohio: History of an Average Ohio County, (Cambridge, Ohio: W.G. Wolfe, 1943). Online at FamilySearch Digital Library

Reference Books

Additional books pertaining to research in this locality.

Record Collections

General Collections

Ancestry.com, FamilySearch.org, MyHeritage.com, FindMyPast.com etc. catalog titles about the locality

United States Record Finder on familysearch.org

Bible Records and Compiled Genealogies

Links to websites that have Bible records for the locality

Ohio Bible Records on familysearch.org

Cemetery Records

Links to cemetery records in the locality

Census Records and Substitutes

Links to different types of censuses: federal, state, town, colonial, territorial, census substitutes, etc.

United States Federal Census 1820 > Ohio > Guernsey

United States Federal Census 1830

Church Records

List the various denominations and where their records are kept.

Ohio Church Records — a general information page on familysearch.org

Determining the Church Your Ancestor Attended familysearch.org

Ohio, Church and Civil Births and Baptisms, 1765-1947  familysearch.org

Court Records

Links to court record collections and descriptions of what they contain

Guernsey County Clerk of Courts: Location of Court Records (Case Files, Docket appearances, etc.) PDF  — Guernsey County Clerk of Courts

Guernsey County Clerk of Courts homepage

Court records, 1810-1862 [Court of Common Pleas]  familysearch.org

Court records, 1811-1856 [Ohio Supreme Court]  familysearch.org

Ohio, Guernsey County, Common Pleas Journal and appearance dockets  [1829 – 1990] familysearch.org

Ohio, Guernsey County, Common Pleas Journal and appearance dockets, 1810-1938 at familysearch.org

Ethnic Records

List the various ethnic groups in the locality and what unique record collections are available about them.

Immigration and Naturalization

Describe immigration in the locality and link to the associated record collections.

Land Records

Land records were kept as of 1802

Ohio Land and Property  familysearch.org wiki

The Official Ohio Lands Book (pdf format)  Knepper, George W., pub. By Ohio State Auditor Office, 2002

The Northwest and the Ordinances, 1783-1858  Library of Congress (summarized history)

Land Ordinance of 1785  wikipedia.org

Northwest Ordinance of 1787  wikipedia.org

Guernsey County Recorder  – has land records

Deed records, 1810-1901; index, 1802-1968   familysearch.org

Guernsey County Township Maps  

Legislative Records

Link to collections about legislative records, if applicable, i.e. Virginia’s legislative petitions.

Military Records

Colonial, militia, war, regimental histories, etc.

Newspapers and Directories

Link to websites which contain digitized newspapers for your locality or how to find them if they aren’t digitized.

UF Digital Collections: Guernsey County (Ohio) Newspapers [early 20th century only]

The Digital Archives of Guernsey Memorial Library   OCR text is poor, with no option to fix as with CDNC. However, clicking on the link available allows you to see a digitized mage of the page.

Ohio Newspaper Archives 1795-2021  genealogybank.com

Probate Records

Link to record collections about will administration, probate, etc.

Probate records began to be kept as of 1812.

Ohio Probate Records, 1789-1996  familysearch.org    “Probate records and estate files from county courthouses in Ohio. The content and time period varies by county.”

Administration and execution dockets, 1812-1992  Probate Court (Guernsey County) on familysearch.org

Vital Records (Birth, Marriage, Death)

List the start of registration for birth, marriage, and death records. List any Gretna greens.

Birth and death records kept at the county-level as of 1867.  Marriage records kept as of 1810.

Birth records v. 1-3, 1867-1909, 1941-1963 Guernsey County Probate Judge; familysearch.org

Marriage records, 1810-1951, 1992-1997; index to marriages, ca. 1810-1930 Guernsey County Probate Court; familysearch.org

Death records, 1867-1960 Guernsey County Probate Judge; familysearch.org

Tax Records

Link to tax record collections, personal property tax, land tax, etc.

Guernsey County, OH Tax Duplicates 1816-1832  Guernsey County, Ohio Auditor. Familysearch.org

MyHeritage Amazing Time-Machine is now launched

MyHeritage has launched a new photograph feature on their website. To borrow a sentence straight from their announcement email, “With the AI Time Machine™, you can see yourself as an Egyptian pharaoh, a medieval knight or a Viking, a 19th-century lord or lady, and much more, in just a few clicks! “

MyHeritage suggests uploading some close-ups, some upper body shots, some profile shots and some full-body poses. So, what are the photo results like? I did two rounds — one using photos taken within the last year where I was fairly careless with my choices (resulting in themed images with a noticeable frown), and then a second round in which I took care to use more flattering photos of my (younger) self.

One of my faves is this image. Apparently, I was born to wear a crown 🙂

Or maybe I should have been a cowgirl?

Both of these AI images I find fairly flattering but they’re clearly airbrushed, my eyes appear gray rather than blue, and my mouth is not true-to-life. But it’s all in fun, right?

Punk Rocker Me and 16th Century Royalty Me look sufficiently like the real me, but Greek Goddess Me doesn’t look like me at all! Still, a cool picture. Perhaps I’ll use that as my Facebook profile pic.

Some other themes are below. There are some glitches with the AI — the head is cut off in many of the “1950’s Illustrated” theme. The mouth and teeth in “1970s Hair” don’t match reality. “18th Century France” and “Ottoman Empire” themes, at least for the photos I used, were two of the least realistic, IMO.

I’m including the “Race Car” theme below. You can go modern with that theme (as well as “Astronaut” and “Futuristic Cyborg”).

Later on, I did a second round of photos, this time choosing photos that were about 15 years old and uploading almost 30 photos total. (Suggested is 10 – 25.) Although the themes are the same, the AI results you get will be completely different.

These themes are Saxon, Cowgirl, Viking (I look startlingly like my mother in that photo — not that she goes around with horns on her head — but I do get my Danish heritage from her side), 1970s flower child, 18th century bride and punk rocker.

The funniest picture I got was this one — the 3-armed (!) Saxon warrior with the slit skirt up to her navel. In general, it seems the AI struggles with realistic hands and fingers — in one photo I have 7 fingers, and in several other photos I have 3 arms. (Of course that might be due to my own photo selection.)

Both of the image sets below belong to the Saxon theme. There is a painterly quality to the images, and a few where my head is cut-off.

Below are the themes 1950s Chic. They look like me, but also look painted. Then, Roman — which looked unrealistic. The AI struggles with a human-looking face for the full-body photos, probably because the full body photos I uploaded have relatively small facial features to go by.

The other themes are 1920s Black & White, and finally Baroque which looks least like me of all the themes. (In this set of images, anyway. The second go-round was better.) I suspect that the miss on the similarity is due to the Baroque theme using waist-up “portraits” and again, there’s not enough clarity on the facial features.

Finally, a last few more — from Celtic, Shaman and Punk Rocker themes.

This was fun, like dressing up in costume — and in some cases looking like my ancestors might have looked. MyHeritage has a FAQ, sample photos, and a how-to video on their site if you want to try it!

AncestryDNA is now assigning a parental side to your matches

I’ll go one better than the parental split about your ethnicity… now it’s your matches. Well, for most people. (Sigh, not yet me, as you can see below!)

That said, I really can’t complain because all the accounts of DNA testers I manage already have the new parental split. (Perhaps it’s because I’ve got a really old account?) I digress… Mom has her split, and Dad has his. I’m super excited about Mom’s split, because she actually has several hundred paternal matches!! Her dad was born in the United States, but both his parents (and his eldest brother) were born in the Marche region of Italy.

Turns out Mom has hundreds of matches who have ancestors from Fano, Italy (where my Mom’s paternal grandfather was born). None match our known surnames — but we know so few anyway.

And with respect to Mom’s maternal matches, I’m psyched that so many were in line with what I had researched already. One thing I noticed, though, about her “unassigned” matches were that a fair number of them are clustered to her Hill/Geho line (from southwest Penn to Guernsey County, Ohio): her great-great grandmother’s parent’s line. I’m not entirely sure why Ancestry marked these matches as Unassigned, but pretty much the entire cluster of those matches is Unassigned so at least it’s consistent.

If you have done DNA testing at Ancestry, do you have the new feature on your account yet? And, if so, has it helped you?

(BTW — side note — I spoke with an Ancestry representative about a week or so ago; they said the rollout will be continuing for the next few months.)

AncestryDNA has a ethnicity-by-parent breakout now

I saw from following DNASleuth’s blog that Ancestry has a new ethnicity feature, wherein your received ethnicity is assigned to either Parent 1 or Parent 2. So, naturally, I had to check it out. Ethnicity estimates were also revised!

My dad formerly (as of last week) was listed at 100% Irish. He is no longer. Now he’s 90% Irish, with the remaining 10% being Scottish and Welsh. And, honestly, in the past, AncestryDNA has shown him with Scottish, Welsh, and even English ethnicities. It all depends on the calculation at the time, I guess.

All that said, I believe this estimate is quite in line with the paper genealogy, and the birthplaces of my great-grandparents. I have 4 Irish/Celtic great-grands, 2 Italian great-grands, 1 great-grandparent whose parents were born in and immigrated from southern Denmark, and one great-grandparent whose line in the U.S. extends back to early 1700s and is largely of German and English descent.

If you have taken a DNA test at Ancestry, do go check out the new info!

1950 U.S. Census — Volunteer Project at Familysearch.org

Today I spent about 2 hours validating that the computer-generated indexes already created — and not all 50 states are yet done — were accurate. I worked on Indiana, Oregon, and Arizona. Technology has come such a long way in the past 10 years; I am amazed at how accurate the indexed data appears already.

You can validate names in a given state, or, if the name validation is complete, you can validate family groups. And the cool thing is you can select names, so for the family groups I was validating (in Oregon and Arizona) I specifically searched for COPPLE households. (And recognized some of the names I already have in my COPPLE tree on Ancestry.com)

There is plenty to do for anyone interested, and you can do just a little bit or do a lot — any amount helps get the indexing done faster.

Copples in the News: Triplets born in Gilbert, Arizona

Back in the spring of 1935, three daughters were born to Mr. and Mrs. Jesse Ross Copple, who were Oklahoma natives living in Arizona at the time.

I believe this Jesse Ross was married to Mary Elvira Goins, and was kin to me through both my Copple and Wright lines. His 3rd great-grandparents were Jacob Peter Copple and Mary Elizabeth Garren (or Fouts). Their son Jacob Peter Copple married Elizabeth Wright, who was also kin to me, being the granddaughter of Richard and Ann [- ? -] Wright, my 7th great-grandparents.

The likely family tree of these triplets, my distant cousins, is below:

 

“Girl Triplets Born in Gilbert,” Arizona Republic (Phoenix, Arizona), 3 May 1935, p. 38, col 3; Newspapers.com (https://www.newspapers.com : accessed 25 Sept 2020).

 

Copples in the News: a new Copple Surname Group on Facebook!

I have recently created a Copple surname group on Facebook for persons interested in DNA, genealogy and researching their Copple kin. This private group is all about connecting with folks who have a Copple line in their family tree, and trying to tie DNA test results to that Copple branch. Variant spellings include Copple / Cople/ Cobble/ Cauble/ Capple / Gobble.

If your DNA/genealogy interests or your family tree branch includes Copple, please consider joining! You can check it out here.

.

4th Cousins on Ancestry.com: a quick study

 

Last week in the “Genetic Genealogy Tips & Techniques” group on Facebook, Blaine Bettinger posted a study of his own 4th-cousins-and-closer matches on Ancestry.com which can be viewed here.   I decided to do the same.  These are my results:

Cathy’s 4th cousin (and closer) matches on Ancestry.com

Matches which are included here are matches who, in general, share at least 20 cM of DNA with me (although I have some matches at the 20 cM level who are labeled as “distant” cousins).

The “Amt DNA” information does NOT come from Ancestry; it comes from having done a process called “chromosome mapping” or “visual phasing” and it required the DNA results from both my parents, as well as from my sibs, compared against that of my 1st and 2nd cousins who have tested. On my dad’s side, the amount shared skews towards my grandmother, in part because one of my X chromosomes comes from her and her alone.

The number of matches sharing >= 50 cM with me also skews towards my paternal grandmother because 2 of my dad’s 3 maternal 1st cousins have tested at Ancestry, as well as some of their children and grandchildren. All are no more distant than 2C1R to me. (Note: in that figure I do not include my dad, my sibling, or my paternal 1st cousins — since they share both paternal grandparents with me.)

However, in total numbers of matches, my two grandparents with “colonial” ancestry (and by that I mean roots in the U.S. at least as early as 1790 — but not necessarily as far back as, say, 1650), are the ones with the most matches. That seems to correlate with what I’ve heard from others who have tested at Ancestry. My paternal grandfather has one line — his maternal grandfather — that is “colonial”. My maternal grandmother has 2 lines — both of her maternal grandparents are “colonial”.

I compared the paternal and maternal labeling, but it doesn’t tell me much, in my opinion. Ancestry only labels the DNA match as paternal or maternal if the match is >= 20 cM for both parent and child. Where there are differences in the totals, it is due to the match being >= 20 cM for me, but not for my parent. That’s an artifact of the computer algorithms.

Finally, tree availability in and of itself may not be the be-all end-all for matches. 85% of the matches I identify as paternal unknowns — I cannot discern which grandparent they are kin to — have public trees. The trees have done nothing to help me figure out how that match is related to me! Any suggestions?

Copples in the News — Sam and Libby get married

This is the wedding notice of my great-great grandparents, Samuel Adams Englehart and Libby Copple (here listed as Libby Jewell). I posted about Sam here. He was 26 in December 1878 when he married Libby Jewell at the home of her adoptive mother, Mrs. Polly Esther (Keeler) (Jewell) (Fike) Rose.

Libby was 17 years old on her wedding day. She was born in Mendocino County, California in 1861 to Ben Franklin Copple and his wife Phoebe (Harvey) Copple, who died in childbirth or very soon after Libby was born. But that’s a story for another post.

“Married: Englehart-Jewell,” Healdsburg Enterprise (Healdsburg, California), 26 Dec 1878, pg 2, col 1; digital images, California Digital Newspaper Collection, (http://cdnc.ucr.edu : accessed 3 Sep 2020).