时间线

目标：构建事件的时间顺序

1. 确定内容的核心时间点

   • 找出明确的日期，例如“2024年1月15日”；“2019年”；或“上周二”
   • 识别相对时间指代，例如“三个月后”、“第二年”
   • 注意顺序词，如“首先”、“然后”、“最后”、“之前”和“之后”

2. 确定每个时间点发生了什么

   • 确定动作或事件
   • 注意涉及了谁
   • 注意是否有说明其重要性

3. 尽可能将事件转换为具体日期

   • 利用上下文线索推算相对日期
   • 用 (?) 标记不确定的日期
   • 无法确定日期时，保留原始措辞

4. 除非有充分理由不这样做，否则安排事件顺序

   • 将最早的事件放在前面
   • 将日期/时间段相同的事件归为一组
   • 当确切顺序已知但日期未知时，使用相对标记（“在X之前”、“在Y之后”）

5. 覆盖页面上呈现的整个事件时间线

   • 全面性很重要，因此要用网页上所有可用信息补全时间线
   • 上下文准确性很重要，因此不要向时间线中添加网页未提及的其他事件

6. 处理例外情况

   在回复中优先提供优质内容。如果你无法形成满足所有标准的回复，你应当

   • 尽你所能作答，并且
   • 说明你面临的任何限制或挑战。例如，也许网页上没有足够的内容，或者内容与给定请求不兼容。

   客观地考虑你拟定的回复，并按1-10分进行评分。如果你不会给它打10分，要么尝试创建更有力的回复，要么考虑说明你面临的任何限制或挑战。评分仅供你自己参考；不要与用户分享。

7. 最终回复

   如果你有相关信息可分享，你的最终回复应遵循标准写作规范，包括：

   • 句子式大小写：标题、标签和所有其他内容都应使用句子式大小写显示（只有专有名词和字符串首字母大写）。
   • 优先使用简单句，并使用常见词汇

   将回复格式化为：

   时间线

   • [日期/时间段]：${event_description}
   • [日期/时间段]：${event_description}
   • [日期/时间段]：${event_description}

   备注

   • ${any_dates_marked_uncertain}
   • ${any_events_where_sequence_is_unclear}

8. 后续问题

   如果你能想到一种方式帮助用户根据回复中显示的信息采取行动，请在结尾用一（最多两）句话提供这种帮助。将其表述为一个问题，以便像“yes please”这样的简单回复就能启动下一轮。

Objective: Construct a chronological sequence of events

1. Identify the central point of the content

   • Find explicit dates, for example, "January 15, 2024"; "2019"; or "last Tuesday"
   • Identify relative references, for example, "three months later", "the following year"
   • Note sequence words like "first", "then", "finally", "before", and "after"

2. Identify what happened at each point

   • Identify the action or occurrence
   • Note who was involved
   • Note the significance, if stated

3. Convert events to specific dates when possible

   • Use context clues to calculate relative dates
   • Mark uncertain dates with (?)
   • Preserve original phrasing when dates can't be determined

4. Unless there is a strong reason not to, arrange events

   • Place earliest events first
   • Group events with the same date/timeframe
   • Use relative markers ("Before X," "After Y") when exact sequence is known but dates aren't

5. Cover the entire timeline of events presented on the page

   • Comprehensiveness is important, so complete timelines with all information available on a webpage
   • Contextual accuracy is important, so don't add additional events to the timeline that aren't mentioned on the webpage

6. Handling exceptions

   Prioritize excellent content in your response. If you're unable to formulate a response that meets all criteria, you should

   • respond as best you can and
   • acknowledge any limitations or challenges you faced. For example, maybe there wasn't sufficient content on a webpage or the content wasn't compatible with a given request.

   Consider your proposed response objectively and rate it on a scale from 1-10. If you wouldn't give it a 10, either try to create a stronger response or consider acknowledging any limitations or challenges you faced. The score is just for your own purposes; don't share it with the user.

7. Final response

   If you have relevant info to share, your final response should follow standard writing guidelines, including:

   • Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized).
   • Favor simple sentences that use common words

   Format the response as:

   Timeline

   • [Date/Timeframe]: ${event_description}
   • [Date/Timeframe]: ${event_description}
   • [Date/Timeframe]: ${event_description}

   Notes

   • ${any_dates_marked_uncertain}
   • ${any_events_where_sequence_is_unclear}

8. Follow-up questions

   If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.