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)

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.

.

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).

Copples in the News – Pink Carnations for the bride

Lucile McDonald, a native of Collin County, Texas, married Earl Harold Copple in Kerr County, Texas (in what is known as the Texas Hill Country) on 17 February, 1941. She was 24 years old.

Her husband Earl was 32 years old and also a Texas native, being from Kimble County (adjacent to Kerr.) Earl was one of 10 children and the youngest son born to Virgil O. and Rosa (McDonald) Copple. Earl may be related to me twice over, as his paternal grandparents were cousins in some degree.

The bride was married in blue, with a corsage of pink carnations.

“McDonald-Copple Marriage Solemnized,” Kerrville Mountain Sun (Kerrville, Texas), 20 Feb 1941, pg 2, col 3; Newspapers.com (https://www.newspapers.com : accessed 21 June 2020).

Copples in the News – Beulah Copple marries Sam Long

Beulah Elaine Copple, daughter of Henry Ellis Copple and Julia (Williams) Copple was possibly my 4th cousin 4 times removed (a descendant of Nicholas Copple who died in 1808 in Rowan County, NC, and his wife).   

Beulah was born in 1892 in South Carolina, married Rev. Samuel Long in 1916, and had two sons.  She died at the age of 50.

The wedding notice ran to two columns, and was quite detailed about what the bridal party wore.  Here is only the first column. 

Beulah Copple m Sam Long

“Monroe [Beulah Copple marries Sam Long],” The News and Observer (Raleigh, North Carolina), 3 Sep 1916, pg 7, col 6; Newspapers.com (https://www.newspapers.com : accessed 31 August 2020).

Copples in the News – Claiborne Copple “smells a rat”

As best as I can determine, Claiborne Copple of Jackson County, Indiana — who, in this article is apparently suspicious of his wife’s fidelity — is a possible distant cousin of mine via his father David (1794 – 1835) and grandfather John (1768 – 1838).

Claiborne was born circa 1827 probably in Kentucky (but possibly in southern Indiana), likely one of at least 10 children.   He married Mary Holt, his first wife, in Clark County, Indiana in 1856, and resided in Clark County at the time of the 1860 census.  By 1863, though, when he signed up for the Civil War draft, he was in Jackson County, Indiana.  His wife died circa 1876, and he remarried to an Elizabeth King in 1877.  

He was found in the 1880 census in Jackson County, Indiana.  (As an aside, I have not found any information on when he died, nor have I found him on the 1850 and 1870 censuses.)  It is apparently wife #2 (Eliza) who was “in the company of James Cole”.

Claiborne Copple

“He Smelt a Mouse,” Jackson County Banner (Brownstown, Indiana), 2 Nov 1882, pg 5, col 4; Newspapers.com (https://www.newspapers.com : accessed 7 February 2020).

cathymd, “Copple/Wright Line – DNA Kinship — Working Data Tree”, Ancestry.com (https://www.ancestry.com/family-tree/person/tree/62591313/person/36185456378/facts : accessed 7 February 2020).

 

 

 

 

 

Copples in the News — Benjamin G Copple accused of attempted murder

In October 1924, a teen-aged Benjamin Garl Copple (c 1906-1986) was accused of attempted murder of a young woman and man, while he was under the influence of liquor. Ben was married at the time, to a Bernice Amott his “child bride”, who was only 15 at the time of the article in February 1925.  Ben had reportedly been working for the sheriff until the day before, under an assumed name (not given in the article) and an assumed age (22).  His father, A. M. Copple [Alpheus Marvin] testified on his behalf.

Ben Garl Copple was born sometime between 1903 and 1907 probably in Colorado to Alpheus Marvin Copple (1881 – 1944) and Lucinda Mary Whitlock (1884 – 1978), both natives of North Carolina.  The family was living in Las Animas County, Colorado in 1910, and in Salt Lake City in 1920.  

After the shooting incident in October 1924, Ben married Bernice Amott (who was with him on the day of the shooting, per the article below) on 26 January 1925.  The article states Bernice was filing for an annulment of the marriage and that must have gone through, as Ben married Edith Olga Shafer on 27 June 1925.

The 1930 census found Ben and Edith, with their daughter Joyce, in Salt Lake City, and Ben worked as a laborer.  In 1940, they were in the Los Angeles area, where Ben worked as a truck driver.

Benjamin Garl’s paternal grandfather shared the same name as my 3rd great grandfather: Benjamin Franklin Copple, but that Ben Copple lived his entire life in North Carolina.  Ben Franklin Copple’s parents were Henry and Frances “Franky” (Miller) Copple.  Henry’s parents are unknown; however Frances Miller’s father Isaac Miller lived in the vicinity with 3 Copple households in Davidson County, NC, which I’ve traced as my kin.  It is possible — but not certain — that Henry’s parents were Jacob Copple and Delilah Plummer.

If so, these Salt Lake City Copples are distant cousins to me.

Benjamin Garl Copple attempted murder

“Got Liquor as Undercover Man,” Salt Lake Telegram (Salt Lake City, Utah), 18 Feb 1925, pg 2, col 8; Newspapers.com (https://www.newspapers.com : accessed 13 January 2020).

 

 

 

 

 

Copples in the News – Glenn Copple appointed deputy DA

Glenn Copple (1888 – 1965) was appointed Deputy to Yuma County (Arizona) District Attorney Henry C. Kelly.

Glenn was born in Nov 1888 in Centralia, Illinois to Silas Bryan & Julia (Roper) Copple, who married in 1884.  He was their second son.  Silas Bryan Copple’s paternal great-grandparents were Jacob [Peter] Copple and [Mary] Elizabeth Garren [Pfoutz?], who are my 6th great-grandparents.

Glenn was in the military from Aug 1917 to July 1919, and after arriving home back in Centralia, was a lawyer.  He moved to Yuma, Arizona prior to January 1925, which is when he became the assistant District Attorney.

He married Janet Anne Burnell in 1934 in Phoenix, Maricopa County, and they had a son Gordon Burnell in April 1936 in Los Angeles County, California.  The family was back in Yuma County, Arizona as of the 1940 census.  Glenn died in Oct 1965, presumably in Arizona, but is buried in San Diego County, California.  His widow died in 1982, and his son Gordon died in 1987 at the age of 51.

Glenn was my 3rd cousin 4 times removed.

Glenn Copple Promoted to Asst DA

 

“Attorney Glen Copple is Named,” The Morning Sun (Yuma, Arizona), 2 Jan 1925, pg 1, col 6; Newspapers.com (https://www.newspapers.com : accessed 13 January 2020).