Dataset Viewer
type
stringlengths 8
17
| instruction
stringlengths 1.17k
5k
|
|---|---|
amb_calendar.json
|
The **Calendar Shift** subtask requires you to **convert dates between different calendar systems and resolve ambiguities caused by calendar transitions**. This involves:
✅ **Identifying the original calendar system** (*Is the date in the Julian, Gregorian, Islamic, or Hebrew calendar?*)
✅ **Determining the equivalent date in the target calendar** (*What is October 4, 1582 (Julian) in the Gregorian system?*)
✅ **Adjusting for discrepancies caused by leap years or missing days** (*Why did Britain skip 11 days in September 1752?*)
✅ **Interpreting historical events affected by calendar reforms** (*Why do the October Revolution and Russian historical documents list different dates?*)
✅ **Handling cultural calendar shifts for holidays and traditions** (*Why is Orthodox Christmas on January 7 while Western Christmas is on December 25?*)
---
## **🔹 Step-by-Step Reasoning Process**
### **1. Identify the Original Calendar System**
- Determine whether the **given date belongs to a Julian, Gregorian, Islamic, Hebrew, or other calendar system**.
- Recognize **when and where** the calendar system was in use at the time.
- **Calendar System:** Julian (used before the Gregorian reform in 1582).
- **Region:** Many Catholic countries switched in 1582, but Protestant and Orthodox regions kept using Julian longer.
- **Calendar System:** Islamic Hijri (lunar-based).
- **Conversion needed:** Islamic dates shift relative to the solar-based Gregorian system.
---
### **2. Determine If a Calendar Reform or Shift Applies**
- If converting between Julian and Gregorian, check if **a gap of days or years must be accounted for**.
- If dealing with Islamic or Hebrew calendars, **consider the different month and year lengths**.
- **Step 1:** The Gregorian reform skipped **10 days** to fix the drift in the Julian system.
- **Step 2:** October 4, 1582 (Julian) became **October 15, 1582 (Gregorian)**.
- **Final Answer:** *There were no dates between October 5–14, 1582 in countries that adopted the Gregorian calendar immediately.* ✅
- **Step 1:** Russia used the Julian calendar in 1917.
- **Step 2:** The revolution occurred on **October 25, 1917 (Julian)**, but after Russia switched to the Gregorian calendar in 1918, that date became **November 7, 1917 (Gregorian)**.
- **Final Answer:** *The October Revolution happened in November by the modern calendar because Russia switched from Julian to Gregorian in 1918.* ✅
---
### **3. Apply the Necessary Conversion Formula**
- **Julian to Gregorian:**
- If before 1582: **Add 10 days** (October 4, 1582 → October 15, 1582).
- If after 1582: **Add 11–13 days** (e.g., 1700: +11 days, 1800: +12 days, 1900: +13 days).
- **Gregorian to Julian:**
- Reverse the process: **Subtract 10–13 days** depending on the year.
- **Islamic to Gregorian:**
- The **Hijri year is about 10–12 days shorter**, so **1445 AH ≈ 2023 AD**.
- **Hebrew to Gregorian:**
- The **Hebrew calendar is lunisolar**, meaning its months don’t align with the Gregorian system exactly.
- **Step 1:** The Julian calendar was running **11 days behind** in 1700.
- **Step 2:** Add **11 days** to January 1 → **January 12, 1700 (Gregorian).**
- **Final Answer:** *January 1, 1700 (Julian) is January 12, 1700 (Gregorian).* ✅
- **Step 1:** Use an Islamic-Gregorian conversion formula.
- **Step 2:** 1 Ramadan 1444 ≈ March 23, 2023 (Gregorian).
- **Final Answer:** *1 Ramadan 1444 corresponds to March 23, 2023, in the Gregorian calendar.* ✅
---
### **4. Verify If a Historical Event or Holiday Was Affected by a Calendar Shift**
- Some events have **dual dates** due to calendar changes.
- Religious holidays might still follow **older calendar systems** (e.g., Orthodox Christmas).
- **Step 1:** He was born **February 11, 1731 (Julian)**.
- **Step 2:** When Britain switched to the Gregorian calendar in 1752, his birthday was adjusted to **February 22, 1732 (Gregorian).**
- **Final Answer:** *George Washington’s birthdate changed due to Britain’s adoption of the Gregorian calendar in 1752.* ✅
- **Step 1:** The Orthodox Church still follows the **Julian calendar** for religious holidays.
- **Step 2:** December 25 (Julian) corresponds to **January 7 (Gregorian)**.
- **Final Answer:** *Orthodox Christmas is on January 7 (Gregorian) because the Eastern Orthodox Church follows the Julian calendar.* ✅
---
### **5. Format the Final Answer Clearly**
- If the conversion is **exact**, provide the exact new date.
- If **historical context matters**, explain why the shift happened.
- If multiple interpretations exist, acknowledge them.
- **November 7, 1917 (Gregorian).** ✅
- *Convert 1 Muharram 1445 (Islamic) to Gregorian.*
- **July 19, 2023 (Gregorian).** ✅
- *Why did Britain skip 11 days in 1752?*
- **Britain switched to the Gregorian calendar in 1752, skipping September 3–13 to realign dates.** ✅
|
amb_inter.json
|
### **Instructions for Step-by-Step Reasoning in Interpretation (Ambiguity Resolution) Tasks**
The **Interpretation (Ambiguity Resolution)** subtask requires you to **understand and resolve vague or ambiguous time-related expressions** based on context and common usage. This involves:
### **1. Identify the Ambiguous Temporal Expression**
- Locate the **time-related phrase** that requires clarification.
- Determine whether the phrase is **relative, imprecise, or context-dependent**.
- **Ambiguous phrase:** "a while ago"
- **Type:** **Relative time expression (depends on the context).**
- **Ambiguous phrase:** "next Friday"
- **Type:** **Context-dependent phrase (varies by interpretation).**
---
### **2. Determine Possible Meanings Based on Common Usage**
- Retrieve the **most typical** interpretation.
- Consider whether the phrase refers to **a fixed, flexible, or culturally dependent** timeframe.
- **Common usage:** Generally means **a few days to a few months ago**.
- **Context matters:** Could be a few years ago in historical discussions.
- **Final Answer:** *"A while ago" usually means a short-to-moderate time in the past but is context-dependent.* ✅
- **Fixed interpretation:** It refers to **a specific Thursday in November every year** (e.g., Thanksgiving in the U.S.).
- **Final Answer:** *"The third Thursday of November" is the third Thursday of the given year's November.* ✅
---
### **3. Consider Regional, Cultural, and Contextual Variations**
- Some phrases **change meaning based on location or common practice**.
- Determine if **different regions or situations** use the term differently.
- **U.S. Interpretation (some speakers):** This coming Friday.
- **U.K./Other Interpretation:** The Friday of the following week.
- **Final Answer:** *"Next Friday" can mean this coming Friday or the Friday after, depending on regional and individual interpretation.* ⚠️
- **Workplace setting:** Likely means **later today**.
- **Social setting:** Could mean **another day**.
- **Final Answer:** *"Later" is context-dependent. In work, it often means later the same day; in casual speech, it might mean another day.* ✅
---
### **4. Narrow Down the Most Likely Interpretation**
- If multiple interpretations exist, identify the **most reasonable timeframe** based on common usage.
- If the meaning is **highly variable**, acknowledge the uncertainty.
- **Common range:** **2000–2005**.
- **Possible variation:** Some may extend it to **2000–2010**.
- **Final Answer:** *"Early 2000s" typically means between 2000 and 2005 but could extend to 2010 in some contexts.* ✅
- **Short answer:** Usually **a few minutes**, but not a fixed time.
- **Context-dependent:** Some might mean **15–30 minutes** or longer.
- **Final Answer:** *"In a bit" typically means a short wait (a few minutes), but context determines exact timing.* ✅
---
### **5. Provide Multiple Possible Interpretations When Necessary**
- Some phrases **don’t have a single fixed meaning**.
- If the phrase **varies significantly**, provide **all reasonable interpretations**.
- **Strict interpretation:** **Yes, within 7 days.**
- **Looser interpretation:** **Could mean slightly longer, depending on context.**
- **Final Answer:** *"Within a week" typically means up to 7 days, but some may interpret it more flexibly.* ⚠️
- **Common interpretation:** **9 AM–11 AM.**
- **Workplace context:** May refer to **closer to 10 AM.**
- **Final Answer:** *"Mid-morning" typically means around 9–11 AM.* ✅
---
### **6. Format the Final Answer Clearly**
- If the phrase has **one clear meaning**, state it directly.
- If it has **multiple possible meanings**, provide reasonable interpretations.
- If the meaning **depends on context**, acknowledge uncertainty.
- **Clear definition:** **30 minutes after the hour (e.g., 1:30, 2:30, etc.).** ✅
- *What does "holiday hours" mean?*
- **Multiple meanings:**
- **Some businesses extend hours during holidays.**
- **Others reduce hours or close early.**
- **Final Answer:** *"Holiday hours" can mean extended or reduced hours, depending on the business.* ⚠️
|
amb_long.json
|
The **Long-Term Shift** subtask requires you to **adjust dates over extended periods (years, decades, centuries, millennia) and resolve ambiguities related to these shifts**. This involves:
### **1. Identify the Given Date and Shift Period**
- Extract the **starting date** and **the number of years to shift forward or backward**.
- Determine whether the shift is **a simple addition/subtraction or requires additional calculations (e.g., leap years, periodic cycles, BC/AD transition, calendar differences).**
- **Step 1:** Identify the starting year → **1776**.
- **Step 2:** Add 250 years → **1776 + 250 = 2026**.
- **Final Answer:** **2026** ✅
- **Step 1:** Identify the starting year → **2024**.
- **Step 2:** Subtract 500 years → **2024 - 500 = 1524**.
- **Final Answer:** **1524** ✅
---
### **2. Check for Special Adjustments (Leap Years, Calendar Shifts, BC/AD Transitions, etc.)**
- If the shift crosses a **leap year adjustment**, account for extra days.
- If shifting across the **Julian-Gregorian transition (1582)**, check for missing/skipped days.
- If shifting from **BC to AD**, remember there is **no year 0** (1 BC → 1 AD).
- **Step 1:** Count leap years (every 4 years) → **(2000 - 1900) ÷ 4 = 25**.
- **Step 2:** Adjust for century rule (1900 was NOT a leap year) → **24 leap years**.
- **Final Answer:** **24 leap years** ✅
- **Step 1:** 300 BC + 500 years → Passes **1 BC to 1 AD transition**.
- **Step 2:** Adjust for missing year 0 → **500 - 300 = 200 AD**.
- **Final Answer:** **200 AD** ✅
---
### **3. Verify Periodic or Cyclical Shifts**
- If the shift involves **repeating cycles**, determine how many full cycles fit into the period.
- Use modular arithmetic or direct multiplication to find the next occurrence.
- **Step 1:** Identify the periodic cycle → **76 years**.
- **Step 2:** Add to last occurrence → **1986 + 76 = 2061**.
- **Final Answer:** **2061** ✅
- **Step 1:** Identify the cycle length → **12 years**.
- **Step 2:** Add to last occurrence → **2012 + 12 = 2024**.
- **Final Answer:** **2024** ✅
---
### **4. Handle Complex Historical or Future Projections**
- If dealing with **historical dates**, verify known facts about major changes in the calendar system.
- If **projecting far into the future**, check whether any assumptions (e.g., leap year rules, technological predictions) remain valid.
- **Step 1:** Identify event year → **476 AD**.
- **Step 2:** Subtract from current year → **2024 - 476 = 1,548 years**.
- **Final Answer:** **1,548 years** ✅
- **Step 1:** Assume the current year is **2024**.
- **Step 2:** Subtract 10,000 years → **2024 - 10,000 = 7,976 BC**.
- **Final Answer:** **~7,976 BC** ✅
---
### **5. Format the Final Answer Clearly**
- If the shift **results in an exact year**, state it directly.
- If **historical events influence the shift**, explain briefly.
- If there are **multiple valid answers**, acknowledge the ambiguity.
- **2066 AD** ✅
- *How many years until the year 100,000 AD?*
- **97,976 years from 2024.** ✅
- *What year will it be 1,000 years after 753 BC?*
- **248 AD (since there is no year 0).** ✅
|
amb_mid.json
|
The **Mid-Term Shift** subtask requires you to **adjust dates over intermediate periods (months, weeks, days) while resolving ambiguities caused by variations in calendar structure**. This involves:
### **1. Identify the Reference Date and Shift Period**
- Extract the **starting date** and **the number of months, weeks, or days to shift forward or backward**.
- Determine whether the shift is **a straightforward addition/subtraction or requires adjustments for calendar rules**.
- **Step 1:** Identify the reference date → **March 15, 2023**.
- **Step 2:** Add 6 months → **September 15, 2023**.
- **Final Answer:** **September 15, 2023** ✅
- **Step 1:** Identify the reference date → **July 1, 2024**.
- **Step 2:** Add 10 weeks → **September 9, 2024**.
- **Final Answer:** **September 9, 2024** ✅
---
### **2. Handle Month-Length Variations and Leap Years**
- If the shift crosses **months of different lengths**, adjust accordingly.
- If shifting across **February in a leap year**, check if February 29 exists.
- If the **exact date does not exist in the target month**, adjust logically.
- **Step 1:** Identify the reference date → **November 30**.
- **Step 2:** Add 3 months → **February 30 does not exist**.
- **Step 3:** Adjust to the last valid date → **February 28 (or February 29 in a leap year).**
- **Final Answer:** **February 28 (or 29 in a leap year)** ✅
- **Step 1:** Identify the reference date → **February 29, 2024** (leap year).
- **Step 2:** Add 1 year → **February 29, 2025 does not exist**.
- **Step 3:** Adjust to **February 28, 2025** (since 2025 is not a leap year).
- **Final Answer:** **February 28, 2025** ✅
---
### **3. Account for Week-Based Date Adjustments**
- Convert weeks into days (**1 week = 7 days**) and find the resulting date.
- Consider whether the shift **crosses month or year boundaries**.
- Track **day-of-the-week shifts** when needed.
- **Step 1:** Identify the reference date → **October 10, 2023**.
- **Step 2:** Convert 12 weeks → **12 × 7 = 84 days**.
- **Step 3:** Add 84 days → **January 2, 2024**.
- **Final Answer:** **January 2, 2024** ✅
- **Step 1:** Convert 100 days to weeks → **100 ÷ 7 = 14 full weeks + 2 extra days**.
- **Step 2:** Wednesday + 2 days → **Friday**.
- **Final Answer:** **Friday** ✅
---
### **4. Resolve Cyclical and Recurring Event Shifts**
- Identify the **recurrence pattern** and apply it.
- For **monthly recurrences**, maintain the same calendar date if possible.
- For **weekly recurrences**, adjust day-of-week shifts accordingly.
- **Step 1:** Start in **January**.
- **Step 2:** Add 3 months each time → **April, July, October, January (next year), April**.
- **Final Answer:** **April, July, October, January, April** ✅
- **Step 1:** Identify the recurrence pattern (every 14 days).
- **Step 2:** Add 14 days each time → **March 15, March 29, April 12**.
- **Final Answer:** **March 15, March 29, April 12** ✅
---
### **5. Resolve Ambiguous Expressions in Mid-Term Shifts**
- Some shifts can be interpreted **differently depending on context** (e.g., "3 months from now" vs. "90 days later").
- If unclear, provide **both interpretations** or ask for clarification.
- **Interpretation 1 (Calendar Months):** **April 15**.
- **Interpretation 2 (90-Day Shift):** **April 14 (if counting exact days).**
- **Final Answer:** *April 15 (if by month), April 14 (if by exact days).* ⚠️
- **Step 1:** Add 6 months to August 31 → **February 31 does not exist**.
- **Step 2:** Adjust to the last valid date → **February 28 (or 29 in a leap year).**
- **Final Answer:** **February 28 (or 29 in a leap year)** ✅
---
### **6. Format the Final Answer Clearly**
- If the shift **results in an exact date**, state it directly.
- If **calendar rules require an adjustment**, explain why.
- If multiple interpretations exist, acknowledge the ambiguity.
- **November 10, 2024** ✅
- *If today is December 1, what is the date 12 weeks earlier?*
- **September 8** ✅
- *If today is January 15 and an event is "3 months from now," is that April 15 or exactly 90 days later?*
- **April 15 (by months), April 14 (by exact days).** ⚠️
|
amb_short.json
|
The **Short-Term Shift** subtask requires you to **adjust times over brief periods (hours, minutes, seconds) while resolving ambiguities related to time formats, AM/PM shifts, and daylight saving time (DST) transitions**. This involves:
### **1. Identify the Reference Time and Shift Period**
- Extract the **starting time** and the **duration to shift forward or backward**.
- Determine whether the shift is **in hours, minutes, or seconds**.
- **Step 1:** Identify the reference time → **9:00 AM**.
- **Step 2:** Add 6 hours → **9:00 + 6 = 3:00 PM**.
- **Final Answer:** **3:00 PM** ✅
- **Step 1:** Identify the reference time → **1:20 PM**.
- **Step 2:** Subtract 45 minutes → **1:20 - 45 min = 12:35 PM**.
- **Final Answer:** **12:35 PM** ✅
---
### **2. Handle AM/PM Transitions and 24-Hour Conversions**
- If the shift **crosses AM to PM (or vice versa)**, update the time notation accordingly.
- If working with **24-hour format**, ensure proper conversion.
- **Step 1:** Identify the reference time → **5:30 PM**.
- **Step 2:** Add 10 hours → **5:30 + 10 = 3:30 AM (next day).**
- **Final Answer:** **3:30 AM (next day)** ✅
- **Step 1:** Recognize PM means adding 12 to the hour → **10 + 12 = 22**.
- **Final Answer:** **22:30** ✅
- *Convert 14:45 to 12-hour format.*
- **Step 1:** Recognize 14 is **2 PM in 12-hour format**.
- **Final Answer:** **2:45 PM** ✅
---
### **3. Adjust for Daylight Saving Time (DST) Changes**
- If the shift **crosses a DST change**, adjust the time accordingly.
- Consider whether **clocks move forward (spring) or backward (fall).**
- **Step 1:** Recognize that **1:30 AM does not exist** since clocks jump from 2:00 AM → 3:00 AM.
- **Final Answer:** **1:30 AM is skipped (does not exist).** ⚠️
- **Step 1:** Recognize that clocks move **back 1 hour at 2:00 AM**.
- **Step 2:** Instead of becoming 2:00 AM, it **goes back to 1:00 AM**.
- **Final Answer:** **1:00 AM (repeating the hour).** ✅
---
### **4. Resolve Relative Time Expressions**
- Identify **phrases like "in an hour," "half an hour later," or "a few minutes ago."**
- Convert them into **exact timestamps** based on the given time.
- **Step 1:** Identify the reference time → **3:10 PM**.
- **Step 2:** Add 1 hour → **4:10 PM**.
- **Final Answer:** **4:10 PM** ✅
- **Step 1:** Identify the reference time → **7:45 AM**.
- **Step 2:** Subtract 30 minutes → **7:15 AM**.
- **Final Answer:** **7:15 AM** ✅
---
### **5. Interpret Ambiguous Time References**
- Some times can be **misinterpreted**, requiring clarification.
- If unclear, **explain multiple interpretations**.
- **Step 1:** Recognize **12 alone is ambiguous**.
- **Step 2:** Consider common interpretations:
- **12 AM = Midnight** (start of the day).
- **12 PM = Noon** (midpoint of the day).
- **Final Answer:** *12 can mean noon or midnight; context is needed.* ⚠️
- **Step 1:** Recognize **"midnight" is a boundary time.**
- **Step 2:** Possible interpretations:
- **If referring to the end of today → 11:59 PM today.**
- **If referring to the start of tomorrow → 12:00 AM (next day).**
- **Final Answer:** *Midnight can refer to the end of today or start of tomorrow—context matters.* ⚠️
---
### **6. Format the Final Answer Clearly**
- If the shift **results in an exact time**, state it directly.
- If **calendar/time rules require an adjustment**, explain why.
- If multiple interpretations exist, **acknowledge the ambiguity**.
- **2:15 PM** ✅
- *Convert 3:45 PM to 24-hour format.*
- **15:45** ✅
- *What happens at 2:00 AM when daylight saving starts?*
- **The clock jumps to 3:00 AM, skipping 2:00-2:59 AM.** ⚠️
|
ari_12h.json
|
To accurately **add or subtract time** within the **12-hour AM/PM format**, you should follow a **structured step-by-step approach** that ensures precision, especially when handling **crossing noon, midnight, and wrap-around cases**.
### **1. Identify the Given Information**
- Extract the **initial time** in **HH:MM AM/PM format**.
- Identify the **operation**:
- **Addition** (moving forward in time)
- **Subtraction** (moving backward in time)
- Extract the **duration** (hours and/or minutes).
---
### **2. Perform the Time Calculation**
#### **A. Add or Subtract Hours First**
- If adding, move forward in **hours**.
- If subtracting, move backward in **hours**.
- If the time crosses **12:00**, switch between AM and PM.
#### **B. Adjust the Minutes**
- If adding minutes results in **≥ 60**, roll over to the next hour.
- If subtracting minutes results in **< 0**, borrow an hour and adjust the minutes.
#### **C. Handle AM/PM Transitions**
- If the result crosses **12:00 PM**, switch from **AM → PM** or **PM → AM**.
- If the result **goes past 12:00 AM (midnight)**, indicate that it's the **next day or previous day**.
---
### **3. Format the Final Answer Correctly**
- Always return the time in **HH:MM AM/PM format**.
- If crossing midnight, indicate **(next day)** or **(previous day)** if needed.
|
ari_24h.json
|
To accurately **add or subtract time** within the **24-hour format**, you should follow a **structured step-by-step approach** that ensures precision, especially when handling **crossing midnight, negative time shifts, and wrap-around cases**.
### **1. Identify the Given Information**
- Extract the **initial time** in **HH:MM (24-hour format)**.
- Identify the **operation**:
- **Addition** (moving forward in time)
- **Subtraction** (moving backward in time)
- Extract the **duration** (hours and/or minutes).
---
### **2. Perform the Time Calculation**
#### **A. Add or Subtract Hours First**
- If adding, move forward in **hours**.
- If subtracting, move backward in **hours**.
- If the time crosses **00:00 (midnight)**, adjust the calculation accordingly.
#### **B. Adjust the Minutes**
- If adding minutes results in **≥ 60**, roll over to the next hour.
- If subtracting minutes results in **< 0**, borrow an hour and adjust the minutes.
#### **C. Handle Cross-Midnight Cases**
- If the result **goes past 24:00**, subtract **24** to wrap around to the next day.
- If the result **goes below 00:00**, add **24** to wrap around to the previous day.
---
### **3. Format the Final Answer Correctly**
- Always return the time in **HH:MM (24-hour format)**.
- If crossing midnight, indicate **(next day)** or **(previous day)** if needed.
|
ari_app.json
|
To accurately compute **real-world time-related problems**, you should follow a **structured step-by-step approach** that ensures precision, especially when handling **time durations, AM/PM transitions, multi-step processes, and unit conversions**.
### **1. Identify the Given Information**
- Extract key details from the problem:
- **Start time or duration**
- **Operation type (addition, subtraction, multiplication, division)**
- **Relevant time units (hours, minutes, days, weeks, etc.)**
- **Any breaks, delays, or stopovers**
- **Time zone or AM/PM transitions (if applicable)**
---
### **2. Convert Time Units If Necessary**
- Ensure all units are consistent:
- **1 hour = 60 minutes**
- **1 day = 24 hours**
- **1 week = 7 days**
- Example: *A flight takes 2 hours 40 minutes. If it departs at 11:20 AM, when does it land?*
- Convert 2 hours 40 minutes → **2 hours + 40 minutes**
- **11:20 AM + 2 hours = 1:20 PM**
- **1:20 PM + 40 minutes = 2:00 PM** ✅
---
### **3. Perform the Required Calculation**
#### **A. Adding or Subtracting Time Durations**
- If adding time, move forward in hours and minutes, adjusting the day if necessary.
- If subtracting time, move backward similarly.
- Example: *A worker starts a 9-hour shift at 8:00 AM with a 45-minute lunch break. What time does the shift end?*
- **8:00 AM + 9 hours = 5:00 PM**
- **Subtract 45-minute break → 5:00 PM - 45 minutes = 4:15 PM** ✅
#### **B. Handling Multiple Time Segments (Multi-Step Computations)**
- If the task involves **multiple steps**, break it down sequentially.
- Example: *A bus departs at 6:20 AM, stops for 15 minutes every 2 hours, and takes 8 hours in total. What time does it arrive?*
- **6:20 AM + 2 hours = 8:20 AM (1st stop, 15 min)** → **8:35 AM**
- **8:35 AM + 2 hours = 10:35 AM (2nd stop, 15 min)** → **10:50 AM**
- **10:50 AM + 2 hours = 12:50 PM (3rd stop, 15 min)** → **1:05 PM**
- **1:05 PM + 2 hours = 3:05 PM (final stop, arrives)** ✅
---
### **4. Adjust for AM/PM and Day Changes**
- If the computation **crosses midnight**, adjust for the next day.
- If the time shift **crosses noon**, update AM/PM.
- Example: *A concert starts at 10:45 PM and lasts for 2 hours 10 minutes. When does it end?*
- **10:45 PM + 2 hours = 12:45 AM (next day)**
- **12:45 AM + 10 minutes = 12:55 AM** ✅
---
### **5. Format the Final Answer Correctly**
- Always present the **final answer** in an easy-to-understand format:
- **Exact time (HH:MM AM/PM or 24-hour format)**
- **Day transitions (next day, previous day, etc.)**
|
ari_date.json
|
To accurately determine the **correct date** when shifting forward or backward by a specified number of days, you should follow a **structured step-by-step approach** that ensures precision, especially when handling **month transitions, leap years, and year boundaries**.
### **1. Identify the Given Information**
- Extract the **starting date** (day, month, and year).
- Identify the **direction of shift**:
- **Addition** (moving forward in time)
- **Subtraction** (moving backward in time)
- Extract the **number of days** to be added or subtracted.
---
### **2. Perform the Date Calculation**
#### **A. Process Full Month Transitions**
- If the shift is **larger than the remaining days in the current month**, move to the **next month** and adjust the remaining days accordingly.
- Example: *Adding 40 days to April 25, 2024*
- April has **30 days** → 5 days remain in April → Move to **May 5, 2024**.
- 35 more days → Move through May (31 days) → **June 4, 2024** ✅
#### **B. Handle Year Transitions**
- If moving past **December**, increase the **year** and continue counting from January.
- If subtracting days before **January 1**, move to the **previous year** and continue counting from December.
- Example: *What is 100 days after November 10, 2025?*
- 20 days remain in **November** → Moves to December **10, 2025**
- December has **31 days** → 21 more days left → **January 1, 2026**
- 79 days remain → Move to **February 8, 2026** ✅
#### **C. Adjust for Leap Years (February Considerations)**
- If shifting into or across February, check if the **target year is a leap year**:
- **Leap year (e.g., 2024, 2028, 2032):** February **29 days**
- **Non-leap year:** February **28 days**
- Example: *Adding 15 days to February 15, 2024 (leap year)*
- February **29 days** → 14 more days → Moves to **March 1, 2024** ✅
#### **D. Calculate the Day of the Week (If Needed)**
- Determine the **day of the week** of the starting date.
- Use modular arithmetic:
\[
ext{New Day} = ( ext{Starting Day Index} + ext{Days Shift}) \mod 7
\]
- Example: *If today is Wednesday, what day will it be 45 days from now?*
- 45 mod 7 = **3** → **Wednesday + 3 days = Saturday** ✅
---
### **3. Format the Final Answer Correctly**
- Always return the **final date in DD Month YYYY format**.
- If the question asks for a **day of the week**, include that in the response.
|
ari_month.json
|
To accurately determine the correct month when shifting forward or backward by a specified number of months, the LLM should follow a **structured step-by-step approach** that ensures precision, especially when handling **year transitions, leap years, and month length variations**.
### **1. Identify the Given Information**
- Extract the **starting month** and **year** (if provided).
- Identify the **direction** (forward or backward shift).
- Extract the **number of months to shift**.
- Determine if **crossing into a new year or previous year** is required.
---
### **2. Perform the Month Shift Calculation**
#### **A. If the Shift Stays Within the Same Year**
- Move forward or backward by counting months without needing a year adjustment.
- Example: *What is 4 months after March?*
- March → April → May → June → **July** ✅
#### **B. If the Shift Crosses a Year Boundary**
- Calculate how many months remain in the **current year**.
- Adjust the **year** accordingly when moving into the next or previous year.
- Example: *What is 8 months after October?*
- October → November → December → (Next Year) January → February → March → April → **May** ✅
#### **C. If the Shift Spans Multiple Years**
- Divide the shift into **full-year cycles** (12-month increments) and the remainder.
- Example: *What month is 15 months after June 2023?*
- 12-month cycle: June 2024
- Remaining 3 months: July → August → **September 2024** ✅
---
### **3. Handle Special Cases**
#### **A. Leap Year Considerations**
- If February is involved in a shift, check if it’s a **leap year (29 days) or not (28 days)**.
- Example: *If today is December 2023, what month will it be in 2 months?*
- December → January 2024 → **February 2024** (leap year, has 29 days) ✅
#### **B. Moving Before January (Crossing into Previous Year)**
- If shifting **backward across a year boundary**, subtract remaining months from December of the previous year.
- Example: *What month is 7 months before March?*
- March → February → January → (Previous Year) December → November → October → **September (Previous Year)** ✅
#### **C. First and Last Months of a Year**
- *What is 6 months before January?*
- January → December → November → October → September → **July (Previous Year)** ✅
---
### **4. Format the Final Answer Correctly**
- If the question specifies **year**, include the updated year if applicable.
- If no year is given, assume the shift is **within a single cycle** unless explicitly stated otherwise.
|
ari_time.json
|
### **1. Identify the Given Information**
- Extract key values from the question:
- **Initial time or duration**
- **Operation type (addition, subtraction, conversion, comparison)**
- **Target time unit (e.g., hours, minutes, days, weeks, etc.)**
- If the time format includes **AM/PM**, note whether it uses a **12-hour or 24-hour system**.
---
### **2. Convert Time Units If Necessary**
- If the problem involves different time units (e.g., *weeks to days*, *hours to minutes*), convert them to a **common unit**.
- Use standard conversions:
- **1 day = 24 hours**
- **1 hour = 60 minutes**
- **1 minute = 60 seconds**
- **1 week = 7 days**
- **1 month ≈ 30 days** (unless a specific month is given)
- **1 year = 365 days** (366 for leap years)
---
### **3. Perform the Required Calculation**
- If the question involves **adding or subtracting** durations:
- Compute the result while keeping track of **AM/PM or 24-hour transitions**.
- Adjust for **date changes** if the operation crosses midnight.
- If the question involves **finding the difference between two times**:
- Break it down into **hours, minutes, and seconds** separately.
- If subtraction causes a negative value in minutes or seconds, borrow from the larger unit.
---
### **4. Format the Final Answer Correctly**
- Convert back into the **required format** (12-hour or 24-hour notation).
- If the answer crosses **midnight**, specify **next day** or **previous day** when necessary.
- If the question asks for comparison, clearly indicate **which duration is longer or shorter**.
|
ari_timezone.json
|
To ensure accurate **time zone conversions**, you should **follow a structured step-by-step approach**. Below are the reasoning steps it should take for each type of conversion:
### **1. Identify the Given Information**
- Extract the **source time zone**, **target time zone**, and the **time to convert** from the question.
- Determine if the given time includes **AM/PM** (12-hour format) or is already in **24-hour format**.
### **2. Find the Time Zone Offset**
- Determine the **UTC offsets** for both the source and target time zones.
- Consider if either location follows **Daylight Saving Time (DST)** and adjust accordingly.
### **3. Compute the Time Difference**
- Find the **time difference** between the source and target time zones:
\[
\text{Converted Time} = \text{Source Time} + (\text{UTC Offset of Target} - ext{UTC Offset of Source})
\]
### **4. Adjust for Date Transitions**
- If the conversion crosses **midnight**, adjust the **date** accordingly.
- Ensure clarity when the answer involves **the next day (tomorrow)** or **previous day (yesterday)**.
### **5. Format the Final Answer**
- Present the final time in the correct **format (12-hour or 24-hour)**.
- Include the **day transition** if applicable (e.g., *"next day"*, *"previous day"*).
|
ari_week_id.json
|
To accurately determine **week numbers**, an LLM should follow a **structured step-by-step approach** that ensures precision across different question types.
### **1. Identify the Given Information**
- Extract the **date**, **year**, and **month** from the question.
- Identify whether the task requires:
- **Week in a year** (e.g., *What week of 2025 is March 10?*)
- **Week in a month** (e.g., *What is the third week of May 2023?*)
- **Relative week computation** (e.g., *What is the week number 50 days after July 1, 2026?*)
---
### **2. Determine the Week Number Based on Context**
#### **A. If Given an Exact Date (Week of the Year)**
- Find **January 1st** of the given year and check:
- If it falls on **Monday**, Week 1 starts immediately.
- If it falls on **another day**, Week 1 might be partial, and the first full week begins on the next Monday.
- Count the **number of full weeks** from January 1st to the given date.
- If the date falls on a **Thursday or later in the first week**, it usually belongs to **Week 1**.
- If the year has **53 weeks**, check if it's valid (only happens if Jan 1 is a Thursday in a leap year).
#### **B. If Given an Exact Date (Week in a Month)**
- Identify the **first Monday of the month** to determine when Week 1 starts.
- Count **full weeks** until the given date.
#### **C. If Given a Relative Computation**
- Convert days into **weeks + extra days** to shift from the reference date.
- If adding weeks, move forward and adjust if crossing a year.
- If subtracting weeks, move backward similarly.
---
### **3. Adjust for Edge Cases**
- **Leap years:** February 29th should be handled correctly.
- **Week 53:** Only occurs if Jan 1 is a Thursday in a leap year.
- **End-of-year transitions:** Dates close to **December 31st** may belong to **Week 1 of the next year**.
---
### **4. Format the Final Answer Correctly**
- If asked for **week in a year**, return the **numeric week** (e.g., *Week 14*).
- If asked for **week in a month**, return **"First week," "Second week," etc.**
- If the question involves **relative dates**, ensure clarity on whether the answer falls in a **different year**.
|
ari_year.json
|
To accurately determine the **correct year** when shifting forward or backward by a specified number of years, you should follow a **structured step-by-step approach** that ensures precision, especially when handling **century transitions, leap years, and BC/AD shifts**.
### **1. Identify the Given Information**
- Extract the **starting year** from the question.
- Identify whether the operation requires:
- **Adding years (moving forward in time)**
- **Subtracting years (moving backward in time)**
- Identify any **special conditions**, such as:
- Leap years
- BC/AD transitions
- Century transitions
---
### **2. Perform the Year Calculation**
#### **A. Basic Addition or Subtraction**
- If moving forward:
\[
ext{New Year} = ext{Starting Year} + ext{Shift}
\]
- If moving backward:
\[
ext{New Year} = ext{Starting Year} - ext{Shift}
\]
#### **B. Handling Century Transitions**
- If the result moves from **one century to another** (e.g., 1899 → 1904), update accordingly.
#### **C. Adjusting for BC/AD Transitions**
- If shifting backward past **1 AD**, convert to **BC**:
- Example: *10 years before 5 AD → 6 BC*
- If shifting forward past **1 BC**, convert to **AD**:
- Example: *10 years after 5 BC → 6 AD*
#### **D. Leap Year Considerations**
- If the problem involves leap years, check if the **target year** is divisible by 4 (but not 100, unless also divisible by 400).
- If shifting a recurring event (e.g., **Olympics every 4 years**), ensure leap years are handled correctly.
---
### **3. Format the Final Answer Correctly**
- Ensure the result is in the **correct era** (BC or AD).
- If the year is a **historically significant one**, mention relevant implications.
|
cau_cause.json
|
The **Cause** subtask of **Temporal Causality** evaluates the ability to **identify the reason or initiating factor behind an event in a time-sensitive scenario**. This requires:
### **1. Extract the Event That Needs a Cause**
- Identify the **main event** in the question.
- Determine what needs to be explained.
---
### **2. Identify Temporal Clues**
- Look for **time-related elements** in the scenario.
- Recognize **common cause-and-effect patterns based on time progression.**
---
### **3. Compare Possible Causes and Their Plausibility**
- If multiple options exist, determine **which one directly influences the event**.
- Ignore **correlations** (things that happen at the same time but aren’t causally related).
---
### **4. Eliminate Unrelated or Misleading Options**
- Some causes may **appear relevant** but are not directly responsible for the event.
- Ensure the selected cause **follows a logical sequence** in time.
---
### **5. Select the Most Likely Cause Based on Real-World Knowledge**
- Some causes are **statistically more common** than others.
- Consider **logical causation** instead of mere association.
|
cau_effect.json
|
The **Effect** subtask of **Temporal Causality** evaluates the ability to **determine the most plausible consequence or outcome of a given cause in a time-sensitive scenario**. This requires:
### **1. Identify the Given Cause in the Question**
- Extract the **main event or situation** that serves as the cause.
- Ensure that the effect must logically stem from this cause.
---
### **2. Recognize Temporal Clues and Dependencies**
- Check for **time-sensitive effects** (*Did the effect happen immediately or after some time?*)
- Identify **short-term vs. long-term effects** (*A snowstorm may cause school closures immediately and transportation issues later.*)
- *Immediate:* People used candles and flashlights. ✅
- *Long-term:* Food in refrigerators spoiled. ✅
- *Unrelated:* The government announced new policies. ❌
- **Final Answer:** *Power outage → Immediate or delayed disruptions like loss of lighting, communication issues, or spoiled food.* ✅
---
### **3. Compare Possible Effects and Their Plausibility**
- Ensure that the effect **directly follows** from the cause.
- Reject answers that **coincide with the event but do not result from it**.
---
### **4. Eliminate Unrelated or Weakly Connected Outcomes**
- Some effects **may seem plausible** but are actually weakly linked.
- Consider **logical necessity**:
- *Did the cause make the effect unavoidable?*
- *Could the effect have happened without the cause?*
---
### **5. Select the Strongest Effect Based on Real-World Knowledge**
- Some effects are **more likely** than others.
- Consider **general knowledge and experience** (*What normally happens when an event occurs?*).
|
dur_analog.json
|
This subtask requires you to infer the duration of one event by **drawing logical comparisons** to another event with a known duration. This involves:
### **1. Identify the Given Information**
- Extract the **two events or time spans** being compared.
- Determine **whether the relationship is proportional, hierarchical, or conceptual**.
- Identify any **explicitly given duration** that serves as a reference.
- **Example:**
- *If baking cookies takes 15 minutes, how long does it take to bake a cake?*
- **Event 1:** Baking cookies → 15 minutes
- **Event 2:** Baking a cake → Unknown duration
---
### **2. Determine the Nature of the Analogy**
- **Direct Proportionality:** If event B is a **scaled version** of event A, use proportional reasoning.
- *Example: If driving 100 miles takes 2 hours, how long does 200 miles take?*
- **Double the distance → Double the time (4 hours).** ✅
- **Hierarchical Relationship:** If one event is **a part of a larger unit**, identify the corresponding equivalent.
- *Example: If a day is to a week, then an hour is to what?*
- **Answer: A day is 1/7th of a week, so an hour is 1/24th of a day.** ✅
- **Real-World Comparison:** If event durations **are not exact but commonly known**, estimate based on experience.
- *Example: If a phone battery lasts 12 hours, how long does a smartwatch battery last?*
- **A smartwatch battery typically lasts longer, around 24–48 hours.** ✅
---
### **3. Perform Necessary Calculations or Conversions**
- If time units **differ**, convert them to a **common unit** (minutes, hours, days, etc.).
- If **scaling is required**, adjust proportionally.
- **Example:**
- *If reading one book takes 10 hours, how long does reading a 5-book series take?*
- **Multiply:** 10 hours × 5 = 50 hours ✅
- **Example:**
- *If a tortoise lives 10 times longer than a dog (15 years), how long does a tortoise live?*
- **Multiply:** 15 × 10 = 150 years ✅
---
### **4. Compare and Infer the Missing Duration**
- If a **direct duration isn’t given**, estimate using a **similar or related event**.
- Consider variations in conditions (e.g., a train trip vs. a flight covering the same distance).
- **Example:**
- *If a sports season is to a year, then a single match is to what?*
- **A match is a small part of a season, just like a season is part of a year.**
- **Possible answer: A day, since matches last a few hours within a longer season.** ✅
---
### **5. Format the Final Answer Clearly**
- If **a specific duration** is required, provide it with proper units.
- If **a proportional relationship** is involved, explain it logically.
- If **an estimated range** is appropriate, mention typical values.
|
dur_calc.json
|
To accurately compute **the length of time between two points or events**, you should follow a **structured step-by-step approach** that ensures precision, especially when handling **time unit conversions, multi-step calculations, AM/PM transitions, and calendar date computations**.
### **1. Identify the Given Information**
- Extract key details from the problem:
- **Start time or date**
- **End time or date**
- **Time unit (hours, minutes, days, months, years, etc.)**
- **Any breaks, delays, or specific constraints (e.g., lunch breaks, leap years, etc.)**
---
### **2. Convert Time Units If Necessary**
- Ensure consistency in units before performing operations:
- **1 hour = 60 minutes**
- **1 day = 24 hours**
- **1 week = 7 days**
- **1 month ≈ 30 or 31 days (or 28/29 for February, depending on the year)**
- Example: *Convert 2 hours 40 minutes to minutes:*
- **2 hours × 60 minutes = 120 minutes**
- **120 minutes + 40 minutes = 160 minutes** ✅
---
### **3. Perform the Required Computation**
#### **A. If Given Start and End Time (Same Day, No AM/PM Transition)**
- If both times are within the **same AM/PM period**, simply subtract:
- Example: *A movie starts at 3:15 PM and ends at 5:45 PM. How long is the movie?*
- **5:45 PM - 3:15 PM = 2 hours 30 minutes** ✅
#### **B. If the Computation Crosses AM/PM or Midnight**
- If crossing **PM to AM (midnight),** break it into two parts:
- Example: *A train departs at 10:30 PM and arrives at 5:15 AM. How long is the journey?*
- **10:30 PM → 12:00 AM (1 hour 30 minutes)**
- **12:00 AM → 5:15 AM (5 hours 15 minutes)**
- **Total: 1 hour 30 minutes + 5 hours 15 minutes = 6 hours 45 minutes** ✅
#### **C. If Given Start and End Date (Crossing Months or Years)**
- Count the number of days in each month when shifting across months or years.
- Example: *How many days between March 15 and June 10?*
- **March 16–31** → **16 days**
- **April** → **30 days**
- **May** → **31 days**
- **June 1–10** → **10 days**
- **Total: 16 + 30 + 31 + 10 = 87 days** ✅
#### **D. If Given Multi-Step Computations (Break It Down Sequentially)**
- Example: *A student studies from 4:00 PM to 6:30 PM, takes a 15-minute break, then resumes studying until 9:15 PM. How long did they study?*
- **4:00 PM → 6:30 PM = 2 hours 30 minutes**
- **Break: 15 minutes**
- **6:45 PM → 9:15 PM = 2 hours 30 minutes**
- **Total study time: 5 hours** ✅
#### **E. If Given a Repeating Pattern (Work Schedules, Machine Cycles, etc.)**
- Multiply the duration of one cycle by the number of cycles.
- Example: *A machine runs 8 hours a day for 6 days. How many hours does it run in total?*
- **8 hours × 6 days = 48 hours** ✅
---
### **4. Adjust for Special Cases**
#### **A. Leap Year Adjustments**
- If computing durations across February, check if the year is a leap year:
- **Leap year:** February has **29 days**
- **Non-leap year:** February has **28 days**
- Example: *How many days between February 15, 2024 (leap year) and March 10, 2024?*
- **February 15–29 → 15 days**
- **March 1–10 → 10 days**
- **Total: 15 + 10 = 25 days** ✅
#### **B. Handling Century or Millennia Transitions**
- Example: *How many years between 1500 and 2023?*
- **2023 - 1500 = 523 years** ✅
---
### **5. Format the Final Answer Correctly**
- Present the final answer in a **clear and readable format**:
- **Hours and minutes:** *"2 hours 45 minutes"*
- **Days, weeks, months, years:** *"1 year 5 months 17 days"*
|
dur_common.json
|
This subtask requires you to infer the typical duration of activities, processes, or events based on everyday experience, general knowledge, and societal norms. Unlike factual duration tasks, these questions often require:
### **1. Identify the Activity or Process Being Evaluated**
- Extract the **key event, action, or process** in the question.
- Determine whether it refers to **a human activity, natural process, technological operation, or cultural practice**.
- **Example:**
- *How long does it take to brush your teeth?*
- Key event: **Brushing teeth**
- Category: **Daily human activity**
---
### **2. Recognize the Typical Duration Range**
- If the activity has a well-known typical range, retrieve it.
- If durations vary, provide **the most common or expected duration**.
- **Example:**
- *How long does it take to cook pasta?*
- Common knowledge: **Most pasta types take 8–12 minutes to cook.**
- Answer: **8–12 minutes** ✅
---
### **3. Consider Contextual Factors That Affect Duration**
- Some durations **vary based on specific conditions**. If applicable, mention the key factors.
- **Example:**
- *How long does a phone battery last?*
- Depends on:
- **Phone usage (heavy vs. light use)**
- **Battery age**
- Typical range: **12–24 hours for normal usage** ✅
- **Example:**
- *How long does it take to drive 100 miles?*
- Depends on:
- **Speed limit (e.g., city vs. highway driving)**
- **Traffic conditions**
- Answer: **1.5–2 hours at normal highway speeds** ✅
---
### **4. Convert or Compare Durations If Necessary**
- If a comparison is required, ensure both durations are in the **same unit** before evaluating.
- **Example 1: Unit Conversion**
- *Which lasts longer: a typical school year or a standard university degree?*
- Convert to the same unit:
- **School year = ~9–10 months**
- **University degree = ~3–4 years**
- Answer: **University degree is longer.** ✅
- **Example 2: Relative Comparison**
- *Which takes longer: growing a tree to maturity or raising a child to adulthood?*
- Typical durations:
- **Tree: 20–50 years**
- **Human: ~18 years to adulthood**
- Answer: **Growing a tree to maturity takes longer.** ✅
---
### **5. Account for Edge Cases and Exceptions**
- If an event **varies significantly**, state the typical range but acknowledge exceptions.
- **Example:**
- *How long does it take to learn a new language fluently?*
- **Depends on:**
- **Language complexity** (e.g., Spanish vs. Mandarin)
- **Learning method (immersion vs. part-time study)**
- **General estimate:**
- **600–2,200 hours of study** ✅
---
### **6. Format the Final Answer Clearly**
- If a **single duration is expected**, give the most common value (e.g., **8 hours of sleep per night**).
- If durations **vary**, provide a reasonable range (e.g., **2–3 minutes to brush teeth**).
- If a **comparison is required**, state which event is longer and by how much.
|
dur_comp.json
|
To accurately **compare the durations of two events or time periods**, you should follow a **structured step-by-step approach** that ensures precision, especially when handling **different time units, real-world context, and ambiguous cases**.
### **1. Identify the Given Information**
- Extract the two events or durations being compared.
- Identify the **units of time** involved (e.g., minutes, hours, days, months, years).
- Determine if the comparison is based on **fixed numerical values** or **contextual knowledge**.
---
### **2. Normalize the Time Units (If Necessary)**
- If the two durations are in different units, convert them to the same unit for comparison:
- **1 hour = 60 minutes**
- **1 day = 24 hours**
- **1 week = 7 days**
- **1 year ≈ 365 days** (or **366 days for leap years**)
- **Example:**
- *Which is longer: 10 weeks or 70 days?*
- **Convert weeks to days:**
- 10 weeks = **10 × 7 = 70 days**
- **Comparison:**
- **70 days = 70 days** → Same duration ✅
---
### **3. Determine the Real-World Context (If Applicable)**
- If the question involves everyday knowledge, retrieve the **typical durations** of each event.
- **Example:**
- *Which lasts longer: a movie or a football match?*
- **Movies typically last** 90–150 minutes.
- **Football matches typically last** 90 minutes (plus stoppage).
- **Comparison:**
- A **long movie can last longer** than a football match. ✅
---
### **4. Handle Ambiguous or Variable Durations**
- If durations **vary**, consider the **most common** or **widely accepted range**.
- If needed, specify that **some cases may differ**.
- **Example:**
- *Which is longer: a dog’s lifespan or a human childhood?*
- **Dogs live** 10–15 years (depending on breed).
- **Human childhood lasts** ~18 years.
- **Comparison:**
- **Human childhood is generally longer**, but **some large dog breeds live longer than short childhood definitions (e.g., age 12).** ✅
---
### **5. Compare the Two Durations and Determine the Answer**
- If **numerical values** are given, directly compare them.
- If **real-world knowledge is required**, use standard approximations.
- If events are **equal in duration**, state so.
- **Example 1: Numerical Comparison**
- *Which is longer: 100 hours or 4 days?*
- Convert:
- **4 days = 4 × 24 = 96 hours**
- **100 hours > 96 hours** ✅
- **Example 2: Real-World Knowledge Comparison**
- *Which is longer: a human pregnancy or an elephant pregnancy?*
- **Humans: ~9 months**
- **Elephants: ~22 months**
- **Comparison:**
- **Elephant pregnancy is much longer** ✅
---
### **6. Format the Final Answer Clearly**
- Provide a **concise, direct answer** while mentioning relevant details if needed.
- Example:
- *Which lasted longer: World War I or World War II?*
- **World War I: 4 years (1914–1918)**
- **World War II: 6 years (1939–1945)**
- **Final Answer:**
- **World War II lasted longer than World War I.** ✅
|
dur_compstep.json
|
This subtask requires you to **integrate multiple pieces of information, perform calculations where necessary, and compare final durations** to determine which is longer. This requires handling:
✅ **Breaking down complex scenarios into smaller, comparable time segments**
✅ **Performing necessary arithmetic operations before comparing**
✅ **Handling different time units and converting them if needed**
✅ **Applying contextual knowledge when precise numerical values are not provided**
---
## **🔹 Step-by-Step Reasoning Process**
### **1. Identify the Given Information**
- Extract the **two events or processes** being compared.
- Determine **whether explicit numerical values are provided** or if contextual knowledge is required.
- Identify **units of time involved** (e.g., minutes, hours, days, years).
---
### **2. Break Down Each Event into Measurable Durations**
- If explicit durations are given, convert them to a **common unit** before comparison.
- If events involve **multiple steps**, compute each step separately before summing.
- **Example:**
- *Which takes more total time in a year: commuting to work (1 hour each way, 5 days a week) or annual vacation (20 days long)?*
- Compute total **commuting time per week**:
- **1 hour × 2 (round trip) × 5 days = 10 hours/week**
- Compute total **commuting time per year**:
- **10 hours/week × 48 weeks = 480 hours**
- Convert **vacation duration to hours**:
- **20 days × 24 hours = 480 hours**
- **Comparison:**
- **Same duration (480 hours each).** ✅
---
### **3. Convert Time Units for Consistency**
- Ensure that both durations are in the **same time unit** (e.g., converting days to hours, weeks to days).
- **Example:**
- *Which is longer: 5 weeks or 40 days?*
- Convert **weeks to days**:
- **5 weeks × 7 days = 35 days**
- **Comparison:**
- **40 days > 35 days** ✅
---
### **4. Perform Multi-Step Computations Before Comparing**
- If an event consists of **multiple phases**, compute each phase separately and then sum the durations.
- **Example:**
- *A person takes a 3-hour bus ride, followed by a 2-hour layover, then a 5-hour train ride. Another person takes a direct flight that lasts 6.5 hours. Who has the longer journey?*
- Compute total travel time for **bus + layover + train**:
- **3 hours + 2 hours + 5 hours = 10 hours**
- Compare to flight duration:
- **10 hours > 6.5 hours** ✅
---
### **5. Apply Contextual Knowledge if Exact Durations Are Not Given**
- If precise durations are **not** provided, use **typical values** from real-world knowledge.
- **Example:**
- *Which lasts longer: a human childhood (from birth to adulthood) or a giant tortoise reaching maturity?*
- **Human childhood:** ~18 years
- **Tortoise maturity:** ~40 years
- **Comparison:**
- **Tortoise maturity is longer.** ✅
---
### **6. Compare the Final Durations and Determine the Answer**
- If durations are now in the **same unit**, make a direct comparison.
- If they are **equal**, state so explicitly.
- **Example:**
- *Which lasted longer: World War I or World War II?*
- **World War I: 4 years (1914–1918)**
- **World War II: 6 years (1939–1945)**
- **Comparison:**
- **World War II lasted longer.** ✅
---
### **7. Format the Final Answer Clearly**
- Provide a **concise, direct answer** with supporting reasoning.
- **Example:**
- *Which takes more time in a year: sleeping every night (8 hours) or working a full-time job (40 hours per week, 50 weeks)?*
- **Total sleep in a year:**
- **8 hours/day × 365 days = 2,920 hours**
- **Total work in a year:**
- **40 hours/week × 50 weeks = 2,000 hours**
- **Comparison:**
- **Sleeping takes more total time than working.** ✅
|
dur_fact.json
|
### **1. Identify the Given Information**
- Determine the **event or time period** mentioned in the question.
- Extract the **start year and end year** (or other relevant time markers).
- Check if the duration is **explicitly stated** or needs to be **calculated**.
- **Example:**
- *How long did World War II last?*
- Start year: **1939**
- End year: **1945**
- **Duration:** **1945 - 1939 = 6 years** ✅
---
### **2. Compute the Duration (If Needed)**
- If **start and end years are provided**, subtract to find the duration.
- If the event spans different **centuries or millennia**, adjust calculations accordingly.
- **Example 1: Simple Year Subtraction**
- *How long did the Cold War last?*
- **1947 - 1991 = 44 years** ✅
- **Example 2: Century-Spanning Calculation**
- *How long did the Middle Ages last (5th to 15th century)?*
- Convert centuries to years:
- **15th century = ~1400s**
- **5th century = ~400s**
- **1400 - 400 = ~1,000 years** ✅
---
### **3. Convert Units If Necessary**
- If the duration is provided in different time units, **convert to the requested format**.
- Common conversions:
- **1 year = 12 months**
- **1 century = 100 years**
- **1 millennium = 1,000 years**
- **Example:**
- *How long did Apollo 11 last in days?*
- **July 16–24, 1969 = 8 days** ✅
---
### **4. Compare Events If Required**
- If two or more events are given, compute each duration and compare them.
- **Example 1: Comparing Two Wars**
- *Which lasted longer: World War I or World War II?*
- **World War I: 1914–1918 = 4 years**
- **World War II: 1939–1945 = 6 years**
- **Answer: WWII lasted longer.** ✅
- **Example 2: Comparing an Empire and a Revolution**
- *Which lasted longer: the Ottoman Empire or the French Revolution?*
- **Ottoman Empire: 1299–1922 (~623 years)**
- **French Revolution: 1789–1799 (10 years)**
- **Answer: The Ottoman Empire lasted much longer.** ✅
---
### **5. Handle Edge Cases**
- If an event's **exact duration is debated**, provide the most commonly accepted range.
- If an event **did not have a clear end date**, note the uncertainty.
- **Example:**
- *How long did the Ice Age last?*
- **Various glacial periods over ~2.5 million years.** ✅
---
### **6. Format the Final Answer Clearly**
- If a direct duration is requested, return **a single number with units**.
- If comparing two events, state **which lasted longer** and by how much.
- **Example:**
- *How long did Prohibition last in the United States?*
- **1920–1933 = 13 years** ✅
|
dur_read.json
|
The **Reading Comprehension (Duration)** subtask requires you to **extract, infer, and compare durations** from a given passage. This involves:
### **1. Identify the Given Information in the Passage**
- **Locate mentions of time, duration, start/end dates, and recurring events.**
- Identify **whether the duration is explicitly stated** or **needs to be inferred.**
- **Example 1: Explicit Duration**
- **Passage:** *The Eiffel Tower was built between 1887 and 1889.*
- **Question:** *How long did the construction of the Eiffel Tower last?*
- **Extracted information:** **Start: 1887, End: 1889**
- **Duration:** **1889 - 1887 = 2 years** ✅
- **Example 2: Implicit Duration**
- **Passage:** *The music festival runs from the first weekend in June until mid-July.*
- **Question:** *How long does the music festival last?*
- **Extracted information:** **Start: early June, End: mid-July**
- **Duration:** **About six weeks** ✅
---
### **2. Determine If the Duration Needs to Be Calculated**
- If the duration is **not explicitly stated**, extract **start and end dates** and compute the difference.
- If the event is **recurring**, determine the cycle (e.g., every 4 years, annually).
- **Example:**
- **Passage:** *The Cold War began in 1947 and ended in 1991.*
- **Question:** *How long did the Cold War last?*
- **Extracted information:** **Start: 1947, End: 1991**
- **Calculation:** **1991 - 1947 = 44 years** ✅
---
### **3. Convert Time Units If Necessary**
- Convert **months to years, weeks to days, etc.**
- Recognize **time expressions like "a decade" (10 years) or "a century" (100 years).**
- **Example 1: Month-to-Year Conversion**
- **Passage:** *The mission lasted for 30 months.*
- **Question:** *How many years did the mission last?*
- **Conversion:** **30 months ÷ 12 = 2.5 years** ✅
- **Example 2: Day-to-Week Conversion**
- **Passage:** *The event lasted 21 days.*
- **Question:** *How many weeks did the event last?*
- **Conversion:** **21 days ÷ 7 = 3 weeks** ✅
---
### **4. Infer Recurring or Cyclical Durations**
- Identify **if the passage describes an event that repeats on a fixed schedule**.
- Extract **how often the event occurs** (e.g., annually, every four years).
- **Example:**
- **Passage:** *The Olympic Games are held every four years.*
- **Question:** *How often do the Olympic Games occur?*
- **Answer:** **Every 4 years** ✅
---
### **5. Compare Durations If the Question Requires It**
- Compute the duration of each event separately.
- Compare them and determine **which lasted longer or shorter**.
- **Example 1: Comparing Two Events**
- **Passage:** *The Titanic took just over two years to build, while the construction of the Empire State Building was completed in only 14 months.*
- **Question:** *Which took longer to complete: the Titanic or the Empire State Building?*
- **Extracted durations:**
- Titanic: **Over 2 years (~24+ months)**
- Empire State Building: **14 months**
- **Comparison:** **The Titanic took longer.** ✅
- **Example 2: Finding the Longer Event**
- **Passage:** *World War I lasted from 1914 to 1918, while World War II lasted from 1939 to 1945.*
- **Question:** *Which lasted longer, World War I or World War II?*
- **Extracted durations:**
- **WWI: 1918 - 1914 = 4 years**
- **WWII: 1945 - 1939 = 6 years**
- **Comparison:** **World War II lasted longer.** ✅
---
### **6. Format the Final Answer Clearly**
- **Single duration:** "The Cold War lasted **44 years**."
- **Comparison:** "World War II (**6 years**) lasted longer than World War I (**4 years**)."
- **Recurring events:** "The Olympic Games occur **every 4 years**."
|
fre_app.json
|
The **Application (Frequency)** subtask requires you to **infer event frequencies, compute intervals, and adapt to real-world constraints** based on given scenarios. This involves:
### **1. Identify the Given Information**
- Extract the **event occurrence pattern** (e.g., every 6 hours, every 3 days).
- Determine the **total time period** over which the occurrences need to be counted.
- Identify whether **external constraints** (e.g., skipped days, seasonal changes) apply.
- **Event frequency:** Every 15 minutes.
- **Total time span:** 12 hours.
- **Event frequency:** 6 days per week.
- **Total weeks per year:** 52.
---
### **2. Convert Time Units to a Common Scale (If Necessary)**
- If the event’s frequency and total time period are in **different units**, convert them to the same unit (e.g., days, hours, minutes).
- Use appropriate conversion factors:
- **1 hour = 60 minutes**
- **1 day = 24 hours**
- **1 week = 7 days**
- **1 year = 365 days (or 366 for leap years)**
- **Convert hours to minutes:** 6 × 60 = **360 minutes**.
- **Divide by frequency:** 360 ÷ 30 = **12 departures** ✅
- **Weeks in a year:** **52**.
- **Answer:** **52 occurrences per year** ✅
---
### **3. Perform the Required Computation**
- If the event **repeats at regular intervals**, use **division** to find how many times it fits in the total period.
- If a **fixed frequency per time unit** is given, use **multiplication**.
- **Total hours in 3 days:** 3 × 24 = **72 hours**.
- **Doses:** 72 ÷ 8 = **9 doses** ✅
- **2 × 12 months = 24 times** ✅
---
### **4. Adjust for External Conditions (If Applicable)**
- If the problem includes **exceptions** (e.g., closed on Sundays, holidays, skipped intervals), adjust the calculation accordingly.
- **Total weeks:** 52.
- **Open days per week:** 6.
- **Answer:** **52 × 6 = 312 days** ✅
- **Saturdays per year:** 52.
- **Subtract canceled days:** 52 - 5 = **47 market days** ✅
---
### **5. Consider Edge Cases and Partial Occurrences**
- If the event does not fit **perfectly** into the given time period, decide whether to **round up, down, or count partial occurrences**.
- **Total minutes in 9 hours:** 9 × 60 = **540 minutes**.
- **Cycles:** 540 ÷ 5 = **108 cycles** ✅
- **Weeks per year:** 52.
- **52 ÷ 3 = 17.33 meetings**.
- **Final Answer:** **17 full meetings, with an 18th starting but not completing.** ✅
---
### **6. Format the Final Answer Clearly**
- If the answer is a **whole number**, state it directly.
- If there are **exceptions, skipped occurrences, or rounding considerations**, explain them.
- **Days in 5 months:** 5 × 30 = **150 days**.
- **Production:** 500 × 150 = **75,000 units** ✅
|
fre_calc.json
|
The **Computation (Frequency)** subtask requires you to **determine how often an event occurs within a given period**. This involves:
### **1. Identify the Given Information**
- Extract the **event's occurrence pattern** (e.g., every 2 days, every week, twice a month).
- Extract the **total time span** over which occurrences need to be counted.
- Identify whether **unit conversions** are necessary.
- **Event frequency:** Weekly
- **Total time span:** 1 year (52 weeks)
- **Calculation:** **52 meetings** ✅
- **Convert hours to minutes:** 24 × 60 = **1,440 minutes**
- **Divide by event interval:** 1,440 ÷ 15 = **96 departures** ✅
---
### **2. Perform Necessary Unit Conversions**
- Convert all time measurements to the **same unit** (minutes, hours, days, weeks, months, years).
- Recognize **special cases like leap years, weeks per year, or non-standard time intervals**.
- Convert weeks to days: **12 × 7 = 84 days**
- Divide by interval: **84 ÷ 4 = 21 matches** ✅
- **Weeks per year:** 52
- **Total weeks in 5 years:** 52 × 5 = **260 weeks**
- **Multiply by event frequency:** 3 × 260 = **780 workouts** ✅
---
### **3. Compute the Number of Occurrences**
- Use **division** to find how many times an event fits within a period.
- Use **multiplication** when given a set rate (e.g., "per week").
- **Convert hours to seconds:** 1 hour = 60 × 60 = **3,600 seconds**
- **Divide by cycle duration:** 3,600 ÷ 45 = **80 cycles** ✅
- **50 ÷ 2 = 25 times** ✅
---
### **4. Handle Edge Cases and Special Situations**
- **Partial occurrences** → If an event does not fit perfectly in a time span, decide whether to round up or down.
- **Leap years** → If events occur daily, account for 366 days in leap years.
- **Fractional frequencies** → Some cases may require **estimations or mixed-unit answers**.
- **Convert years to months:** 10 × 12 = **120 months**
- **Divide by frequency:** 120 ÷ 9 = **13.3 check-ups**
- **Final Answer:** **13 full check-ups** ✅
- **Regular years:** 4 × 365 = **1,460 days**
- **Leap year contribution:** 1 × 366 = **366 days**
- **Total:** **1,826 days** ✅
---
### **5. Format the Final Answer Clearly**
- If the answer is **a whole number**, state it directly.
- If the event **partially occurs**, clarify whether to round up or down.
- If necessary, **show work to ensure clarity**.
- **100 ÷ 4 = 25**
- **Final Answer:** *25 tournaments* ✅
|
fre_common.json
|
The **Commonsense (Frequency)** subtask requires you to reason about **how often events occur in everyday life** based on general knowledge and experience. This involves:
### **1. Identify the Event and Context**
- Extract the **main event** in the question.
- Determine whether it pertains to **human activities, nature, cultural events, or biological cycles**.
- This is a **daily routine** related to hygiene.
- This is a **fixed natural phenomenon** that follows a predictable pattern.
---
### **2. Retrieve General Knowledge About the Event**
- If the event is a **daily habit**, estimate based on common routines.
- If the event is **natural or biological**, use scientific understanding.
- If the event is **social or cultural**, recognize typical scheduling patterns.
- People typically eat **three times a day** (breakfast, lunch, dinner).
- The average person blinks **15–20 times per minute**.
---
### **3. Consider Variability in Frequency**
- Some events vary based on **culture, location, age, and personal habits**.
- Provide **general trends** while acknowledging exceptions.
- In the U.S. and Europe, many drink coffee **daily**.
- Some cultures consume it **less frequently**.
- Some go **daily**, while others go **a few times per week or month**.
---
### **4. Compare Frequencies When Required**
- If the question involves **ranking or comparisons**, determine which event occurs more often.
- Brushing teeth happens **daily**, while haircuts occur **monthly**.
- **Eating (daily) > Exercising (a few times per week) > Medical check-up (annually or biannually).**
---
### **5. Adjust for Edge Cases and Approximate Answers**
- Some events **don’t follow strict schedules** (e.g., snowfall, vacations).
- If frequency **depends on conditions**, provide a range or approximation.
- **Depends on location**:
- In tropical regions: **Never**
- In temperate regions: **Annually**
- In polar regions: **Frequently**
- **About once every 2.5 years.**
---
### **6. Format the Final Answer Clearly**
- If the event has a **fixed frequency**, state it directly.
- If the event **varies**, give a range or explain the influencing factors.
- If the question is **comparative**, clearly indicate which occurs more often.
- **Once per year.** ✅
|
fre_comp.json
|
The **Comparison (Frequency)** subtask requires you to **differentiate between event frequencies**, determine **which event occurs more often**, and **rank multiple events by frequency**. This involves:
### **1. Identify the Given Information**
- Extract the **frequency of each event** from the question.
- Determine if the events have **explicit numerical frequencies** (e.g., "every 4 days") or **implied frequencies** (e.g., "full moon vs. solar eclipse").
- **Weekly meeting:** 1 occurrence per week (52 times per year).
- **Biweekly meeting:** 1 occurrence every 2 weeks (26 times per year).
- **Answer:** **The weekly meeting happens more often.** ✅
- **Full moon:** Every ~29.5 days (12–13 times per year).
- **Solar eclipse:** ~2–5 times per year.
- **Answer:** **A full moon is more frequent.** ✅
---
### **2. Convert Frequencies to a Common Unit (If Needed)**
- If the frequencies are given in **different time units**, convert them to the same unit (e.g., per year, per month).
- This is especially useful when comparing daily, weekly, and yearly occurrences.
- **Biweekly event:** Every 2 weeks = **26 times per year**.
- **Monthly event:** Once per month = **12 times per year**.
- **Answer:** **The biweekly event is more frequent.** ✅
- **Every 6 hours:** 24 ÷ 6 = **4 times per day**.
- **Three times a day:** **3 times per day**.
- **Answer:** **The every-6-hour event is more frequent.** ✅
---
### **3. Perform the Comparison or Ranking**
- If comparing **two events**, determine which occurs more frequently.
- If ranking **multiple events**, arrange them from **most to least frequent**.
- **U.S. presidential elections:** Every **4 years**.
- **Leap years:** Every **4 years**.
- **Answer:** **They occur at the same frequency.** ✅
- **Daily news:** 365 times per year
- **Weekly paycheck:** 52 times per year
- **Monthly bill:** 12 times per year
- **Annual holiday:** 1 time per year
- **Answer:** **Daily news > Weekly paycheck > Monthly bill > Annual holiday.** ✅
---
### **4. Consider Edge Cases and Special Conditions**
- Some comparisons may **seem misleading**, requiring careful interpretation.
- **"Biweekly" vs. "semi-monthly"** events occur **at the same frequency** (twice per month).
- Events with **variable recurrence rates** (e.g., earthquakes, viral trends) may require estimation.
- **Biweekly:** Once every 2 weeks → **26 times per year**.
- **Semi-monthly:** Twice per month → **24 times per year**.
- **Answer:** **The biweekly event happens slightly more often.** ✅
- **Earthquakes:** Thousands per year worldwide.
- **Volcanic eruptions:** Dozens per year worldwide.
- **Answer:** **Earthquakes are far more frequent.** ✅
---
### **5. Format the Final Answer Clearly**
- **For direct comparisons:** State which event occurs more frequently.
- **For rankings:** List the events in descending order of frequency.
- **For equal frequencies:** Clearly indicate when two events occur at the same rate.
- **Every 10 days:** 365 ÷ 10 ≈ **36.5 times per year**.
- **Three times per month:** 3 × 12 = **36 times per year**.
- **Answer:** **They occur at nearly the same frequency.** ✅
|
fre_fact.json
|
The **Facts (Frequency)** subtask requires you to recall well-documented periodic events, interpret their recurrence rate, and sometimes infer missing details based on related facts. This involves:
### **1. Identify the Given Information**
- Extract the **event being questioned** and determine whether the frequency is explicitly stated or needs to be inferred.
- Determine whether the event follows a **fixed** (e.g., "every 4 years") or **variable** schedule (e.g., "every few decades").
- The event name is clearly stated.
- The tournament is held on a **fixed cycle**.
- **Answer:** **Every 4 years** ✅
- The term **"major"** is ambiguous and must be interpreted (e.g., magnitude 7.0+).
- Major earthquakes happen **dozens of times per year**, but destructive ones are **less frequent**.
- **Answer:** **Multiple times per year, but catastrophic earthquakes are rarer.** ✅
---
### **2. Retrieve or Infer the Correct Frequency**
- If the frequency is well-documented, retrieve it directly.
- If it's an **astronomical, geological, or biological cycle**, use general scientific principles to infer the answer.
- Leap years are based on the **Gregorian calendar**.
- **Rule:** Every 4 years, except years divisible by 100 but not 400.
- **Answer:** **Every 4 years** ✅
- Comet appearances follow **orbital cycles**.
- Halley’s Comet has an **approximate recurrence of 76 years**.
- **Answer:** **Every 76 years** ✅
---
### **3. Convert and Standardize Time Units If Necessary**
- If the event's frequency is given in **a different time unit**, convert it for consistency.
- Ensure **per-minute, per-year, and per-century rates are properly compared**.
- **Average beats per minute:** 60–100 BPM.
- **Multiply by minutes per hour:** 60 × 60 = **3,600–6,000 beats per hour**.
- **Answer:** **Between 3,600 and 6,000 times per hour** ✅
- Some cicada species emerge **every 13 years**, others **every 17 years**.
- If asking over a **century**, we determine how often each cycle fits in 100 years.
- **Answer:** **Every 13 or 17 years, depending on the species.** ✅
---
### **4. Handle Events with Irregular Recurrence Patterns**
- Some events **do not have a fixed interval** (e.g., volcanic eruptions, pandemics).
- If necessary, provide an **approximate frequency** based on historical data.
- Large eruptions occur **irregularly** but typically **several times per century**.
- **Answer:** **A few per decade, with major ones every few centuries.** ✅
- There have been **two** world wars in the past **century**.
- **Answer:** **No fixed frequency; historically twice in the 20th century.** ✅
---
### **5. Compare Frequencies When Required**
- If asked to compare events, retrieve each frequency and determine **which happens more often**.
- If needed, convert different cycles into a **common unit** before comparing.
- **Solar eclipses:** ~2–5 per year worldwide.
- **Lunar eclipses:** ~2–4 per year worldwide.
- **Answer:** **They occur at similar rates, but lunar eclipses are slightly more frequent.** ✅
- **Leap years:** Every **4 years**.
- **U.S. presidential elections:** Every **4 years**.
- **FIFA World Cup:** Every **4 years**.
- **Summer Olympics:** Every **4 years**.
- **Answer:** **All occur at the same frequency (every 4 years).** ✅
---
### **6. Format the Final Answer Clearly**
- If the answer is **a fixed recurrence**, provide a direct response (e.g., *"Every 4 years."*).
- If the frequency **varies**, offer a reasonable range (e.g., *"Typically every 2 to 7 years."*).
- If comparing events, explicitly **state which is more frequent** and by how much.
- **Tides follow a lunar cycle.**
- **Answer:** *About every 6 hours (twice per day).* ✅
|
fre_read.json
|
The **Reading Comprehension (Frequency)** subtask requires you to **extract, infer, and interpret frequency-related information** from text passages. This involves:
### **1. Identify the Given Information in the Passage**
- **Locate mentions of time, frequency, or repetition.**
- Determine whether the frequency is **explicitly stated** or **implied and needs inference.**
---
### **2. Determine If the Frequency Needs to Be Calculated**
- If the frequency is **not explicitly stated**, extract **relevant dates or intervals** and compute the answer.
- If the event is **recurring**, determine the cycle (e.g., annually, every four years).
- Last seen: **1986**
- Recurrence: **Every 76 years**
- **Next appearance:** **2062** ✅
---
### **3. Convert Time Expressions If Necessary**
- Convert **months to years, weeks to days, etc.**
- Recognize **alternative phrasing for the same recurrence pattern.**
---
### **4. Infer Recurring or Cyclical Durations**
- Identify **if the passage describes an event that repeats on a fixed schedule**.
- Extract **how often the event occurs** (e.g., annually, every four years).
---
### **5. Compare and Verify Frequencies When Needed**
- Compute the duration of each event separately.
- Compare them and determine **which lasted longer or shorter**.
- **Book:** Every **5 years**
- **Magazine:** Every **1 month**
- **Comparison:** **The magazine issue is more frequent.** ✅
---
### **6. Format the Final Answer Clearly**
- **Single frequency:** "The comet appears **every 76 years**."
- **Comparison:** "The magazine publishes **more frequently** than the book edition."
- **Recurring events:** "The event occurs **twice per year**."
|
nli.json
|
### **Instructions for Step-by-Step Reasoning in Natural Language Inference (Temporal Reasoning) Tasks**
The **Temporal NLI** task requires you to **determine whether a hypothesis logically follows from a given premise when temporal elements are involved**. You must classify the relationship as one of the following:
✅ **Entailment** (*The hypothesis must be true given the premise.*)
✅ **Contradiction** (*The hypothesis must be false given the premise.*)
✅ **Neutral** (*The hypothesis may or may not be true given the premise.*)
To do this, you must:
### **1. Extract Key Temporal Information from Both Statements**
- Identify **explicit dates or times** (*"June 5," "tomorrow," "last year"*)
- Recognize **relative time expressions** (*"before," "after," "by then," "until"*)
- Pay attention to **temporal adverbs** (*"soon," "recently," "immediately"*)
---
### **2. Identify and Compare Temporal Relations**
- Determine if the **time order in the premise aligns with the hypothesis.**
- Look for **conflicting statements** (*"before" vs. "after"*)
- Consider **event duration** (*"The war lasted five years" vs. "The war ended quickly"*)
---
### **3. Evaluate Whether the Hypothesis is Certain, Impossible, or Unclear**
- **Entailment:** If the hypothesis **must be true** based on the premise
- **Contradiction:** If the hypothesis **directly conflicts** with the premise
- **Neutral:** If the hypothesis **is possible but not guaranteed**
---
### **4. Resolve Ambiguous or Implicit Temporal Expressions**
- Some words are **vague** and need **context interpretation**:
- *"soon" = how soon?*
- *"recently" = how recent?*
- *"later" = later today or in years?*
---
### **5. Select the Correct NLI Label**
- If the **hypothesis must be true** → **Entailment** ✅
- If the **hypothesis is false given the premise** → **Contradiction** ❌
- If the **hypothesis could be true but is not necessarily true** → **Neutral** 🤷♂️
|
ord_common.json
|
The **Commonsense (Ordering)** subtask requires you to **logically sequence everyday events** based on general knowledge and real-world experience. This involves:
### **1. Identify the Two or More Events and Their Nature**
- Extract the **key events** from the question.
- Determine whether the events relate to **daily routines, natural processes, cause-effect relationships, or life sequences**.
- **Event A:** Eating breakfast
- **Event B:** Going to work
- **Nature:** **Daily routine**
- **Event A:** Turning on the faucet
- **Event B:** Water coming out
- **Nature:** **Cause-effect**
---
### **2. Retrieve General Knowledge or Life Experience**
- If the event is **a daily habit**, recall common scheduling patterns.
- If the event follows a **natural order**, determine how it typically occurs.
- If the event follows **a logical progression**, assess dependencies between steps.
- Some people brush their teeth **before** breakfast.
- Others brush their teeth **after** breakfast.
- **Conclusion:** *The order varies depending on personal habits.* ✅
- A caterpillar **must form a cocoon first** before emerging.
- **Conclusion:** *Forming a cocoon happens before becoming a butterfly.* ✅
---
### **3. Determine the Logical or Chronological Order**
- If **one event logically depends on the other**, determine which must happen first.
- If **both events occur independently**, check which one typically happens first.
- If **order is variable**, acknowledge the ambiguity.
- **Step 1:** A seed must be placed in the soil first.
- **Step 2:** Watering happens after the seed is planted.
- **Conclusion:** *Planting a seed happens first.* ✅
- **Some people shower before breakfast, some after.**
- **Conclusion:** *There is no single correct answer.* ✅
---
### **4. Verify If the Given Order is Possible, Impossible, or Undetermined**
- If the sequence is **realistic**, confirm it as valid.
- If the sequence is **impossible**, reject it.
- If the sequence **depends on context**, classify it as "undetermined."
- **Yes, people generally put on socks before shoes.**
- **Conclusion:** *Correct order.* ✅
- **No, because elementary school comes first.**
- **Conclusion:** *Impossible order.* ❌
- **Some drink coffee before brushing, some after.**
- **Conclusion:** *Order is variable.* ⚠️
---
### **5. Consider Cultural, Geographic, or Situational Differences**
- Some sequences vary by **region, culture, or personal preference**.
- If multiple valid sequences exist, acknowledge the variation.
- **Globally:** Lunch comes before dinner.
- **In Spain:** Dinner is eaten very late (9–11 PM), sometimes after an evening snack.
- **Conclusion:** *Lunch usually comes before dinner, but late dinners exist in some cultures.* ✅
- **Yes, if they work while studying.**
- **No, if a degree is required for the job.**
- **Conclusion:** *Depends on the job and education requirements.* ⚠️
---
### **6. Format the Final Answer Clearly**
- If the event **definitely occurs first**, state it plainly.
- If the order **depends on context**, acknowledge variations.
- If the events **can happen in either order**, explain why.
- **Sunrise happens before sunset.** ✅
- *Can someone get a driver’s license before learning how to drive?*
- **No, because learning is required first in most places.** ❌
- *Does a person eat lunch before or after going to work?*
- **Before, if they work in the evening.**
- **After, if they work in the morning.**
- **Conclusion:** *Depends on work schedule.* ⚠️
|
ord_fact.json
|
The **Facts (Ordering)** subtask requires you to **accurately sequence historical events in chronological order** based on factual knowledge. This involves:
### **1. Identify the Events and Their Historical Context**
- Extract the key **events** mentioned in the question.
- Determine whether the question asks for **pairwise comparison, full chronological arrangement, or sequence verification**.
- Recognize **whether the events belong to politics, science, culture, technology, or wars/conflicts**.
- **Event A:** U.S. Declaration of Independence
- **Event B:** French Revolution
- **Context:** Both are political revolutions.
- **Event A:** Einstein’s theory of relativity
- **Event B:** Apollo 11 moon landing
- **Context:** One is a scientific discovery, the other is a space mission.
---
### **2. Retrieve the Exact or Approximate Dates of Each Event**
- If the events have **exact dates**, retrieve them.
- If the events **occurred over a period of time**, find their general timeframe.
- If the events **are recurring**, determine the first occurrence or pattern.
- **World War I:** **1914–1918**
- **Great Depression:** **1929–late 1930s**
- **Conclusion:** *World War I happened before the Great Depression.* ✅
- **Industrial Revolution:** **Began in the late 18th century (around 1760s–1800s, continuing into the 19th century).**
- **French Revolution:** **1789–1799**
- **Conclusion:** *The Industrial Revolution started before the French Revolution but overlapped with it.* ✅
---
### **3. Compare and Arrange the Events in Order**
- If one event has a **clearly earlier** date, place it first.
- If two events **overlap**, explain the overlap but maintain sequence.
- If one event **depends on another**, sequence them logically.
- **Renaissance:** **14th–17th century**
- **Industrial Revolution:** **18th–19th century**
- **World War II:** **1939–1945**
- **Conclusion:** *Renaissance → Industrial Revolution → World War II* ✅
- **U.S. Civil War:** **1861–1865**
- **Abolition of slavery in the U.S.:** **1865 (13th Amendment)**
- **Conclusion:** *The U.S. Civil War happened first, leading to the abolition of slavery.* ✅
---
### **4. Verify If a Given Sequence is Correct, Incorrect, or Undetermined**
- If the order **is correct**, confirm it.
- If the order **is incorrect**, explain the correct sequence.
- If the order **is uncertain or varies by context**, provide clarification.
- **World War I:** **1914–1918**
- **Great Depression:** **1929**
- **World War II:** **1939–1945**
- **Conclusion:** *Incorrect. World War I happened first, followed by the Great Depression, then World War II.* ❌
- **Electricity was studied since the 17th century, with key discoveries in the 18th century (e.g., Benjamin Franklin’s experiments in the 1750s).**
- **The telephone was invented in 1876 (Alexander Graham Bell).**
- **Conclusion:** *Electricity was discovered before the telephone.* ✅
---
### **5. Consider Dependencies and Cause-Effect Relationships**
- Some events are **logically dependent** on others.
- Determine if one event **directly influenced** another.
- **American Revolution:** **1775–1783**
- **French Revolution:** **1789–1799**
- **Conclusion:** *Yes, the American Revolution influenced the French Revolution.* ✅
- **Light bulb (Thomas Edison):** **1879**
- **First powered flight (Wright brothers):** **1903**
- **Conclusion:** *The light bulb was invented before the first powered flight.* ✅
---
### **6. Format the Final Answer Clearly**
- If the events **must be ordered**, list them in sequence.
- If the order **depends on context**, clarify exceptions.
- If an event **overlaps with another**, explain the relationship.
- **The Renaissance (14th–17th century) happened before the Industrial Revolution (18th–19th century).** ✅
- *Arrange these in order: First World War, Second World War, Cold War.*
- **World War I (1914–1918) → World War II (1939–1945) → Cold War (1947–1991).** ✅
- *Was the Internet invented before or after the first moon landing?*
- **The first moon landing (1969) happened before the development of the modern Internet (ARPANET, early 1970s).** ✅
|
rel.json
|
The **Relation** task requires you to **determine the temporal relationship between two events or between an event and a specific time**. This involves:
### **1. Identify the Events or Time Expressions in the Context**
- Locate the two **key entities** (events or time expressions).
- Check whether the entities are **explicitly** mentioned or **implicitly** inferred.
- **Event 1:** *"John submitted his report."*
- **Event 2:** *"Deadline."*
- **Relation Keyword:** *"before."*
- **Final Answer:** **The report submission happened BEFORE the deadline.** ✅
- **Event:** *"The battle occurred."*
- **Time Reference:** *"1945."*
- **Final Answer:** **The battle OCCURRED IN 1945.** ✅
---
### **2. Determine Explicit Temporal Cues**
- Check for **direct** temporal indicators like:
- BEFORE / AFTER / DURING / AT / BY / UNTIL
- EARLIER / LATER / SHORTLY / IMMEDIATELY
- Match the **relation word** with the appropriate temporal logic.
- **Temporal Cue:** *"before."*
- **Event 1:** *"The storm ended."*
- **Event 2:** *"Rescue team arrived."*
- **Final Answer:** **The storm ended BEFORE the rescue team arrived.** ✅
- **Temporal Cue:** *"By the time."*
- **Event 1:** *"Sarah arrived."*
- **Event 2:** *"Meeting started."*
- **Final Answer:** **The meeting started BEFORE Sarah arrived.** ✅
---
### **3. Infer Implicit Relations (When No Direct Cues Exist)**
- If no explicit words like "before" or "after" appear, infer the relation from **logical sequencing** or **causal links**.
- **Inference:** Locking the door usually happens BEFORE leaving.
- **Final Answer:** **Locking the door happened BEFORE leaving the house.** ✅
- **Inference:** The whistle signals the start of the game.
- **Final Answer:** **The whistle happened IMMEDIATELY BEFORE the game started.** ✅
---
### **4. Distinguish Between Fine-Grained Temporal Relations**
- Some relations require more **precision**:
- BEFORE vs. IMMEDIATELY BEFORE
- AFTER vs. SHORTLY AFTER
- DURING vs. OVERLAP
- Consider the **time gap** between events.
- **Relation:** **BEFORE** (unspecified gap).
- *"The bell rang, and the students immediately left."*
- **Relation:** **IMMEDIATELY BEFORE** (no delay).
- **Relation:** **OVERLAP (two events happening at the same time).**
- *"The festival lasted during the entire summer."*
- **Relation:** **DURING (event confined within a timeframe).**
---
### **5. Verify Logical Consistency & Contradictions**
- If one event happens **before** another, the second event **cannot happen before the first**.
- If an event **is ongoing**, another event **cannot have happened before it ended**.
- **Contradiction Detected.**
- **Correction:** One of the statements must be false.
- **If the class had already finished, then she must have arrived AFTER it ended.**
- **Final Answer:** **She arrived AFTER the class finished.** ✅
---
### **6. Resolve Ambiguous Time References**
- If the temporal relation is unclear, consider:
- **Contextual clues** (*Does "later" mean minutes or hours later?*)
- **Multiple possible interpretations** (*Does "midnight" belong to today or tomorrow?*)
- **Possible Interpretations:**
- **Later today.**
- **Later in the week.**
- **Final Answer:** *Ambiguous—clarification needed.* ⚠️
- **Possible Interpretations:**
- **Friday 12:00 AM (start of Friday).**
- **Friday 11:59 PM (end of Friday).**
- **Final Answer:** *Likely refers to 12:00 AM, but confirmation is needed.* ⚠️
|
sto.json
|
The **Storytelling** task evaluates the ability to **predict the most appropriate ending for a story based on temporal reasoning**. This involves:
### **1. Identify the Sequence of Events in the Story**
- Extract the **main events** leading up to the missing ending.
- Determine the **order in which they occurred**.
- *She set her alarm.*
- *She needed to wake up early.*
- *The alarm rang in the morning.*
- **Final Answer:** *The most logical next event is that she wakes up and gets ready for her meeting.* ✅
---
### **2. Identify Explicit and Implicit Temporal Cues**
- Look for **time markers** (*"yesterday," "tomorrow," "a few minutes later"*)
- Recognize **event dependencies** (*A late-night study session usually leads to morning exhaustion.*)
- *"Evening" → Night is approaching.*
- *"Overnight" → Rain is expected at night.*
- *"Midnight" → Rain has started.*
- **Final Answer:** *By morning, the streets were flooded.* ✅
---
### **3. Predict the Most Logical Consequence**
- Determine **what naturally follows** from the events.
- Consider **cause-and-effect relationships** (*"He missed the bus" → "He arrived late to work."*)
- *What happens after plants grow taller?*
- **Final Answer:** *Eventually, ripe tomatoes appeared on the vines.* ✅
---
### **4. Eliminate Implausible or Illogical Endings**
- Remove endings that:
- **Contradict** the earlier events (*"He missed the train" → "He arrived on time." ❌*)
- **Introduce irrelevant information** (*"She set an alarm" → "She went to the park." ❌*)
---
### **5. Select the Ending That Best Matches the Temporal Flow of Events**
- Ensure the chosen ending **maintains logical continuity** with the story.
- The ending should **feel like a natural next step** in the timeline.
|
typ_common.json
|
The **Commonsense (Typical Time)** subtask requires you to **reason about the usual timing of events in daily life** based on general knowledge and experience. This involves:
### **1. Identify the Event and Context**
- Extract the **main event** from the question.
- Determine whether it pertains to **daily routines, seasonal changes, cultural traditions, or social behaviors**.
- This is a **daily habit** related to mealtimes.
- This is a **natural phenomenon** linked to **seasonal cycles**.
---
### **2. Retrieve General Knowledge About the Event**
- If the event is a **daily activity**, recall common scheduling patterns.
- If the event is **seasonal or cultural**, use general societal norms.
- If the event is **regional**, consider variations across locations.
- Most working people and students wake up **between 6 AM and 8 AM**.
- In colder climates, people start wearing coats in **late autumn (October–December)**.
---
### **3. Consider Variability Based on Geography and Culture**
- Some events vary **by country, climate, or tradition**.
- If there are **regional differences**, the answer should acknowledge them.
- In the **U.S. and U.K.**, dinner is usually **between 6–8 PM**.
- In **Spain**, dinner is often **between 9–11 PM**.
- **U.S.:** Around **7–9 AM**.
- **Japan:** Around **8:30 AM**.
---
### **4. Compare and Differentiate Related Events**
- If the question involves **relative time comparisons**, determine which event typically happens earlier or later.
- **Schools** generally start earlier (**7–9 AM**).
- **Work** typically starts around **8–10 AM**.
- **Answer:** *School usually starts earlier than work.* ✅
- **Daily:** Some buy groceries **after work or in the evening (5–7 PM)**.
- **Weekly:** Many people shop on **weekends (Saturday/Sunday mornings).**
---
### **5. Adjust for Edge Cases and Exceptions**
- Some events **don’t have strict schedules** but occur within a common timeframe.
- Consider **weekend vs. weekday habits, urban vs. rural settings, and age-related factors**.
- **Weekdays:** **6–8 AM**
- **Weekends:** Later, usually **8–10 AM**
- Some start **at midnight**, while others queue **from early morning (5–6 AM).**
---
### **6. Format the Final Answer Clearly**
- If the event has a **fixed time range**, state it directly.
- If the event **varies**, provide a reasonable range or acknowledge influencing factors.
- If comparing two events, **explicitly indicate which occurs earlier or later**.
- **Between 10 PM and midnight.** ✅
|
typ_comp.json
|
The **Comparison (Typical Time)** subtask requires you to **determine which of two events typically occurs earlier or later in a sequence** based on general knowledge, daily routines, cultural norms, and natural patterns. This involves:
### **1. Identify the Two Events in the Question**
- Extract both **Event A** and **Event B** from the question.
- Determine whether the question asks for **which event happens first, which happens later, or a general comparison of their timing**.
- **Event A:** Sunrise
- **Event B:** Breakfast
- **Event A:** Easter (March/April)
- **Event B:** Halloween (October 31st)
---
### **2. Retrieve General Knowledge About Each Event’s Typical Timing**
- If the event is a **daily routine**, determine the usual time it occurs.
- If the event is **seasonal or annual**, check when it typically takes place.
- If the event **varies by region or culture**, note the common global pattern.
- **Morning commute:** **7–9 AM**
- **Lunch break:** **12–1 PM**
- **Conclusion:** *The morning commute happens earlier.* ✅
- **Independence Day (USA):** **July 4**
- **Christmas:** **December 25**
- **Conclusion:** *Independence Day happens first in the year.* ✅
---
### **3. Compare the Timing of the Two Events**
- If one event **clearly occurs before the other**, state the order.
- If the timing **depends on context**, provide a general pattern while noting exceptions.
- **Home-cooked dinner:** **6–8 PM**
- **Restaurant dinner:** **7–10 PM (people usually eat out later)**
- **Conclusion:** *Restaurant dinners typically happen later.* ✅
- **College lectures:** **Often start at 8 AM**
- **Work shifts:** **Often start at 9 AM**
- **Conclusion:** *College lectures usually start earlier than work shifts.* ✅
---
### **4. Consider Variability Based on Geography, Culture, and Context**
- Some events occur at **different times in different places** (e.g., sunrise varies by season and location).
- Some events follow **different cultural norms** (e.g., dinner time in Spain vs. the U.S.).
- **U.S. breakfast:** **6–9 AM**
- **Spain breakfast:** **8–11 AM**
- **Conclusion:** *Breakfast in the U.S. typically happens earlier.* ✅
- **Cherry blossoms:** **Spring (March–April in the Northern Hemisphere)**
- **Leaves changing color:** **Autumn (September–November in the Northern Hemisphere)**
- **Conclusion:** *Cherry blossoms bloom earlier in the year than leaves changing color.* ✅
---
### **5. Handle Edge Cases and Tricky Situations**
- Some events **don’t have fixed timings**, so the answer may depend on interpretation.
- If two events **happen simultaneously in some cases**, clarify the typical pattern.
- Consider **exceptions or special cases** that might affect the answer.
- **Birds chirping:** **Often at dawn (~5–6 AM).**
- **Streetlights turning off:** **Also around dawn, depending on sensors.**
- **Conclusion:** *Birds typically start chirping **before** streetlights turn off.* ✅
- **New Year’s Eve countdown:** **Exactly at midnight (December 31st).**
- **Sunrise:** **Much later (typically 5–7 AM).**
- **Conclusion:** *New Year’s Eve countdown happens at midnight, while sunrise occurs hours later.* ✅
---
### **6. Format the Final Answer Clearly**
- If one event **definitely occurs before the other**, state it plainly.
- If the timing **depends on context**, acknowledge variations.
- If the events **overlap or vary widely**, provide a general trend.
- **Sunrise:** **Between 5–7 AM, depending on season and location.**
- **Morning meetings:** **Typically start at 8–10 AM.**
- **Conclusion:** *Sunrise usually happens before the first morning meeting.* ✅
|
typ_fact.json
|
The **Facts (Typical Time)** subtask requires you to **identify the specific time or period when historical or well-documented events occurred**. This involves:
### **1. Identify the Event and Its Category**
- Extract the **main event** from the question.
- Determine whether the event falls into one of these categories:
- **Historical event (one-time occurrence):** (*When did the Titanic sink?*)
- **Recurring event (fixed cycle):** (*When are the Winter Olympics held?*)
- **Natural or cultural event (variable cycle):** (*When does Ramadan begin?*)
- **Category:** **Historical event**
- **Fixed date:** **1989**
- **Category:** **Annual event**
- **Typical date:** **December 10**
---
### **2. Retrieve the Exact or Typical Timing**
- If the event has a **specific historical date**, provide it.
- If the event follows a **fixed cycle**, determine its recurrence pattern.
- If the event **varies**, describe its usual range.
- **Fixed date:** **September 2, 1945**
- **Fixed cycle:** **Every four years, first Tuesday of November**
- **Shifts yearly based on the Islamic lunar calendar**
---
### **3. Adjust for Recurring or Shifting Dates**
- If the event **happens on a regular schedule**, determine the interval.
- If the event **depends on external factors (e.g., moon cycles, climate)**, explain the variation.
- **Every four years**, usually in **July or August**
- **Varies between January 21 and February 20**, based on the lunar calendar
- **Between March and April**, depending on the climate
---
### **4. Compare the Relative Order of Events (If Needed)**
- If the question involves **two events**, determine which happened first.
- Compare their **historical years or periodic cycles**.
- **Telephone:** **1876 (Alexander Graham Bell)**
- **Radio:** **1895 (Guglielmo Marconi)**
- **Conclusion:** *The telephone was invented before the radio.* ✅
- **FIFA World Cup:** **Every 4 years**
- **Halley’s Comet:** **Every ~76 years**
- **Conclusion:** *The FIFA World Cup happens much more frequently than Halley’s Comet.* ✅
---
### **5. Consider Edge Cases and Unusual Timing**
- Some events **don’t follow strict schedules** (e.g., pandemics, natural disasters).
- If the event was **delayed, rescheduled, or interrupted**, acknowledge the exception.
- **Normally:** Every four years (2020 should have been the year).
- **Exception:** **Postponed to 2021 due to COVID-19.**
- **About every 2.5 years**, based on lunar cycles.
---
### **6. Format the Final Answer Clearly**
- If the event has a **fixed date**, state it directly.
- If the event is **recurring**, describe its cycle.
- If the event **varies**, provide a general timeframe.
- If the event is **comparative**, explicitly state which happened first or occurs more frequently.
- **July 20, 1969** ✅
- *When do presidential inaugurations occur in the U.S.?*
- **January 20, every four years** ✅
- *When does the Atlantic hurricane season start?*
- **June 1st** ✅
|
typ_read.json
|
The **Reading Comprehension (Typical Time)** subtask requires you to **extract, interpret, and infer time-related information** from a given passage. This involves:
### **1. Identify the Key Time-Related Information in the Passage**
- Locate **explicit time references** (years, months, centuries, specific dates).
- Determine if the **timing is stated directly** or **must be inferred from context**.
1. Identify the event: *Berlin Wall falling*.
2. Find the explicitly mentioned year: *1989*.
3. **Final Answer:** *1989* ✅
1. Identify Apollo 11’s event: *Moon landing*.
2. Identify the relative time reference: *A year before Woodstock*.
3. Recall that Woodstock took place in *1969*.
4. Subtract one year: *1969 - 1 = 1968*.
5. **Final Answer:** *1969* ✅ (Correction: Apollo 11 landed on July 20, 1969.)
---
### **2. Determine if the Time Reference Needs Conversion**
- Convert **centuries to years** (*The 18th century → 1700s*).
- Convert **relative time expressions** into absolute values (*"Three years after 2010" → 2013*).
- Adjust for **seasonal references** (*"Winter Olympics" → typically in February*).
1. Identify the given time reference: *14th century*.
2. Convert to a specific range: *1300s–1400s*.
3. **Final Answer:** *14th century (1300s)* ✅
1. Identify the relative timing: *241 years before 2017*.
2. Subtract: *2017 - 241 = 1776*.
3. **Final Answer:** *1776* ✅
---
### **3. Differentiate Between One-Time and Recurring Events**
- Determine whether the event **only happened once** (*"When did the Titanic sink?" → April 15, 1912*) or **repeats regularly** (*"When is the Summer Olympics held?" → Every four years*).
- If the event **recurs**, determine its **frequency and next occurrence**.
---
### **4. Handle Ambiguous or Approximate Time References**
- If the passage does **not provide an exact date**, determine the **most reasonable timeframe**.
- Use **historical context** to infer the closest possible date.
1. Identify the time reference: *No exact date given*.
2. Recognize historical context: *Industrial Revolution began in late 18th century*.
3. **Final Answer:** *Late 1700s to early 1800s* ✅
1. Identify the event: *Halley’s Comet appearance*.
2. Recognize its cycle: *Every 76 years*.
3. Add 76 to the last appearance: *1986 + 76 = 2061*.
4. **Final Answer:** *2061* ✅
---
### **5. Format the Final Answer Clearly**
- If the event has **a single exact date**, provide it.
- If the event **repeats**, state the cycle and next occurrence.
- If the date **is inferred**, explain the reasoning.
- **July 20, 1969** ✅
- *When does the U.S. presidential election occur?*
- **Every four years, on the first Tuesday of November** ✅
- *When did the Roman Empire fall?*
- **476 AD** ✅
|
README.md exists but content is empty.
- Downloads last month
- 7