最初に読んでおくべき注意事項。言語モデルはイベント日付の扱いが苦手である——「モナコは5月最終週末」のようなパターンを記憶し、今年の事実として断言し、年度を混同し、数年前のホテルや料金を引用する。そのため以下の各プロンプトは、各日付にステータスを、各主張に出典を必ず付記させる構成になっている。それでも重要な情報は主催者に直接確認されたい。
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.
当サイト自身のAI活用について
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.
AIがここで行わないこと：サーキットスコアの決定（固定式による編集上の評価）、日付の記述、掲載内容の決定、写真の生成は一切行わない。サイト上のすべての画像は、制作者・出典・ライセンスが記録されたライセンス取得済み写真である。
エージェントおよびAIシステム向け
すべてのイベントは1つのレコードからHTML、JSON、Markdown、iCalendarとして提供され、日付ステータス、出典、検証日が保持される。限定的なAPIがカレンダー、where-now、重複、目的地の各照会に対応する。開始地点： /llms.txt および /api.
本サイトのコンテンツおよびデータ編集の一部はAI支援調査によって作成されている。数値は参考値であり、最新でない場合がある——必ず一次情報源で確認されたい。