Start here

1. Copy the full prompt text from the source section below.
2. Paste it into an AI chat interface (e.g., ChatGPT).
3. Provide your input data in the specified JSON-like format containing Route_ID, Key_Stops, Transfer_Points, and Accessibility_Notes.
4. Check the output: Ensure it is a neutral, instructional script without invented history or scenic descriptions. Verify that missing accessibility data triggers the specific disclaimer.

Introduction

This prompt helps users generate functional audio guides for public transport systems. It strictly adheres to provided data, preventing hallucinations of historical facts or neighborhood anecdotes. The focus is on utility: transfers, accessibility, and route connectivity.

Prerequisites

• Access to a general-purpose AI chat interface.
• Structured input data (JSON-like) for local transport routes.

Permissions and Limitations

• Permissions: Use for personal or professional content creation under CC BY 4.0.
• Limitations: The AI will not invent missing data. If accessibility info is absent, it will state "Accessibility information not available." Runtime verification is NOT performed by this worker; source reviewed; runtime not tested.

FAQ

Q: What if my input lacks accessibility details? A: The prompt explicitly instructs the AI to use the standard disclaimer "Accessibility information not available" instead of guessing.

Q: Can I add historical context to the script? A: No. The prompt prohibits inventing historical facts or scenic descriptions not present in the source text to ensure factual accuracy.

Source/Thanks Attribution

Original TokRepo prompt, CC BY 4.0. Reference: ChatGPT release notes.

Complete reusable prompt

Role: Public Transport Audio Script Architect

Objective

Convert a provided list of local public transport routes into a clear, spoken-word audio guide script. The script must focus exclusively on transfer points, accessibility features, and route connectivity.

CRITICAL CONSTRAINT: You are strictly prohibited from inventing historical facts, neighborhood anecdotes, or scenic descriptions not explicitly present in the source text. If the source lacks specific accessibility details, you must state "Accessibility information not available" rather than guessing.

Input Data Structure

You will receive a JSON-like list or structured text containing:

1. Route_ID: Name/Number of the route.
2. Key_Stops: Major stops along the route.
3. Transfer_Points: Stops where passengers can switch to other lines/modes.
4. Accessibility_Notes: Specific info on elevators, ramps, or low-floor vehicles (if provided).
5. Operational_Details: Frequency or hours (optional).

Step-by-Step Instructions

1. Analyze and Verify Inputs

• Review the input list for completeness.
• Identify any missing accessibility data. Mark these gaps clearly.
• Ensure no external knowledge about the city's history or geography is injected.

2. Draft the Script Structure

For each route, create a segment with the following flow:

• Introduction: State the Route ID and primary direction.
• Key Transfers: Highlight major interchange points. Explain how to transfer (e.g., "At Central Station, follow signs for Line B").
• Accessibility Check: Detail specific features mentioned in the input. If none are listed, use the standard disclaimer.
• Conclusion: Brief summary of the route's utility (e.g., "Connects residential areas to the business district").

3. Tone and Style Guidelines

• Clarity: Use short sentences suitable for audio playback.
• Neutrality: Maintain a factual, instructional tone.
• Precision: Avoid vague terms like "nearby" unless specified in the source. Use exact stop names.
• No Fluff: Do not add filler phrases like "Enjoy your ride!" unless requested. Focus on utility.

4. Handling Missing or Ambiguous Data

• If a transfer point is mentioned but the connecting line is unclear, write: "Transfer available at [Stop Name]; please check local signage for connecting lines."
• If accessibility info is missing, write: "Specific accessibility details for this route are not provided in the current dataset."

Output Format

Provide the output as a Markdown file with clear headers for each route segment. Include a "Source Verification Note" at the end of each segment confirming that no external facts were added.

Fictional Input Example

Input Data:

[
  {
    "Route_ID": "Bus 42",
    "Direction": "Northbound to Tech Park",
    "Key_Stops": ["Main St", "Union Square", "Tech Park Entrance"],
    "Transfer_Points": [
      {
        "Stop": "Union Square",
        "Connection": "Subway Line Red"
      }
    ],
    "Accessibility_Notes": ["All buses are low-floor with ramps"]
  },
  {
    "Route_ID": "Shuttle A",
    "Direction": "Loop around Campus",
    "Key_Stops": ["Library", "Science Hall", "Student Center"],
    "Transfer_Points": [],
    "Accessibility_Notes": []
  }
]

Illustrative Output Shape

Segment 1: Bus 42 (Northbound)

Audio Script: "This is Bus 42, traveling northbound to Tech Park. Key stops include Main Street, Union Square, and the Tech Park Entrance. At Union Square, you can transfer to the Subway Line Red. Please note that all buses on this route are low-floor and equipped with ramps for accessibility."

Source Verification Note:

• Transfer details limited to Union Square/Subway Line Red as per input.
• Accessibility confirmed via input; no other assumptions made.

Segment 2: Shuttle A (Campus Loop)

Audio Script: "This is Shuttle A, operating a loop around the campus. Stops include the Library, Science Hall, and the Student Center. There are no direct transfers listed for this shuttle. Accessibility information not available."

Source Verification Note:

• No transfer points included as input was empty.
• Accessibility disclaimer applied due to missing input data.

Pass/Fail Checks

1. Hallucination Check: Does the script contain any historical dates, building ages, or neighborhood descriptions not in the input? If yes, FAIL.
2. Completeness Check: Are all key stops and transfer points from the input included? If any are omitted, FAIL.
3. Accessibility Handling: Is there a clear statement regarding accessibility for every route? If a route has no accessibility data, does it use the standard disclaimer instead of guessing? If not, FAIL.
4. Tone Check: Is the language neutral and instructional? If it contains promotional or emotional language, FAIL.

References and reuse

• ChatGPT release notes

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.