Hugging Face's logo

Datasets:
JasonYan777
/
PersonaSignal-PersonaQuestions-Locale-And-Time-Zone-gpt-5

Modalities:
Text
Formats:
parquet
Languages:
English
Size:
< 1K
Tags:
curator
Libraries:
Datasets
pandas
License:
Dataset card Data Studio Files
xet
 Community
Dataset Viewer
Auto-converted to Parquet Duplicate
dimension_name
stringclasses
1 value
dimension_values
listlengths
10
10
dimension_description
stringclasses
1 value
question
stringlengths
64
180
why_differ
stringlengths
113
259
how_subtle
stringlengths
84
214
sampled_value
stringclasses
9 values
num_distractors
int64
5
5
ground_truth_persona
stringlengths
114
298
distractor_personas
listlengths
5
5
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Plan a one-week meal prep schedule for next month that fits a standard office workweek and uses produce that’s in season, including when to shop and batch-cook.
Seasonality and weekend rhythms vary by locale and hemisphere, shifting which ingredients feel ‘peak’ and whether shopping happens on one or two weekend days. Some personas favor Monday-start planning and place heavier prep before or after a typical rest day.
Variation appears in which days anchor the plan, how shopping vs. cooking is sequenced, and the kinds of produce and cooking methods emphasized (cooler- vs. warmer-weather), not in named holidays or regional terms.
US Eastern
5
An office worker living in Boston with a standard 9–5 schedule. Uses a 12-hour clock, MM/DD dates, and US customary units like cups and ounces. Plans to shop on the weekend and batch-cook, using locally in-season produce next month.
[ "An office worker living in Seattle with a standard 9–5 schedule. Uses a 12-hour clock, MM/DD dates, and US customary units. Plans to shop on the weekend and batch-cook, using West Coast seasonal produce next month.", "An office worker based in London with a standard 9–5 schedule. Uses 24-hour time, DD/MM dates, ...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Suggest three feasible 90-minute time windows to host a virtual workshop that can include participants across North America, Europe, and East Asia without running too late locally.
Each persona balances overlap differently based on their own local evenings and early mornings, nudging windows toward times that are less disruptive for them. Daylight-saving observance changes the perceived ‘comfortable’ overlap bands.
Differences show up as favored windows (e.g., early morning vs. late evening) and justification about sleep-friendly choices, not explicit time-zone names or offsets.
US Pacific
5
A coordinator based in San Francisco on the U.S. West Coast. Plans virtual events with participants from North America, Europe, and East Asia. Uses a 12-hour clock and month/day/year dates.
[ "An organizer in New York on the U.S. East Coast. Coordinates meetings across North America, Europe, and East Asia. Uses a 12-hour clock and month/day/year dates.", "A facilitator in London. Arranges sessions with colleagues from North America, Europe, and East Asia. Uses 24-hour time and day/month/year formattin...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Design a weekly review-and-planning ritual with deep-work blocks, check-ins, and a light wrap-up, and say which day to start the cycle.
Some personas naturally start the week on different days and cluster check-ins early or late in the week. Local work norms shape whether deep work is morning- or afternoon-led and when the wrap-up fits best.
Cues emerge from which weekday anchors the sequence and how time-of-day focus is distributed, rather than overt references to calendars or regions.
India
5
A professional based in Bengaluru on a standard Monday–Friday schedule. Plans in local IST and uses day–month–year dates with 24-hour times. Wants a clear weekly cadence with deep-work blocks, brief check-ins, and a light end-of-week wrap-up.
[ "A professional in New York on a Monday–Friday workweek. Schedules in Eastern Time and prefers a 12-hour clock with month–day–year dates. Wants a practical weekly cadence with deep work blocks, short check-ins, and a light wrap-up.", "A London-based professional on a standard Monday–Friday routine. Uses UK busine...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
I’m starting a morning running routine next month. Recommend start times to avoid heat or darkness and how to adjust over the month.
Sunrise timing and typical temperatures differ across locales and seasons, shifting whether pre-dawn, dawn, or post-work slots are safest and most pleasant. Some personas also account for humidity or monsoon-like patterns.
The answer’s timing emphasis (e.g., ‘after first light’ vs. ‘before it warms up’) and gradual adjustments reveal locale-aware reasoning without naming places or showing formatted times.
EU Central
5
A casual runner living in Munich planning to start morning runs next month. Uses 24-hour time, day–month dates, and Celsius for weather checks. Schedules around local sunrise and civil twilight.
[ "An early riser in San Diego planning to begin morning runs next month. Uses the 12-hour clock, month–day dates, and Fahrenheit for weather. Schedules by local West Coast sunrise and twilight.", "A runner in Leeds starting a morning routine next month. Uses 24-hour time, day–month dates, and Celsius. Plans around...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Propose a posting schedule for a personal blog and social channels that reaches local audiences during commute and lunch breaks on weekdays.
Commuting and meal-time patterns vary by region, so optimal posting windows slide earlier or later. Some personas favor a single midday post, others a morning-and-evening cadence based on local habits.
Signals appear in which windows are recommended and how they’re prioritized (morning commute vs. late evening scroll), not in explicit clock formats or city references.
EU Central
5
A personal blogger living in Berlin, coordinating posts for readers across Germany and nearby countries. Uses 24-hour time and follows CET/CEST. Wants weekday posts to align with local commuter windows and lunch hours.
[ "A personal blogger based in San Francisco, planning updates for a West Coast audience. Uses 12-hour time and follows PST/PDT. Seeks weekday posting times that match local commute and lunch breaks.", "A personal blogger in London focusing on local readers. Uses 24-hour time and observes GMT/BST. Aims to schedule ...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
I want to follow a live international sports tournament on weeknights without sacrificing sleep. Help me pick which matches to watch live and which to catch as replays.
Depending on locale, live events may land in the small hours or early evenings, changing which slots are ‘sane’ to watch. Personas with no daylight-saving shifts may see consistency, whereas others plan around upcoming clock changes.
The plan’s selection criteria and sleep-protective windows reveal local time pressures, not direct mentions of time zones or event branding.
UK
5
A sports fan living in Manchester who uses the 24-hour clock and day–month–year dates. Works a standard Monday–Friday schedule and aims to be asleep by 23:00 local and up around 06:30. Wants help choosing which weeknight matches to watch live versus as replays to avoid losing sleep.
[ "A sports fan in Seattle who uses the 12-hour clock and month–day–year dates. Works a standard Monday–Friday schedule, aims to be asleep by 11:00 pm local and up around 6:30 am. Wants guidance on which weeknight matches to watch live versus as replays to maintain sleep.", "A sports fan near New York who uses the ...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Outline a six-week care plan for balcony plants that balances watering with typical daylight and rain patterns, and avoids overwatering.
Season and climate conventions differ, so some personas will space watering farther apart during cooler, wetter periods, while others plan morning waterings to beat sustained heat. Daylength trends affect timing recommendations.
Differences show in cadence and time-of-day preferences and references to ‘cooler mornings’ or ‘afternoon dryness,’ not explicit climate labels or geographical names.
US Eastern
5
A balcony gardener in Boston who checks local sunrise times and weekly rainfall forecasts. Uses the 12-hour clock, mm/dd dates, and imperial measurements. Keeps herbs and compact ornamentals in containers and wants a clear six-week routine to avoid overwatering.
[ "A balcony gardener in San Francisco planning care around cool mornings, coastal fog, and mild afternoons. Uses the 12-hour clock, mm/dd dates, and imperial measurements. Grows container herbs and flowers and checks a weather app to time watering.", "A balcony gardener in London who plans around long daylight and...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Recommend two humane weekly slots for a recurring check-in that includes teammates on the US west coast and in India, explaining the trade-offs.
Based on the assistant’s locale, they may nudge toward early-morning or late-evening compromises that feel less disruptive locally. DST vs. non-DST regions shift which overlaps are most comfortable over time.
Personalization emerges in which compromise windows are favored and how the trade-offs are framed, not in stating specific zone abbreviations or offsets.
Australia
5
A remote professional in Melbourne who schedules around local business hours. Uses 24-hour time, day-month-year dates, metric units, and accounts for AEST/AEDT shifts. Keeps a straightforward calendar without unusual constraints.
[ "Works from San Francisco and plans meetings within local business hours. Uses a 12-hour clock, month/day/year dates, and observes PST/PDT. Keeps scheduling simple without special constraints.", "Based in New York and organizes days around standard office hours. Uses a 12-hour clock, month/day/year dates, and obs...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Help me choose a consistent two-hour focus window each workday next week that minimizes interruptions and aligns with natural alertness.
Local norms for quiet hours and post-lunch lulls vary; some personas lean toward early-morning deep work, others late afternoon, influenced by typical daylight and meal timing. Heat or power-peak hours can also shift preferences.
Cues are in the chosen time-of-day and rationale (e.g., before the day ‘spools up’ vs. post-lunch dip avoidance), not explicit time stamps or regional markers.
US Eastern
5
A professional working standard Monday–Friday office hours in New York City. Uses the 12-hour clock and plans around local business hours. Looking to set a consistent two-hour focus block during the workday.
[ "A professional working standard Monday–Friday office hours in Seattle. Uses the 12-hour clock and plans around local West Coast business hours. Looking to set a consistent two-hour focus block during the workday.", "A professional based in London with a standard Monday–Friday office routine. Uses the 24-hour clo...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
I’m timing a few wardrobe basics purchases this month to catch typical seasonal markdowns without waiting too long. When would you shop?
End-of-season cycles differ by hemisphere and retail culture, so personas suggest earlier or later windows for discounts. Some anticipate mid-season clearances or month-end promotions based on local patterns.
The advice’s timing logic (early vs. late month, pre- vs. post-season turnover) signals locale without naming specific holidays or sale events.
Africa
5
Based in Johannesburg and planning wardrobe basics purchases around local end-of-season sales. Uses day–month–year dates, a 24-hour clock, and ZAR pricing. Shops both local chains and regional e-commerce, aiming not to wait past typical clearance periods.
[ "Lives in New York and times clothing buys to typical U.S. end-of-season markdowns. Uses month–day–year dates, 12-hour time, and USD pricing. Shops national retailers online and in-store, aiming to catch discounts without missing sizes.", "Based in London and plans wardrobe basics around high-street end-of-season...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
I’m taking a course with weekly office hours at 18:00 UTC. Outline when to attend live versus watch replays and how to structure prep and review.
18:00 UTC lands at very different local times, making live attendance easy for some personas and impractical for others. DST changes reconfigure what counts as a reasonable live slot.
Subtlety is in whether live attendance is encouraged and the surrounding prep windows chosen, not in listing conversions or zone labels.
Japan
5
An online learner on a UTC+9 schedule. Uses a 24-hour clock, the metric system, and YYYY/MM/DD dates; currency is yen. Follows a Monday–Friday routine.
[ "An online learner on a UTC−5/−4 schedule. Uses a 12-hour clock, the imperial system, and MM/DD/YYYY dates; currency is dollars. Follows a Monday–Friday routine.", "An online learner on a UTC±0/±1 schedule. Uses a 24-hour clock and DD/MM/YYYY dates; currency is pounds, measures mostly metric. Follows a Monday–Fri...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Plan a Saturday housecleaning sprint around a lazy breakfast and a mid-afternoon commitment, with smart sequencing to avoid backtracking.
Local daylight and typical afternoon rhythms influence whether heavier tasks are front-loaded or delayed. Some personas assume later shop hours for supply runs, others keep everything before mid-afternoon.
Variation appears in task ordering and pacing relative to the afternoon anchor, not in explicit clock formats or locale cues.
US Pacific
5
Lives in a small one-bedroom apartment in Seattle. Enjoys a lazy Saturday breakfast and has a mid-afternoon appointment to catch. Uses 12-hour times and US-style dates, and wants a smart, no-backtracking cleaning sequence.
[ "Lives in a small one-bedroom apartment in Boston. Enjoys a lazy Saturday breakfast and has a mid-afternoon appointment to catch. Uses the 12-hour clock and month/day/year dates, and wants a smart, no-backtracking cleaning sequence.", "Lives in a small one-bedroom apartment in London. Enjoys a lazy Saturday break...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
I’ll have a four-day weekend next month and will host friends one evening. Propose menus and prep timing that keep cooking light and seasonal.
Which part of the month aligns with lighter or heartier foods varies by locale and season. Personas may place the hosting night earlier or later depending on when markets are fresher or days are cooler.
Differences show via the seasonal lean of menus and which day is chosen for hosting, not through named holidays or regional dishes.
US Pacific
5
A home cook in Oakland, California, planning an evening get-together during a long weekend next month. Shops West Coast farmers markets, uses 12-hour time, month/day dates, and cups/ounces. Prefers light, seasonal dishes with minimal hands-on cooking.
[ "A home cook in Boston planning an evening with friends over a long weekend next month. Shops Northeast farmers markets, uses 12-hour time, month/day dates, and cups/ounces. Prefers light, seasonal dishes and easy prep.", "A home cook near London planning a relaxed evening with friends during a bank-holiday weeke...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Set quarterly maintenance reminders for the next year—filters, decluttering, backups—so they avoid awkward weeks and time shifts.
Personas in DST regions aim to dodge clock-change weeks and end-of-year crunches, while non-DST locales spread tasks evenly. Fiscal-year timing can influence which quarter feels busier.
Cues come from which weeks are avoided or favored and the rationale given, not from naming local observances or specific date formats.
US Eastern
5
A person living in New York who keeps a digital calendar. Uses the MM/DD date format and 12-hour time with AM/PM. Wants quarterly reminders that steer clear of the local clock-change weeks in March and November.
[ "A resident of Seattle who keeps a digital calendar. Uses the MM/DD date format and 12-hour time. Wants quarterly reminders that avoid the local daylight saving switch weeks in March and November.", "Someone based in London who keeps a digital calendar. Uses 24-hour time and day–month–year dates. Wants quarterly ...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Propose an ideal daily rhythm for deep work, meetings, exercise, and errands that aligns with when shops tend to stay open later and when outdoor light is best.
Late-opening retail evenings and daylight patterns vary across locales and seasons, shifting errands to specific days and moving exercise to morning vs. evening. Heat patterns also affect outdoor timing.
The plan’s placement of errands and workouts by day and time-of-day carries the signal without naming local customs or hours.
EU Central
5
A remote worker based in Berlin who follows CET/CEST and uses the 24-hour clock. Uses euros and the metric system. Local shops typically stay open until around 20:00–22:00 on weekdays, with limited Sunday trading.
[ "A remote worker based in New York who follows ET and uses the 12-hour clock. Uses US dollars and imperial measurements. Local shops commonly stay open late, often until 21:00–22:00, with regular Sunday hours.", "A remote worker based in London who follows GMT/BST and comfortably uses the 24-hour clock. Uses poun...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Suggest three after-work time slots for a small online meetup that would maximize local attendance yet end early enough for family time.
Typical workday end times and dinner hours differ, so recommended windows drift earlier or later. Some personas avoid very late starts due to early starts the next day; others are comfortable with later evening slots.
Personalization shows in which evening windows are proposed and how ‘early enough’ is reasoned, not in explicit clock notation.
EU Central
5
A professional based in Berlin. Keeps a standard 9:00–17:30 workday, uses 24-hour time, and schedules in CET/CEST.
[ "A professional based in San Francisco. Keeps a standard 9-to-5 workday, uses the 12-hour clock, and schedules in Pacific Time (PT/PDT).", "A professional based in London. Works typical office hours, uses 24-hour time, and plans around GMT/BST.", "A professional based in Bengaluru. Keeps a standard workday, use...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Create a two-week dinner rotation using peak-fresh ingredients and schedule cooking to avoid running the oven during the hottest parts of the day.
Heat and seasonal availability vary by locale, pushing oven-heavy meals to cooler nights in some places and lighter stovetop options elsewhere. Sunset timing affects when ‘hottest part’ occurs.
Signals appear in meal types and whether cooking is slated for earlier or later, not in mention of regional produce names.
Australia
5
A home cook in Sydney, where summer afternoons run hot; schedules any oven use after sunset and does prep in the early morning. Uses AEST/AEDT, day-month-year dates, Celsius, and metric measurements. Buys peak-season local produce.
[ "Cooking from Los Angeles, where summer afternoons are scorching, so avoids oven use mid-day and bakes after 8 pm or at dawn. Uses PT (PST/PDT), month-day-year dates, Fahrenheit, and US customary units. Buys peak-season local produce.", "Based in London with mild mornings and occasional hot spells in the afternoo...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
I need to place three international calls this week—to New York, Tokyo, and Berlin. Propose respectful windows for each and suggest an order across the week.
Personas weigh their own local comfort alongside the other cities, preferring windows that avoid extreme early/late locally. DST differences shift which days and times feel most balanced.
Cues come from which windows are chosen and the sequencing across the week, not from explicit conversions or zone acronyms.
Africa
5
A professional working from Nairobi, Kenya (UTC+3). Uses the 24-hour clock and day-month-year dates. Plans calls during standard local weekday business hours.
[ "A professional in Seattle, Washington (UTC−8 in winter, UTC−7 in summer). Uses the 12-hour clock and month-day-year dates. Plans calls during standard local business hours.", "Working from London, England (UTC+0 in winter, UTC+1 in summer). Uses the 24-hour clock and day-month-year format. Schedules within typic...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
I’m setting a morning routine for the darker months to get natural light at the right time and keep sleep steady. What would you change as the season progresses?
The onset and intensity of darker months vary by latitude and hemisphere, altering when to seek light exposure and whether to bias activity earlier or later. DST transitions can also affect morning light timing.
The advice’s shifting emphasis on light-timing and minor schedule nudges betrays locale, without naming places or showing date formats.
US Pacific
5
Lives on the U.S. West Coast, planning mornings around local sunrise in cities like Seattle or San Francisco. Uses a 12-hour clock and observes the daylight saving time shifts in early November and mid-March. Aims to keep sleep steady while adjusting morning light exposure through fall and winter.
[ "Based in New York on the East Coast. Uses a 12-hour clock and follows the U.S. daylight saving changes in early November and mid-March. Wants to keep a consistent sleep routine while timing morning light through fall and winter.", "Lives in England and plans mornings by local sunrise. Uses a 24-hour clock and ob...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Suggest a simple weekly home energy plan that avoids peak-rate hours for major appliances without being inconvenient.
Peak hours and their severity vary by region, pushing heavy usage earlier morning, mid-day, or late evening. Some personas also account for seasonal load patterns.
Differences surface as preferred appliance windows and justifications about comfort vs. cost, not explicit tariff names or regional utilities.
Australia
5
A renter in Melbourne following AEST/AEDT. On a time-of-use electricity plan where weekday late afternoon and evening are pricier, with cheaper overnight hours. Prefers a simple weekly routine using 24-hour times and kWh.
[ "Lives in Seattle on PST/PDT. Time-of-use plan has higher weekday late-afternoon/evening rates and cheaper overnight hours. Uses 12-hour time and kWh.", "Based in London observing GMT/BST. Tariff offers off-peak overnight (akin to Economy 7/10) and higher early-evening weekday rates. Uses 24-hour time and kWh.", ...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Help me pick two 45-minute windows each day this week to exercise outdoors without heat or glare.
Local sunrise/sunset and daily temperature patterns vary by region and season, shifting the safest and most comfortable windows. The assistant will prioritize early or late slots differently based on typical daylight and heat where the user is.
Differences show up as earlier dawn or later dusk preferences and brief notes about warmth or brightness, not explicit references to place or climate names.
US Eastern
5
Lives in the New York City area. Uses a 12-hour AM/PM clock and month/day date format. Plans outdoor activity around local sunrise/sunset and checks the local forecast.
[ "Based in the Seattle area. Uses a 12-hour AM/PM clock and month/day date format. Plans outdoor time by local sunrise/sunset and checks the local forecast.", "Lives in London. Uses a 24-hour clock and day/month date format. Times outdoor exercise by local sunrise/sunset and the local weather outlook.", "Lives i...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
I’m hosting a 60-minute live webinar for a mixed audience; propose three start times that balance reach and presenter alertness.
Local time zones shape which hours feel alert for the host and how they overlap with other regions’ waking hours. The assistant will choose different anchor times that preserve the host’s energy while offering global coverage.
Variation appears in the chosen local-hour clusters and reasoning about overlap windows, without naming any regions or time zones outright.
US Pacific
5
A webinar host located in San Francisco on the U.S. West Coast. Uses a 12-hour clock and schedules in local time, observing daylight saving shifts. Aims to reach North America, Europe, and Asia while avoiding extreme hours.
[ "Based in New York on the U.S. East Coast. Plans in local time with a 12-hour clock and accounts for daylight saving. Wants broad international reach without hosting at very late or very early hours.", "A host in London coordinating global audiences. Uses local UK conventions, often a 24-hour clock, and switches ...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Draft a morning routine that fits typical work hours and allows for a calm commute.
Customary workday start times and traffic peaks differ across locales. The assistant’s suggested wake, prep, and departure times shift to align with local rhythms.
Cues come from the routine’s clock times and buffer recommendations, not from explicit mentions of cities or transport systems.
India
5
A professional in Bengaluru with a typical 9:30–6 office schedule. Uses 12-hour time and follows a calendar without daylight saving changes. Commutes by metro or rideshare and wants to time departures to miss the heaviest traffic.
[ "A professional in New York City with a standard 9–5 office schedule. Uses 12-hour time and adjusts for EST/EDT daylight saving. Relies on the subway and wants to avoid the brunt of the morning rush.", "A professional in London working roughly 9–5. Uses 24-hour time and observes GMT/BST changes. Takes the Tube an...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Schedule recurring weekly focus blocks for the next quarter; I want them at the start of the week.
The definition of the week’s first day differs, changing which day the blocks land on. Some conventions also affect how week numbering aligns within a quarter.
The placement of the block and subtle references to week structure reveal the convention without naming weekdays or standards.
EU Central
5
A professional based in Central Europe operating on CET/CEST. The week starts on Monday and they use the 24-hour clock. Dates are written in day-month-year.
[ "A professional based on the U.S. West Coast operating on PT (PST/PDT). The week starts on Sunday and they use the 12-hour clock with AM/PM. Dates are written in month/day/year.", "A professional based on the U.S. East Coast operating on ET (EST/EDT). The week starts on Sunday and they use the 12-hour clock with ...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Plan errands for the weekend so I avoid crowds and closed doors.
Weekend shopping patterns and opening practices differ; some places see reduced hours or closures on one weekend day. The assistant will bias toward specific days and times to avoid issues.
The answer shifts the recommended day and timing with gentle caveats about busy periods, not explicit references to local laws.
EU Central
5
Lives in Munich and plans weekend errands around local shop hours. Uses 24-hour time, metric units, and euro pricing. Knows most stores are closed on Sundays and that Saturday midday tends to be busiest.
[ "Based in Seattle and scheduling in local time. Uses the 12-hour clock and is used to retailers open seven days a week, including Sundays. Knows Saturdays and Sunday afternoons draw the biggest crowds.", "Living in Leeds and following local trading hours. Uses 24-hour time and expects Sunday opening with shorter ...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
I have a live sports final this weekend; help me watch without wrecking sleep and still catch the key moments.
Local broadcast timing may be prime time or very late/early. The assistant adapts with strategies like naps, highlight focus, or normal evening routines.
Sleep and viewing strategies implicitly reveal whether the match is aligned with evening hours or off-hours, without naming locations or leagues.
UK
5
Lives in Leeds and plans weekend viewing around local GMT/BST. Uses the 24-hour clock and day-month-year dates. Wants to watch an international sports final live without sacrificing sleep.
[ "Based near Seattle and schedules around Pacific Time. Uses the 12-hour clock with month-day-year dates. Hopes to catch a weekend championship game live while keeping a solid sleep schedule.", "Living in Berlin and operating on Central European Time (CET/CEST). Uses the 24-hour clock and day-month-year dates. Aim...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Set up a two-month study plan that finishes by 03/06 with weekly checkpoints.
Different date-order conventions lead to interpreting the target as early March or early June. The backward plan, pacing, and milestone placement will reflect that interpretation.
Only the scheduling structure and the final-week range expose the date reading; no explicit discussion of format standards is needed.
US Eastern
5
An online learner based in New York who schedules in Eastern Time. Uses the U.S. month/day date format and a 12-hour clock. Follows U.S. conventions for calendars, currency, and measurements.
[ "An online learner in San Francisco who schedules in Pacific Time. Uses the U.S. month/day date format and a 12-hour clock. Follows U.S. conventions for calendars, currency, and measurements.", "An online learner in London who schedules on local UK time. Uses day/month date format and a 24-hour clock. Follows UK ...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Recommend Do Not Disturb hours that protect sleep but still allow early calls when necessary.
Typical quiet hours and early-call feasibility vary with local norms and daylight. The assistant balances bedtime and early availability differently.
The exact start/end times and mention of exception windows reveal local expectations without naming time zones.
Australia
5
A remote worker in Melbourne who keeps a standard 9–5 schedule locally. Occasionally accepts early-morning calls with other regions. Plans in AEST/AEDT, uses day-first dates and the 24-hour clock.
[ "A professional in Boston keeping a typical 9–5 workday. Sometimes needs to take early calls with other time zones. Schedules in ET and uses the 12-hour clock with month-first dates.", "Works from London on a standard office-day routine. May take occasional early calls with overseas teams. Uses GMT/BST, day-first...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Design calendar templates for meetings: headers, date format, and time stamps that feel natural.
Preferred date ordering, clock style, and week layout vary by locale. The assistant will choose formats that align with local conventions.
Conventions emerge through formatting choices (order, separators, clock), not through explicit statements about regions.
US Eastern
5
Works from New York on standard office projects. Uses a 12-hour clock with AM/PM and month-first dates (MM/DD/YYYY). Labels times as ET.
[ "Works from Seattle on standard office projects. Uses a 12-hour clock with AM/PM and month-first dates (MM/DD/YYYY). Labels times as PT.", "Works from London on standard office projects. Uses a 24-hour clock and day-first dates (DD/MM/YYYY). Labels times as GMT or BST.", "Works from Berlin on standard office pr...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Suggest the best times to send important emails to get replies the same day.
Workday rhythms and lunch times differ, shaping peak responsiveness windows. The assistant will prioritize different morning or afternoon slots.
The recommendation’s time bands and sequencing hint at local habits without naming any country or schedule standard.
Africa
5
An office professional based in Nairobi, Kenya. Works regular local business hours Monday–Friday. Uses the 24-hour clock, day–month–year dates, and plans around East Africa Time.
[ "An office professional based in New York, USA. Works regular local business hours Monday–Friday. Uses the 12-hour clock with month/day/year dates and follows Eastern Time.", "An office professional in London, UK. Works regular local business hours Monday–Friday. Uses a 24-hour clock with day–month–year dates and...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Outline a pre-work news check that covers markets and headlines efficiently in 15 minutes.
Which market sessions intersect with morning varies by time zone. The assistant will alter the order and timing of checks around local openings and overnight developments.
The sequence and emphasis (overnight recap vs pre-open preview) hint at locale without naming specific exchanges.
Japan
5
An office professional in Tokyo starting work early. Uses a 24-hour clock and writes dates as YYYY/MM/DD; comfortable with yen prices and local holidays. Follows the Nikkei 225, TOPIX, and Asia-Pacific market moves before overseas sessions.
[ "A professional in New York beginning the day before the opening bell. Prefers a 12-hour clock and MM/DD/YYYY dates; thinks in US dollars. Checks S&P 500, Dow, and Nasdaq futures with pre-market headlines.", "A London-based professional working the local morning. Uses a 24-hour clock, DD/MM/YYYY dates, and prices...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Plan a monthly maintenance hour for household tasks so it rarely lands on a holiday.
Holiday distributions and typical nonworking days differ, affecting which weekdays are safest. The assistant will bias scheduling to avoid local clusters of closures.
Advice to prefer certain weekdays or offsets from period boundaries conveys local patterns without naming specific holidays.
US Pacific
5
Lives on the U.S. West Coast and plans by local time (PST/PDT), observing U.S. federal and state holidays like Presidents’ Day and Thanksgiving. Uses month/day date format and 12-hour AM/PM time. Wants a recurring monthly household maintenance hour that rarely conflicts with local holidays.
[ "Lives on the U.S. East Coast and plans by ET (EST/EDT), observing U.S. federal and state holidays. Uses month/day date format and 12-hour AM/PM time. Wants a recurring monthly household maintenance hour that rarely conflicts with local holidays.", "Based in the UK and schedules by local time (GMT/BST), observing...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
I tend to run in the evening; suggest safer timing and hydration strategy for the hot months.
Evening heat and humidity profiles vary; some places need later starts, others earlier. The assistant adjusts timing, shade-seeking, and fluid strategy accordingly.
Shifts in recommended start windows and caution emphasis appear without explicit climate or location labels.
US Pacific
5
A recreational evening runner based near San Diego on the West Coast. I plan runs after work using a 12-hour clock, think in miles, and follow temperatures in Fahrenheit. Looking for safer timing and hydration ideas for summer and early-fall heat waves.
[ "An evening runner living in Atlanta on the East Coast. I schedule runs after work using a 12-hour clock, track miles, and watch Fahrenheit heat alerts. Seeking safer timing and hydration during humid summer months.", "An evening runner in Manchester. I use a 24-hour clock, track kilometres, and watch Celsius for...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Propose a posting schedule for a weekly newsletter so it reaches readers fresh in the morning.
Local morning routines and email-check habits vary, as do weekend norms. The assistant will suggest different days and hours to maximize freshness.
The day-of-week and hour choices signal local routines subtly, avoiding explicit locale references.
US Eastern
5
A newsletter editor living in New York with a standard Monday–Friday routine. Uses month/day date formatting and 12-hour times. Wants weekly emails to land in inboxes early morning local time.
[ "A newsletter editor in San Francisco with a typical weekday routine. Uses month/day dates and 12-hour times. Wants deliveries timed for early morning in their area.", "A newsletter editor based in London with a standard workweek. Uses day/month dates and 24-hour times. Prefers the send to arrive early morning lo...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Help me block quiet hours for deep work that won’t collide with routine deliveries or building maintenance.
Common delivery and maintenance windows differ by region and building norms. The assistant will position deep-work blocks to sidestep local disturbance patterns.
The timing rationale mentions typical windows in general terms, revealing patterns without naming providers or places.
EU Central
5
A remote professional based in Berlin, planning in CET/CEST and comfortable with 24-hour times. Lives in an apartment where routine parcel drops arrive late morning and building maintenance is usually mid-morning on weekdays.
[ "A remote professional in Seattle who schedules in PT/PDT and uses the 12-hour clock. Lives in an apartment where routine parcel drops arrive late morning and building maintenance is usually mid-morning on weekdays.", "A remote professional in New York working on ET/EDT and using the 12-hour clock. Lives in an ap...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
I need two 30-minute grocery runs this week; schedule them to minimize lines.
Store lull times differ across locales due to lunch, evening, or weekend behaviors. The assistant selects different off-peak windows accordingly.
Recommendations focus on narrowly timed windows with brief justifications that imply local rhythms without naming them.
EU Central
5
Based in Berlin and planning errands in CET/CEST. Prefers the 24-hour clock and day–month–year dates. Uses euros and metric measurements. Looking to time two quick supermarket runs this week to avoid lines.
[ "Located in Portland, Oregon, and schedules around Pacific Time (PST/PDT). Uses the 12-hour clock with month/day/year dates. Pays in US dollars and uses miles and pounds for measures. Wants two short grocery trips this week timed to avoid lines.", "Living in London and planning around UK time (GMT/BST). Comfortab...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Create reminders for biweekly team meetings and adjust automatically around any clock changes.
Some regions shift clocks seasonally while others do not. The assistant may add buffer notes or automation around those changes, or omit them entirely.
Inclusion or absence of DST-related precautions hints at locale without explicitly naming the practice.
Australia
5
Works from Sydney and schedules in AEST, switching to AEDT during daylight saving. Uses day–month–year dates and 24-hour time. Needs biweekly team reminders that automatically adjust when local clocks change.
[ "Based in New York, following EST and shifting to EDT for daylight saving. Uses month–day–year dates and the 12-hour clock. Needs biweekly meeting reminders that auto-adjust to local clock changes.", "Works in London, operating on GMT and moving to BST in summer. Uses day–month–year dates and 24-hour time. Expect...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Plan a Saturday afternoon gathering in a public park: when should I start to catch comfortable light?
Sun angle, temperature, and sunset vary by place and season, shifting the ideal start time. The assistant balances warmth and daylight differently.
The start-time recommendation and light comfort reasoning subtly reflect local daylight patterns without place names.
Africa
5
A Nairobi-based weekend planner who schedules activities in East Africa Time. Uses a 24-hour clock, metric measurements, and day–month–year dates. There’s no daylight saving shift to account for when picking times.
[ "Plans weekend outings around Seattle, following Pacific Time with seasonal PST/PDT changes. Uses a 12-hour AM/PM clock and US month/day/year dates. Comfortable with miles and Fahrenheit.", "Organizes plans from London, aligned with GMT/BST. Typically uses the 24-hour clock, metric units, and day–month–year dates...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Set a daily writing slot that aligns with my lowest chance of interruption at home.
Household and neighborhood quiet periods vary; in some places early mornings are calm, others have midafternoon lulls. The assistant’s chosen slot reflects local patterns.
The suggested hour and justification reference general quiet trends rather than any location-specific facts.
US Pacific
5
Lives in Portland, Oregon, and keeps a regular 9–5 workday from home. Uses the 12-hour clock and MM/DD/YYYY dates. Plans around local West Coast holidays and daylight saving changes.
[ "Lives in Boston and follows a standard 9–5 routine on the East Coast. Uses the 12-hour clock and MM/DD/YYYY dates. Schedules around local US holidays and Eastern daylight saving shifts.", "Based in Leeds with UK business hours and GMT/BST changes. Uses the 24-hour clock and DD/MM/YYYY dates. Keeps a steady weekd...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
I have a standing call with someone eight hours away; propose a stable time that works year-round.
Seasonal clock shifts can change the relative offset for some, but not all, regions. The assistant will either build in seasonal adjustments or choose a resilient window.
The plan’s inclusion of seasonal caveats or a fixed compromise window implies local clock practices without naming them.
Australia
5
A remote worker in Sydney coordinating across regions. Uses day/month/year dates, 24-hour time, and follows AEST/AEDT daylight saving. Keeps standard weekday availability.
[ "A consultant in San Francisco coordinating with global teams. Uses the 12-hour clock and month/day/year dates, observing PST/PDT daylight saving. Keeps standard weekday availability.", "A project coordinator in New York working with multiple time zones. Uses the 12-hour clock with month/day/year dates and observ...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Draft a four-week meal prep plan that avoids long cooking at the hottest times.
Peak heat windows differ regionally and seasonally. The assistant will choose morning or late-evening prep based on local temperature patterns.
Timing preferences and brief heat-avoidance notes communicate context without explicit geographic cues.
EU Central
5
A home cook based in Berlin, planning around Central European Time (CET/CEST). Uses a 24-hour clock, dd.mm.yyyy dates, and metric measurements. Wants a four-week meal prep plan that avoids long cooking during late-afternoon heat, preferring morning or evening prep.
[ "Lives on the U.S. West Coast and schedules around Pacific Time (PST/PDT). Uses a 12-hour clock, mm/dd/yyyy dates, and Fahrenheit/imperial measurements. Wants a four-week meal prep plan that keeps long cooking away from the hottest mid-to-late afternoon hours.", "Based in England and follows UK time (GMT/BST). Us...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
I want my personal week to start with planning; place a 90-minute review at the start of each week.
The start of the week differs by convention, affecting where the review lands. The assistant aligns it to the user’s local norm.
The placement alone reveals the convention, without naming the weekday or any locale.
Australia
5
Works from Sydney. Uses AEST/AEDT, 24-hour time, and DD/MM/YYYY dates, with Monday as the start of the week. Maintains a standard digital calendar.
[ "Works from San Francisco. Uses PT (PST/PDT), 12-hour time and MM/DD/YYYY dates, with Sunday as the start of the week. Maintains a standard digital calendar.", "Works from London. Uses GMT/BST, prefers 24-hour time and DD/MM/YYYY dates, with Monday as the start of the week. Maintains a standard digital calendar."...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Choose quiet hours to read on public transport without crowding.
Peak commute patterns differ, with earlier or later rushes depending on norms. The assistant will pick windows that miss local peaks.
The selected times subtly track local rush-hour shapes without explicit references to transit systems.
Japan
5
A commuter in Tokyo who rides the JR and Tokyo Metro most days. Uses 24-hour time and follows JST. Wants guidance on the calmest travel windows to read without crowds.
[ "A commuter in New York City who rides the subway most days. Uses 12-hour time and follows EST/EDT. Wants guidance on the calmest travel windows to read without crowds.", "A commuter in London who rides the Tube most days. Uses 24-hour time and follows GMT/BST. Wants guidance on the calmest travel windows to read...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Set a recurring monthly reminder near salary credit so I adjust budgets promptly.
Common pay timing differs (start, mid, or end of month). The assistant places reminders to match local payroll norms.
The suggested offset from period boundaries implies local pay cycles without naming currencies or employers.
EU Central
5
Lives in Munich, operating on CET/CEST. Uses 24-hour time and day-first dates (dd/mm/yyyy), budgeting in euros. Salary is usually credited near month-end and they keep a standard weekday schedule.
[ "Lives in Seattle, on PT (PST/PDT). Uses 12-hour time and month-first dates (mm/dd/yyyy), budgeting in US dollars. Salary usually posts near month-end, with a standard weekday routine.", "Based in New York, on ET (EST/EDT). Uses 12-hour time and mm/dd/yyyy dates, budgeting in USD. Salary tends to arrive near the ...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Give me three options for a 75-minute lunch workout that won’t clash with typical break times.
Lunch timings vary; some regions break earlier, others later. The assistant’s windows avoid the local lunch peak.
Proposed start times subtly indicate lunch culture without explicit cultural labels.
Brazil
5
Based in São Paulo with a standard office schedule. Uses 24-hour time and day/month date formats. Wants three 75-minute lunchtime workout options that avoid the usual local lunch rush.
[ "Located in San Francisco and working a typical office schedule. Uses 12-hour time with AM/PM and month/day dates. Wants three 75-minute lunch workout options that steer clear of the usual noon crowd.", "Based in London with a standard office routine. Uses 24-hour time and day/month dates. Looking for three 75-mi...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Help me plan a weekly call with family in two different continents so I’m not up past my bedtime.
The user’s evening aligns differently with other regions depending on local time and clock shifts. The assistant anchors to comfortable local hours with feasible overlap.
The chosen local-hour windows and any seasonal notes convey context without naming time zones.
Africa
5
Based in Nairobi, keeps East Africa Time and uses 24-hour clocks with day–month–year dates. Planning a weekly family call across two continents and wants to avoid staying up late.
[ "Lives in Seattle, follows Pacific Time with 12-hour clocks and month–day–year dates. Organizing a weekly family call across two continents and wants to avoid late nights.", "Located in Manchester, follows UK time (GMT/BST), uses 24-hour clocks and day–month–year dates. Planning a weekly family call across two co...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
I’m preparing a timeline for a release on the first business day next month; sketch key checkpoints.
Local holiday and weekend patterns affect which day counts as the first business day and how to stage preceding checkpoints.
Checkpoint placement and buffers imply the underlying calendar without listing specific holidays.
India
5
A project coordinator in Bengaluru who works a standard Monday–Friday schedule and observes local public holidays. Plans in IST (UTC+5:30) with day-month-year dates and 24-hour time. Budgets in rupees and uses metric units when estimating.
[ "Based in New York, follows a typical Monday–Friday office rhythm and local public holidays. Schedules in Eastern Time (ET) and prefers MM/DD/YYYY with a 12-hour clock. Uses US dollars and imperial measures when relevant.", "Working from London with a standard Monday–Friday cadence and local bank holidays. Operat...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Suggest a bedtime window that balances early light exposure and social time.
Sunrise and evening activity norms vary, changing optimal bedtimes. The assistant balances wake quality and social availability differently.
The bedtime recommendation shifts subtly with rationale about light and routines, not place names.
US Pacific
5
Lives in Seattle with a standard 9-to-5 workday. Uses the 12-hour clock and month/day date format common locally. Wants a bedtime window that supports stepping outside soon after local sunrise while leaving room for evening social plans.
[ "Based in New York City with a typical 9-to-5 schedule. Uses the 12-hour clock and month/day date format. Seeks a bedtime window that enables morning light exposure after local sunrise while preserving time for social evenings.", "Living in London and working regular office hours. Uses the 24-hour clock and day/m...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Create a simple travel day checklist for a morning departure with minimal lines.
Airport peak patterns and security timing vary locally. The assistant adjusts target arrival time and prep steps to match typical morning congestion.
Arrival buffers and sequencing reveal local expectations without naming airports or agencies.
UK
5
A traveler living in London who plans mornings around local GMT/BST. Prefers 24-hour times like 06:00 and writes dates as 18/03/2025. Uses local conventions when noting travel details.
[ "A traveler based in New York operating on EST/EDT. Uses the 12-hour clock (e.g., 6:00 AM) and writes dates as 03/18/2025. Follows U.S. conventions for travel notes.", "A traveler in Berlin on CET/CEST. Uses 24-hour times (e.g., 06:00) and writes dates as 18.03.2025. Follows continental European conventions.", ...
locale_and_time_zone
[ "US Pacific", "US Eastern", "UK", "EU Central", "India", "China Mainland", "Japan", "Brazil", "Australia", "Africa" ]
Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.
Propose a calendar color and label scheme for personal events, with week numbers for the next 6 weeks.
Week numbering and first-day conventions differ across locales. The assistant’s labels and counts reflect local standards.
Subtle differences in week labels and numbering emerge through the scheme, without citing standards or regions.
Japan
5
Lives in Tokyo and plans personal events in UTC+9. Uses Monday-start weeks, 24-hour time, and dates like 2025/11/03, with week numbers shown. Uses an English interface and prefers a simple color-coded personal calendar.
[ "Lives near Seattle and plans personal events in Pacific Time (UTC-8/UTC-7). Prefers Sunday-start weeks, 12-hour time with AM/PM, and dates like 11/03/2025, with week numbers shown. Uses an English interface and wants a straightforward color-coded calendar.", "Based in London and working with GMT/BST. Uses Monday...
Made with Curator

Dataset card for PersonaSignal-PersonaQuestions-Locale-And-Time-Zone-gpt-5

This dataset was made with Curator.

Dataset details

A sample from the dataset:

{
    "dimension_name": "locale_and_time_zone",
    "dimension_values": [
        "US Pacific",
        "US Eastern",
        "UK",
        "EU Central",
        "India",
        "China Mainland",
        "Japan",
        "Brazil",
        "Australia",
        "Africa"
    ],
    "dimension_description": "Controls the user's geographic location, timezone, date/time formatting preferences, and cultural conventions for calendar, currency, and measurements.",
    "question": "Plan a one-week meal prep schedule for next month that fits a standard office workweek and uses produce that\u2019s in season, including when to shop and batch-cook.",
    "why_differ": "Seasonality and weekend rhythms vary by locale and hemisphere, shifting which ingredients feel \u2018peak\u2019 and whether shopping happens on one or two weekend days. Some personas favor Monday-start planning and place heavier prep before or after a typical rest day.",
    "how_subtle": "Variation appears in which days anchor the plan, how shopping vs. cooking is sequenced, and the kinds of produce and cooking methods emphasized (cooler- vs. warmer-weather), not in named holidays or regional terms.",
    "sampled_value": "US Eastern",
    "num_distractors": 5,
    "ground_truth_persona": "An office worker living in Boston with a standard 9\u20135 schedule. Uses a 12-hour clock, MM/DD dates, and US customary units like cups and ounces. Plans to shop on the weekend and batch-cook, using locally in-season produce next month.",
    "distractor_personas": [
        "An office worker living in Seattle with a standard 9\u20135 schedule. Uses a 12-hour clock, MM/DD dates, and US customary units. Plans to shop on the weekend and batch-cook, using West Coast seasonal produce next month.",
        "An office worker based in London with a standard 9\u20135 schedule. Uses 24-hour time, DD/MM dates, and metric units. Plans to shop on the weekend and batch-cook, using British seasonal produce next month.",
        "An office worker based in Berlin with a standard 9\u20135 schedule. Uses 24-hour time, DD.MM.YYYY dates, and metric units. Plans to shop on the weekend and batch-cook, using Central European seasonal produce next month.",
        "An office worker in Bengaluru with a standard 9\u20135 schedule. Uses 24-hour time, DD/MM/YYYY dates, and metric units. Plans to shop on the weekend and batch-cook, using locally in-season produce in India next month.",
        "An office worker in Melbourne with a standard 9\u20135 schedule. Uses 24-hour time, DD/MM/YYYY dates, and metric units. Plans to shop on the weekend and batch-cook, using Australian seasonal produce next month."
    ]
}

Loading the dataset

You can load this dataset using the following code:

from datasets import load_dataset

dataset = load_dataset("JasonYan777/PersonaSignal-PersonaQuestions-Locale-And-Time-Zone-gpt-5")
Downloads last month
6
Number of rows:
50
Total file size:
52.7 kB