id stringlengths 21 21 | kind stringclasses 3
values | options listlengths 2 6 | target listlengths 2 6 | state stringlengths 155 243 | question stringclasses 7
values | domain stringclasses 1
value | family stringclasses 1
value | source stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|
v3_7a5ac4a7dc508289_n | noul | [
"false",
"true"
] | [
0.81,
0.19
] | The nightly feed passed all 47 freshness checks; additionally shows referential breaks against the dim table. Context: under SOX controls, shortly after a software update. Reported by the on-call engineer. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_64cad838069bfa1b_n | noul | [
"false",
"true"
] | [
0.55,
0.45
] | The fact-sales table shows values outside physical bounds; additionally arrived 3 hours late. Context: in the sandbox only, during the holiday freeze. Reported by the monitoring system. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_1e47c0596dfb9606_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.02,
0.48,
0.28,
0.21,
0.01
] | An api-delivered dataset shows values outside physical bounds; additionally passed all 47 freshness checks. Context: feeding the quarterly report, while on-call rotation changed. Reported by the supervisor. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_e0d3c1ee95aedb6c_n | noul | [
"false",
"true"
] | [
0.96,
0.04
] | The customer table has a row count variance of -18%; additionally has 12,000 duplicate keys today. Context: under SOX controls, during the morning shift. Reported by the monitoring system. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_b57694734e7fd94b_n | noul | [
"false",
"true"
] | [
0.29,
0.71
] | An api-delivered dataset shows referential breaks against the dim table; additionally has a row count variance of -18%. Context: upstream of the ML feature store, during the system migration. Reported by the automated check. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_a7d59ab11f5a2a41_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.09,
0.27,
0.44,
0.18,
0.01
] | An api-delivered dataset arrived 3 hours late; additionally passed all 47 freshness checks. Context: under SOX controls, during the holiday freeze. Reported by the automated check. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_43a0b04e96061fdf_n | noul | [
"false",
"true"
] | [
0.36,
0.64
] | The fact-sales table exhibits schema drift in 2 columns; additionally has a row count variance of -18%. Context: under SOX controls, with staffing at reduced levels. Reported by the review queue. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_e8bfcdd20a7895fb_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.11,
0.18,
0.63,
0.07,
0
] | A sensor telemetry stream shows values outside physical bounds; additionally shows referential breaks against the dim table. Context: in the sandbox only, during the quarterly review. Reported by the on-call engineer. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_eac8efc6fb236ef8_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.58,
0.41,
0.01,
0
] | An api-delivered dataset arrived 3 hours late; additionally has 12,000 duplicate keys today. Context: feeding the quarterly report, following a recent audit. Reported by the on-call engineer. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_86951e48b46712b1_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.07,
0.29,
0.33,
0.27,
0.03
] | The fact-sales table lost its partition for one region; additionally is byte-identical to yesterday. Context: under SOX controls, under reduced staffing. Reported by the on-call engineer. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_7dd720f15105da81_n | noul | [
"false",
"true"
] | [
0.93,
0.07
] | An api-delivered dataset shows referential breaks against the dim table; additionally exhibits schema drift in 2 columns. Context: in the sandbox only, during the system migration. Reported by the monitoring system. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_93f4e87e68d6fef2_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.14,
0.08,
0.77,
0.01
] | A sensor telemetry stream shows values outside physical bounds; additionally arrived 3 hours late. Context: feeding the quarterly report, as part of a compliance sweep. Reported by the supervisor. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_e42a2b9ed39529df_n | noul | [
"false",
"true"
] | [
0.85,
0.15
] | A sensor telemetry stream exhibits schema drift in 2 columns; additionally shows values outside physical bounds. Context: in the sandbox only, following a recent audit. Reported by the on-call engineer. | Is this scenario one where: this blocks the monthly close? | data_quality | technical | yuri_v3 |
v3_3bca7e6eacff7252_n | noul | [
"false",
"true"
] | [
0.29,
0.71
] | The fact-sales table exhibits schema drift in 2 columns; additionally has 12,000 duplicate keys today. Context: feeding the quarterly report, mid-incident. Reported by the review queue. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_c122abf63bfef586_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.39,
0.23,
0.36,
0.02
] | An api-delivered dataset has 12,000 duplicate keys today; additionally exhibits schema drift in 2 columns. Context: feeding the quarterly report, during the system migration. Reported by the supervisor. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_48205101db704ad3_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.55,
0.45,
0,
0
] | The nightly feed contains unexpected unicode in key columns; additionally shows values outside physical bounds. Context: under SOX controls, mid-incident. Reported by the supervisor. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_cad508f0b0b0e00f_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.05,
0.75,
0.19,
0
] | A sensor telemetry stream has 12,000 duplicate keys today; additionally shows 0.4% null rate where none existed. Context: in the sandbox only, during the morning shift. Reported by the on-call engineer. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_99b43ace4dea31d3_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.36,
0.04,
0.57,
0.03
] | An api-delivered dataset is byte-identical to yesterday; additionally has 12,000 duplicate keys today. Context: feeding the quarterly report, during the system migration. Reported by the on-call engineer. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_e87bf4bbd2432aa3_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.2,
0.79,
0.01
] | The fact-sales table has a row count variance of -18%; additionally exhibits schema drift in 2 columns. Context: upstream of the ML feature store, during the morning shift. Reported by the operator. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_af912ed0d439949b_n | noul | [
"false",
"true"
] | [
0.85,
0.15
] | The nightly feed shows referential breaks against the dim table; additionally passed all 47 freshness checks. Context: upstream of the ML feature store, while on-call rotation changed. Reported by the automated check. | Is this scenario one where: this blocks the monthly close? | data_quality | technical | yuri_v3 |
v3_66b6e3eadd798d2b_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.44,
0.51,
0.04,
0.01
] | The nightly feed shows a sudden distribution shift in one field; additionally shows values outside physical bounds. Context: feeding the quarterly report, immediately after go-live. Reported by the operator. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_ca56fdd72c1a063b_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.12,
0.4,
0.45,
0.03
] | The nightly feed is byte-identical to yesterday; additionally shows values outside physical bounds. Context: under SOX controls, as part of a compliance sweep. Reported by the monitoring system. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_93660f6279b8021c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.04,
0.09,
0.74,
0.13,
0
] | The nightly feed exhibits schema drift in 2 columns; additionally shows values outside physical bounds. Context: in the sandbox only, at the end of the fiscal period. Reported by the operator. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_65feede711c5a39e_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.4,
0.57,
0.02,
0.01
] | An api-delivered dataset passed all 47 freshness checks; additionally shows referential breaks against the dim table. Context: upstream of the ML feature store, under reduced staffing. Reported by the automated check. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_376db311091b4a08_n | noul | [
"false",
"true"
] | [
0.95,
0.05
] | An api-delivered dataset is byte-identical to yesterday; additionally shows values outside physical bounds. Context: feeding the quarterly report, during a scheduled maintenance window. Reported by the supervisor. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_f55feb3d6fc34796_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.04,
0.14,
0.75,
0.07,
0
] | The nightly feed exhibits schema drift in 2 columns; additionally is byte-identical to yesterday. Context: in the sandbox only, during normal operations. Reported by the supervisor. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_6e2ac95cbd2673c7_n | noul | [
"false",
"true"
] | [
0.95,
0.05
] | A sensor telemetry stream lost its partition for one region; additionally shows values outside physical bounds. Context: upstream of the ML feature store, during peak load. Reported by the review queue. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_50d602aa67f6b196_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.52,
0.26,
0.21,
0.01
] | The fact-sales table lost its partition for one region; additionally has 12,000 duplicate keys today. Context: feeding the quarterly report, immediately after go-live. Reported by the automated check. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_af08b6b9d8699a31_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.44,
0.13,
0.42,
0.01
] | The fact-sales table has 12,000 duplicate keys today; additionally lost its partition for one region. Context: upstream of the ML feature store, immediately after go-live. Reported by the supervisor. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_0cd3cdb23428e960_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.74,
0.26,
0,
0
] | An api-delivered dataset has 12,000 duplicate keys today; additionally lost its partition for one region. Context: upstream of the ML feature store, during peak load. Reported by the on-call engineer. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_0d91c95c4815254e_n | noul | [
"false",
"true"
] | [
0.47,
0.53
] | An api-delivered dataset shows values outside physical bounds; additionally has 12,000 duplicate keys today. Context: under SOX controls, with staffing at reduced levels. Reported by the supervisor. | Is this scenario one where: this blocks the monthly close? | data_quality | technical | yuri_v3 |
v3_0a0059277078f063_n | noul | [
"false",
"true"
] | [
0.53,
0.47
] | The customer table arrived 3 hours late; additionally shows values outside physical bounds. Context: under SOX controls, while on-call rotation changed. Reported by the review queue. | Is this scenario one where: this blocks the monthly close? | data_quality | technical | yuri_v3 |
v3_1cf0792ff33ae5ef_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.48,
0.5,
0.01
] | An api-delivered dataset contains unexpected unicode in key columns; additionally lost its partition for one region. Context: feeding the quarterly report, during the morning shift. Reported by the review queue. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_830e2ef56ba20ffe_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.39,
0.59,
0.01
] | The nightly feed is byte-identical to yesterday; additionally has a row count variance of -18%. Context: feeding the quarterly report, shortly after a software update. Reported by the automated check. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_d613ebc614d92c8b_n | noul | [
"false",
"true"
] | [
0.94,
0.06
] | The fact-sales table shows referential breaks against the dim table; additionally shows a sudden distribution shift in one field. Context: in the sandbox only, with staffing at reduced levels. Reported by the operator. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_1ca5e60138166d6e_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.16,
0.82,
0.02
] | An api-delivered dataset contains unexpected unicode in key columns; additionally has 12,000 duplicate keys today. Context: upstream of the ML feature store, shortly after a software update. Reported by the monitoring system. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_ac139f9ea01b4b3d_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.03,
0.85,
0.12
] | An api-delivered dataset arrived 3 hours late; additionally lost its partition for one region. Context: under SOX controls, under an active deadline. Reported by the review queue. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_ba955b39714cf79e_n | noul | [
"false",
"true"
] | [
0.95,
0.05
] | The customer table has 12,000 duplicate keys today; additionally shows values outside physical bounds. Context: in the sandbox only, during an external partner integration. Reported by the on-call engineer. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_0248364b2bc0eaa4_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.62,
0.37,
0.01,
0
] | A sensor telemetry stream shows referential breaks against the dim table; additionally shows 0.4% null rate where none existed. Context: upstream of the ML feature store, mid-incident. Reported by the operator. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_e986107884e2d6ce_n | noul | [
"false",
"true"
] | [
0.76,
0.24
] | A sensor telemetry stream shows referential breaks against the dim table; additionally passed all 47 freshness checks. Context: feeding the quarterly report, under an active deadline. Reported by the monitoring system. | Is this scenario one where: this blocks the monthly close? | data_quality | technical | yuri_v3 |
v3_2f42931fc79c7721_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.09,
0.35,
0.52,
0.03
] | The fact-sales table is byte-identical to yesterday; additionally has a row count variance of -18%. Context: feeding the quarterly report, under reduced staffing. Reported by the on-call engineer. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_62af8ae84a8e8268_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.4,
0.43,
0.16,
0.01
] | The customer table is byte-identical to yesterday; additionally shows 0.4% null rate where none existed. Context: feeding the quarterly report, with a new vendor onboarded. Reported by the on-call engineer. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_52d0aa97ed9e42d4_n | noul | [
"false",
"true"
] | [
0.77,
0.23
] | The customer table exhibits schema drift in 2 columns; additionally passed all 47 freshness checks. Context: upstream of the ML feature store, during the holiday freeze. Reported by the on-call engineer. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_3c08298b0c05010c_n | noul | [
"false",
"true"
] | [
0.91,
0.09
] | The fact-sales table lost its partition for one region; additionally shows a sudden distribution shift in one field. Context: under SOX controls, with a new vendor onboarded. Reported by the automated check. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_55fbc571b840e94e_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.09,
0.22,
0.43,
0.23,
0.02
] | The customer table passed all 47 freshness checks; additionally is byte-identical to yesterday. Context: feeding the quarterly report, with staffing at reduced levels. Reported by the operator. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_54c8b88458ede8e3_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.54,
0.37,
0.03,
0.06
] | An api-delivered dataset is byte-identical to yesterday; additionally shows a sudden distribution shift in one field. Context: feeding the quarterly report, with staffing at reduced levels. Reported by the review queue. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_515021364c5a7c81_n | noul | [
"false",
"true"
] | [
0.71,
0.29
] | An api-delivered dataset shows 0.4% null rate where none existed; additionally has 12,000 duplicate keys today. Context: feeding the quarterly report, during the system migration. Reported by the review queue. | Is this scenario one where: this blocks the monthly close? | data_quality | technical | yuri_v3 |
v3_461582b8442051a5_n | noul | [
"false",
"true"
] | [
0.66,
0.34
] | The nightly feed contains unexpected unicode in key columns; additionally shows a sudden distribution shift in one field. Context: upstream of the ML feature store, at the end of the fiscal period. Reported by the on-call engineer. | Is this scenario one where: this blocks the monthly close? | data_quality | technical | yuri_v3 |
v3_ab892b83fdfdef84_n | noul | [
"false",
"true"
] | [
0.51,
0.49
] | The customer table contains unexpected unicode in key columns; additionally is byte-identical to yesterday. Context: feeding the quarterly report, during a scheduled maintenance window. Reported by the supervisor. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_06122c9e2d50e375_n | noul | [
"false",
"true"
] | [
0.66,
0.34
] | An api-delivered dataset is byte-identical to yesterday; additionally shows 0.4% null rate where none existed. Context: in the sandbox only, shortly after a software update. Reported by the supervisor. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_8e5099304761b01d_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.05,
0.82,
0.13,
0
] | A sensor telemetry stream shows a sudden distribution shift in one field; additionally shows referential breaks against the dim table. Context: upstream of the ML feature store, during the system migration. Reported by the operator. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_b571ddcd8c3f18ff_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.32,
0.5,
0.13,
0.05
] | The nightly feed shows referential breaks against the dim table; additionally shows values outside physical bounds. Context: in the sandbox only, while on-call rotation changed. Reported by the supervisor. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_01d989fc5f717aa4_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.35,
0.51,
0.09,
0.05
] | The nightly feed shows a sudden distribution shift in one field; additionally has a row count variance of -18%. Context: in the sandbox only, under reduced staffing. Reported by the on-call engineer. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_1db5371c811f69ce_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.16,
0.69,
0.13,
0.02,
0
] | A sensor telemetry stream has a row count variance of -18%; additionally passed all 47 freshness checks. Context: under SOX controls, as part of a compliance sweep. Reported by the monitoring system. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_26ce079be5ca57a7_n | noul | [
"false",
"true"
] | [
0.44,
0.56
] | The fact-sales table passed all 47 freshness checks; additionally has a row count variance of -18%. Context: under SOX controls, shortly after a software update. Reported by the automated check. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_dd2356c6efb009fe_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.05,
0.33,
0.49,
0.13
] | The nightly feed shows referential breaks against the dim table; additionally arrived 3 hours late. Context: in the sandbox only, while legacy systems are still active. Reported by the supervisor. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_d670a835ce09a921_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.08,
0.88,
0.04
] | The nightly feed has 12,000 duplicate keys today; additionally lost its partition for one region. Context: upstream of the ML feature store, with staffing at reduced levels. Reported by the review queue. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_edd8a0bad7bfcf82_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.2,
0.49,
0.09,
0.22
] | The customer table shows a sudden distribution shift in one field; additionally contains unexpected unicode in key columns. Context: in the sandbox only, as part of a compliance sweep. Reported by the on-call engineer. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_aea729105e12ce7b_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.65,
0.33,
0,
0.02
] | The fact-sales table shows a sudden distribution shift in one field; additionally passed all 47 freshness checks. Context: upstream of the ML feature store, immediately after go-live. Reported by the monitoring system. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_545d8056a89be081_n | noul | [
"false",
"true"
] | [
0.63,
0.37
] | The nightly feed passed all 47 freshness checks; additionally has a row count variance of -18%. Context: under SOX controls, under reduced staffing. Reported by the review queue. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_82951d16b8b63c82_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.05,
0.66,
0.22,
0.07,
0
] | The nightly feed has a row count variance of -18%; additionally passed all 47 freshness checks. Context: upstream of the ML feature store, under an active deadline. Reported by the supervisor. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_7a4f6bf67a382297_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.21,
0.13,
0.51,
0.14
] | The customer table has 12,000 duplicate keys today; additionally passed all 47 freshness checks. Context: upstream of the ML feature store, under an active deadline. Reported by the automated check. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_37448f130195f08c_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.11,
0.45,
0.43,
0.01
] | The nightly feed passed all 47 freshness checks; additionally shows a sudden distribution shift in one field. Context: under SOX controls, during a scheduled maintenance window. Reported by the monitoring system. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_05c8a5064273c503_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.17,
0.81,
0.02
] | The customer table exhibits schema drift in 2 columns; additionally lost its partition for one region. Context: feeding the quarterly report, as part of a compliance sweep. Reported by the operator. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_7dc72a087435adee_n | noul | [
"false",
"true"
] | [
0.8,
0.2
] | The customer table shows referential breaks against the dim table; additionally shows a sudden distribution shift in one field. Context: upstream of the ML feature store, immediately after go-live. Reported by the on-call engineer. | Is this scenario one where: this blocks the monthly close? | data_quality | technical | yuri_v3 |
v3_46e38ff3d9f5309a_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.19,
0.49,
0.3,
0.02
] | A sensor telemetry stream shows 0.4% null rate where none existed; additionally passed all 47 freshness checks. Context: under SOX controls, mid-incident. Reported by the on-call engineer. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_f4e0fb07c08f28eb_n | noul | [
"false",
"true"
] | [
0.38,
0.62
] | The fact-sales table lost its partition for one region; additionally passed all 47 freshness checks. Context: under SOX controls, during an external partner integration. Reported by the on-call engineer. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_a72e67a95eae4fd9_n | noul | [
"false",
"true"
] | [
0.57,
0.43
] | A sensor telemetry stream is byte-identical to yesterday; additionally shows a sudden distribution shift in one field. Context: upstream of the ML feature store, as part of a compliance sweep. Reported by the operator. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_6e26754997692d02_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.52,
0.48,
0,
0
] | An api-delivered dataset shows values outside physical bounds; additionally is byte-identical to yesterday. Context: upstream of the ML feature store, following a recent audit. Reported by the on-call engineer. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_5d69c7393a10bc2f_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.55,
0.26,
0.18,
0.01
] | The customer table shows referential breaks against the dim table; additionally has a row count variance of -18%. Context: upstream of the ML feature store, during the system migration. Reported by the automated check. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_432b3320d3e68a32_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.2,
0.78,
0.02
] | The fact-sales table shows values outside physical bounds; additionally exhibits schema drift in 2 columns. Context: feeding the quarterly report, during the morning shift. Reported by the monitoring system. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_258ff403753a5de8_n | noul | [
"false",
"true"
] | [
0.95,
0.05
] | The nightly feed has 12,000 duplicate keys today; additionally shows values outside physical bounds. Context: in the sandbox only, under reduced staffing. Reported by the operator. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_391e6b45bbf1fe2e_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.19,
0.79,
0.02
] | The fact-sales table has a row count variance of -18%; additionally shows values outside physical bounds. Context: upstream of the ML feature store, during a scheduled maintenance window. Reported by the review queue. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_0017a18d288c815c_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.32,
0.44,
0.24,
0
] | The fact-sales table has a row count variance of -18%; additionally passed all 47 freshness checks. Context: feeding the quarterly report, under an active deadline. Reported by the supervisor. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_fe648be3383421d5_n | noul | [
"false",
"true"
] | [
0.32,
0.68
] | The customer table has a row count variance of -18%; additionally contains unexpected unicode in key columns. Context: upstream of the ML feature store, during the quarterly review. Reported by the review queue. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_22211085f1e86acb_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.02,
0.03,
0.94,
0.01
] | A sensor telemetry stream arrived 3 hours late; additionally shows values outside physical bounds. Context: under SOX controls, during peak load. Reported by the operator. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_1160b35038a45a24_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.12,
0.03,
0.53,
0.32
] | The customer table arrived 3 hours late; additionally passed all 47 freshness checks. Context: in the sandbox only, under an active deadline. Reported by the automated check. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_786ee1ab1e7a7c69_n | noul | [
"false",
"true"
] | [
0.96,
0.04
] | The customer table shows referential breaks against the dim table; additionally has 12,000 duplicate keys today. Context: under SOX controls, while legacy systems are still active. Reported by the monitoring system. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_abf3ca8a3d5a20c0_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.46,
0.52,
0.01
] | The fact-sales table contains unexpected unicode in key columns; additionally lost its partition for one region. Context: in the sandbox only, under an active deadline. Reported by the supervisor. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_b0ef4df62c9a7cee_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.08,
0.88,
0.04
] | The fact-sales table shows referential breaks against the dim table; additionally has 12,000 duplicate keys today. Context: upstream of the ML feature store, while on-call rotation changed. Reported by the operator. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_a65b860233dbd18d_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.34,
0.65,
0,
0.01
] | The nightly feed has a row count variance of -18%; additionally shows referential breaks against the dim table. Context: upstream of the ML feature store, immediately after go-live. Reported by the monitoring system. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_3e02b10260baaf6b_n | noul | [
"false",
"true"
] | [
0.47,
0.53
] | The fact-sales table shows referential breaks against the dim table; additionally passed all 47 freshness checks. Context: under SOX controls, with staffing at reduced levels. Reported by the supervisor. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_6d63fb709145bb01_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.05,
0.68,
0.27
] | The customer table has 12,000 duplicate keys today; additionally lost its partition for one region. Context: under SOX controls, during normal operations. Reported by the on-call engineer. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_c161a02faaee74be_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.38,
0.61,
0.01
] | The fact-sales table lost its partition for one region; additionally exhibits schema drift in 2 columns. Context: upstream of the ML feature store, during the morning shift. Reported by the monitoring system. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_06e0bd0839276c50_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.3,
0.7,
0,
0
] | The customer table exhibits schema drift in 2 columns; additionally contains unexpected unicode in key columns. Context: feeding the quarterly report, at the end of the fiscal period. Reported by the review queue. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_5e517dac8b9ce285_n | noul | [
"false",
"true"
] | [
0.56,
0.44
] | The nightly feed is byte-identical to yesterday; additionally exhibits schema drift in 2 columns. Context: under SOX controls, following a recent audit. Reported by the operator. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_c25283f72018463c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.05,
0.31,
0.29,
0.32,
0.03
] | The customer table passed all 47 freshness checks; additionally has 12,000 duplicate keys today. Context: in the sandbox only, immediately after go-live. Reported by the monitoring system. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_d8334e1704d98e98_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.38,
0.61,
0.01,
0
] | The customer table shows a sudden distribution shift in one field; additionally shows 0.4% null rate where none existed. Context: upstream of the ML feature store, immediately after go-live. Reported by the automated check. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_bf18332a24d24c69_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.43,
0.55,
0.01,
0.01
] | A sensor telemetry stream exhibits schema drift in 2 columns; additionally contains unexpected unicode in key columns. Context: in the sandbox only, at the end of the fiscal period. Reported by the supervisor. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_3e04c7ea59e70e31_n | noul | [
"false",
"true"
] | [
0.83,
0.17
] | An api-delivered dataset is byte-identical to yesterday; additionally exhibits schema drift in 2 columns. Context: feeding the quarterly report, during the system migration. Reported by the review queue. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_ede100a8b008dfeb_n | noul | [
"false",
"true"
] | [
0.83,
0.17
] | The nightly feed is byte-identical to yesterday; additionally shows 0.4% null rate where none existed. Context: upstream of the ML feature store, while on-call rotation changed. Reported by the supervisor. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_a3308471205c2b85_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.13,
0.61,
0.26,
0
] | The customer table passed all 47 freshness checks; additionally shows a sudden distribution shift in one field. Context: feeding the quarterly report, during an external partner integration. Reported by the review queue. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_b13f8dc98fa015ec_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.17,
0.62,
0.16,
0.05,
0,
0
] | An api-delivered dataset passed all 47 freshness checks; additionally arrived 3 hours late. Context: under SOX controls, during a scheduled maintenance window. Reported by the automated check. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_3ec5cfb6c7075b68_n | noul | [
"false",
"true"
] | [
0.97,
0.03
] | A sensor telemetry stream shows values outside physical bounds; additionally shows referential breaks against the dim table. Context: upstream of the ML feature store, mid-incident. Reported by the monitoring system. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_f2d460ce31cbfb3b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.04,
0.4,
0.39,
0.16,
0.01
] | The nightly feed shows values outside physical bounds; additionally passed all 47 freshness checks. Context: in the sandbox only, under an active deadline. Reported by the review queue. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_e1fde44f2912d062_n | noul | [
"false",
"true"
] | [
0.66,
0.34
] | An api-delivered dataset exhibits schema drift in 2 columns; additionally is byte-identical to yesterday. Context: feeding the quarterly report, while on-call rotation changed. Reported by the review queue. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_447278ca30d7e2da_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.02,
0.48,
0.49,
0.01
] | A sensor telemetry stream shows referential breaks against the dim table; additionally arrived 3 hours late. Context: under SOX controls, during the quarterly review. Reported by the supervisor. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_984741a363ed28cd_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.6,
0.4,
0,
0
] | The fact-sales table contains unexpected unicode in key columns; additionally shows values outside physical bounds. Context: upstream of the ML feature store, immediately after go-live. Reported by the monitoring system. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_1fce6f2c60694b23_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.11,
0.2,
0.69,
0
] | A sensor telemetry stream shows a sudden distribution shift in one field; additionally lost its partition for one region. Context: under SOX controls, under an active deadline. Reported by the operator. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_f0eaa4a8c77172be_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.11,
0.11,
0.4,
0.38
] | The fact-sales table arrived 3 hours late; additionally shows values outside physical bounds. Context: in the sandbox only, during the holiday freeze. Reported by the monitoring system. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
End of preview. Expand in Data Studio
JEV corpus - data_quality
9,789 typed calibrated decision rows from the jev-distill-corpus-v3 corpus (domain: data_quality).
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