Sunday, April 5, 2026

Best of the Genea-Blogs - Week of 29 March to 4 April 2026

  Scores of genealogy and family history bloggers write hundreds of posts every week about their research, their families, and their interests. I appreciate each one of them and their efforts.


My criteria for "Best of ..." are pretty simple - I pick posts that advance knowledge about genealogy and family history, address current genealogy issues, provide personal family history, are funny or are poignant. I don't list posts destined for most daily blog prompts or meme submissions (but I do include summaries of them), or my own posts.

Here are my picks for great reads from the genealogy blogs for this past week:

*  Bringing Ancestors to Life (Again): Testing NotebookLM’s New Cinematic Video Overview Feature by Diane Henriks on Know Who Wears the Genes In Your Family.

*  Documents That Prove Family Relationships by Kenneth R. Marks on The Ancestor Hunt.

*  Genealogy Tips: Research Her in HIS Activities by Gena Philibert-Ortega on GenealogyBank Blog.

*  The New FamilyTreeDNA NGS Family Finder Test by Roberta Estes on DNAeXplained -- Genetic Genealogy.

*  Turn Anything into a GEDCOM File — With Any AI Tool and The Genealogical Research Assistant (GRA): Free for Every AI Platform by Steve Little on Vibe Genealogy.

*  Jonny’s RootsTech 2026 recap by Jonny Perl on DNA Painter Blog.

*  What Makes You Crazy About Genealogy? by DiAnn Iamarino Ohama on Fortify Your Family Tree.

* 5 Best AI Genealogy Research Prompts for Beginners: Finally, AI Genealogy Research That Doesn’t Feel Overwhelming by Thomas MacEntee on Genealogy Bargains.

*  A Visit to the Family Heritage Experience at American Ancestors  by Heather Wilkinson Rojo on Nutfield Genealogy.

*  Why AI Needs More Context: Lessons from a Mary Crawford Biography by Marcia Crawford P hilbrick on Heartland Genealogy.

*  What Your Census Records Are Actually Telling You (And What You’ve Been Missing) by Denyse Allen on Chronicle Makers.

*  DNA to Records, Triangulation to Documents by Nate Douglas on No Parents Listed.

*  A Visual Tagging System for DNA Matches by Jon Smith on Family Locket.

*  We Are Not Always Who We Think We Are: What Family History Teaches Us About Identity by Paul Chiddicks on Paul Chiddicks.

*  Modernizing Your Roots: Essential Tech Tips for the 21st-Century Genealogist by Carole McCulloch on Essential Genealogy.

*  A Calculated Guess Is Great by Jim Bartlett on Segment-ology.

Here are pick posts by other geneabloggers this week: 


*  Friday’s Family History Finds [3 April 2026] by Linda Stufflebean on Empty Branches on the Family Tree.
*  GenStack [4 April 2026] by Robin Stewart on Genealogy Matters.

Readers are encouraged to go to the blogs listed above and read their articles, and add the blogs to your Favorites, Feedly, another RSS feed, or email if you like what you read. Please make a comment to them also - all bloggers appreciate feedback on what they write.

Did I miss a great genealogy blog post? Tell me! I currently am reading posts from over 900 genealogy bloggers using Feedly, but I still miss quite a few it seems.


Read past Best of the Genea-Blogs posts here.

             ==========================================================

Copyright (c) 2026, Randall J. Seaver


Please comment on this post on the website by clicking the URL above and then the "Comments" link at the bottom of each post. Share it on X, Facebook, or Pinterest using the icons below. Or contact me by email at randy.seaver@gmail.com.  Please note that all comments are moderated and may not appear immediately.

Subscribe to receive a free daily email from Genea-Musings using www.Blogtrottr.com.

Using Steve Little's AI Genealogy Research Assistant V8.5.1c To Develop a Research Plan

 I wrote about Using Steve Little's Genealogy Research Assistant V8 to Develop a GPS Proof Summary on 25 February 2026, which used Version 8 of Steve Little's Genealogy Research Assistant tool.

Steve continues to improve and expand the Genealogy Research Assistant (GRA) tool -- see Steve's blog post The Genealogical Research Assistant (GRA): Free for Every AI Platform for the latest update. The custom prompt is available for several Artificial Intelligence platforms, including OpenAI ChatGPT, Anthropic Claude and Google Gemini (all with FREE and PAID access).

1)  I chose to use OpenAI ChatGPT. The Genealogy Research Assistant V8.5.1c prompt is at   https://chatgpt.com/g/g-69701d25d61c819192c2db4589b366d9-genealogical-research-assistant.

I wanted to ask the GRA to provide a research plan for finding the maiden name, birth date and place, and parents' names of my 5th great-grandmother Jerusha --?-- who married Burgess Metcalf in about 1769, probably in Keene, New Hampshire. I provided limited data about her (I don't have much more!) in my prompt:

"I can't find any records for my 5th great-grandmother Jerusha --?-- who married Burgess Metcalf in about 1769 in Keene NH and had 10 children. The family moved to Piermont NH in 1773 and lived out their lives there. Please provide a research plan for me to find Jerusha's maiden name, birth date and place, and parents names."


2)  Here is the Research Plan guidance that GRA V8.5.1c provided:

You’re dealing with a classic 18th-century “elusive wife” problem—and your instincts are right: this will require indirect evidence, cluster research, and careful correlation.

What the evidence currently supports (baseline)

From compiled and authored materials:

  • Jerusha (—?—) married Burgess Metcalf before about 1770, probably in Keene, New Hampshire (Genea-Musings)

  • She was born about 1750 and died 9 June 1817 in Piermont, NH (Genea-Musings)

    Her maiden name, parents, and birthplace are unknown in current research (Genea-Musings)

  • A proposed maiden name “Chandler” lacks supporting records and may derive from a child’s given name (Genea-Musings)

Evidence assessment

  • These statements come from authored sources (compiled genealogies/blogs citing earlier works).

  • Information about Jerusha is largely indeterminate (informants unknown).

  • Evidence for her identity is indirect at best.

👉 Conclusion: Your research question is complex (identity + parentage pre-1800) → requires a broad, multi-source strategy.


GPS Research Plan

OBJECTIVE

Identify Jerusha (—?—):

  • Maiden name

  • Birth date and place

  • Parents

SUBJECT

Jerusha (—?—), wife of Burgess Metcalf, lived Keene → Piermont, NH (ca. 1769–1817)

KNOWN FACTS (to anchor research)

  • Married by ~1770 (likely Keene)

  • First child ~1770

  • Lived Piermont from 1773 onward

  • Died 1817 in Piermont

  • Had 10+ children

WORKING HYPOTHESIS

Jerusha was:

  • From Keene or nearby Cheshire County, OR

  • From a family migrating with/near the Metcalfs, OR

  • Connected to a Piermont associate (land, church, or neighbors)


SOURCES TO SEARCH (Prioritized)

Priority

Source Type

Repository

Rationale

Status

1

Church records (CHR)

Keene & early Piermont Congregational

Pre-vital era marriages often only here

Key

2

Town records (VIT/OTH)

Piermont Town Records (1765–1825)

Early entries may mention wife or origins

Key

3

Land records (LND)

Grafton County deeds

Wives often named; possible relatives nearby

Key

4

Probate (PRO)

Cheshire & Grafton counties

Identify potential fathers naming “Jerusha Metcalf”

Key

5

Marriage clusters (CHR/VIT)

Keene & nearby towns

Identify all Jerusha marriages 1765–1775

Key

6

Baptisms of children (CHR)

Piermont/Keene churches

Sponsors/witnesses may be relatives

High

7

Revolutionary War records (MIL)

Burgess Metcalf file

Pensions sometimes mention wives/family

Medium

8

Local histories (AUTHORED)

County/town histories

Clues to intermarrying families

Medium

9

Tax lists & early censuses (OTH/CEN)

Piermont

Identify neighbors (FAN cluster)

Medium

10

Cemetery records (OTH)

Piermont burial grounds

Check for adjacent family plots

Medium


FAN CLUSTER (Critical for this case)

Person/Group

Relationship

Records to Check

Chandler families in Piermont

Possible connection (name clue)

Land, probate, church

Jenness (land seller)

Associate

Deeds, neighbors

Early Piermont settlers

Neighbors

Tax lists, church

Children’s spouses’ families

In-laws

Marriage witnesses

Metcalf siblings

Family

Shared migration patterns


STRATEGIC APPROACH (What will actually break this case)

1. Reconstruct ALL early Piermont families (1760s–1780s)

This is essential.

Why:

  • Jerusha likely came with or near them

  • Women’s identities often surface only through cluster context

👉 Build a mini-community study, not just one person.


2. Land records (HIGH VALUE)

Focus on:

  • 1773 purchase (Burgess Metcalf)

  • Adjacent landowners

  • Later deeds (look for wife’s release of dower)

Why it matters:

  • Wife may be named explicitly

  • Neighbors may be relatives


3. Church records (highest probability source)

Search for:

  • Marriage entry (~1768–1772)

  • Baptisms of early children (especially first 2–3)

Key clues:

  • Witnesses

  • Membership transfers (“dismissed from Keene church”)


4. Probate “reverse search”

Instead of searching for Jerusha—search for:

Men who died in Cheshire/Grafton counties (1770–1820)
who named a daughter “Jerusha Metcalf”

This is often the breakthrough method.


5. Analyze children’s naming patterns (with caution)

Children include:

  • Meletiah (husband’s mother)

  • Chandler (possible clue)

  • Jerusha (self-naming pattern)

⚠️ Interpretation:

  • “Chandler” could reflect maiden name—but currently unsupported evidence

Treat as:

  • Indirect evidence hypothesis, not fact


6. Map migration chain

Metcalf family moved:

  • Massachusetts → Keene (~1750) → Piermont (1773)

👉 Investigate:

  • Families making the same move sequence

  • Especially daughters named Jerusha (born ~1745–1755)


7. Same-name analysis (critical)

You must identify:

  • All Jerusha (unknown surname) in:

    • Keene

    • Nearby towns (Westmoreland, Swanzey, Walpole)

Then:

  • Eliminate those who married other men

  • Track those who disappear (possible Jerusha Metcalf)


SUCCESS CRITERIA

You will have a credible conclusion when you find:

  • A record naming:

    • “Jerusha [surname], wife of Burgess Metcalf” (Direct evidence), OR

  • A correlated cluster showing:

    • Jerusha linked to a specific family via land, probate, or church (Indirect evidence strong enough for a proof argument)


Reality Check (GPS honesty)

At present:

  • Evidence for her maiden name = Not Proved

  • “Chandler” hypothesis = Possible but unsupported

  • Identity resolution will likely require a proof argument, not a simple record


If you want next step help

I can help you:

  • Build a Piermont FAN cluster reconstruction

  • Create a targeted probate search list

  • Or analyze any document you already have

This is exactly the kind of case where a structured, GPS approach pays off—but it’s also one that typically requires assembling indirect evidence across many records rather than finding a single answer.

======================================

3)  Note that the GRA tool searched the Internet for information, and found my blog post from 2008 (The Elusive Jerusha --?-- (1750?-1817, who married Burgess Metcalf)).  However, it did not quote my blog post from 2017 (52 Ancestors - Week 158: #223 Jerusha (--?--) Metcalf (1750-1817) of New Hampshire), which has a bit more information.

You can see the logical layout of the Genealogy Research Assistant in the ChatGPT5 text above.  

4)  The research plan seems very comprehensive, and I will try to follow it as best I can. I have looked for Keene and Piermont, New Hampshire colonial records in the past without much success.  The Keene vital records for the period are restricted in the FamilySearch Catalog, so I need a FamilySearch Center visit.

5)  I will try some of the other GRA Verson 8.5.1c research and analysis opportunities also.

6)  Please read ALL of Steve's recent blog post and try out the Genealogy Research Assistant tool!

==============================================

Links to my blog posts about using Artificial Intelligence are on my Randy's AI and Genealogy page. Links to AI information and articles about Artificial Intelligence in Genealogy by other genealogists are on my AI and Genealogy Compendium page.


Copyright (c) 2026, Randall J. Seaver

Please comment on this post on the website by clicking the URL above and then the "Comments" link at the bottom of each post.  Share it on Twitter, Facebook, or Pinterest using the icons below.  Or contact me by email at randy.seaver@gmail.com. Note that all comments are moderated, and may not appear immediately.

Subscribe to receive a free daily email from Genea-Musings using www.Blogtrottr.com.

Betty and Fred's Story: September to Mid-October 1943

 The AI-assisted ABC Biography of my mother, Betty Virginia (Carringer) Seaver, is in ABC Biography of #3 Betty Virginia (Carringer) Seaver (1919-2002) of San Diego, California. I also  wrote Betty's Story: The First-Year Art Teacher about the start of her teaching career.

The AI-assisted ABC Biography of my father, Frederick Walton Seaver, is in ABC Biography of #2 Frederick Walton Seaver Jr. (1911-1983) of Massachusetts and San Diego, California.  I also wrote Fred's Story: The Three-Day Cross-Country Escape  and Fred's Story: "I Need A Girl" about him coming to San Diego, and wanting for a girlfriend.

Then I wrote 21 more chapters of their life together (listed at the end of this post).

And now we are up to September and October 1943 and they are still waiting for the birth of their baby: 


                  (AI NotebookLM Infographic - Betty and Fred's Story - September to mid-October 1943)

1)  Based on the biographies and the earlier stories, I asked Anthropic Claude Sonnet 4.5 to tell another story - what happened next (I offered some suggestions!)?  Here is the next story (edited for more detail and accuracy):


Building a Family Together:  September To 

Mid-October 1943

Early September 1943 - Work and War

Fred's work at Rohr continued to be demanding, even as Betty stayed home preparing for the baby. The production targets kept increasing—the B-24 Liberator was proving crucial in the European air campaign, and every aircraft needed the parts Rohr produced.

Fred came home exhausted every night, often having worked ten or twelve hours. His team had stabilized at fourteen people after hiring two more workers, but the turnover was constant. Someone would work for a few weeks, then quit or get drafted or move to a better-paying job at another defense plant.

"I'm training people constantly," Fred told Betty over dinner one night. "As soon as someone gets competent, they leave and I have to start over with someone new."

"Can you hire more experienced people?"

"Everyone with experience is already employed. We're hiring whoever we can find—older men, teenagers, women who've never worked in manufacturing before. And I'm supposed to turn them into qualified material controllers in a matter of weeks."

The war news was mixed. Allied forces had invaded Sicily in July and were pushing north through Italy. But the Pacific war seemed endless—island after island, each one paid for in blood. The casualty lists kept growing.

Fred's draft classification remained 1-A, but expectant fathers received temporary deferments. Once the baby was born, he'd have a few months of safety, but after that, he could be called up at any time.

They didn't talk about it often—the possibility that Fred might be drafted, might be sent overseas, might not come back. But it hung over them constantly, a shadow they couldn't escape.

"Let's just focus on now," Betty said when the worry became too much. "You're here now. The baby's coming soon. We have each other now. That's what matters."

"You're right. We can't live in fear of what might happen."

But late at night, Betty would wake to find Fred staring at the ceiling, clearly unable to sleep, clearly thinking about the future and all its uncertainties.

Mid-September 1943 - Shopping for Fred's Birthday

Fred's thirty-second birthday was October 15th—the same day their baby was due. Betty was now eight months pregnant, enormous and uncomfortable, but determined to find Fred a good birthday present.

"I'm going shopping with Sally," she announced one Saturday morning.

"You can barely walk. Let me come with you."

"No. It's for your birthday. You can't be there when I buy it."

Sally drove Betty to downtown Chula Vista, walking slowly through the shops. Everything was difficult now—her feet hurt constantly, her back ached, she had to stop frequently to rest. But she was determined.

She found what she was looking for in a men's clothing store—a beautiful leather briefcase, professional and well-made. Fred's current bag for carrying work documents was falling apart, and she knew he'd appreciate something nice.

The clerk wrapped it carefully, and Betty struggled back to the car, feeling the baby shift and kick in protest at all the movement.

At home, she hid the briefcase in the back of the linen closet, where Fred would never look. Then she collapsed on the sofa, exhausted from the simple shopping trip.

"How did it go?" Fred asked when he came in from the garden.

"Fine. I found something perfect. But you're not getting any other hints."

"We're not doing anything elaborate for my birthday, right? You'll be nine months pregnant. We're not going out to dinner or having a party."

"Probably not. Though we might have the baby on your birthday. Dr. McCausland said the due date is October 15th."

"Wouldn't that be something? My birthday and the baby's birthday on the same day."

"Let's hope not. I'd like you to be able to have your own special day without competing with our child."

Late September 1943 - Final Doctor's Appointments

Betty had been seeing Dr. McCausland monthly throughout her pregnancy, but in September, the appointments became more frequent—every two weeks, then weekly as October approached.

At the late September appointment, Dr. McCausland did a thorough examination.

"Everything looks good, Mrs. Seaver. The baby is in the right position, your blood pressure is normal, you're healthy. I'd estimate you're carrying a good-sized baby—probably seven to eight pounds."

"Where will I have the baby?" Betty asked. She'd been meaning to ask this question for weeks but kept forgetting.

"Paradise Valley Sanitarium in National City. It's the closest hospital to you, and they have an excellent maternity ward. I have privileges there, so I'll be able to attend the delivery."

"A sanitarium? That sounds like a mental hospital."

Dr. McCausland laughed. "I know the name is old-fashioned. It used to be a tuberculosis sanitarium back in the 1920s, but it's been a regular hospital for years now. They just never changed the name. It's perfectly respectable, I promise."

"What do I need to bring?"

"A suitcase with nightgowns, toiletries, and clothes for going home. We'll keep you for about five days after the delivery, assuming no complications. And your husband should be prepared to drive you there quickly when labor starts."

Fred, who'd accompanied Betty to this appointment, nodded seriously. "I'll make sure the car is always ready. Keep the gas tank full, check the tires, have a route planned."

"Good. First babies can take a while—labor often lasts twelve to twenty hours or more. But when her contractions are five minutes apart and regular, bring her in. Don't wait until the last minute."

Driving home, Betty was thoughtful. Paradise Valley Sanitarium. In just a few weeks, she'd be there, giving birth to their child.

"Are you scared?" Fred asked.

"Terrified. Everyone says labor is the worst pain imaginable. What if I can't do it?"

"You can do it. Women have been doing it for thousands of years. And I'll be there with you."

"Will they let you in the delivery room?"

"I don't know. Some hospitals allow husbands, some don't. But either way, I'll be at the hospital, waiting, ready to meet our baby."

Early October 1943 - Baby Names

Two weeks before the baby's due date, Betty and Fred finally sat down to seriously discuss names. They'd been avoiding the conversation, unable to agree, but time was running out.

"If it's a boy, I want to name him after my father," Fred said. "Frederick Walton Seaver III."

"I'm not sure about that," Betty said carefully. "I know you loved your father, but three Fredericks in a row seems like a lot. What if he wants his own identity?"

"We could call him by a nickname. Freddy, maybe. Or his middle name—Walton. That's different from Frederick."

"What about Ranslow? I've always loved that name – my grandmother’s grandfather was Ranslow – he and his wife adopted Della’s father, Devier. We could call him Ranny. Ranslow Lyle Seaver."

"Ranslow's nice. But I really want to honor my father somehow. He died before we got married, before he could meet you or know about this baby. This is a way to keep his memory alive."

They debated back and forth, neither willing to fully compromise.

"What if we use both names?" Betty suggested. "Ranslow Frederick Seaver. Ranslow as the first name, Frederick as the middle name. That way we honor your father without calling the baby Frederick."

Fred considered this. "Ranslow Frederick. I can live with that. We'd call him Ranny?"

"Ranny. I like it."

"And if it's a girl?"

This was easier. They both loved the name Virginia—Betty’s middle name.

"Virginia Emily Seaver," Betty suggested. "Virginia after the state, Emily after my mother."

"What about my mother? She should be honored too."

"Bessie as a middle name?"

"No, that doesn't flow. What about Alma? That's my mother's first name but she goes by Bessie —Alma Emily Seaver."

“Alma Emily. That's beautiful. I love it."

So it was decided: Ranslow Frederick if a boy, Alma Emily if a girl. They'd call the boy Ranny and the girl... Alma, Amy, Emmy? They'd decide when they met her.

October 15, 1943 - Fred's Birthday

Fred woke on his thirty-second birthday to find Betty already awake, sitting up in bed with considerable effort.

"Happy birthday," she said, leaning over to kiss him. "Thirty-two years old."

"Thank you. And thank you for not going into labor on my birthday. I appreciate the baby waiting."

"Tell the baby that, not me. I have no control over this situation anymore."

Fred helped Betty out of bed—a complicated maneuver now that she was nine months pregnant. She waddled to the kitchen where she'd hidden his birthday breakfast preparations the night before.

"I made you a coffee cake," she announced, pulling it from the cupboard. "And I have bacon and eggs ready to cook."

"You didn't have to do all that."

"It's your birthday. Of course I did."

They ate breakfast together, and then Betty presented Fred with his gift—the leather briefcase she'd bought weeks earlier.

Fred's face lit up when he opened it. "Betty, this is beautiful. And so practical—my current bag is falling apart."

"I know. I figured you needed something professional for work."

"It's perfect. Thank you."

"There's one more thing." Betty handed him a card she'd made herself, with a drawing on the front of a man holding a baby. Inside, she'd written: To Fred on your 32nd birthday. Next year, you'll be celebrating with our baby. I love you more than words can say. Love, Betty.

Fred's eyes filled with tears as he read it. "Next year. Our baby will be almost a year old."

"If the baby ever decides to arrive. I'm starting to think this child plans to stay in there forever."

"Dr. McCausland said first babies are often late. Even up to a week."

Betty groaned. "A week sounds like an eternity. I'm so uncomfortable. I can't sleep, I can't get comfortable, I can't even see my feet anymore."

"Want to take a walk? Might help move things along."

They walked slowly around the neighborhood, Betty stopping frequently to rest and catch her breath. The October day was beautiful—warm but not hot, with a gentle breeze. Several neighbors called out birthday wishes to Fred as they passed.

For dinner, Betty had invited the Carringers over for a small birthday celebration. Emily brought a pot roast (not trusting Betty to cook at nine months pregnant), Georgianna brought her famous apple pie, and Della sent fresh bread.

Lyle presented Fred with a nice tie and tie clasp, plus some cigars.

"For celebrating," Lyle said. "Your birthday now, and when the baby arrives."

They ate dinner at the small table, crowded but cozy, talking about everything except when the baby might come—everyone was carefully avoiding the subject, knowing Betty was anxious about it.

After dinner, they sang "Happy Birthday" to Fred, and he blew out the candles on Georgianna's pie.

"What did you wish for?" Betty asked.

"Can't tell you or it won't come true. But it involves a healthy baby and all of us making it through this war safely."

As the evening wound down and the Carringers prepared to leave, Emily pulled Betty aside.

"You're doing well, sweetheart. I know you're uncomfortable and anxious, but you look healthy. The baby will come when it's ready."

"I just want this to be over. I want to meet our baby."

"Soon. Very soon. And then you'll never sleep again, and you'll look back on these last days of pregnancy with nostalgia."

After everyone left, Fred and Betty sat together on the sofa, Betty's feet in Fred's lap while he massaged them gently.

"Thirty-two," Fred said. "When I was twenty-two, I never imagined I'd be here—married, about to become a father, working in California instead of Massachusetts. Life takes strange turns."

"Good turns, though?"

"The best turns. Meeting you was the best thing that ever happened to me."

"Even though I'm currently the size of a house and can't do anything without help?"

"Especially now. You're growing our baby. That's pretty miraculous."

They sat in comfortable silence, Fred's hands on Betty's belly, feeling the baby move and shift.

"Any day now," Betty said. "Our lives are about to change completely."

"I can't wait. I'm terrified, but I can't wait."

"Me too. Both at the same time."

They went to bed early, both tired, both thinking about the week ahead. Somewhere inside Betty, their baby was waiting, ready to be born, ready to join their family.

Fred fell asleep with his hand on Betty's belly, feeling their child moving beneath his palm.

Eight more days until the due date.

But babies came when they were ready.

And soon—very soon—their baby would be ready.


To be continued...

==========================================

2) Here is the Google NotebookLM Video Overview about Fred and Betty's life in September to mid-October 1943: 

3)  This story is historical fiction based on real people -- my parents -- and a real event in a real place.  I don't know the full story of these events -- but this is how it might have been. I hope that it was at least this good! Claude is such a good story writer!  I added some details and corrected some errors in Claude's initial version.

Stay tuned for the next chapter in this family story.

Here are the previous chapters:

                           ==============================================

Links to my blog posts about using Artificial Intelligence are on my Randy's AI and Genealogy page. Links to AI information and articles about Artificial Intelligence in Genealogy by other genealogists are on my AI and Genealogy Compendium page.

Copyright (c) 2026, Randall J. Seaver


Please comment on this post on the website by clicking the URL above and then the "Comments" link at the bottom of each post.  Share it on Twitter, Facebook, or Pinterest using the icons below.  Or contact me by email at randy.seaver@gmail.com.  Please note that all comments are moderated, and may not appear immediately.

Subscribe to receive a free daily email from Genea-Musings using www.Blogtrottr.com.

Saturday, April 4, 2026

Saturday Night Genealogy Fun -- What Was a "Turning Point" In Your Parent's Life?

 Calling all Genea-Musings Fans: 

 It's Saturday Night again - 

time for some more Genealogy Fun!!



Here is your assignment if you choose to play along (cue the Mission Impossible music, please!):


1)  Family stories are often about "Turning Points" and "Major Decisions."  

2)  This week, please describe a "Turning Point" in the life of one of your parents (or for both of them, or for grandparents).  Describe the decision, and discuss the outcome of it.

2)  Share the turning point with all of us by writing your own blog post, writing a comment on this blog post, or put it in a Substack post, Facebook Note, or some other social media system.  Please leave a comment on this post so others can find it.


Here's mine:

The most important "Turning Point" in my father's life was his decision to come to California from Massachusetts in December 1940.  I told the story in Fred's Story: "The Three-Day Cross-Country Escape."

My father's life was turned upside down and he made the best of it. He met my mother, married her in 1942, had a son Randy, served in the U.lS. Navy in 1944-5, came home and had two more sons, became an insurance agent, a world class bowler, a competitive and crafty youth baseball coach, and eventually a grandfather of four.

Without this decision, I would not be the person I am in this place and time. I might not have an extensive Mayflower and New England ancestry, or the engineer's mind.  My wife might have married someone else, and our daughters might have very different genetics. My mother might have become a world-famous artist.  My father might have been a baseball player or a rock star.  

If I wasn't who I am, would the genealogy research process be any different?  Hmmm, probably not.  


                                =============================================


Copyright (c) 2026, Randall J. Seaver

Please comment on this post on the website by clicking the URL above and then the "Comments" link at the bottom of each post.  Share it on Twitter, Facebook, or Pinterest using the icons below.  Or contact me by email at randy.seaver@gmail.comNote that all comments are moderated, and may not appear immediately.

Subscribe to receive a free daily email from Genea-Musings using www.Blogtrottr.com.

Ask AI: "Am I Wrong To Write Historical Fiction About My Ancestors?"

 Some people in the genealogy and family history community (notably on Facebook) have stated that Artificial Intelligence should not be used to create "historical fiction" about a historical person.  Some commenters say that we as family historians should only base stories on our own memories, on sourced records, on actual words spoken by that person, or in witness accounts of the person.  

I understand that point of view.  BUT (a big but...) I don't have memories, family stories, witness accounts, etc. for most of my ancestors - only for myself, my parents, my grandparents, but I have thousands of records for my ancestors. 

How can I tell the stories of my ancestors and their lives so that my relatives and descendants can better understand my life and the ancestors' lives?

As my blog readers and Facebook friends know, I have been telling "historical fiction" stories about my ancestors for over a year now in an attempt to understand the lives of my ancestors.  I do this by asking questions about how did the ancestors live their lives, what historical and social events affected them, what were the major decisions or turning points in their lives, etc.  

Am I wrong to do that?  My view is that this is a useful and legitimate activity as long as I identify the results as "Historical fiction" and "how it might have been" and avoid stating that it is how it really was for the ancestors in the time and place they lived.

1)  I decided to see what OpenAI ChatGPT5 thought about it.  Here is my prompt:  

"I'm an experienced genealogist but a technical writer and don't tell stories well with emotion or feelings, and have stories about my ancestors only from my parents and my own memories. Is it wrong to use AI to tell historical fiction stories about my ancestors - 'the way it might have been' based on the facts I have from source records with names, relationships, events, dates, places, etc.?"


(AI OpenAI ChatGPT5 image - crafting historical family stories)

And here is ChatGPT5's response:

Not wrong at all—if you handle it honestly and carefully. In fact, what you’re describing sits in a long tradition. Family historians have always tried to bridge the gap between documented facts and lived experience. The key is how you frame it.

Think of it this way: you’re not replacing history—you’re interpreting it.

a)  Where it works well

Using AI to create “the way it might have been” stories can:

  • Bring otherwise dry records to life (census lines, land deeds, probate files)

  • Help descendants connect emotionally with people they’d otherwise see as names and dates

  • Explore plausible daily life based on known context (time, place, occupation, culture)

That’s especially valuable in genealogy, where the record is often skeletal. You already know that even a well-documented ancestor leaves a lot unsaid.

b)  Where you need to be careful

The line to watch is between fact and invention. Problems arise when:

  • Fiction is presented as proven truth

  • Readers can’t tell what is documented vs. imagined

  • Details contradict known historical realities

Those are fixable issues with good discipline.

c)  A practical, traditional approach (that works beautifully)

You might appreciate this—it aligns with careful, evidence-based work:

1. Keep your proof standard intact -- Maintain your fully documented, source-based biography (your “anchor”).

2. Create a clearly labeled companion piece -- Call it something like: “A Historical Reconstruction”

  • “A Day in the Life (Imagined)”

  • “Based on Records of…”

3. Ground every scene in evidence -- For example:

  • If he was a millwright → describe mill work typical of that region and period

  • If she lived in 1870 Iowa → use known housing, clothing, weather patterns

  • If a child died young → you can explore the emotional weight, but don’t invent specific dialogue or events without signaling it

4. Signal uncertainty honestly -- Phrases like:

  • “He likely…”

  • “She may have…”

  • “It is reasonable to imagine…”

That keeps your integrity intact.

c)  Why this actually strengthens your work

You’re doing something many genealogists struggle with—making ancestors human again.

Records tell us:

  • what happened

  • when

  • where

But they rarely tell us:

  • what it felt like

  • what a day looked like

  • what mattered to them

Careful historical storytelling fills that gap without distorting the record.

d)  One more thought (from a traditional angle)

Before AI, people did this by hand—writing sketches, local histories, even family lore narratives. AI is just a new tool for an old instinct: honoring the past by trying to understand it.

Used responsibly, it’s not cutting corners—it’s extending your ability to interpret the past.


If you’d like, I can take one of your ancestors—say Devier Lamphier Smith or Della Carringer—and show you exactly how to build a clean, well-labeled “historical reconstruction” from your known facts.

2)  My next prompt was:  

"One of my thoughts is that what I am doing is acting as a ghostwriter for my ancestor who cannot speak for him or herself. Is that a fair thought? Is there another term besides novelist?"

The ChatGPT5 response was:

That’s a very fair way to think about it—and, frankly, a respectful one.

“Ghostwriter” fits better than you might expect, because you’re not trying to replace your ancestor’s voice—you’re trying to reconstruct a voice that history didn’t preserve. In genealogy, that’s a meaningful distinction. You’re working from evidence, not inventing freely.

That said, there are a few terms that might suit what you’re doing even more precisely, depending on how you want to present your work:

a)  Terms that fit your approach

  • Historical Interpreter --- This has a solid, traditional feel. It suggests you are explaining and giving life to the past based on evidence—much like a museum interpreter or living history presenter.
  • Narrative Genealogist -- A nice blend of your two worlds. It keeps your identity grounded in documented research while acknowledging that you’re shaping it into story form.
  • Family Historian (Narrative Form) -- Simple and honest. Many respected genealogists have done exactly this—writing sketches or reminiscences to accompany the record.
  • Historical Reconstructor -- This leans into what you’re actually doing: rebuilding a plausible lived experience from fragments.
  • Creative Nonfiction Writer (Genealogical) -- Useful if you ever share this more broadly. It signals: this is rooted in fact, but told with narrative technique.
  • First-Person Historical Reimagining -- Not a title for yourself, but a good label for the pieces. It clearly tells readers what they’re getting.


b)  Why “ghostwriter” still works

Your instinct is sound because:

  • You’re writing in his voice, not yours

  • You’re constrained by known facts and context

  • You’re not claiming he actually said these words

It’s almost like you’re giving him a chance to testify, based on the record he left behind.


A small but important guardrail

The only caution I’d add—very much in keeping with your careful approach—is this:

Pair the idea of “ghostwriting” with transparency.

For example, a simple note like:

“This narrative is a historically informed reconstruction based on documented facts and context. The words are imagined, but the circumstances are grounded in evidence.”

That keeps your integrity intact while still allowing the story to breathe.


c)  A traditional perspective you might appreciate

In earlier generations, family historians often wrote “reminiscences” or “sketches” of ancestors—sometimes even in first person—especially when preserving stories for children and grandchildren. They understood, as you do, that facts alone don’t carry memory forward.

You’re really doing the same thing—just with better tools and a bit more discipline.


If you want, I can help you settle on a consistent label and format you could use across all your ancestor narratives so future readers immediately understand what they’re reading.

=================================

3)  Let's stop here for now. I hope that this will result in honest discussions about this issue and not devolve into rancor and division. I think it needs to be discussed.

4)  My understanding is that OpenAI ChatGPT5 and most other large language models try to be positive and support the information presented to them as a prompt or opinion.  Do you think ChatGPT5 is trying to fool me with these responses?

==============================================

Links to my blog posts about using Artificial Intelligence are on my Randy's AI and Genealogy page. Links to AI information and articles about Artificial Intelligence in Genealogy by other genealogists are on my AI and Genealogy Compendium page.


Copyright (c) 2026, Randall J. Seaver

Please comment on this post on the website by clicking the URL above and then the "Comments" link at the bottom of each post.  Share it on Twitter, Facebook, or Pinterest using the icons below.  Or contact me by email at randy.seaver@gmail.com. Note that all comments are moderated, and may not appear immediately.

Subscribe to receive a free daily email from Genea-Musings using www.Blogtrottr.com.