Etymology requesting tool/gramplet

Today I asked an AI to dissect a person’s name because I did not recognize the heritage of the name. Afterwards, I asked for a well-written prompt that would have generated all the information that had required several prompt revisions.

The prompt was long. So the thought occurs that it would be useful to have a tool/gramplet that pushes a form-field driven prompt to a preferred AI.

The following is for a Person’s Name. But similar prompts would be useful for: geographical gazetteer etymology of a Place, or; key historical (local, national, global) events that would impact a person’s timeline.

Analyze the name ‘[Full Name]’ (provide both in original script and Western alphabet if applicable) and offer insights on:

Probable heritage, cultural background, and language of origin
Phonetic pronunciation and stress patterns (if not obvious)
Western alphabet representation (if originally in a different script)
Meaning and origin of given name and family name
Naming system (e.g., patrilineal, matronymic)
Common variations, nicknames, or honorifics

Then, explain how to address this person in different social contexts:

Formal settings (e.g., official correspondence, academic environment)
Business interactions (e.g., workplace, professional networking)
Casual acquaintance (e.g., social gatherings, community events)
Friendly or familiar settings

Include cultural considerations, etiquette, and any specific naming conventions or address protocols relevant to the person’s likely cultural background. If uncertain about any aspects, indicate so and provide the most likely possibilities based on available information.

See Onomastics: where to store name etymology?

for places:

Using [Preferred Gazetteer Name] as the primary source, provide a concise summary for [Place Name] between [Start Year] and [End Year], focusing on key genealogical data:

Official name(s) and any significant name changes
Precise geographical location (coordinates if available)
Era-specific and modern Administrative jurisdictions (country, state/province, county/district)
Era-specific and modern boundaries in KML format (if available)
Notable boundary changes or incorporations
Population statistics at key intervals, if available

If [Preferred Gazetteer Name] lacks any of this information, specify secondary sources to be used, prioritizing [List of Preferred Secondary Sources]. Limit each point to 1-2 sentences. Include only the most relevant information for genealogical research. For the KML boundaries, provide links or instructions on how to access them if they’re not directly available in the response. If any information is unavailable or uncertain, clearly state this and provide the most likely possibilities based on available data.

Further on the [Preferred Gazetteer Name] input:

GeoNames (created by Marc Wick at www.geonames.org) is a well-known and widely used geographical gazetteer. It would certainly be recognized as a preferred gazetteer for many applications.

To format GeoNames as a [Preferred Gazetteer Name] in the prompt, you could use: “GeoNames (www.geonames.org)” This format clearly identifies the gazetteer name and provides its primary web address. If you wanted to be more formal or include additional information, you could use: “GeoNames Geographical Database (www.geonames.org, created by Marc Wick)”

Either of these formats would be suitable for use in the prompt as the [Preferred Gazetteer Name]. The choice between them depends on how much detail you want to include in the prompt itself.

That did not return a quality response when I put in a known place with historical jurisdictions changed 3 times.

Let’s refine your prompt to ensure it elicits more comprehensive and quality information. Here’s a revised version that emphasizes the need for detailed historical context, particularly regarding administrative jurisdictions and boundaries:


Prompt:

"Using GeoNames (www.geonames.org) as the primary source, provide a detailed summary for New Castle, Lawrence County, Pennsylvania between 1799 and today, focusing on key genealogical data:

  1. Official name(s) and any significant name changes.
  2. Precise geographical location (coordinates if available).
  3. Historical administrative jurisdictions from 1799 to the present, including:
    • The original county (Allegheny County) in 1799.
    • Changes to Mercer and Beaver counties in 1800.
    • The formation of Lawrence County in 1849.
  4. Era-specific and modern boundaries in KML format (if available).
  5. Notable boundary changes or incorporations throughout its history.
  6. Population statistics at key intervals, if available.

Please provide a chronological overview of the administrative changes, highlighting any relevant historical context that may affect genealogical research. If GeoNames lacks any of this information, specify secondary sources to be used, prioritizing [List of Preferred Secondary Sources]. Limit each point to 1-2 sentences. Include only the most relevant information for genealogical research. For the KML boundaries, provide links or instructions on how to access them if they’re not directly available in the response. If any information is unavailable or uncertain, clearly state this and provide the most likely possibilities based on available data."


Key Improvements:

  1. Emphasized Historical Context: The prompt now specifically asks for historical administrative jurisdictions and changes over time, ensuring that the response includes the necessary details about Allegheny, Mercer, Beaver, and Lawrence counties.

  2. Chronological Overview: By requesting a chronological overview, it encourages a more structured response that highlights the sequence of changes.

  3. Clear Sections: Each section is clearly defined, which helps in organizing the information better.

  4. Focus on Genealogical Relevance: The prompt maintains a focus on what is relevant for genealogical research, guiding the responder to provide pertinent information.

Feel free to adjust any specific wording or details to better fit your needs!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.