Place Research Prompt
Use this prompt to research a new place before drafting its wiki page. Run it in a tool that has web access (search + fetch) — without it, the coordinates and URLs will be guessed rather than verified. Replace `[PLACE]` with the target (e.g. "Beaune, Burgundy, France").
The "if you cannot find it, write not found — do not fabricate" rule is deliberate: for this wiki, accuracy beats completeness, and fabricated Google Maps links or coordinates are worse than a blank.
The prompt
``` You are a meticulous travel researcher. Research the following place and return a structured guide: [PLACE — e.g. "Beaune, Burgundy, France"]
Cover these categories. Aim for 4–8 entries per category where the place supports it (a small village will have fewer — that's fine, don't pad with filler or invent options):
1. Places to stay — a range across budget, mid-range, and high-end / characterful (boutique hotels, B&Bs/chambres d'hôtes, notable inns) 2. Restaurants — a deliberate mix: casual/local, mid-range, and one or two special-occasion. Note the cuisine and rough price level. 3. Breweries / bars / cider houses 4. Wineries, vineyards, and tasting rooms (cellar-door / dégustation) 5. Historic sites & cultural landmarks 6. Must-see sights & signature experiences 7. Off-the-beaten-track finds — places a typical tourist would miss (local markets, walks, small producers, viewpoints, artisans). Search Atlas Obscura (https://www.atlasobscura.com/) for this place and fold any relevant entries in here — it is an excellent source for the unusual and overlooked. When an item comes from Atlas Obscura, include its atlasobscura.com page URL alongside the other links.
FOR EVERY SINGLE ENTRY in categories 1–7, provide ALL of the following fields. If you genuinely cannot find one, write "not found" — do NOT fabricate a URL, address, or coordinate. Accuracy matters more than completeness.
- Name
- Category (from the list above)
- One-line description (why it's worth it)
- Price level (€ / €€ / €€€ / €€€€) where applicable
- Address
- Official website URL
- TripAdvisor URL
- Yelp URL
- Google Maps place URL (the canonical maps.google.com/?cid=... or
google.com/maps/place/ link for the specific listing)
- Latitude, Longitude (decimal degrees, e.g. 47.0245, 4.8400)
ALSO provide a TRANSPORTATION & GETTING AROUND section for this place. This is about the destination as a whole, not per-entry. Cover:
- Getting there: Is there a train station? Name the station(s) and the main
rail connections (which cities/lines, rough journey times, TGV/regional). Nearest airport and distance. Long-distance bus options (e.g. FlixBus).
- Getting around locally: public transport (bus/tram/metro lines, how
frequent, day-pass options), and how walkable the place is.
- Bike & e-bike: rental shops, bike-share, dedicated cycle routes/greenways.
- Taxis & rideshare: availability (is Uber/Bolt present, or taxi-only?).
- Car: is a car needed or optional? Parking situation, any low-emission
zone (ZFE) or access restrictions.
- Practical verdict: can a visitor manage car-free here, or is a car
effectively required? One or two sentences.
For each named transport service (station, airport, bus operator, bike-rental, local transit authority), include its official website URL where one exists — otherwise "not found". Do not fabricate timetables; give approximate journey times and flag anything that should be checked against a live timetable.
Output format: a Markdown table per category (1–7), with one row per entry and one column per field above. Render the TRANSPORTATION section as prose with short sub-headings (Getting there / Getting around / Bike / Taxis & rideshare / Car / Verdict). After everything, add a short "Notes & caveats" section flagging anything seasonal, closed, reservation-only, or where data was uncertain.
Verify URLs resolve to the actual business, not a generic search page. Prefer primary sources (the venue's own site) for the website field. Cite or note when a place's existence/details could not be confirmed. ```
Notes on running it
- Google Maps place URLs are the field most often returned wrong — models tend to hand back a search URL instead of the canonical place link. The prompt calls this out, but spot-check a few.
- Coordinates & URLs need web access. A model without live search will hallucinate lat/long; rely on the "not found" rule.
- Feeding results into the wiki: output maps cleanly onto the typed page blocks in `build_site.py` — lodging/restaurant rows into `VILLAGE_PAGES`, individual landmarks into `PLACE_PAGES`. Keep the per-place URL fields so the "Websites, info & maps" reference tables stay populated (see the Wiki Index note on business reference links).
- Transportation section feeds the car-free planning that runs through this wiki (e.g. Épernay to Marlenheim: Car-Free Travel (Source Summary), Burgundy Car-Free, 12-Day Public-Transit Itinerary: Champagne · Alsace · Burgundy). The "can you manage car-free here?" verdict is the line to lift into those pages.