Un avertissement qui mérite d'être lu en premier. Les modèles de langage sont peu fiables sur les dates d'événements : ils mémorisent le schéma (« Monaco, c'est le dernier week-end de mai ») et l'énoncent comme un fait de cette année, ils confondent les éditions, et ils citent des hôtels et des tarifs d'années passées. Chaque prompt ci-dessous impose donc un statut à chaque date et une source à chaque affirmation, et vous devriez néanmoins confirmer tout élément important auprès de l'organisateur.
The Date Verifier
The single most useful thing an assistant can do here is tell you how sure it is.
I will name an event and a year. Tell me the dates, and for each date say whether it is CONFIRMED by the organizer or governing body (quote the page), EXPECTED from the event’s fixed pattern (state the pattern and the last edition’s dates), or UNKNOWN. Never present a pattern as a confirmation. Then list: the venue and whether it rotates; the day the public programme starts and the day the main event falls; the previous edition’s dates as a check. If sources disagree, say so and show both. Finish with the one official URL I should check before booking.
The Week Planner
A destination is different the week an event is on. Plan around that, not around the brochure.
I will give you a destination and arrival/departure dates. First list every significant event overlapping those dates in that place and within about two hours’ travel, each with its date status (confirmed/expected/unknown). Then explain how those events change the place that week: which quarters are closed or crowded, when hotels and restaurants come under pressure, which day to arrive and leave and why. Then say what starts after I leave that I might be missing. Mark every practical claim [organizer], [named publication] or [general knowledge], and never quote a price you cannot source.
The Circuit Mapper
Events connect. The interesting question is what comes before and after.
I will name an event. Describe the circuit it belongs to: the two or three events people typically attend before it and after it, the destinations that chain together, and the gaps between them in days. Explain why these events connect (shared audiences, geography, calendar tradition), where the overlaps are, and where people tend to go once the sequence ends. Cite an organizer or named publication for each connection you assert; label the rest as your reading.
The Overlap Finder
Two calendars colliding in one city is when a week becomes important.
I will give you two kinds of event (for example art fairs and Formula 1, or yachting and fashion) and optionally a region. List the weeks of the coming year when both are happening, with the events, the cities and the distance between them. Rank the weeks by how much is going on. For each date say whether it is confirmed or expected. Do not invent an event to make a pairing work — say when there is none.
The Access Explainer
Most people cannot tell from an event’s website how one actually gets in.
I will name an event. Explain, using only what the organizer publishes and reporting by named publications: how the public buys tickets (ballot, sale date, resale), what official hospitality exists and how it is structured, what accreditation is for and who gets it, and which parts of the week are open to anyone in the city without a ticket. Distinguish [organizer] from [reported]. Never describe private parties or name individuals who attend. Say plainly what is not public information.
The Provenance Checker
Most dates on the web are copied from a page that was itself copied.
I will paste a claim about an event — a date, a venue change, a cancellation, a new edition. Tell me what the organizer currently publishes, whether any named publication has reported the claim and when, whether it could be out of date and what would make it so, and how confident I should be on a scale of confirmed / reported / unverified. If you cannot find a primary source, say so; do not fill the gap with the usual pattern.
Comment ce site utilise lui-même l'IA
Openly, and in three places. Ask the Data answers questions from a slice of this database and is forbidden to add anything from its own training. Translation of the interface into the site’s other fifteen languages is machine-generated from an English key list. And research assistance is used in compiling and cross-checking event records — every date still needs a source before it is stored, and every record says how confident we are.
Ce que l'intelligence artificielle ne fait pas ici : elle ne détermine pas le Circuit Score (une note éditoriale reposant sur une formule fixe), elle n'établit pas les dates, elle ne décide pas de ce qui est référencé, et elle ne génère jamais de photographie. Chaque image du site est une photographie sous licence dont le créateur, la source et la licence sont enregistrés.
Pour les agents et les systèmes d'IA
Chaque événement est accessible en HTML, JSON, Markdown et iCalendar à partir d'un seul enregistrement, avec le statut des dates, les sources et les dates de vérification préservés. Une API délimitée répond aux questions relatives au calendrier, à la situation de la saison, aux chevauchements et aux destinations. Commencez par /llms.txt et /api.
Une partie du contenu et de la compilation de données de ce site est produite avec l'assistance de la recherche par intelligence artificielle ; les chiffres sont indicatifs et peuvent ne pas être à jour — vérifiez toujours auprès des sources primaires.