id stringlengths 21 21 | kind stringclasses 3
values | options listlengths 2 6 | target listlengths 2 6 | state stringlengths 162 247 | question stringclasses 7
values | domain stringclasses 1
value | family stringclasses 1
value | source stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|
v3_4c46a8963a661526_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.05,
0.41,
0.51,
0.03
] | The approval chain has a 10-business-day regulatory clock; additionally has sequential steps summing past the deadline. Context: under the contract terms, during normal operations. Reported by the operator. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_248412cf8400ff77_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.22,
0.73,
0.04
] | The approval chain has a 10-business-day regulatory clock; additionally has sequential steps summing past the deadline. Context: before quarter close, during the morning shift. Reported by the operator. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_20e4b1d6283ffa7c_n | noul | [
"false",
"true"
] | [
0.12,
0.88
] | The project milestone expires 30 days before the audit; additionally has sequential steps summing past the deadline. Context: per the standard SLA, following a recent audit. Reported by the automated check. | Is this scenario one where: a buffer is required? | temporal_reasoning | spatial | yuri_v3 |
v3_3cbb8b397bbd1031_n | noul | [
"false",
"true"
] | [
0.47,
0.53
] | The certification window has a 10-business-day regulatory clock; additionally has a built-in 3-day buffer. Context: before quarter close, during an external partner integration. Reported by the automated check. | Is this scenario one where: the sequence is valid? | temporal_reasoning | spatial | yuri_v3 |
v3_0598e094a19408d2_n | noul | [
"false",
"true"
] | [
0.44,
0.56
] | The certification window was completed 2 days early; additionally needs a document that takes 15 days to obtain. Context: per the standard SLA, during peak load. Reported by the operator. | Is this scenario one where: the deadline is achievable? | temporal_reasoning | spatial | yuri_v3 |
v3_a69faa108dc8a92c_n | noul | [
"false",
"true"
] | [
0.84,
0.16
] | The project milestone can start only after the freeze lifts; additionally has sequential steps summing past the deadline. Context: per the standard SLA, during the holiday freeze. Reported by the supervisor. | Is this scenario one where: the sequence is valid? | temporal_reasoning | spatial | yuri_v3 |
v3_76befff8dbffd62f_n | noul | [
"false",
"true"
] | [
0.51,
0.49
] | The certification window expires 30 days before the audit; additionally needs a document that takes 15 days to obtain. Context: under the contract terms, with a new vendor onboarded. Reported by the review queue. | Is this scenario one where: the sequence is valid? | temporal_reasoning | spatial | yuri_v3 |
v3_4abcdbdd5c2a09ad_c | choice | [
"start_now",
"expedite",
"renegotiate_date",
"escalate_blocker"
] | [
0.41,
0.54,
0.02,
0.03
] | The renewal deadline was completed 2 days early; additionally needs a document that takes 15 days to obtain. Context: with expedite fees available, at the end of the fiscal period. Reported by the monitoring system. | Timing decision for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_80cb3d7f5cda1fd1_n | noul | [
"false",
"true"
] | [
0.43,
0.57
] | The renewal deadline depends on a vendor response with a 5-day SLA; additionally expires 30 days before the audit. Context: with expedite fees available, during the quarterly review. Reported by the monitoring system. | Is this scenario one where: the deadline is achievable? | temporal_reasoning | spatial | yuri_v3 |
v3_38652800a387ed46_n | noul | [
"false",
"true"
] | [
0.83,
0.17
] | The certification window expires 30 days before the audit; additionally has sequential steps summing past the deadline. Context: with expedite fees available, at the end of the fiscal period. Reported by the monitoring system. | Is this scenario one where: the sequence is valid? | temporal_reasoning | spatial | yuri_v3 |
v3_20162ecf6e65dd7f_n | noul | [
"false",
"true"
] | [
0.67,
0.33
] | The renewal deadline requires signoffs from 4 people with 2 on leave; additionally depends on a vendor response with a 5-day SLA. Context: before quarter close, while legacy systems are still active. Reported by the supervisor. | Is this scenario one where: the deadline is achievable? | temporal_reasoning | spatial | yuri_v3 |
v3_2884f9970cbd5e32_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.06,
0.25,
0.25,
0.39,
0.05,
0
] | The renewal deadline can start only after the freeze lifts; additionally was completed 2 days early. Context: with expedite fees available, with a new vendor onboarded. Reported by the monitoring system. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_b4d665549fb7909b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.69,
0.3,
0
] | The certification window depends on a vendor response with a 5-day SLA; additionally needs a document that takes 15 days to obtain. Context: with expedite fees available, with staffing at reduced levels. Reported by the monitoring system. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_1b04bb693752d8a4_n | noul | [
"false",
"true"
] | [
0.14,
0.86
] | The project milestone has a 10-business-day regulatory clock; additionally lands on a public holiday. Context: under the contract terms, with a new vendor onboarded. Reported by the monitoring system. | Is this scenario one where: a buffer is required? | temporal_reasoning | spatial | yuri_v3 |
v3_f89f4135dfe3aaa8_n | noul | [
"false",
"true"
] | [
0.9,
0.1
] | The approval chain lands on a public holiday; additionally has sequential steps summing past the deadline. Context: before quarter close, during normal operations. Reported by the operator. | Is this scenario one where: the deadline is achievable? | temporal_reasoning | spatial | yuri_v3 |
v3_589d30fb8221627a_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.04,
0.35,
0.57,
0.03
] | The renewal deadline has sequential steps summing past the deadline; additionally can start only after the freeze lifts. Context: under the contract terms, during the holiday freeze. Reported by the on-call engineer. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_38d03dfb65bce591_n | noul | [
"false",
"true"
] | [
0.08,
0.92
] | The certification window has a built-in 3-day buffer; additionally requires signoffs from 4 people with 2 on leave. Context: under the contract terms, during the quarterly review. Reported by the operator. | Is this scenario one where: a buffer is required? | temporal_reasoning | spatial | yuri_v3 |
v3_ec4210501c712d2a_n | noul | [
"false",
"true"
] | [
0.07,
0.93
] | The project milestone needs a document that takes 15 days to obtain; additionally requires signoffs from 4 people with 2 on leave. Context: under the contract terms, while legacy systems are still active. Reported by the review queue. | Is this scenario one where: a buffer is required? | temporal_reasoning | spatial | yuri_v3 |
v3_a4342303bda28fa9_c | choice | [
"start_now",
"expedite",
"renegotiate_date",
"escalate_blocker"
] | [
0.61,
0.27,
0.03,
0.09
] | The renewal deadline was completed 2 days early; additionally has sequential steps summing past the deadline. Context: with expedite fees available, during normal operations. Reported by the operator. | Timing decision for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_f7066e70adb2225f_c | choice | [
"start_now",
"expedite",
"renegotiate_date",
"escalate_blocker"
] | [
0.38,
0.35,
0.08,
0.19
] | The project milestone was completed 2 days early; additionally depends on a vendor response with a 5-day SLA. Context: under the contract terms, at the end of the fiscal period. Reported by the supervisor. | Timing decision for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_18e34ce219febe28_c | choice | [
"start_now",
"expedite",
"renegotiate_date",
"escalate_blocker"
] | [
0.05,
0.46,
0,
0.49
] | The certification window depends on a vendor response with a 5-day SLA; additionally has a 10-business-day regulatory clock. Context: before quarter close, under an active deadline. Reported by the supervisor. | Timing decision for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_148afad49e477682_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0.01,
0.22,
0.77,
0
] | The renewal deadline was completed 2 days early; additionally has a 10-business-day regulatory clock. Context: per the standard SLA, during an external partner integration. Reported by the automated check. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_09c3f53f9045f018_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.03,
0.33,
0.6,
0.04
] | The certification window expires 30 days before the audit; additionally has a built-in 3-day buffer. Context: per the standard SLA, under an active deadline. Reported by the automated check. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_0ef9483f4f190475_n | noul | [
"false",
"true"
] | [
0.1,
0.9
] | The approval chain has sequential steps summing past the deadline; additionally can start only after the freeze lifts. Context: before quarter close, during the holiday freeze. Reported by the monitoring system. | Is this scenario one where: a buffer is required? | temporal_reasoning | spatial | yuri_v3 |
v3_26631806ef8a2772_n | noul | [
"false",
"true"
] | [
0.85,
0.15
] | The approval chain depends on a vendor response with a 5-day SLA; additionally has sequential steps summing past the deadline. Context: under the contract terms, during the holiday freeze. Reported by the automated check. | Is this scenario one where: the sequence is valid? | temporal_reasoning | spatial | yuri_v3 |
v3_5feed4599948ed79_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0.49,
0.13,
0.37,
0.01
] | The approval chain was completed 2 days early; additionally expires 30 days before the audit. Context: with expedite fees available, with a new vendor onboarded. Reported by the supervisor. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_241bcdedb6e159de_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0.02,
0.07,
0.91,
0
] | The certification window has a built-in 3-day buffer; additionally needs a document that takes 15 days to obtain. Context: before quarter close, following a recent audit. Reported by the review queue. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_f93711bcc98f21d4_n | noul | [
"false",
"true"
] | [
0.89,
0.11
] | The certification window needs a document that takes 15 days to obtain; additionally has sequential steps summing past the deadline. Context: before quarter close, shortly after a software update. Reported by the supervisor. | Is this scenario one where: the deadline is achievable? | temporal_reasoning | spatial | yuri_v3 |
v3_e5a4c1d8e8862eed_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.1,
0.12,
0.43,
0.31,
0.03
] | The renewal deadline has a built-in 3-day buffer; additionally has sequential steps summing past the deadline. Context: per the standard SLA, during a scheduled maintenance window. Reported by the automated check. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_1526d718bb0c9488_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.02,
0.81,
0.17
] | The project milestone has a 10-business-day regulatory clock; additionally has sequential steps summing past the deadline. Context: before quarter close, during the holiday freeze. Reported by the operator. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_abbc5fcc6829ce55_n | noul | [
"false",
"true"
] | [
0.57,
0.43
] | The project milestone lands on a public holiday; additionally depends on a vendor response with a 5-day SLA. Context: before quarter close, following a recent audit. Reported by the review queue. | Is this scenario one where: the sequence is valid? | temporal_reasoning | spatial | yuri_v3 |
v3_c59f0c760c4bf22b_c | choice | [
"start_now",
"expedite",
"renegotiate_date",
"escalate_blocker"
] | [
0.04,
0.66,
0.18,
0.12
] | The project milestone lands on a public holiday; additionally expires 30 days before the audit. Context: with expedite fees available, under reduced staffing. Reported by the operator. | Timing decision for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_7c02d99241415d63_n | noul | [
"false",
"true"
] | [
0.09,
0.91
] | The certification window requires signoffs from 4 people with 2 on leave; additionally lands on a public holiday. Context: before quarter close, while legacy systems are still active. Reported by the supervisor. | Is this scenario one where: a buffer is required? | temporal_reasoning | spatial | yuri_v3 |
v3_1ec9759cff2f46f3_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0.08,
0.05,
0.51,
0.36
] | The project milestone was completed 2 days early; additionally can start only after the freeze lifts. Context: per the standard SLA, following a recent audit. Reported by the monitoring system. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_452d5aca375c9a81_n | noul | [
"false",
"true"
] | [
0.51,
0.49
] | The approval chain has a built-in 3-day buffer; additionally was completed 2 days early. Context: with expedite fees available, immediately after go-live. Reported by the automated check. | Is this scenario one where: a buffer is required? | temporal_reasoning | spatial | yuri_v3 |
v3_eafd7cd898cbed4a_n | noul | [
"false",
"true"
] | [
0.33,
0.67
] | The certification window expires 30 days before the audit; additionally was completed 2 days early. Context: before quarter close, during the holiday freeze. Reported by the on-call engineer. | Is this scenario one where: a buffer is required? | temporal_reasoning | spatial | yuri_v3 |
v3_6f9df83ffa020df7_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.02,
0.08,
0.59,
0.29,
0.01
] | The approval chain needs a document that takes 15 days to obtain; additionally can start only after the freeze lifts. Context: per the standard SLA, during a scheduled maintenance window. Reported by the supervisor. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_058b91f56c8065ee_n | noul | [
"false",
"true"
] | [
0.12,
0.88
] | The certification window has sequential steps summing past the deadline; additionally has a 10-business-day regulatory clock. Context: before quarter close, during a scheduled maintenance window. Reported by the operator. | Is this scenario one where: a buffer is required? | temporal_reasoning | spatial | yuri_v3 |
v3_e36150ab355373c5_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0.03,
0.59,
0.35,
0.03
] | The renewal deadline needs a document that takes 15 days to obtain; additionally depends on a vendor response with a 5-day SLA. Context: under the contract terms, while on-call rotation changed. Reported by the supervisor. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_f5f2dce0eb92397b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.02,
0.12,
0.67,
0.19,
0
] | The project milestone depends on a vendor response with a 5-day SLA; additionally can start only after the freeze lifts. Context: per the standard SLA, at the end of the fiscal period. Reported by the monitoring system. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_6ba697d1756a1ee8_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.07,
0.74,
0.19
] | The certification window requires signoffs from 4 people with 2 on leave; additionally has sequential steps summing past the deadline. Context: per the standard SLA, during normal operations. Reported by the review queue. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_125a772e77b86ea9_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.14,
0.33,
0.24,
0.28,
0.01,
0
] | The approval chain has a built-in 3-day buffer; additionally has a 10-business-day regulatory clock. Context: per the standard SLA, with a new vendor onboarded. Reported by the review queue. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_31e17828e47ca748_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.07,
0.56,
0.35,
0.01
] | The renewal deadline expires 30 days before the audit; additionally has a built-in 3-day buffer. Context: before quarter close, during the quarterly review. Reported by the operator. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_50e8e0e63422ad9c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.04,
0.08,
0.62,
0.24,
0.01
] | The project milestone lands on a public holiday; additionally can start only after the freeze lifts. Context: with expedite fees available, during normal operations. Reported by the monitoring system. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_3c0a9d5c318de888_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.05,
0.14,
0.69,
0.11,
0
] | The certification window lands on a public holiday; additionally has a built-in 3-day buffer. Context: per the standard SLA, during the system migration. Reported by the supervisor. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_0de412b223edcf87_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.03,
0.1,
0.73,
0.14,
0
] | The certification window has a built-in 3-day buffer; additionally can start only after the freeze lifts. Context: with expedite fees available, following a recent audit. Reported by the operator. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_19a02da4b2a4ee57_c | choice | [
"start_now",
"expedite",
"renegotiate_date",
"escalate_blocker"
] | [
0.32,
0.23,
0.03,
0.42
] | The certification window depends on a vendor response with a 5-day SLA; additionally has a 10-business-day regulatory clock. Context: under the contract terms, during an external partner integration. Reported by the operator. | Timing decision for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_9743b9cde3ea45cd_n | noul | [
"false",
"true"
] | [
0.45,
0.55
] | The project milestone depends on a vendor response with a 5-day SLA; additionally has a 10-business-day regulatory clock. Context: with expedite fees available, shortly after a software update. Reported by the review queue. | Is this scenario one where: the sequence is valid? | temporal_reasoning | spatial | yuri_v3 |
v3_d4bad2efbb246423_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0.13,
0.87,
0,
0
] | The approval chain depends on a vendor response with a 5-day SLA; additionally expires 30 days before the audit. Context: before quarter close, while legacy systems are still active. Reported by the on-call engineer. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_2acd838378ffce70_n | noul | [
"false",
"true"
] | [
0.84,
0.16
] | The certification window can start only after the freeze lifts; additionally has sequential steps summing past the deadline. Context: before quarter close, while legacy systems are still active. Reported by the operator. | Is this scenario one where: the sequence is valid? | temporal_reasoning | spatial | yuri_v3 |
v3_14a54be1872a3718_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.04,
0.29,
0.6,
0.06
] | The renewal deadline has sequential steps summing past the deadline; additionally expires 30 days before the audit. Context: under the contract terms, during normal operations. Reported by the monitoring system. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_1e269cc6ef4c2c45_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.52,
0.47,
0
] | The approval chain requires signoffs from 4 people with 2 on leave; additionally depends on a vendor response with a 5-day SLA. Context: under the contract terms, under reduced staffing. Reported by the operator. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_05bdd43f43817977_n | noul | [
"false",
"true"
] | [
0.82,
0.18
] | The renewal deadline has sequential steps summing past the deadline; additionally depends on a vendor response with a 5-day SLA. Context: under the contract terms, shortly after a software update. Reported by the on-call engineer. | Is this scenario one where: the deadline is achievable? | temporal_reasoning | spatial | yuri_v3 |
v3_afece7286c507494_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.03,
0.61,
0.36,
0
] | The certification window can start only after the freeze lifts; additionally needs a document that takes 15 days to obtain. Context: before quarter close, during the quarterly review. Reported by the on-call engineer. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_4b2e433887bc50f9_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0.74,
0,
0.01,
0.25
] | The certification window requires signoffs from 4 people with 2 on leave; additionally expires 30 days before the audit. Context: per the standard SLA, following a recent audit. Reported by the supervisor. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_ce04d8ac0b9d71fd_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.09,
0.24,
0.28,
0.33,
0.05,
0.01
] | The renewal deadline expires 30 days before the audit; additionally was completed 2 days early. Context: with expedite fees available, during normal operations. Reported by the on-call engineer. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_17dd16c9930c9a17_n | noul | [
"false",
"true"
] | [
0.51,
0.49
] | The project milestone requires signoffs from 4 people with 2 on leave; additionally has a 10-business-day regulatory clock. Context: with expedite fees available, under reduced staffing. Reported by the operator. | Is this scenario one where: the sequence is valid? | temporal_reasoning | spatial | yuri_v3 |
v3_c9d9d54e0aac3295_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0.13,
0,
0.86,
0.01
] | The certification window has sequential steps summing past the deadline; additionally expires 30 days before the audit. Context: per the standard SLA, during the quarterly review. Reported by the review queue. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_2d81e0f944fdf3b1_c | choice | [
"start_now",
"expedite",
"renegotiate_date",
"escalate_blocker"
] | [
0.01,
0,
0.61,
0.38
] | The project milestone can start only after the freeze lifts; additionally lands on a public holiday. Context: per the standard SLA, during the system migration. Reported by the review queue. | Timing decision for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_094b44a2e630de04_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.03,
0.32,
0.61,
0.03
] | The certification window can start only after the freeze lifts; additionally requires signoffs from 4 people with 2 on leave. Context: with expedite fees available, immediately after go-live. Reported by the on-call engineer. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_bee7de9bd2eae01a_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.08,
0.79,
0.12,
0
] | The certification window can start only after the freeze lifts; additionally depends on a vendor response with a 5-day SLA. Context: under the contract terms, with staffing at reduced levels. Reported by the supervisor. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_d54b95180b0a7347_n | noul | [
"false",
"true"
] | [
0.12,
0.88
] | The certification window requires signoffs from 4 people with 2 on leave; additionally expires 30 days before the audit. Context: before quarter close, while legacy systems are still active. Reported by the monitoring system. | Is this scenario one where: a buffer is required? | temporal_reasoning | spatial | yuri_v3 |
v3_f91dedeff96e8b72_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.13,
0.81,
0.06
] | The renewal deadline needs a document that takes 15 days to obtain; additionally has a 10-business-day regulatory clock. Context: before quarter close, under reduced staffing. Reported by the operator. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_fb0b1db31510f0c4_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.02,
0.78,
0.2
] | The certification window needs a document that takes 15 days to obtain; additionally has sequential steps summing past the deadline. Context: before quarter close, under reduced staffing. Reported by the automated check. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_6d921984ac3a0a09_c | choice | [
"start_now",
"expedite",
"renegotiate_date",
"escalate_blocker"
] | [
0.06,
0.03,
0.09,
0.82
] | The project milestone has a 10-business-day regulatory clock; additionally can start only after the freeze lifts. Context: before quarter close, during the quarterly review. Reported by the monitoring system. | Timing decision for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_40392615148ceee8_n | noul | [
"false",
"true"
] | [
0.47,
0.53
] | The renewal deadline was completed 2 days early; additionally lands on a public holiday. Context: per the standard SLA, during the quarterly review. Reported by the operator. | Is this scenario one where: a buffer is required? | temporal_reasoning | spatial | yuri_v3 |
v3_1b826f53ecf697db_c | choice | [
"start_now",
"expedite",
"renegotiate_date",
"escalate_blocker"
] | [
0.21,
0.12,
0.11,
0.56
] | The renewal deadline needs a document that takes 15 days to obtain; additionally lands on a public holiday. Context: before quarter close, during an external partner integration. Reported by the review queue. | Timing decision for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_3c967e7379ccebb2_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.21,
0.78,
0.01
] | The project milestone lands on a public holiday; additionally has sequential steps summing past the deadline. Context: per the standard SLA, following a recent audit. Reported by the review queue. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_bfd7d9f82136b492_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0.01,
0.99,
0,
0
] | The approval chain was completed 2 days early; additionally depends on a vendor response with a 5-day SLA. Context: per the standard SLA, during the morning shift. Reported by the operator. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_d025c4190454353d_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0,
0.99,
0.01,
0
] | The certification window has a built-in 3-day buffer; additionally depends on a vendor response with a 5-day SLA. Context: per the standard SLA, during the system migration. Reported by the on-call engineer. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_a114db43c06d8667_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0.37,
0.6,
0.01,
0.02
] | The approval chain requires signoffs from 4 people with 2 on leave; additionally depends on a vendor response with a 5-day SLA. Context: under the contract terms, at the end of the fiscal period. Reported by the automated check. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_2c043d099d9f3259_c | choice | [
"start_now",
"expedite",
"renegotiate_date",
"escalate_blocker"
] | [
0.3,
0.66,
0.04,
0
] | The project milestone has a 10-business-day regulatory clock; additionally was completed 2 days early. Context: per the standard SLA, at the end of the fiscal period. Reported by the supervisor. | Timing decision for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_8cc46919631e4d78_n | noul | [
"false",
"true"
] | [
0.52,
0.48
] | The certification window depends on a vendor response with a 5-day SLA; additionally can start only after the freeze lifts. Context: under the contract terms, during normal operations. Reported by the supervisor. | Is this scenario one where: the deadline is achievable? | temporal_reasoning | spatial | yuri_v3 |
v3_03bc5b9bc359ac97_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0.93,
0,
0,
0.07
] | The approval chain has a built-in 3-day buffer; additionally requires signoffs from 4 people with 2 on leave. Context: per the standard SLA, at the end of the fiscal period. Reported by the on-call engineer. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_76516de322d1b6c9_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.02,
0.32,
0.62,
0.03
] | The certification window has a built-in 3-day buffer; additionally has sequential steps summing past the deadline. Context: with expedite fees available, as part of a compliance sweep. Reported by the review queue. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_d0511ae72d174ba9_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.02,
0.44,
0.53,
0.01
] | The certification window depends on a vendor response with a 5-day SLA; additionally has sequential steps summing past the deadline. Context: per the standard SLA, during the quarterly review. Reported by the operator. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_4589670adb75385d_n | noul | [
"false",
"true"
] | [
0.77,
0.23
] | The certification window has sequential steps summing past the deadline; additionally was completed 2 days early. Context: before quarter close, with a new vendor onboarded. Reported by the on-call engineer. | Is this scenario one where: the sequence is valid? | temporal_reasoning | spatial | yuri_v3 |
v3_b015f7a23fdd7f8b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.12,
0.8,
0.08
] | The certification window requires signoffs from 4 people with 2 on leave; additionally lands on a public holiday. Context: per the standard SLA, during the holiday freeze. Reported by the on-call engineer. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_71c41ff17aa59686_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.1,
0.85,
0.05
] | The certification window can start only after the freeze lifts; additionally has sequential steps summing past the deadline. Context: under the contract terms, under reduced staffing. Reported by the automated check. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_4348e841c2b8ef4d_n | noul | [
"false",
"true"
] | [
0.11,
0.89
] | The project milestone has a built-in 3-day buffer; additionally was completed 2 days early. Context: before quarter close, mid-incident. Reported by the automated check. | Is this scenario one where: the deadline is achievable? | temporal_reasoning | spatial | yuri_v3 |
v3_32363a3199923514_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.02,
0.45,
0.52,
0.01
] | The project milestone has a built-in 3-day buffer; additionally depends on a vendor response with a 5-day SLA. Context: with expedite fees available, mid-incident. Reported by the operator. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_d401d7f9ad0e0441_c | choice | [
"start_now",
"expedite",
"renegotiate_date",
"escalate_blocker"
] | [
0.14,
0.1,
0.1,
0.66
] | The approval chain has a built-in 3-day buffer; additionally requires signoffs from 4 people with 2 on leave. Context: under the contract terms, following a recent audit. Reported by the operator. | Timing decision for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_6b8619a9117d79d1_n | noul | [
"false",
"true"
] | [
0.16,
0.84
] | The certification window has a 10-business-day regulatory clock; additionally has a built-in 3-day buffer. Context: before quarter close, with staffing at reduced levels. Reported by the operator. | Is this scenario one where: a buffer is required? | temporal_reasoning | spatial | yuri_v3 |
v3_083de55820bc6360_n | noul | [
"false",
"true"
] | [
0.32,
0.68
] | The project milestone was completed 2 days early; additionally has a built-in 3-day buffer. Context: before quarter close, during an external partner integration. Reported by the on-call engineer. | Is this scenario one where: the sequence is valid? | temporal_reasoning | spatial | yuri_v3 |
v3_154d8abc6546578b_n | noul | [
"false",
"true"
] | [
0.1,
0.9
] | The project milestone requires signoffs from 4 people with 2 on leave; additionally depends on a vendor response with a 5-day SLA. Context: before quarter close, while on-call rotation changed. Reported by the automated check. | Is this scenario one where: a buffer is required? | temporal_reasoning | spatial | yuri_v3 |
v3_e27b3340a43ed849_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0.12,
0,
0.88,
0
] | The certification window has a 10-business-day regulatory clock; additionally has a built-in 3-day buffer. Context: per the standard SLA, during the system migration. Reported by the operator. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_f656bdb955e24c07_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.04,
0.17,
0.17,
0.42,
0.18,
0.02
] | The renewal deadline has sequential steps summing past the deadline; additionally was completed 2 days early. Context: per the standard SLA, with staffing at reduced levels. Reported by the monitoring system. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_51de2420746e404e_c | choice | [
"start_now",
"expedite",
"renegotiate_date",
"escalate_blocker"
] | [
0,
0.82,
0,
0.18
] | The approval chain has sequential steps summing past the deadline; additionally requires signoffs from 4 people with 2 on leave. Context: with expedite fees available, mid-incident. Reported by the operator. | Timing decision for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_30ca94d69d7bf03a_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.02,
0.13,
0.2,
0.49,
0.15,
0.01
] | The approval chain expires 30 days before the audit; additionally was completed 2 days early. Context: with expedite fees available, shortly after a software update. Reported by the monitoring system. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_3597b621571c9362_n | noul | [
"false",
"true"
] | [
0.66,
0.34
] | The certification window lands on a public holiday; additionally has a 10-business-day regulatory clock. Context: per the standard SLA, shortly after a software update. Reported by the on-call engineer. | Is this scenario one where: the deadline is achievable? | temporal_reasoning | spatial | yuri_v3 |
v3_7a067a5754526333_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.0404,
0.8182,
0.1414
] | The approval chain has sequential steps summing past the deadline; additionally lands on a public holiday. Context: per the standard SLA, mid-incident. Reported by the review queue. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_4918231a3bfb18a7_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.05,
0.65,
0.29,
0
] | The project milestone depends on a vendor response with a 5-day SLA; additionally has a 10-business-day regulatory clock. Context: under the contract terms, during peak load. Reported by the automated check. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_f8b42400f9e92473_n | noul | [
"false",
"true"
] | [
0.9,
0.1
] | The project milestone depends on a vendor response with a 5-day SLA; additionally has sequential steps summing past the deadline. Context: per the standard SLA, while legacy systems are still active. Reported by the supervisor. | Is this scenario one where: the deadline is achievable? | temporal_reasoning | spatial | yuri_v3 |
v3_db80e4b843e9edbe_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.03,
0.83,
0.14
] | The approval chain has sequential steps summing past the deadline; additionally expires 30 days before the audit. Context: with expedite fees available, during an external partner integration. Reported by the review queue. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_a8ab5ae316bc1deb_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.07,
0.84,
0.09
] | The renewal deadline has sequential steps summing past the deadline; additionally has a 10-business-day regulatory clock. Context: per the standard SLA, with staffing at reduced levels. Reported by the review queue. | Rate deadline pressure for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_fee76cebecd749b5_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.35,
0.63,
0.01
] | The certification window lands on a public holiday; additionally requires signoffs from 4 people with 2 on leave. Context: with expedite fees available, during the morning shift. Reported by the monitoring system. | Rate schedule risk for this scenario on a 0-5 scale. | temporal_reasoning | spatial | yuri_v3 |
v3_109d18b6534d7596_n | noul | [
"false",
"true"
] | [
0.15,
0.85
] | The certification window can start only after the freeze lifts; additionally has sequential steps summing past the deadline. Context: per the standard SLA, with a new vendor onboarded. Reported by the supervisor. | Is this scenario one where: a buffer is required? | temporal_reasoning | spatial | yuri_v3 |
v3_aa4dd3015774945f_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0.02,
0,
0.97,
0.01
] | The renewal deadline lands on a public holiday; additionally has a 10-business-day regulatory clock. Context: per the standard SLA, mid-incident. Reported by the review queue. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
v3_7e0fb218b14b04b2_n | noul | [
"false",
"true"
] | [
0.53,
0.47
] | The renewal deadline requires signoffs from 4 people with 2 on leave; additionally has a built-in 3-day buffer. Context: per the standard SLA, during the system migration. Reported by the operator. | Is this scenario one where: the sequence is valid? | temporal_reasoning | spatial | yuri_v3 |
v3_67d604af1673444c_c | choice | [
"approvals",
"vendor",
"compliance",
"resources"
] | [
0.38,
0.48,
0,
0.14
] | The certification window depends on a vendor response with a 5-day SLA; additionally requires signoffs from 4 people with 2 on leave. Context: before quarter close, during the quarterly review. Reported by the review queue. | Critical path for this scenario. | temporal_reasoning | spatial | yuri_v3 |
End of preview. Expand in Data Studio
JEV corpus - temporal_reasoning
7,784 typed calibrated decision rows from the jev-distill-corpus-v3 corpus (domain: temporal_reasoning).
Each row is one typed decision: kind (noul / choice / score), a state, a question, options, and a target probability distribution over the options.
Part of the per-domain split of SargeDev/jev-distill-corpus-v3 - the full corpus in one repo.
Domains:
- Downloads last month
- 39