diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000000000000000000000000000000000000..e55102a1fc77a1b37ec45ba36eb8338411a1688d --- /dev/null +++ b/LICENSE @@ -0,0 +1,11 @@ +SGR-Bench is licensed under the Creative Commons Attribution 4.0 +International License (CC BY 4.0). + +You are free to share and adapt the material for any purpose, including +commercial use, provided that appropriate credit is given. + +License URL: +https://creativecommons.org/licenses/by/4.0/ + +Third-party public websites referenced by the dataset remain subject to +their own terms and policies. diff --git a/constraint.jsonl b/constraint.jsonl new file mode 100644 index 0000000000000000000000000000000000000000..7c7582f84b0f1d22702b420a21053cacb95e6493 --- /dev/null +++ b/constraint.jsonl @@ -0,0 +1,50 @@ +{"task_id":"arxiv_001","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"I am organizing the research trajectory of dataset distillation and dataset condensation on arXiv from 2019 to 2021, aiming to identify machine learning papers that discuss replacing large-scale training sets with a small number of synthetic training data points. Search arXiv records from 2019 to 2021 for both the phrases \"dataset distillation\" and \"dataset condensation\". Retain only entries whose primary category is Machine Learning; do not include records that are only cross-listed into Machine Learning by other primary-category papers. From these, further select papers that had a version update in the calendar year following their initial submission and whose current arXiv record still clearly indicates a subsequent publication venue. Finally, output a table sorted by v1 submitted in ascending order, with columns: arXiv ID, term family, cue location, v1 submitted, first next-year version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying items exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Finally, output a table sorted by v1 submitted in ascending order, with columns: arXiv ID, term family, cue location, v1 submitted, first next-year version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying items exist, output NONE.","oracle_answer":"arXiv ID|term family|cue location|v1 submitted|first next-year version|date of that version|primary category|publication-trail source|current publication clue\n1910.02551|Distillation|Title|2019-10-06|v3|2020-05-05|cs.LG|Related DOI|10.1109/IJCNN52387.2021.9533769\n2011.00050|Distillation|Abstract-only|2020-10-30|v2|2021-03-02|cs.LG|Comments|Accepted to ICLR 2021\n2107.13034|Distillation|Title|2021-07-27|v3|2022-01-17|cs.LG|Comments|NeurIPS 2021\n2110.04181|Condensation|Title|2021-10-08|v2|2022-04-21|cs.LG|Journal reference|Proceedings of the IEEE/CVF Winter Conference on Applications of Computer Vision 2023 (WACV)","metadata":{"State-Gated Retrieval":["Only include arXiv records where v1 submitted falls between 2019-01-01 and 2021-12-31.","The title or abstract must explicitly use a phrase from the \"dataset distillation\" or \"dataset condensation\" family, and the semantics must refer to replacing large-scale training sets with a small number of synthetic training data points.","The current primary category must be cs.LG. Do not include records that are only cross-listed into Machine Learning by other primary-category papers.","The paper must have a version update in the calendar year following its initial submission, and the current record must still clearly indicate a subsequent publication venue."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Root searches yield candidate arXiv IDs","Each candidate abstract page yields primary category, v1 date, first next-year version, cue location, and publication-trail source","Answer rows are produced only after deduplication and detail-page validation"],"control_dependency":["Records must be filtered by original submission year, with per-record validation that a next-calendar-year version exists","Cross-listed-only hits must be excluded, and the current primary category must be validated on abstract pages","Searches must cover both Title and Abstract because valid distillation hits can appear only in the abstract","Topic matches without a current publication trail still fail until the Comments, Journal reference, or Related DOI field is checked on the record page"],"freeze":{"historical_window":"v1 year in {2019, 2020, 2021}"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only include arXiv records where v1 submitted falls between 2019-01-01 and 2021-12-31.","The title or abstract must explicitly use a phrase from the \"dataset distillation\" or \"dataset condensation\" family, and the semantics must refer to replacing large-scale training sets with a small number of synthetic training data points.","The current primary category must be cs.LG. Do not include records that are only cross-listed into Machine Learning by other primary-category papers.","The paper must have a version update in the calendar year following its initial submission, and the current record must still clearly indicate a subsequent publication venue."],"exclusion_conditions":["Exclude records whose current primary category is not cs.LG and are only cross-listed to cs.LG.","Exclude records where the title or abstract contains the words \"distillation\" or \"condensation\" but does not correspond to the dataset distillation or dataset condensation research line.","Exclude records that have no next-calendar-year version update, or whose current record contains no clearly visible publication clue."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"required literal first row shown in the oracle","schema":["arXiv ID","term family","cue location","v1 submitted","first next-year version","date of that version","primary category","publication-trail source","current publication clue"],"dedup_key":"bare arXiv ID without version suffix","date_format":"YYYY-MM-DD","term_family_extraction":{"allowed_families":["Distillation","Condensation"],"tie_break":"if both families appear, prefer the title hit; if both appear only in the abstract, keep the first abstract occurrence"},"cue_location":{"Title":"qualifying cue appears only in the title","Abstract-only":"qualifying cue appears only in the abstract","Title + Abstract":"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name"},"publication_trail_source":["Comments","Journal reference","Related DOI"],"current_publication_clue":"keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue","sorting_or_selection":{"primary":"v1 submitted ascending","secondary":"arXiv ID ascending"},"stop_condition":["all four corrected result pages are exhausted","all unique candidate IDs are opened to abstract-page depth","for every surviving candidate, the abstract page, current browse context, and publication-trail fields are checked before emitting the final ordered table"]}}} +{"task_id":"arxiv_002","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":10,"instruction":"I am compiling a reading list of 2022 research on reasoning prompts for large language models. I want to find arXiv papers whose first version was submitted in 2022 and that explicitly focus on chain-of-thought or self-consistency reasoning methods. Start with arXiv records first submitted in 2022. First, check whether the title or abstract explicitly contains clues related to chain-of-thought or self-consistency. Then, retain only papers whose primary category is Computation and Language; do not include records that are only cross-listed from other primary categories. Next, verify that these papers actually had a version update in 2023, and confirm that the current arXiv record's comments field clearly indicates subsequent publication information. Finally, output a table sorted in ascending order by the date of each paper's earliest 2023 version update, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2023 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Finally, output a table sorted in ascending order by the date of each paper's earliest 2023 version update, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2023 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.","oracle_answer":"arXiv ID|cue family|cue location|v1 submitted|first 2023 version|date of that version|primary category|publication clue\n2210.01240|Chain-of-thought|Title + Abstract|2022-10-03|v2|2023-01-25|cs.CL|Published as a conference paper at ICLR 2023\n2205.11916|Chain-of-thought|Abstract-only|2022-05-24|v4|2023-01-29|cs.CL|Accepted to NeurIPS2022\n2203.11171|Self-consistency; Chain-of-thought|Title + Abstract|2022-03-21|v4|2023-03-07|cs.CL|Published at ICLR 2023; camera ready version at ICLR 2023\n2210.03629|Chain-of-thought|Abstract-only|2022-10-06|v3|2023-03-10|cs.CL|v3 is the ICLR camera ready version\n2210.03350|Chain-of-thought|Abstract-only|2022-10-07|v2|2023-05-23|cs.CL|To appear at Findings of EMNLP 2023\n2212.10001|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-01|cs.CL|ACL-23 Camera Ready\n2212.08061|Chain-of-thought|Abstract-only|2022-12-15|v2|2023-06-04|cs.CL|ACL 2023 Main Conference\n2212.10071|Chain-of-thought|Abstract-only|2022-12-20|v2|2023-06-13|cs.CL|ACL 2023 camera-ready\n2212.10509|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-23|cs.CL|ACL'23 Camera Ready\n2211.12588|Chain-of-thought; Self-consistency|Abstract-only|2022-11-22|v4|2023-10-23|cs.CL|Published at TMLR 2023","metadata":{"State-Gated Retrieval":["Only include arXiv papers whose v1 was submitted in 2022.","The title or abstract must explicitly contain clues related to chain-of-thought or self-consistency.","The current primary category must be cs.CL; do not include records that are only cross-listed from other primary categories.","Must have had a version update in 2023, and the current comments field must clearly indicate subsequent publication information."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["root searches yield candidate arXiv IDs","each candidate abstract page yields primary category, v1 date, first 2023 version, comments/publication clue","answer rows are produced only after deduplication and detail-page validation"],"control_dependency":["searches must cover both Title and Abstract fields because valid rows can appear only in the abstract","cross-listed hits whose primary category is not cs.CL must be excluded, and the primary category must be validated on the abstract page","topic-matched hits must be validated against a current Comments publication clue before they can be accepted","2023 candidates must be identified by original submission year and full version-history checks, rather than by latest-date proxies"],"freeze":{"historical_window":"v1 submitted in 2022; version-history event in 2023"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only include arXiv papers whose v1 was submitted in 2022.","The title or abstract must explicitly contain clues related to chain-of-thought or self-consistency.","The current primary category must be cs.CL; do not include records that are only cross-listed from other primary categories.","Must have had a version update in 2023, and the current comments field must clearly indicate subsequent publication information."],"exclusion_conditions":["Exclude records whose current primary category is not cs.CL, even if they appear in relevant search results.","Exclude records that contain only vague abbreviations or weakly related hints, but whose title and abstract lack explicit CoT/self-consistency semantics.","Exclude records that have no 2023 version update, or whose current record lacks a direct publication clue."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"required literal first row shown in the oracle","schema":["arXiv ID","cue family","cue location","v1 submitted","first 2023 version","date of that version","primary category","publication clue"],"dedup_key":"bare arXiv ID without version suffix","date_format":"YYYY-MM-DD","cue_family":["Chain-of-thought","Self-consistency"],"cue_location":{"Title":"qualifying cue appears only in the title","Abstract-only":"qualifying cue appears only in the abstract","Title + Abstract":"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name"},"publication_clue":{"source":"Comments field only","extraction":"keep the shortest phrase that still preserves the current publication-status clue"},"sorting_or_selection":{"primary":"date of the earliest 2023 version ascending","secondary":"arXiv ID ascending"},"stop_condition":["all corrected result pages are exhausted","all unique candidate IDs are opened to abstract-page depth","for every surviving candidate, the current browse context, Comments field, and full Submission history are checked before emitting the final ordered table"]}}} +{"task_id":"arxiv_003","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"I am compiling a reading list of early vision Transformer research. Identify arXiv papers whose first version was submitted in Q4 2020 and whose title or abstract explicitly uses vision- or image-domain Transformer terminology. First, filter for papers with a first-submission date in Q4 2020. Then check whether the title or abstract explicitly contains vision- or image-related Transformer expressions. Retain only papers whose primary category is Computer Vision and Pattern Recognition. Next, confirm that the paper had at least one version update in 2021, and check whether the current arXiv record clearly indicates subsequent publication information. Finally, output a table sorted in ascending order by the date of each paper's earliest 2021 version. Columns: arXiv ID, cue family, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying items exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Output a table sorted in ascending order by the date of each paper's earliest 2021 version. Columns: arXiv ID, cue family, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying items exist, output NONE.","oracle_answer":"arXiv ID|cue family|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication-trail source|current publication clue\n2101.01097|Vision Transformer|Abstract-only|2020-12-30|v2|2021-01-08|cs.CV|Journal reference|IEEE Int. Conf. on Image Processing (ICIP) 2021\n2012.12556|Visual Transformer; Vision Transformer|Title + Abstract|2020-12-23|v2|2021-01-15|cs.CV|Comments; Related DOI|Accepted by TPAMI 2022; 10.1109/TPAMI.2022.3152247\n2012.00364|Image Processing Transformer|Title + Abstract|2020-12-01|v3|2021-05-28|cs.CV|Comments|CVPR 2021\n2011.08019|Vision Transformer|Title + Abstract|2020-11-16|v2|2021-06-02|cs.CV|Comments|Accepted for Publication in IJCB2021\n2010.11929|Vision Transformer|Abstract-only|2020-10-22|v2|2021-06-03|cs.CV|Comments|ICLR camera-ready version","metadata":{"State-Gated Retrieval":["Only include arXiv papers whose v1 submitted date falls in Q4 2020.","The title or abstract must explicitly contain vision- or image-domain Transformer-related expressions.","The current primary category must be cs.CV.","The paper must have had a version update in 2021, and the current record must clearly indicate a subsequent publication venue."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["root searches yield candidate arXiv IDs","candidate abstract pages yield v1 submitted date, first 2021 version, primary category, cue location, and publication-trail source","answer rows depend on deduplication plus detail-page validation"],"control_dependency":["searches must cover both Title and Abstract because valid positives can appear only in the abstract","candidate eligibility must be determined by the original-submission date window rather than by arXiv-ID or announcement intuition","candidate filtering must use full Submission-history validation rather than most-recent-submission filtering","searches must use the broader semantic cue state rather than a ViT-only entry point, because ViT-only hits can be false positives","publication-trail false positives still require Comments / Journal reference / Related DOI validation before final inclusion"],"freeze":{"historical_window":"v1 submitted from 2020-10-01 through 2020-12-31; version-history event in 2021"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only include arXiv papers whose v1 submitted date falls in Q4 2020.","The title or abstract must explicitly contain vision- or image-domain Transformer-related expressions.","The current primary category must be cs.CV.","The paper must have had a version update in 2021, and the current record must clearly indicate a subsequent publication venue."],"exclusion_conditions":["Exclude records whose current primary category is not cs.CV and are only cross-listed.","Exclude records that contain only weak cues such as Transformer or ViT, but whose title and abstract lack explicit vision- or image-domain expressions.","Exclude records that had no version update in 2021, or whose current record contains no direct publication clue."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"required literal first row shown in the oracle","schema":["arXiv ID","cue family","cue location","v1 submitted","first 2021 version","date of that version","primary category","publication-trail source","current publication clue"],"dedup_key":"bare arXiv ID without version suffix","date_format":"YYYY-MM-DD","cue_family_extraction":"record every qualifying family actually present and join multiple families with `; ` in the emitted field","cue_location":{"Title":"qualifying cue appears only in the title","Abstract-only":"qualifying cue appears only in the abstract","Title + Abstract":"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name"},"publication_trail_source":["Comments","Journal reference","Related DOI"],"current_publication_clue":"keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue","sorting_or_selection":{"primary":"date of the earliest 2021 version ascending","secondary":"arXiv ID ascending"},"stop_condition":["all corrected result pages are exhausted","all unique candidate IDs are opened to abstract-page depth","for every surviving candidate, the abstract page, current browse context, Comments field, Journal reference, Related DOI, and full Submission history are checked before emitting the final ordered table"]}}} +{"task_id":"arxiv_004","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"I am compiling a reading list of certified robustness defense research from the first half of 2020. I want to find arXiv papers whose first version was submitted between January and June 2020 and whose title or abstract explicitly focuses on smoothed classifiers, randomized smoothing and its variants, certified defenses against backdoor or poisoning attacks, or partition aggregation. Start with arXiv records whose first submission date falls between January and June 2020. Check whether the title or abstract explicitly mentions randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor/poisoning, or partition aggregation. Then retain only papers whose primary category is Machine Learning; do not include records that are only cross-listed from other primary categories. Next, confirm that these papers actually had a version update in 2021, and check whether the current arXiv record clearly indicates formal publication or acceptance information. Finally, output a table sorted by the date of each paper's earliest 2021 version in ascending order, with columns: arXiv ID, defense family, threat/topic cue, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Finally, output a table sorted by the date of each paper's earliest 2021 version in ascending order, with columns: arXiv ID, defense family, threat/topic cue, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.","oracle_answer":"arXiv ID|defense family|threat/topic cue|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication clue\n2002.10733|De-randomized smoothing; Randomized smoothing|patch attacks|Title + Abstract|2020-02-25|v3|2021-01-08|cs.LG|NeurIPS 2020\n2006.04062|Smoothed classifiers; Randomized smoothing|certified L2 robustness|Title + Abstract|2020-06-07|v4|2021-01-08|cs.LG|NeurIPS 2020\n2003.08904|RAB; Randomized smoothing|backdoor attacks|Title + Abstract|2020-03-19|v4|2021-02-26|cs.LG|IEEE Symposium on Security and Privacy 2023\n2006.14768|Deep Partition Aggregation|general poisoning attacks; label-flipping poisoning attacks|Title + Abstract|2020-06-26|v2|2021-03-18|cs.LG|ICLR 2021\n2002.12398|Transformation-specific smoothing; Randomized smoothing|semantic transformations|Title + Abstract|2020-02-27|v4|2021-09-17|cs.LG|2021 ACM SIGSAC Conference on Computer and Communications Security (CCS '21)","metadata":{"State-Gated Retrieval":["Only include arXiv papers whose v1 submission date falls between 2020-01-01 and 2020-06-30.","The title or abstract must explicitly focus on randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor or poisoning attacks, or partition aggregation.","The current primary category must be cs.LG.","The paper must have had a version update in 2021, and the current record must clearly indicate formal publication or acceptance information."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["root searches yield candidate arXiv IDs","candidate abstract pages yield v1 date, primary category, full Submission history, cue location, and current publication clue","final rows depend on deduplication plus detail-page validation"],"control_dependency":["candidate filtering must use the original-submission window together with full 2021 version-history validation, because valid rows can have later newest versions","cross-listed hits whose primary category is not the target category must be excluded, with category validation on detail pages","searches must cover the broader certified-defense family, including partition-aggregation and backdoor/poisoning variants, rather than smoothing-only entries","topic+venue hits must be confirmed by detail-history validation that a 2021 version actually exists"],"freeze":{"historical_window":"v1 submitted from 2020-01-01 through 2020-06-30; version-history event in 2021"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only include arXiv papers whose v1 submission date falls between 2020-01-01 and 2020-06-30.","The title or abstract must explicitly focus on randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor or poisoning attacks, or partition aggregation.","The current primary category must be cs.LG.","The paper must have had a version update in 2021, and the current record must clearly indicate formal publication or acceptance information."],"exclusion_conditions":["Exclude records whose current primary category is not cs.LG, even if semantically related.","Exclude records that are only broadly related to robustness, defense, or backdoor/poisoning but do not meet the required certified-defense semantics.","Exclude records that have no version update in 2021 or no current publication clue."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"required literal first row shown in the oracle","schema":["arXiv ID","defense family","threat/topic cue","cue location","v1 submitted","first 2021 version","date of that version","primary category","publication clue"],"dedup_key":"bare arXiv ID without version suffix","date_format":"YYYY-MM-DD","defense_family_extraction":"record every qualifying defense family actually present and join multiple families with `; ` in the emitted field","threat_topic_cue":"keep the shortest qualifying threat or topic cue that justifies inclusion","cue_location":{"Title":"qualifying cue appears only in the title","Abstract-only":"qualifying cue appears only in the abstract","Title + Abstract":"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name"},"publication_clue":"keep the shortest phrase that still preserves venue or publication-status information","sorting_or_selection":{"primary":"date of the earliest 2021 version ascending","secondary":"arXiv ID ascending"},"stop_condition":["all corrected result pages are exhausted","all unique candidate IDs are opened to abstract-page depth","for every surviving candidate, the abstract page, current browse context, Comments field, and full Submission history are checked before emitting the final ordered table"]}}} +{"task_id":"census_001","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":20,"instruction":"Using the 2014–2018 American Community Survey 5-year estimates, identify counties with limited internet access, a high share of seniors living alone, weak transportation conditions, and low income. Scope the analysis to North Carolina counties from this dataset and use the North Carolina statewide values from the same release as the comparison baseline. First, select counties with at least 4,000 households lacking internet access. Then, retain only counties that simultaneously meet all of the following conditions: share of households without internet access higher than the statewide share; share of households with a householder aged 65 or older living alone higher than the statewide share; share of households without a vehicle higher than the statewide share; and median household income lower than the statewide median. Finally, output all qualifying counties as a single line, sorted alphabetically by county name. Each county should be formatted as County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome, with counties separated by commas. Percentage fields should be given to three decimal places without a percent sign.","start_url":"https://www.census.gov/data.html","output_format":"Output all qualifying counties as a single line, sorted alphabetically by county name. Each county should be formatted as County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome, with counties separated by commas. Percentage fields should be given to three decimal places without a percent sign.","oracle_answer":"Beaufort County|5988|30.986|16.083|7.664|43688,Bladen County|4194|30.026|13.681|10.417|32378,Cleveland County|11599|31.449|12.469|7.825|40393,Columbus County|7371|33.045|15.148|7.958|36398,Duplin County|7574|34.773|14.370|7.424|38850,Edgecombe County|7454|34.879|13.720|11.225|35516,Halifax County|7575|35.873|14.657|11.565|34251,Lenoir County|4923|21.292|15.614|11.699|38387,Nash County|8617|23.467|13.597|7.917|48362,Richmond County|5193|28.001|13.706|9.269|36091,Robeson County|19814|43.103|11.312|9.854|33679,Rockingham County|9938|26.714|14.166|7.164|42490,Rutherford County|7583|28.783|16.033|6.335|40347,Sampson County|8216|34.907|14.088|7.686|39068,Scotland County|4971|37.909|13.910|11.470|35617,Surry County|7595|26.203|13.762|6.779|41068,Vance County|5131|30.444|12.347|11.600|37282,Wayne County|9709|20.163|11.742|8.456|42192,Wilkes County|7046|24.849|14.773|5.992|40829,Wilson County|7652|23.817|13.322|9.540|42850","metadata":{"State-Gated Retrieval":["Use only North Carolina county data from the 2014-2018 American Community Survey 5-year estimates, and use the North Carolina statewide values from the same release as the comparison baseline.","Retain only counties with at least 4,000 households lacking internet access, and where the share of households without internet access, the share of households with a householder aged 65+ living alone, and the share of households without a vehicle are all higher than the statewide shares, and the median household income is lower than the statewide median.","Output the final results sorted alphabetically by county name, retaining the six required fields."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the 2014-2018 ACS 5-year product and North Carolina county geography yield the full county candidate set plus the statewide baseline row","the relevant ACS tables yield no-internet households, senior-living-alone share, no-vehicle share, and median household income for each county and the state baseline","final rows are produced only after the 5-year product/geography setup is fixed consistently and the full county filtering chain is executed from B28002 through the downstream filters"],"control_dependency":["the 2018 ACS 5-year Detailed Tables product must be used instead of the 2018 ACS 1-year product","county coverage must be established under one consistent product-and-geography setup rather than by piecemeal fixes within the current table","all downstream county comparisons must use the same 5-year statewide baseline and the same all-counties geography"],"freeze":{"historical_window":"2014-2018 American Community Survey 5-year estimates for North Carolina counties, using the North Carolina statewide row from the same release as the comparison baseline"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Use only North Carolina county data from the 2014-2018 American Community Survey 5-year estimates, and use the North Carolina statewide values from the same release as the comparison baseline.","Retain only counties with at least 4,000 households lacking internet access, and where the share of households without internet access, the share of households with a householder aged 65+ living alone, and the share of households without a vehicle are all higher than the statewide shares, and the median household income is lower than the statewide median.","Output the final results sorted alphabetically by county name, retaining the six required fields."],"exclusion_conditions":["Exclude results that incorrectly use the 2018 ACS 1-Year Estimates Detailed Tables or any other non-2014-2018 5-year release.","Exclude results that do not use the North Carolina statewide row from the same release as the comparison baseline.","Exclude any county that does not meet any one of the thresholds or statewide comparison conditions."],"normalization":{"field_separator":"|","record_separator":",","schema":["County","NoInternetHH","NoInternetRatePct","SeniorLivingAloneSharePct","NoVehicleRatePct","MedianIncome"],"county":"use the county display name including the word `County` and excluding a trailing state suffix","dedup_key":"county FIPS / GEOID","percentage_fields":"all percentage fields are plain numbers with exactly three decimal places and no percent sign","numeric_fields":"household counts and median income are emitted as plain integers without commas","sorting_or_selection":"county name alphabetical ascending","stop_condition":["the North Carolina statewide threshold is fixed once from the designated table","all 100 North Carolina counties are covered under the same table/product settings","every surviving county is validated against all four required tables before emission"]}}} +{"task_id":"census_002","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"Using the 2015–2019 American Community Survey 5-year estimates, identify New Mexico counties that simultaneously have a large renter population, significant language barriers, limited internet access, transportation difficulties, low income, and rental stress. Use the New Mexico county-level data from this release and the New Mexico statewide values from the same release as the comparison baseline. First, retain counties with at least 2,500 renter households and at least 500 limited-English-proficient households. Then, keep only counties that meet all of the following conditions: the share of limited-English-proficient households is higher than the statewide share; the share of households with no internet access is higher than the statewide share; the share of households with no vehicle is higher than the statewide share; and the median household income is lower than the statewide median. Next, evaluate the rental housing stress indicators for renter households. Retain only counties that meet at least one of the following: the share of renter households with a rent-to-income ratio of 35% or more is higher than the statewide share, or the share of renter households with more than one occupant per room is higher than the statewide share. If both conditions are met, indicate both. Finally, output all qualifying counties as a single line, sorted alphabetically by county name. Each county should be formatted as County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath, with counties separated by commas. StressPath must be RENT, CROWD, or BOTH. Percentage fields should have three decimal places and no percent sign.","start_url":"https://data.census.gov/advanced","output_format":"Output all qualifying counties as a single line, sorted alphabetically by county name. Each county should be formatted as County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath, with counties separated by commas. StressPath must be RENT, CROWD, or BOTH. Percentage fields should have three decimal places and no percent sign.","oracle_answer":"Doña Ana County|28729|7883|10.127|22.612|6.079|44.172|6.391|40973|BOTH,Luna County|3482|1109|12.455|34.030|8.165|42.700|1.407|29360|RENT,McKinley County|6090|1610|7.688|50.587|10.978|27.568|16.256|33834|CROWD,San Miguel County|3443|1200|10.337|38.470|7.684|47.376|2.440|30946|RENT,Taos County|2854|652|5.387|28.844|5.726|48.823|4.555|38329|RENT","metadata":{"State-Gated Retrieval":["Use only the 2015-2019 American Community Survey 5-year estimates for New Mexico counties, and use the New Mexico statewide values from the same release as the comparison baseline.","Candidate counties must have at least 2,500 renter households and at least 500 limited-English-proficient households. Additionally, the LEP share, no-internet share, and no-vehicle share must all be higher than the statewide shares, and the median household income must be lower than the statewide median.","LEPHH must be computed by summing all four limited-English language groups from C16002. Finally, retain only counties where at least one of Severe Rent Burden or Crowded Renter is higher than the statewide value, and write StressPath according to the rule."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the 2015-2019 ACS 5-year county geography yields New Mexico county candidates and the statewide baseline row","C16002 and the downstream housing/income tables yield LEPHH, LEP share, no-internet share, no-vehicle share, severe rent burden, crowded-renter share, and median income for counties and the state baseline","final rows are produced only after the LEPHH numerator is computed from all four limited-English language groups and the downstream stress-path filters are applied"],"control_dependency":["the LEPHH numerator must be computed from all four limited-English language groups in C16002 rather than from Spanish-only counts","county eligibility and StressPath labels must be determined from the LEPHH measure and statewide LEP baseline defined under that full four-group calculation","the RENT / CROWD / BOTH classification must be determined by evaluating the same county set against both downstream housing-stress branches"],"freeze":{"historical_window":"2015-2019 American Community Survey 5-year estimates for New Mexico counties, using the New Mexico statewide row from the same release as the comparison baseline"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Use only the 2015-2019 American Community Survey 5-year estimates for New Mexico counties, and use the New Mexico statewide values from the same release as the comparison baseline.","Candidate counties must have at least 2,500 renter households and at least 500 limited-English-proficient households. Additionally, the LEP share, no-internet share, and no-vehicle share must all be higher than the statewide shares, and the median household income must be lower than the statewide median.","LEPHH must be computed by summing all four limited-English language groups from C16002. Finally, retain only counties where at least one of Severe Rent Burden or Crowded Renter is higher than the statewide value, and write StressPath according to the rule."],"exclusion_conditions":["Exclude results that treat Spanish-only limited-English households as the entire LEPHH count.","Exclude results that do not use the statewide baseline from the same release or that do not recalculate LEPHH/LEPSharePct/LEPShare_state.","Exclude counties that do not meet the final stress-path condition of RENT, CROWD, or BOTH."],"normalization":{"field_separator":"|","record_separator":",","schema":["County","RenterHH","LEPHH","LEPSharePct","NoInternetPct","NoVehiclePct","SevereRentBurdenPct","CrowdedRenterPct","MedianIncome","StressPath"],"county":"use the county display name including the word `County` and excluding a trailing state suffix","dedup_key":"county FIPS / GEOID","LEPHH":"sum the four designated limited-English-proficient renter-household cells before emitting the integer total","percentage_fields":"all percentage fields are plain numbers with exactly three decimal places and no percent sign","numeric_fields":"household counts and median income are emitted as plain integers without commas","StressPath":{"allowed_values":["RENT","CROWD","BOTH"],"rule":"emit BOTH only when both the severe-rent-burden and crowded-renter signals survive; otherwise emit the single surviving label"},"sorting_or_selection":"county name alphabetical ascending","stop_condition":["all candidate counties are validated under the same geography and product settings","the renter scope and LEP aggregation are checked before the final line is emitted"]}}} +{"task_id":"census_003","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"I am compiling a pre-pandemic county screening list for the California Department of Education to identify counties where, during annual school meal applications and parent data updates, schools cannot rely solely on English online portals and must still provide paper materials and in-person assistance. Use California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline. First, select counties with a population aged 5–17 of at least 75,000. Then, retain counties with at least 2,000 individuals aged 5–17 who speak English \"not well\" or \"not at all\" and whose share of the 5–17 population exceeds the statewide share. Next, check these counties' digital access and income conditions: the share of households with no internet access must exceed the statewide share, and the median household income must be below the statewide median. Finally, among three offline support signals, retain counties where at least two exceed the statewide share: the share of households with no vehicle, the share of minors in households that received SSI, cash public assistance, Food Stamps, or SNAP in the past 12 months, and the share of renter-occupied housing units with more than one occupant per room. Output all qualifying counties in a single line, sorted alphabetically by county name. Each county should be formatted as County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath, with counties separated by commas. SupportPath uses only the three labels BENEFITS, CROWD, and MOBILITY: the public assistance signal corresponds to BENEFITS, the crowded housing signal corresponds to CROWD, and the no-vehicle signal corresponds to MOBILITY. If multiple labels apply, join them with + in the fixed order BENEFITS+CROWD+MOBILITY.","start_url":"https://data.census.gov/advanced","output_format":"Output all qualifying counties in a single line, sorted alphabetically by county name. Each county should be formatted as County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath, with counties separated by commas. SupportPath uses only the three labels BENEFITS, CROWD, and MOBILITY: the public assistance signal corresponds to BENEFITS, the crowded housing signal corresponds to CROWD, and the no-vehicle signal corresponds to MOBILITY. If multiple labels apply, join them with + in the fixed order BENEFITS+CROWD+MOBILITY.","oracle_answer":"Fresno County|200205|5127|2.561|20.588|8.686|46.388|13.967|48730|BENEFITS+CROWD+MOBILITY,Kern County|185802|4130|2.223|21.739|7.058|37.285|14.394|50826|BENEFITS+CROWD,Los Angeles County|1641669|37540|2.287|16.338|9.204|27.238|16.741|61015|BENEFITS+CROWD+MOBILITY,Tulare County|104542|2703|2.586|25.738|6.274|49.347|14.535|44871|BENEFITS+CROWD","metadata":{"State-Gated Retrieval":["Use only California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline.","Retain only counties with a population aged 5–17 of at least 75,000, a SchoolAgeLEP of at least 2,000 with a share exceeding the statewide share, a no-internet share exceeding the statewide share, and a median household income below the statewide median.","SchoolAgeLEP must be the sum of the eight \"not well\" and \"not at all\" cells across the four major language groups in B16004. The final county must also have at least two of the three offline support signals (Mobility, Benefits, Crowd) exceeding the statewide share."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["The 2013–2017 ACS 5-year county geography yields California county candidates and the statewide baseline row.","B16004 and the downstream access/income/support tables yield SchoolAgeLEP, no-internet share, no-vehicle share, child-benefit share, crowded-renter share, and median income for counties and the statewide baseline.","Final rows are produced only after the SchoolAgeLEP numerator is computed from all eight 1980-target language cells and the downstream support-path branches are applied."],"control_dependency":["The SchoolAgeLEP numerator must be computed from the full eight-cell language set in B16004 rather than from only two Spanish LEP cells.","County eligibility and SupportPath labels must be determined from the LEP numerator and candidate set defined under that full eight-cell calculation.","The BENEFITS / CROWD / MOBILITY path labels must be determined by applying all three downstream support branches to the same county set."],"freeze":{"historical_window":"2013–2017 American Community Survey 5-year estimates for California counties, using the California statewide row from the same release as the comparison baseline."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Use only California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline.","Retain only counties with a population aged 5–17 of at least 75,000, a SchoolAgeLEP of at least 2,000 with a share exceeding the statewide share, a no-internet share exceeding the statewide share, and a median household income below the statewide median.","SchoolAgeLEP must be the sum of the eight \"not well\" and \"not at all\" cells across the four major language groups in B16004. The final county must also have at least two of the three offline support signals (Mobility, Benefits, Crowd) exceeding the statewide share."],"exclusion_conditions":["Exclude results that only take the two Spanish LEP rows and do not combine all eight target cells.","Exclude results that do not re-run the B28011, B19013, B08201, B09010, and B25014 branches.","Exclude counties whose final SupportPath does not have at least two signals exceeding the statewide share."],"normalization":{"field_separator":"|","record_separator":",","schema":["County","SchoolAgePop","SchoolAgeLEP","LEPSharePct","NoInternetPct","NoVehiclePct","ChildBenefitSharePct","CrowdedRenterPct","MedianIncome","SupportPath"],"county":"Use the county display name including the word `County` and excluding a trailing state suffix.","dedup_key":"county FIPS / GEOID","SchoolAgeLEP":"Sum the eight designated school-age LEP cells before emitting the integer total.","percentage_fields":"All percentage fields are plain numbers with exactly three decimal places and no percent sign.","numeric_fields":"Population counts and median income are emitted as plain integers without commas.","SupportPath":"Use only BENEFITS, CROWD, and MOBILITY, and when multiple labels apply join them with `+` in the fixed order BENEFITS+CROWD+MOBILITY.","sorting_or_selection":"County name alphabetical ascending.","stop_condition":["All candidate counties are validated under the same geography and product settings.","The school-age LEP aggregation and all three support-signal gates are checked before the final line is emitted."]}}} +{"task_id":"census_004","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":7,"instruction":"Using 2012–2016 American Community Survey 5-year estimates, identify Pennsylvania counties with high senior evacuation support needs that warrant proactive in-person outreach before winter storms. Use Pennsylvania county-level data from the 2012–2016 American Community Survey 5-year estimates, with Pennsylvania statewide values from the same release as the comparison baseline. First, retain counties with a population aged 65 and over of at least 15,000. Then, among those, keep counties with at least 4,000 people aged 65 and over who have ambulatory difficulty, and whose share exceeds the statewide share. Additionally, the county median household income must be below the statewide median. Next, evaluate four evacuation support barriers: share of households with a householder aged 65+ living alone, share of households with no vehicle, share of renter households with no vehicle, and share of mobile homes among all housing units. Retain only counties where at least two of these barriers exceed the statewide values. Finally, output all qualifying counties in a single line, sorted alphabetically by county name. Each county should be formatted as County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath, with counties separated by commas. For BarrierPath, use only the labels ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE. If multiple labels apply, join them with + in the fixed order ALONE+MOBILE_HOME+NO_VEHICLE+RENTER_NO_VEHICLE.","start_url":"https://www.census.gov/data.html","output_format":"Output all qualifying counties in a single line, sorted alphabetically by county name. Each county should be formatted as County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath, with counties separated by commas. For BarrierPath, use only the labels ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE. If multiple labels apply, join them with + in the fixed order ALONE+MOBILE_HOME+NO_VEHICLE+RENTER_NO_VEHICLE.","oracle_answer":"Blair County|23013|5576|24.230|14.917|9.440|24.316|6.388|44033|ALONE+MOBILE_HOME, Cambria County|27058|6308|23.313|15.243|10.309|26.627|4.070|42917|ALONE+MOBILE_HOME+RENTER_NO_VEHICLE, Fayette County|25186|5886|23.370|14.961|9.302|22.290|10.489|40511|ALONE+MOBILE_HOME, Lycoming County|19486|4311|22.124|12.164|9.257|23.312|6.726|48731|ALONE+MOBILE_HOME, Mercer County|21537|4799|22.283|14.090|9.572|24.413|7.912|45831|ALONE+MOBILE_HOME, Philadelphia County|188185|56935|30.255|11.553|30.954|44.924|0.250|39770|NO_VEHICLE+RENTER_NO_VEHICLE, Schuylkill County|26613|6465|24.293|14.357|9.676|23.652|4.080|46573|ALONE+MOBILE_HOME","metadata":{"State-Gated Retrieval":["Use only Pennsylvania county-level data from the 2012-2016 American Community Survey 5-year estimates, and use Pennsylvania statewide values from the same release as the comparison baseline.","Retain only counties with a population aged 65 and over of at least 15,000, at least 4,000 people aged 65 and over with ambulatory difficulty and a share higher than the statewide share, and a median household income below the statewide median.","The 65+ ambulatory difficulty numerator must combine the four target cells from B18105 for ages 65-74 and 75+, male and female. The final county must also have at least two of the four barriers—Alone, No Vehicle, Renter No Vehicle, Mobile Home—higher than the statewide values."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["ACS tables B01001 and B18105 yield county senior-population totals and the full 65+ ambulatory-difficulty numerator.","Statewide comparison tables yield Pennsylvania baselines plus county barrier metrics for living alone, no vehicle, renter no vehicle, mobile home, and median income.","Final rows are produced only after the county candidate set is defined from the full ambulatory-difficulty numerator and the downstream six-table filters are applied."],"control_dependency":["The ambulatory-difficulty numerator must include the full 65+ population across 65-74 and 75+ and male and female cells, rather than only the 75+ cells.","Downstream county eligibility and barrier labels must be determined from the county candidate set defined under that full ambulatory numerator.","The at-least-two-barriers test must compare every county metric against the same Pennsylvania statewide baselines from the same ACS release."],"freeze":{"historical_window":"2012-2016 American Community Survey 5-year estimates for Pennsylvania counties, with Pennsylvania statewide baselines taken from the same release."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Use only Pennsylvania county-level data from the 2012-2016 American Community Survey 5-year estimates, and use Pennsylvania statewide values from the same release as the comparison baseline.","Retain only counties with a population aged 65 and over of at least 15,000, at least 4,000 people aged 65 and over with ambulatory difficulty and a share higher than the statewide share, and a median household income below the statewide median.","The 65+ ambulatory difficulty numerator must combine the four target cells from B18105 for ages 65-74 and 75+, male and female. The final county must also have at least two of the four barriers—Alone, No Vehicle, Renter No Vehicle, Mobile Home—higher than the statewide values."],"exclusion_conditions":["Exclude results that take only the 75 years and over ambulatory difficulty cells and mistakenly treat them as the full 65+ value.","Exclude results that do not use the Pennsylvania statewide baselines from the same release.","Exclude counties whose final BarrierPath does not satisfy the condition of at least two barriers higher than the statewide values."],"normalization":{"field_separator":"|","record_separator":",","schema":["County","SeniorPop","AmbulatoryDifficulty65Plus","AmbDiffPct","SeniorLivingAloneSharePct","NoVehiclePct","RenterNoVehiclePct","MobileHomePct","MedianIncome","BarrierPath"],"county":"Use the county display name including the word `County` and excluding a trailing state suffix.","dedup_key":"county FIPS / GEOID","percentage_fields":"All percentage fields are plain numbers with exactly three decimal places and no percent sign.","numeric_fields":"Population counts and median income are emitted as plain integers without commas.","BarrierPath":"Use only ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE. When multiple labels apply, join them with `+` in the fixed order ALONE+MOBILE_HOME+NO_VEHICLE+RENTER_NO_VEHICLE.","sorting_or_selection":"county name alphabetical ascending","stop_condition":["All candidate counties are validated under the same geography and product settings.","The senior ambulatory-difficulty gate and all barrier-signal gates are checked before the final line is emitted."]}}} +{"task_id":"climategov_001","domain":"NOAA_NCEI_CLIMATE_AT_A_GLANCE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"Screen the four South Texas climate divisions (South Central, Upper Coast, South, and Lower Valley) to identify divisions that remained near-normal to wet over two longer periods yet still had low heating demand in March 1966. Restrict the search strictly to these four divisions; use the official Texas climate-division page for their exact names and numbers.\n\nRetain only divisions that meet all three of the following criteria:\n- The 10-month Palmer Z-Index anomaly ending February 1966 must be at least -0.05.\n- The 24-month Palmer Z-Index anomaly ending December 1966 must be at least -0.10.\n- The March 1966 single-month Heating Degree Days actual value must be below 200°Df.\n\nAfter identifying qualifying divisions, sort them as follows:\n- Primary: sum of the February 1966 10-month Z anomaly and the December 1966 24-month Z anomaly, in descending order.\n- Secondary: March 1966 Heating Degree Days actual value, in ascending order.\n- Tertiary: Texas division number, in ascending order.\n\nOutput a single-line string with qualifying entries separated by commas. Each entry must follow this exact format:\n|||||\n\nThe moisture score is the sum of the February 1966 10-month Z anomaly and the December 1966 24-month Z anomaly, formatted to two decimal places. If no division qualifies, output NONE.","start_url":"https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national","output_format":"Output a single-line string with qualifying entries separated by commas. Each entry must follow this exact format:\n|||||\nThe moisture score is the sum of the February 1966 10-month Z anomaly and the December 1966 24-month Z anomaly, formatted to two decimal places. If no division qualifies, output NONE.","oracle_answer":"7|South Central|0.72|0.35|194°Df|1.07,10|Lower Valley|0.28|0.67|106°Df|0.95,9|South|0.03|0.37|148°Df|0.40","metadata":{"State-Gated Retrieval":["Screen only within the four South Texas divisions defined on the Texas divisional page: South Central, Upper Coast, South, Lower Valley.","Retain divisions that simultaneously satisfy: 1966-02 10-month Palmer Z-Index anomaly >= -0.05; 1966-12 24-month anomaly >= -0.10; 1966-03 1-month Heating Degree Days Value < 200°Df.","Sort by sum of the two Z anomalies descending, then by 1966-03 HDD Value ascending, then by division number ascending."],"dependency_type":"Data","intra_chain":true,"inter_chain":true,"data_dependency":["The official Texas climate-division reference fixes the four South Texas division IDs and names that must be tracked across all later pages.","The 1966-02 10-month Palmer Z-Index anomaly page and the 1966-12 24-month Palmer Z-Index anomaly page jointly identify the four target South Texas divisions.","The 1966-03 1-month Heating Degree Days Value page supplies the last filter; final rows are produced only after intersecting the three divisional screens and then sorting by summed Z-anomaly score, HDD value, and division number."],"freeze":{"historical_window":"Texas climate divisions South Central, Upper Coast, South, and Lower Valley; metrics are fixed to the 1966-02 10-month Palmer Z-Index anomaly, 1966-12 24-month anomaly, and 1966-03 1-month Heating Degree Days Value pages."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Screen only within the four South Texas divisions defined on the Texas divisional page: South Central, Upper Coast, South, Lower Valley.","Retain divisions that simultaneously satisfy: 1966-02 10-month Palmer Z-Index anomaly >= -0.05; 1966-12 24-month anomaly >= -0.10; 1966-03 1-month Heating Degree Days Value < 200°Df.","Sort by sum of the two Z anomalies descending, then by 1966-03 HDD Value ascending, then by division number ascending."],"exclusion_conditions":["Exclude any Texas divisional results outside the four specified South Texas divisions.","Exclude results that misread the 1966-03 HDD page filter field as Anomaly instead of Value.","Exclude any division that fails any time window or threshold condition."],"normalization":{"field_separator":"|","record_separator":",","schema":["texas_division_no","division_name","feb_1966_10mo_z_text","dec_1966_24mo_z_text","mar_1966_hdd_text","moisture_score"],"texas_division_no":"Canonical output uses the short Texas climate-division number; the scorer may accept an equivalent four-digit form, but the emitted oracle uses the short number.","raw_text_fields":"The two Z-index anomaly fields and the March 1966 HDD field preserve the raw displayed text; comparison may ignore optional trailing HDD unit text such as `°Df`.","moisture_score":"Compute as February 1966 10-month Z-index anomaly plus December 1966 24-month Z-index anomaly, formatted with exactly two decimal places.","sorting_or_selection":{"primary":"moisture_score descending","secondary":"March 1966 HDD actual value ascending after numeric normalization","tertiary":"Texas division number ascending"},"eligibility_rule":"Each Texas division is counted once per requested window; if any required window value is missing, exclude the division.","stop_condition":["All candidate Texas divisions are checked under the same base period and anomaly windows.","The unique ordered output string is resolved before emission."]}}} +{"task_id":"climategov_002","domain":"NOAA_NCEI_CLIMATE_AT_A_GLANCE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am researching historical climate patterns in Texas and want to find similar historical years to reference for shoulder-season operational planning. I am particularly interested in regions that recovered from a dry state to near-normal or wet conditions in the early 20th century and had light heating loads during both shoulder-season windows.\n\nIdentify the divisions in NOAA's Climate at a Glance database that meet these criteria. A division is retained only if it satisfies all four hard constraints: the 10-month Palmer Z-Index anomaly ending April 1907 is no higher than -0.30; the 10-month Z-Index anomaly ending April 1923 is no lower than -0.20; the 2-month Heating Degree Days (HDD) actual value ending May 1915 is below 50°Df; and the 5-month HDD actual value ending October 1922 is below 20°Df.\n\nAfter identifying the qualifying divisions, sort them. First compute each division's \"rebound score\" as the April 1923 10-month Z-Index anomaly minus the April 1907 10-month Z-Index anomaly. Sort primarily by rebound score in descending order. If scores are tied, place the division with the smaller October 1922 5-month HDD actual value first. If still tied, give priority to the smaller Texas official division number.\n\nFinally, output the results as a single-line string with divisions joined by commas. Each entry must strictly follow this format: \"|<4-digit division ID>||<1907-04 10-month Z-Index anomaly raw text>|<1923-04 10-month Z-Index anomaly raw text>|<1915-05 2-month HDD actual value raw text>|<1922-10 5-month HDD actual value raw text>|\". If no division meets all conditions, output NONE in uppercase.","start_url":"https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national","output_format":"Output the results as a single-line string with divisions joined by commas. Each entry must strictly follow this format: \"|<4-digit division ID>||<1907-04 10-month Z-Index anomaly raw text>|<1923-04 10-month Z-Index anomaly raw text>|<1915-05 2-month HDD actual value raw text>|<1922-10 5-month HDD actual value raw text>|\". If no division meets all conditions, output NONE in uppercase.","oracle_answer":"10|4110|Lower Valley|-0.36|1.46|10°Df|7°Df|1.82,9|4109|South|-0.33|0.53|23°Df|16°Df|0.86\n10|4110|Lower Valley|-0.36|1.46|10|7|1.82,9|4109|South|-0.33|0.53|23|16|0.86","metadata":{"State-Gated Retrieval":["Retain only Texas divisions that satisfy all four historical conditions: the 10-month Palmer Z-Index anomaly ending April 1907 is no higher than -0.30; the 10-month anomaly ending April 1923 is no lower than -0.20; the 2-month HDD Value ending May 1915 is less than 50°Df; the 5-month HDD Value ending October 1922 is less than 20°Df.","Rebound score is defined as the April 1923 10-month anomaly minus the April 1907 10-month anomaly.","Sort by rebound score descending, then by October 1922 5-month HDD Value ascending, then by Texas division number ascending."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Texas divisional pages yield the 1907-04 and 1923-04 10-month Palmer Z-Index anomalies plus the 1915-05 2-month and 1922-10 5-month HDD values for each division.","The rebound score and the two shoulder-season HDD values are computed only after the same set of candidate divisions survives all four historical filters.","The final output is produced after sorting the surviving divisions by rebound score, then 1922-10 HDD value, then division number."],"control_dependency":["The workflow must cover the 1907, 1923, and 1915 pages as well as the 1922-10 5-month HDD page.","Both HDD pages must be read from Value rather than Anomaly.","The final rebound ranking must be determined after the 1922-10 5-month HDD page excludes 7 South Central and 8 Upper Coast, using ReboundScore as the ordering basis."],"freeze":{"historical_window":"Texas climate divisions evaluated on the 1907-04 and 1923-04 10-month Palmer Z-Index anomaly pages, the 1915-05 2-month HDD Value page, and the 1922-10 5-month HDD Value page."},"answer_type":"mixed multi-line output"},"rubric":{"inclusion_conditions":["Retain only Texas divisions that satisfy all four historical conditions: the 10-month Palmer Z-Index anomaly ending April 1907 is no higher than -0.30; the 10-month anomaly ending April 1923 is no lower than -0.20; the 2-month HDD Value ending May 1915 is less than 50°Df; the 5-month HDD Value ending October 1922 is less than 20°Df.","Rebound score is defined as the April 1923 10-month anomaly minus the April 1907 10-month anomaly.","Sort by rebound score descending, then by October 1922 5-month HDD Value ascending, then by Texas division number ascending."],"exclusion_conditions":["Exclude results that stop after filtering only the 1907, 1923, and 1915 pages without also reading the 1922-10 5-month HDD page.","Exclude results that incorrectly read the 1915 or 1922 HDD page as Anomaly instead of Value.","Exclude any division that does not satisfy all historical window conditions."],"normalization":{"field_separator":"|","record_separator":",","schema":["texas_division_no","division_id_4digit","division_name","apr_1907_10mo_z_text","apr_1923_10mo_z_text","may_1915_2mo_hdd_text","oct_1922_5mo_hdd_text","rebound_score"],"texas_division_no":"Emit the short Texas climate-division number in field 1 and the four-digit division ID in field 2.","raw_text_fields":"The two Z-index anomaly fields preserve the raw displayed text; the two HDD fields preserve the raw displayed text, but comparison may ignore an optional trailing `°Df` suffix.","rebound_score":"Compute as the April 1923 10-month Z-index anomaly minus the April 1907 10-month Z-index anomaly, formatted with exactly two decimal places.","sorting_or_selection":{"primary":"rebound_score descending","secondary":"October 1922 HDD actual value ascending after numeric normalization","tertiary":"Texas division number ascending"},"answer_set_note":"The current oracle stores two equivalent answer sets: one preserves the HDD unit suffixes and one strips them; treat the two HDD columns as equivalent after optional `°Df` removal.","stop_condition":["All candidate Texas divisions are checked under the same anomaly and HDD windows.","The unique ordered output string is resolved before emission."]}}} +{"task_id":"comptox_001","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"Among the following five substances found in records related to European painted products—aniline, cobalt, chromium, 3,3’-dichlorobenzidine, and dibenz[a,h]anthracene—retain only those whose pages explicitly contain the record “Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe.” For each qualifying substance, produce a consolidated list that integrates historical keyword status and the deepest-level use categories. First, check whether each of the following five dated keywords appears (presence only, ignoring any leading numbers): Substances in Products - Canada (4/2014), Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children’s Safe Product Act (4/2020), OEHHA Proposition 65 (1/2023). Record the earliest and latest year-month among the hits. Then, separately from the painted-products record mentioned above, select two use-category routes: one from a daily-consumer perspective with priority order Formulation → Article → Occupation, and one from a production-material perspective with priority order Occupation → Article → Formulation. After selecting each category, drill down along the child category with the highest product count until no further subdivision is possible; if there is a tie at the same level, choose the one with the smaller PUC ID.","start_url":"https://comptox.epa.gov/chemexpo/","output_format":"Finally, sort results by hit count descending; for ties, sort by the consumer-side terminal node’s product count descending. Output format: |||||||||||||. Separate results with commas; if no qualifying items exist, output NONE.","oracle_answer":"DTXSID8020090|5|2014-04|2023-01|Formulation|272|295|type|4|Occupation|301|356|family|27,DTXSID1031040|3|2018-10|2023-01|Formulation|77|94|type|7|Occupation|301|400|family|308,DTXSID9020409|2|2019-03|2023-01|Occupation|321|321|general|11|Occupation|321|321|general|11,DTXSID6020432|2|2019-03|2023-01|Article|313|313|general|1|Occupation|301|356|family|27,DTXSID3031022|1|2023-01|2023-01|Formulation|77|95|type|4|Occupation|301|356|family|185","metadata":{"State-Gated Retrieval":["Screen only the five substances specified in the task, and each target substance page must explicitly contain the record “Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe.”","Check whether each of the five specified dated keywords appears, and record the earliest and latest year-month among the hits.","Then independently select one daily-consumer route and one production-material route, the former following Formulation → Article → Occupation and the latter following Occupation → Article → Formulation, and refine each route separately to its deepest level."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["each chemical page yields the five dated historical keywords, the Europe body-paint/tattoo-ink qualifying record, and the earliest/latest dated-hit months","PUC category paths yield one consumer-side route chosen by Formulation -> Article -> Occupation and one source-side route chosen independently by Occupation -> Article -> Formulation","final rows are produced only after the consumer-side and source-side routes are selected and refined separately for each chemical"],"control_dependency":["the source-side route must be selected independently from the consumer-side route","for each chemical, the second route refinement must follow the production-material priority order rather than the daily-consumer route","family/type/general outputs must be determined only after both route selections are made independently"],"freeze":{"historical_window":"current ChemExpo chemical pages and PUC category paths for the five named substances, using the dated keyword states through 2023-01 and the current Europe body-paint/tattoo-ink record"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Screen only the five substances specified in the task, and each target substance page must explicitly contain the record “Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe.”","Check whether each of the five specified dated keywords appears, and record the earliest and latest year-month among the hits.","Then independently select one daily-consumer route and one production-material route, the former following Formulation → Article → Occupation and the latter following Occupation → Article → Formulation, and refine each route separately to its deepest level."],"exclusion_conditions":["Exclude substances that do not contain the specified Europe body-paint/tattoo-ink record.","Exclude results that directly reuse the same daily-consumer route for the production-material side.","Exclude results that do not independently select and refine both routes according to the specified priority orders."],"normalization":{"field_separator":"|","record_separator":",","schema":["DTXSID","hit_count","earliest","latest","consumer_kind","consumer_general_puc_id","consumer_terminal_puc_id","consumer_level","consumer_products","material_kind","material_general_puc_id","material_terminal_puc_id","material_level","material_products"],"dated_hits":"count only the exact dated keyword strings defined in the source rubric","date_format":"YYYY-MM","kind":"the kind fields use the canonical labels Article, Formulation, or Occupation","level":"the level fields use the canonical labels general, family, or type","products_source":"the Products counts come from the local chemical-detail node for the selected branch, not from an overall aggregate shown elsewhere on the site","sorting_or_selection":{"primary":"hit_count descending","secondary":"consumer_products descending","tertiary":"DTXSID ascending"}}}} +{"task_id":"comptox_002","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":6,"instruction":"In ChemExpo, I want to check whether each of these six substances currently appears more often in material-contact-related uses or in manufacturing-source-related uses, and then select the most representative use category from the corresponding direction. Follow the steps below. First, restrict the scope to these six substances: Di(2-Ethylhexyl) Phthalate, Melamine, Tris(2-Ethylhexyl) Phosphate, 4,5-Dihydro-2-Mercaptoimidazole, Phthalic Acid, Triphenyl Phosphates Tert-Butylated. Then, for each substance, first check whether any of the five material-contact-related label categories appear; score 1 point for each category that appears: Indirect additives food contact (10/2018); Europe, Food contact items; Food contact items, Japan; any keyword containing \"Toys and children's products\"; any keyword containing \"artificial_saliva\" or \"artificial_sweat\". Next, check whether any of the two manufacturing-source-related label categories appear; score 1 point for each category that appears: drinking_water, Europe, manufacturing, plastic_additive; Europe, plastic_additive. Additionally, separately count how many of the following four dated keywords appear: Indirect additives food contact (10/2018); OEHHA Proposition 65 (3/2019); WA Children's Safe Product Act (4/2020); OEHHA Proposition 65 (1/2023). Record the number of hits and the earliest and latest year-month among the hits. Then determine the direction based on which side has a higher score: if the material-contact score is strictly greater than the manufacturing-source score, search for the most representative category for this substance in the order Article → Formulation → Occupation; otherwise, search in the order Occupation → Article → Formulation. After determining the category, from this level onward, at each level only follow the subcategory with the highest product count, continuing until no further subdivision is possible; if there is a tie at the same level, choose the one with the smaller PUC ID.","start_url":"https://comptox.epa.gov/chemexpo/","output_format":"Finally, sort all substances by dated hit count descending; for ties, sort by product count of the selected node descending. Output format: |||||||||||||. Separate results with commas. If datedHits is 0, write NA for both earliest and latest.","oracle_answer":"DTXSID5020607|5|2|4|2018-10|2023-01|contact|Article|309|493|family|1|23|58,DTXSID5020601|4|1|3|2018-10|2023-01|contact|Article|309|309|general|1|5836|1827,DTXSID6020802|4|2|1|2018-10|2018-10|contact|Article|313|313|general|15|1104|675,DTXSID8021484|3|1|1|2018-10|2018-10|contact|Occupation|321|321|general|8|28313|4200,DTXSID0021414|5|0|1|2018-10|2018-10|contact|Article|309|309|general|3|5836|1827,DTXSID20872645|0|1|0|NA|NA|source|Occupation|318|381|family|5|274|107","metadata":{"State-Gated Retrieval":["Only consider the six specified substances, and first compute contactHits, sourceHits, and datedHits on the chemical page.","prioritySide must first be determined by these historical signals, and then a most representative current use category is selected along the corresponding direction.","The current route selection must follow the given kind priority and the same-level smaller PUC ID tie-break rule for further drill-down."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["each chemical page yields contactHits, sourceHits, datedHits, and the earliest/latest dated-hit months from the historical keyword set","after the priority side is chosen, the corresponding current PUC category path yields the representative kind, PUC path, product counts, and curated-chemical counts","final rows are produced only after the historical hit scores determine the side first and the current route is then chosen with the side-specific priority and tie-break rules"],"control_dependency":["historical contact/source signal scores must take priority over current maximum-Products paths","the priority side must be determined from contactHits, sourceHits, and datedHits rather than from current visibility alone","PUC path tie-breaks are valid only after the correct side has been fixed and the route has been traced under that side's rules"],"freeze":{"historical_window":"current ChemExpo chemical pages and PUC category paths for the six named substances, using the stated historical keyword families and dated hits through 2023-01"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only consider the six specified substances, and first compute contactHits, sourceHits, and datedHits on the chemical page.","prioritySide must first be determined by these historical signals, and then a most representative current use category is selected along the corresponding direction.","The current route selection must follow the given kind priority and the same-level smaller PUC ID tie-break rule for further drill-down."],"exclusion_conditions":["Exclude results that ignore historical signals and directly select the path with the maximum current visible Products on the chemical page.","Exclude results that start PUC route selection without first determining the contact/source direction.","Exclude results that do not apply the smaller PUC ID tie-break rule for same-level ties."],"normalization":{"field_separator":"|","record_separator":",","schema":["DTXSID","contactHits","sourceHits","datedHits","earliest","latest","prioritySide","PUCkind","generalPUCID","terminalPUCID","level","Products","PUCDocuments","PUCCuratedChemicals"],"dated_hits":"count only the exact dated keyword strings defined in the source rubric","date_format":"YYYY-MM; if datedHits is 0, earliest and latest are both `NA`","prioritySide":"emit `contact` when contactHits > sourceHits; otherwise emit `source`","kind":"the PUCkind field uses the canonical labels Article, Formulation, or Occupation","level":"the level field uses the canonical labels general, family, or type","products_source":"Products comes from the selected terminal chemical-detail node","terminal_statistics":"PUCDocuments and PUCCuratedChemicals come from the selected terminal PUC detail page Additional Statistics block","sorting_or_selection":{"primary":"datedHits descending","secondary":"Products descending","tertiary":"DTXSID ascending"}}}} +{"task_id":"comptox_003","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"In ChemExpo, first select Formulation categories with a total product count of 15,000 or more. Then, within each category, following the website's default display order, identify the first product family that meets these criteria: the family itself has no assumed attributes and its total product count is at least 3,000; additionally, the family must have at least two distinct specific product types, one with allowed attributes including aerosol and the other including child, and both types must have empty assumed attributes. Next, within each of these two specific product types, compute the product share (type product count divided by family cumulative product count). If shares are equal, compare their Curated Chemicals counts and select the higher one; if still equal, select the type with the smaller PUC ID. After completing the selection on both sides, retain only the better of the two candidate types: first prioritize the type with the higher product share; if shares are equal, compare Product Count (higher wins); if still equal, compare Curated Chemicals (higher wins); if still equal, select the type with the smaller PUC ID.","start_url":"https://comptox.epa.gov/chemexpo/visualizations/","output_format":"Output results sorted by final share in descending order, formatted as: |||||. Join records with commas and no spaces. If no qualifying items exist, output NONE.","oracle_answer":"48|42|62|child|2160/3531|583,137|197|210|child|6934/16904|1135","metadata":{"State-Gated Retrieval":["First, retain only Formulation categories with a total product count of 15,000 or more.","Within each candidate family, both an aerosol-side type and a child-side type must be found: the family itself must have no assumed attributes and a total product count of at least 3,000; both types must also have empty assumed attributes.","All final selections within a family and between the two sides must follow the specified tie-break rules: share, Product Count, Curated Chemicals, and PUC ID."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["The Formulation summary yields the high-product candidate families whose total product count is at least 15,000","Within each family, lower-level type pages yield the aerosol and child candidates, their assumed/allowed attributes, product counts, shares, and curated-chemical counts","Final rows are produced only after a family survives both aerosol and child branches and the winning type is selected by the layered share/product/chemical/PUC tie-break rules"],"control_dependency":["Both the aerosol and child branches within the same family must be fully checked before that family can be retained","If one side is missing, the workflow must reject the family and continue to the next sibling family rather than stop at the first partial hit","The final winner can be selected only after both sides have been independently optimized within the family and then compared against each other"],"freeze":{"historical_window":"Current ChemExpo Formulation families with total product count >= 15,000, evaluated on family/type attributes and current product/chemical counts"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["First, retain only Formulation categories with a total product count of 15,000 or more.","Within each candidate family, both an aerosol-side type and a child-side type must be found: the family itself must have no assumed attributes and a total product count of at least 3,000; both types must also have empty assumed attributes.","All final selections within a family and between the two sides must follow the specified tie-break rules: share, Product Count, Curated Chemicals, and PUC ID."],"exclusion_conditions":["Exclude results that stop as soon as a usable type is found on either side without requiring the same family to cover both aerosol and child sides.","Exclude results that stop as soon as one side is missing instead of continuing to check sibling families at the same level.","Exclude results that do not follow the specified layered tie-break rules to select the winning type within a family and overall."],"normalization":{"field_separator":"|","record_separator":",","schema":["generalPUCID","familyPUCID","typePUCID","side","share","CuratedChemicals"],"dedup_key":"(generalPUCID, familyPUCID, typePUCID, side)","side":"Emit the lower-case branch label exactly as determined in the source workflow","share":"Canonical output uses the raw fraction `type Products / family Cumulative Products` rather than a decimal","CuratedChemicals":"Emit the integer count from the selected type-level node","sorting_or_selection":{"primary":"Share descending by numeric fraction value","secondary":"Type-level Products descending","tertiary":"CuratedChemicals descending, then PUC IDs ascending as tie-breaks"}}}} +{"task_id":"comptox_004","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"In ChemExpo, for the five substances Di(2-Ethylhexyl) Phthalate, Melamine, Phthalic Acid, Tris(2-Ethylhexyl) Phosphate, and Triphenyl Phosphates Tert-Butylated, check whether their historical labels align with their current uses. Follow the steps below. First, restrict the scope to these five substances. For each substance, collect three sets of baseline assessment data. The first set is the \"material contact\" score: check for the presence of the following five label categories, scoring 1 point for each category hit: Indirect additives food contact (10/2018); Europe, Food contact items; Food contact items, Japan; any keyword containing \"Toys and children's products\"; and any keyword containing \"artificial_saliva\" or \"artificial_sweat\". The second set is the \"production source\" score: check for the presence of the following two label categories, scoring 1 point for each category hit: \"drinking_water, Europe, manufacturing, plastic_additive\" and \"Europe, plastic_additive\". The third set is the regulatory profile for specific dates: separately count the total hits for the four exact keywords Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children's Safe Product Act (4/2020), and OEHHA Proposition 65 (1/2023), and record the earliest and latest year-month among all hits. After obtaining these three sets of data, determine the historical side by comparing scores: if the material contact score is strictly greater than the production source score, select a historically recommended kind in the order Article → Formulation → Occupation; otherwise, select in the order Occupation → Article → Formulation. After determining the kind, drill down along the subcategory with the most products at each level until no further subdivision is possible; if there is a tie at the same level, choose the one with the smaller PUC ID. Separately, independently identify the current dominant category for the same substance, ignoring historical clues: directly find the path with the most products among all use categories, drilling down to the terminal level using the same tie-breaking rule (smaller PUC ID). Finally, compare the two results: if the current dominant kind is Article or Formulation and the historical side is material, mark ALIGNED; if the current dominant kind is Occupation and the historical side is source, also mark ALIGNED; otherwise, mark MISALIGNED.","start_url":"https://comptox.epa.gov/chemexpo/","output_format":"Output MISALIGNED records first; within the same group, sort by datedHits descending; if datedHits are equal, sort by currentProducts descending. Format: |||||||||||||||||. Separate records with commas. If datedHits is 0, write NA for both earliest and latest.","oracle_answer":"DTXSID6020802|4|2|1|2018-10|2018-10|material|Article|Furniture and furnishings|Furniture and furnishings|general|15|Occupation|Raw materials|fireproof coatings|type|24|MISALIGNED,DTXSID8021484|3|1|1|2018-10|2018-10|material|Occupation|Laboratory supplies|Laboratory supplies|general|8|Occupation|Laboratory supplies|Laboratory supplies|general|8|MISALIGNED,DTXSID5020607|5|2|4|2018-10|2023-01|material|Article|Construction and building materials|flooring|family|1|Formulation|Home maintenance|paint|type|112|ALIGNED,DTXSID0021414|5|0|1|2018-10|2018-10|material|Article|Construction and building materials|Construction and building materials|general|3|Article|Construction and building materials|Construction and building materials|general|3|ALIGNED,DTXSID20872645|0|1|0|NA|NA|source|Occupation|Industrial products|hydraulic fluid|family|5|Occupation|Industrial products|hydraulic fluid|family|5|ALIGNED","metadata":{"State-Gated Retrieval":["Operate only on the five specified substances, and first compute materialHits, sourceHits, and datedHits from the keyword-set block.","The historically recommended category must be derived independently from these historical signals; the current dominant category must be derived separately from the current use path.","Finally, compare only whether the historically recommended category and the current dominant category align at the coarse side level, and mark ALIGNED or MISALIGNED accordingly."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["each chemical page yields materialHits, sourceHits, datedHits, and the historical recommendation side implied by the keyword set","an independent current PUC category path yields the current dominant category, path labels, and classification counts for the same chemical","final rows are produced only after the historical recommendation and current dominant category are computed independently and then compared at the coarse side level"],"control_dependency":["the historical recommendation must be determined from the keyword-set evidence rather than from the current largest category","historical recommendation must be computed from the keyword-set evidence before alignment is judged","ALIGNED / MISALIGNED status is valid only after the historical and current category directions have been derived independently and then compared"],"freeze":{"historical_window":"current ChemExpo chemical pages and PUC category paths for the five named substances, using the specified historical keyword-set evidence through 2023-01"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Operate only on the five specified substances, and first compute materialHits, sourceHits, and datedHits from the keyword-set block.","The historically recommended category must be derived independently from these historical signals; the current dominant category must be derived separately from the current use path.","Finally, compare only whether the historically recommended category and the current dominant category align at the coarse side level, and mark ALIGNED or MISALIGNED accordingly."],"exclusion_conditions":["Exclude results that simply take the current largest category and treat it as the historically recommended category.","Exclude results that default to ALIGNED without independently deriving the historically recommended category.","Exclude results that fail to compute the historical and current paths separately, instead mixing signals in a single path."],"normalization":{"field_separator":"|","record_separator":",","schema":["DTXSID","materialHits","sourceHits","datedHits","earliest","latest","historySide","recommendedKind","recommendedGeneral","recommendedTerminal","recommendedLevel","recommendedProducts","currentKind","currentGeneral","currentTerminal","currentLevel","currentProducts","status"],"dated_hits":"count only the exact dated keyword strings defined in the source rubric","date_format":"YYYY-MM; if datedHits is 0, earliest and latest are both `NA`","historySide":"emit the lower-case historical winner `material` or `source`","recommended_fields":"these fields describe the historically suggested path","current_fields":"these fields describe the current dominant path","kind":"the kind fields use the canonical labels Article, Formulation, or Occupation","level":"the level fields use the canonical labels general, family, or type","status":"emit `ALIGNED` or `MISALIGNED` exactly","sorting_or_selection":{"primary":"status with MISALIGNED before ALIGNED","secondary":"datedHits descending","tertiary":"currentProducts descending","quaternary":"DTXSID ascending"}}}} +{"task_id":"consumerfinance_001","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"On the CFPB enforcement actions page, for the period 2022 to 2024, find one qualifying administrative enforcement action for each of the three product categories: Deposits, Furnishing, and Prepaid. Then, in the corresponding Consent Order for that action, locate the first occurrence of the consumer redress amount and the civil money penalty amount, along with their page numbers.\n\nSpecifically, first restrict the search to actions on the CFPB enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.\n\nThen, search separately for each of the three product categories: Deposits, Furnishing, and Prepaid. For each category, follow the current default case order on the CFPB website from top to bottom, and select the first action that simultaneously meets all of the following conditions:\n1. The action page provides both a Consent Order and a press release.\n2. The product category label corresponds one-to-one with the target category.\n3. The page explicitly states consumer redress, and the redress amount exceeds $5,000,000.\n4. In addition to consumer redress, the page also explicitly states a civil money penalty.\n\nAfter finding such an action for each product category, open its corresponding Consent Order and locate the two types of monetary information:\n- The specific amount of consumer redress when it first appears in the text, and the page number where it appears.\n- The specific amount of civil money penalty when it first appears in the text, and the page number where it appears.\n\nPage numbers should be based on the physical page numbering of the Consent Order PDF, i.e., the first page is p1, the second page is p2, and so on.","start_url":"https://www.consumerfinance.gov/enforcement/actions/","output_format":"Finally, output the results for the three product categories sorted alphabetically by product name. Output one segment per category in the following format:\n|||||p||p\nIf no qualifying case is found for a category, output:\n|NONE\nJoin the three results with commas, with no spaces.","oracle_answer":"Deposits|Bank of America, N.A.|2023-CFPB-0006|2023-07-11|$80,400,000|p11|$60,000,000|p14,Furnishing|Hyundai Capital America|2022-CFPB-0005|2022-07-26|$13,200,000|p31|$6,000,000|p35,Prepaid|U.S. Bank National Association|2023-CFPB-0019|2023-12-19|$5,700,000|p22|$15,000,000|p26","metadata":{"State-Gated Retrieval":["Only consider administrative enforcement actions on the CFPB Enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.","For each of the three product categories (Deposits, Furnishing, Prepaid), search in the current default order from top to bottom for the first action that simultaneously satisfies: the page provides a Consent Order and a Press release; the Products label corresponds one-to-one with the target category; the action detail page explicitly states consumer redress > $5,000,000 and also states a civil money penalty.","Finally, extract the first-occurrence amounts and page numbers of consumer redress and civil money penalty from the correct Consent Order."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Enforcement-action list pages yield product-branch candidate actions in current default order.","Each action detail page and linked consent-order PDF yield product singularity, document-stack presence, redress/civil-money-penalty amounts, and first-occurrence pages.","Final rows are emitted only after identifying, for each product, the first action that survives detail-page and PDF validation."],"control_dependency":["List-level \"has Consent Order + Press release\" hits must be validated on the detail page for product singularity and money thresholds.","Prepaid candidates force document-level disambiguation among Consent Order, Stipulation, and terminating-order PDFs.","Per-product first-match selection must explicitly skip rejected candidates and validate downstream PDFs before it is finalized."],"freeze":{"historical_window":"Administrative enforcement actions with Initial filing date from 2022-01-01 through 2024-12-31; current default case ordering and currently linked action documents."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only consider administrative enforcement actions on the CFPB Enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.","For each of the three product categories (Deposits, Furnishing, Prepaid), search in the current default order from top to bottom for the first action that simultaneously satisfies: the page provides a Consent Order and a Press release; the Products label corresponds one-to-one with the target category; the action detail page explicitly states consumer redress > $5,000,000 and also states a civil money penalty.","Finally, extract the first-occurrence amounts and page numbers of consumer redress and civil money penalty from the correct Consent Order."],"exclusion_conditions":["Exclude actions where the Products label is not a single target category, or where the action appears relevant only at the list level but the detail page does not confirm it.","Exclude actions that do not clearly satisfy the redress > $5M and independent civil money penalty conditions.","Exclude cases where a Stipulation or Order Terminating the Consent Order is mistakenly used in place of the required Consent Order."],"normalization":{"field_separator":"|","record_separator":",","schema":["Product","Respondent","Docket","FilingDate","RedressUSD","RedressPage","PenaltyUSD","PenaltyPage"],"product_order":"Alphabetical by Product name","fallback_row":"If a product has no qualifying case, emit `|NONE`","date_format":"FilingDate uses YYYY-MM-DD","money_fields":"Canonical output preserves the dollar sign and commas from the oracle, but equivalent comparison may ignore `$` and commas and compare the numeric USD amount.","page_fields":"Page fields use the canonical `pN` form.","document_scope":"Extract both money amounts from the Consent Order PDF only; do not substitute a stipulation, termination order, or other companion document.","selection_rule":"For each product, keep the first action in the default filtered order that fully satisfies every gate in the source rubric."}}} +{"task_id":"consumerfinance_002","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I want to organize the annual household financial stability survey report series in CFPB Reports, whose latest version page still links directly to the 2023 and 2022 editions. Some topics that appeared in the 2022 edition were later dropped from subsequent annual reports, and I want to see which other reports on the site are associated with these dropped topics. First, locate this series within the CFPB Reports section and confirm that the latest version links directly to the two previous editions (2023 and 2022). Then, using the 2022 edition as the baseline, identify topics that appear in the 2022 edition but are no longer retained in subsequent annual reports. Note: exclude the topic specifically used to mark \"belongs to the same survey series.\" Next, for each identified topic, confirm the following one by one: first, the year in which this topic first disappeared from subsequent annual reports; second, when searching for this topic within the CFPB Reports section, among results from 2022 and earlier, which report that does not belong to this series appears first; third, open that report, count how many related resources are listed on the page, how many of those explicitly link to the same survey series, and among those reports that link to the same survey series, how many have appendices labeled alphabetically with at least three sections (e.g., Appendix A, B, C or more); fourth, for the report that survives this multi-level screening, provide its title, publication date, and the alphabetical range of its appendices.","start_url":"https://www.consumerfinance.gov/data-research/research-reports/","output_format":"Finally, output a single-line string sorted alphabetically by topic name: |||||||||","oracle_answer":"Saving|2023|Consumer Savings App Strategies and Savings Outcomes|2022-12-07|4|2|1|Emergency Savings and Financial Security: Insights from the Making Ends Meet Survey and Consumer Credit Panel|2022-03-23|A-D,Student loans|2023|Report of the CFPB Education Loan Ombudsman|2022-10-20|0|0|0|NONE|NONE|NONE","metadata":{"State-Gated Retrieval":["First, locate the CFPB household financial well-being annual report series whose latest version links directly to 2023 and 2022.","Using the 2022 edition as the baseline, retain only topics that appear in 2022 but are no longer retained in subsequent annual reports, and exclude the topic specifically marked as \"belongs to the same survey series.\"","For each topic, find the earliest non-series pivot report from 2022 or earlier, then count its directly listed related resources, how many link back to the same survey series, how many qualify under the appendix rule, and the appendix span of the final qualifying report."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["current CFPB Reports pages yield the 2024 -> 2023 -> 2022 annual-survey chain and the 2022 topic baseline","report detail pages and report-search results yield first-disappearance year, pivot report title/date, related-resource counts, and links back to the annual-survey series","final rows are produced only after separating the first jump target from later return-to-series counting"],"control_dependency":["requiring the pivot report itself to link back to the same survey series incorrectly rules out valid topic rows","title extraction must use the pivot detail page rather than search-result snippets","related-resource expansion must continue even when the pivot report itself does not link back to the same survey series"],"freeze":{"historical_window":"currently linked 2024, 2023, and 2022 CFPB household financial well-being annual reports; topic disappearance is judged over that three-year chain, and pivot-report search is restricted to 2022-and-earlier reports"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["First, locate the CFPB household financial well-being annual report series whose latest version links directly to 2023 and 2022.","Using the 2022 edition as the baseline, retain only topics that appear in 2022 but are no longer retained in subsequent annual reports, and exclude the topic specifically marked as \"belongs to the same survey series.\"","For each topic, find the earliest non-series pivot report from 2022 or earlier, then count its directly listed related resources, how many link back to the same survey series, how many qualify under the appendix rule, and the appendix span of the final qualifying report."],"exclusion_conditions":["Exclude topics that are still retained in subsequent annual reports.","Exclude results that incorrectly treat \"the pivot report itself must link back to the same survey series\" as a hard condition for column 3.","Exclude search results that directly belong to the same survey series or reports from after 2022."],"normalization":{"field_separator":"|","record_separator":",","schema":["topic","first-missing-year","pivot-report-or-NONE","pivot-date-or-NONE","direct-related-count","same-series-count","qualified-count","representative-report-or-NONE","publication-date-or-NONE","appendix-span-or-NONE"],"topic_order":"alphabetical by topic name","date_format":"pivot-date and publication-date use YYYY-MM-DD when present","appendix_span":"canonical span uses compact labels such as `A-D`","none_rule":"if qualified-count is 0, representative-report, publication-date, and appendix-span are all `NONE`"}}} +{"task_id":"consumerfinance_003","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I want to clearly sort out the CFPB's 2020 Debt Collection Rules, including proposal sources, delayed effective date arrangements, final effective dates, and the accompanying quick-reference PDF information on the implementation page. Follow the steps below. First, confirm when each of the two 2020 Debt Collection Rule final rules was issued. Then separately confirm the following for each wave: 1. The issue date of this final rule; 2. Which proposal(s) it developed from, and the public comment deadline for each proposal; 3. Whether the 2021 proposed rule on delaying the effective date covers this wave, and the comment deadline for that proposal; 4. The actual final effective date; 5. Which quick-reference PDF corresponds to this wave on the implementation page; 6. The first heading in the PDF body after skipping the introductory paragraph.","start_url":"https://www.consumerfinance.gov/rules-policy/final-rules/","output_format":"Output a single-line string with results sorted by final-rule issue date in ascending order. Identify each wave by its final rule issue month (YYYY-MM). Use the following format: ||||||||","oracle_answer":"2020-10|2020-10-30|2019-05-07 main|2019-09-18|YES|2021-05-19|2021-11-30|Executive summary of the October 2020 final rule|Coverage and Definitions,2020-12|2020-12-18|2019-05-07 main+2020-02-21 supplemental|2019-09-18+2020-08-04|YES|2021-05-19|2021-11-30|Executive summary of the December 2020 final rule|Validation Information Requirements and Disclosures","metadata":{"State-Gated Retrieval":["Must process the two 2020 Debt Collection Practices (Regulation F) final rules separately, not merge them into one.","For each wave, separately confirm: issue date, corresponding proposal chain and public comment deadlines, whether the 2021 delayed-effective-date proposed rule covers it and its deadline, final effective date, corresponding implementation quick-reference PDF, and the first heading after the introduction in that PDF.","The detail page, proposal chain, and summary PDF for the October wave and the December wave must each be independently verified."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["final-rules index pages and rule-development pages yield the two 2020 Regulation F final-rule waves and their proposal branches","each final-rule detail page, delayed-effective-date proposal page, and implementation quick-reference PDF yields the wave-specific dates, linked proposals, comment deadlines, and first summary heading","final rows are produced only after the October and December waves are traced separately end to end"],"control_dependency":["two same-title final rules force correction from name-based collapsing to issue-date branching","proposal-chain validation must be done per wave; otherwise the later December chain contaminates the October row","implementation PDFs must be matched back to the correct wave rather than accepting the latest quick-reference page"],"freeze":{"historical_window":"the 2020-10 and 2020-12 Debt Collection Rule final-rule waves, their linked 2020 proposal pages, the 2021 delayed-effective-date proposal, and the current implementation-page quick-reference PDFs"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Must process the two 2020 Debt Collection Practices (Regulation F) final rules separately, not merge them into one.","For each wave, separately confirm: issue date, corresponding proposal chain and public comment deadlines, whether the 2021 delayed-effective-date proposed rule covers it and its deadline, final effective date, corresponding implementation quick-reference PDF, and the first heading after the introduction in that PDF.","The detail page, proposal chain, and summary PDF for the October wave and the December wave must each be independently verified."],"exclusion_conditions":["Exclude results that merge the two identically named 2020 final rules into one.","Exclude results that project the December wave's proposal chain or executive-summary heading onto the October wave.","Exclude results that do not independently verify each final-rule detail page and its corresponding PDF."],"normalization":{"field_separator":"|","record_separator":",","schema":["wave","final-rule-date","proposal-chain","proposal-comment-closes","delay-proposal-applied","delay-proposal-comments-close","controlling-effective-date","quick-reference-pdf","summary-heading"],"wave":"wave is the final-rule issue month in YYYY-MM","date_format":"all standalone date fields use YYYY-MM-DD","proposal_chain":"canonical chain joins proposal milestones with `+`, using pieces such as `2019-05-07 main` or `2020-02-21 supplemental` in chronological order","proposal_comment_closes":"join multiple comment-close dates with `+` in the same order as proposal_chain","delay_proposal_applied":"emit `YES` when a delay proposal is part of the chain; otherwise emit `NO`","quick_reference_pdf":"use the displayed quick-reference PDF title, not the filename","summary_heading":"use the first substantive heading from the final-rule PDF","sorting_or_selection":"final-rule-date ascending"}}} +{"task_id":"consumerfinance_004","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"On the CFPB Enforcement Actions page, identify administrative enforcement actions filed in 2024 and subsequently closed, separately for the product categories Credit Cards and Deposits. Then extract the corresponding clause information linking the terminating order to the original Consent Order. Specifically, first restrict the search to administrative enforcement actions on the CFPB Enforcement Actions page whose initial filing date falls between 2024-01-01 and 2024-12-31. Then filter separately for the two product categories: Credit Cards and Deposits. For each category, retain only cases that simultaneously meet the following conditions: the case page shows the case has been closed, with a status of Expired, Terminated, or Vacated; the case page provides all four of these document types: Consent Order, Stipulation, Order Terminating the Consent Order, and Press Release; the page lists exactly one product category, and that single category is the one you are currently targeting. That is, if you are searching for Credit Cards, the page must list only that item and no other categories; the same requirement applies when searching for Deposits. After filtering, each product category may still have more than one case. For each category, retain only the case with the latest initial filing date; if multiple cases share the same filing date, select the one with the smaller docket number. Next, open the Order Terminating the Consent Order for the selected case and record the following three pieces of information: the termination date on this document; the passage in the document that states the legal authority for terminating the consent order, i.e., the termination authority, recording only the original text of its first occurrence; the PDF physical page number where this termination authority first appears. Also, within the text of this terminating order, find the first explicit reference to a paragraph number from the original Consent Order; if it reads \"Paragraphs X and Y,\" take only X. Then, return to the original Consent Order document for this case, locate the referenced paragraph, and record the section heading under which it falls.","start_url":"https://www.consumerfinance.gov/enforcement/actions/","output_format":"Finally, output a single-line string in alphabetical order by product name: ||||||p||. If a product has no qualifying case, output: |NONE","oracle_answer":"Credit Cards|Apple Inc.|2024-CFPB-0012|2024-10-23|2025-09-22|12 U.S.C. § 5563(b)(3)|p1|83|ADMINISTRATIVE PROVISIONS,Deposits|Navy Federal Credit Union|2024-CFPB-0014|2024-11-07|2025-07-01|12 U.S.C. § 5563(b)(3)|p1|106|ADMINISTRATIVE PROVISIONS","metadata":{"State-Gated Retrieval":["Consider only administrative enforcement actions with an Initial filing date in 2024, and search separately in the Credit Cards and Deposits categories.","Cases must have a status of Expired, Terminated, or Vacated, and the page must simultaneously provide a Consent Order, Stipulation, Order Terminating the Consent Order, and Press Release, and the Products field must correspond one-to-one with the target category.","Finally, for each category retain only the most recent qualifying case determined by Initial filing date, and compile the corresponding clause information linking the terminating order to the original Consent Order."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["enforcement-action list pages yield 2024 candidate actions by product branch","each action detail page and linked Consent Order / Stipulation / Order Terminating the Consent Order / Press Release documents yield status, initial filing date, single-product validity, and clause references","final rows are selected only after per-product comparison on Initial filing date and document-stack validation"],"control_dependency":["\"latest\" must be determined by Initial filing date rather than termination date","product filters on the list page are insufficient until the action detail page confirms a single matching product","clause extraction in the terminating order must stay aligned with the original Consent Order rather than a superficially similar section"],"freeze":{"historical_window":"administrative enforcement actions with Initial filing date from 2024-01-01 through 2024-12-31; current action status and currently linked Consent Order / Stipulation / terminating-order / Press Release documents"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Consider only administrative enforcement actions with an Initial filing date in 2024, and search separately in the Credit Cards and Deposits categories.","Cases must have a status of Expired, Terminated, or Vacated, and the page must simultaneously provide a Consent Order, Stipulation, Order Terminating the Consent Order, and Press Release, and the Products field must correspond one-to-one with the target category.","Finally, for each category retain only the most recent qualifying case determined by Initial filing date, and compile the corresponding clause information linking the terminating order to the original Consent Order."],"exclusion_conditions":["Exclude results that use termination date instead of Initial filing date to determine \"latest.\"","Exclude cases with an incomplete document stack or where Products is not a single target category.","Exclude cases where the required clause correspondence between the terminating order and the original Consent Order cannot be established."],"normalization":{"field_separator":"|","record_separator":",","schema":["Product","Respondent","Docket","InitialFilingDate","TerminationDate","TerminationAuthority","TermAuthorityPage","ReferencedParagraph","ConsentSectionHeading"],"product_order":"alphabetical by Product name","fallback_row":"if a product has no qualifying case, emit `|NONE`","date_format":"InitialFilingDate and TerminationDate use YYYY-MM-DD","termination_authority":"use the canonical statute string extracted from the termination order","page_fields":"TermAuthorityPage uses the canonical `pN` form","ReferencedParagraph":"emit the paragraph number as a plain numeric string","ConsentSectionHeading":"emit the uppercase heading of the consent-order section containing the referenced paragraph"}}} +{"task_id":"consumerfinance_005","domain":"CFPB_COMPLAINT_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am preparing an internal outreach memo on historical complaint clusters and need to track a specific set of complaints: from the CFPB Complaint Database, within the current product bucket covering credit reporting and other personal consumer reports, between 2018-01-01 and 2021-12-31, tagged as Servicemember, with a public narrative, and where the text explicitly mentions medical bills or doctors. Please provide two representative complaint clusters: the first is the peak month of this cohort; the second is the latest month in this cohort whose complaint count is still at least half of the peak. For each cluster, report the total complaints for that month, the state with the highest complaint count and its count, the company with the highest complaint count within that state and month and its count, and the earliest complaint received by that company in that state and month, including its ID, date, Issue, and Sub-issue. Output a single line with Peak first, then LatestHalfPeak, using the format: ||||||||||.","start_url":"https://www.consumerfinance.gov/data-research/consumer-complaints/","output_format":"Output a single line with Peak first, then LatestHalfPeak, using the format: ||||||||||. Join the Peak and LatestHalfPeak clusters with a comma. For ties: months are ordered chronologically; states are ordered alphabetically by state abbreviation; companies are ordered alphabetically by company name; for the earliest complaint, use the earliest date, then the smallest Complaint ID if dates are identical.","oracle_answer":"Peak|2018-02|46|CA|28|TRANSUNION INTERMEDIATE HOLDINGS, INC.|9|2806154|2018-02-07|Improper use of your report|Reporting company used your report improperly,LatestHalfPeak|2021-11|23|CA|12|EQUIFAX, INC.|3|4928768|2021-11-19|Problem with a credit reporting company's investigation into an existing problem|Their investigation did not fix an error on your report","metadata":{"State-Gated Retrieval":["Only consider complaints within the current product bucket covering credit reporting and other personal consumer reports, from 2018-01-01 to 2021-12-31, tagged as Servicemember, with a public narrative, and where the text explicitly mentions medical bills or doctors.","The first cluster must be the peak month of the cohort; the second cluster must be the latest month in the cohort whose complaint count is still at least half of the peak.","For each cluster, recompute the top company within the corresponding month + state subset, then locate the earliest complaint received by that company in that state and month."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["current complaint-form taxonomy yields the product bucket that contains credit reporting / other personal consumer reports","filtered complaint records yield month counts, month-state subsets, top companies, and earliest complaint details inside each chosen subset","final rows are produced only after peak month and latest-half-peak month are determined, and each downstream aggregate is computed inside its narrower month-state cohort"],"control_dependency":["the latest month must be defined as the latest month whose count is at least ceil(PeakCount / 2)","overall top-company counts cannot be projected into a month-state subset without recomputation","earliest complaint selection is only valid after the month, state, and company filters are all frozen"],"freeze":{"historical_window":"Complaint Database records received from 2018-01-01 through 2021-12-31 under the current product-bucket mapping for the credit-reporting / other personal consumer reports family; Servicemember + public narrative + medical bills/doctors text cohort"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only consider complaints within the current product bucket covering credit reporting and other personal consumer reports, from 2018-01-01 to 2021-12-31, tagged as Servicemember, with a public narrative, and where the text explicitly mentions medical bills or doctors.","The first cluster must be the peak month of the cohort; the second cluster must be the latest month in the cohort whose complaint count is still at least half of the peak.","For each cluster, recompute the top company within the corresponding month + state subset, then locate the earliest complaint received by that company in that state and month."],"exclusion_conditions":["Exclude results that directly use the latest month with any complaints as the second cluster.","Exclude results that first find the overall top company across the full cohort and then project it onto the month-state subset.","Exclude results that do not first derive the half-peak threshold from PeakCount."],"normalization":{"field_separator":"|","record_separator":",","schema":["Cluster","Month","MonthComplaints","TopState","StateComplaints","TopCompany","CompanyComplaints","EarliestComplaintID","EarliestDate","Issue","SubIssue"],"cluster_order":["Peak","LatestHalfPeak"],"date_format":{"Month":"YYYY-MM","EarliestDate":"YYYY-MM-DD"},"TopState":"use the uppercase two-letter state abbreviation","TopCompany":"use the company display name as shown in the source data","tie_breaks":"for tied months use chronological order; for tied states use state-code alphabetical order; for tied companies use company-name alphabetical order; for the earliest complaint use EarliestDate ascending then Complaint ID ascending","SubIssue":"emit `NONE` when the complaint row has no sub-issue value"}}} +{"task_id":"consumerfinance_006","domain":"CFPB_COMPLAINT_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am writing a crypto-complaint concentration memo. To verify whether complaint peaks within a fixed three-year window are driven only by a few top platforms, I need you to step through the CFPB complaint database and extract relevant data.\n\nFirst, define the underlying data scope. Using the current CFPB complaint form product taxonomy, determine which product bucket Virtual currency currently falls under. Once the bucket is confirmed, strictly limit the time range to 2019-08-26 through 2022-08-26 and retain only complaint records classified under the Virtual currency subcategory within that product bucket. This forms the initial cohort.\n\nSecond, identify two characteristic peak months within this cohort. Step 1: Aggregate complaints by month across the full cohort (with no companies removed) and identify the original peak month (AllCompanies). Step 2: Identify the top two companies by complaint count in that original peak month. Remove all complaint records of these two companies from the entire three-year cohort (not just from the single peak month). Then re-aggregate complaints by month on the remaining data to find the residual peak month (ResidualAfterTop2).\n\nThird, for each of these two peak months, extract detailed data. For each cluster, obtain the total complaint count for that month, the names of the two excluded top companies, and their combined complaint count in the original peak month. Also identify the state with the highest complaint count in that feature month and its complaint count, the most complained-about company within that state and its complaint count, and the full details of the earliest complaint received by that company in that state during that feature month (including Complaint ID, date, Issue, and Sub-issue).\n\nFinally, after completing all the above steps, format the two sets of core parameters into a single string with no spaces. The two rows must be ordered AllCompanies first, ResidualAfterTop2 second. The field order for each row is fixed as: ||||||||||||. To ensure a unique answer: output the two records in AllCompanies then ResidualAfterTop2 order; list ExcludedTop2Companies in descending order of their complaint count in the original peak month, breaking ties alphabetically; for any tie in sorting indicators, sort by field value in ascending alphabetical order; if the earliest complaint date is tied, select the one with the smallest Complaint ID.","start_url":"https://www.consumerfinance.gov/data-research/consumer-complaints/","output_format":"Output the two rows in AllCompanies first, ResidualAfterTop2 second order, joined into a formatted string with no spaces. The field order for each row is fixed as: ||||||||||||.","oracle_answer":"AllCompanies|2021-05|336|Coinbase, Inc.+BAM Management US Holdings Inc.|226|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,ResidualAfterTop2|2020-06|180|Coinbase, Inc.+BAM Management US Holdings Inc.|226|OH|28|PNC Bank N.A.|22|3687376|2020-06-07|Other transaction problem|NONE","metadata":{"State-Gated Retrieval":["Only consider Complaint Database records under the current product bucket for Virtual currency subcategory, with a received date between 2019-08-26 and 2022-08-26.","First determine the AllCompanies original peak month, then identify the top two companies by complaint count in that peak month.","These two companies must be removed entirely from the full three-year cohort, then recompute the residual peak month and all downstream fields based on the remaining cohort."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["current complaint-form taxonomy yields the product bucket for Virtual currency","complaint records within the fixed three-year cohort yield the all-company peak month, per-month top companies, and residual-cohort recomputations after company removal","final rows are produced only after the top-2 companies from the original peak month are removed from the full cohort and downstream aggregates are computed on the resulting cohort"],"control_dependency":["peak-month top companies must be removed from the entire cohort, not only from the original peak month","residual peak detection must be computed from the rewritten cohort rather than by local patching of the original month","downstream state / company / earliest-complaint fields are valid only after the global company-removal step is locked"],"freeze":{"historical_window":"Complaint Database records received from 2019-08-26 through 2022-08-26 under the current product-bucket mapping for Virtual currency"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only consider Complaint Database records under the current product bucket for Virtual currency subcategory, with a received date between 2019-08-26 and 2022-08-26.","First determine the AllCompanies original peak month, then identify the top two companies by complaint count in that peak month.","These two companies must be removed entirely from the full three-year cohort, then recompute the residual peak month and all downstream fields based on the remaining cohort."],"exclusion_conditions":["Exclude results that only locally delete top-2 company records from the original peak month.","Exclude results that do not write the top-2 company set back into the full cohort before recomputing the residual peak.","Exclude results that use downstream state, company, or earliest complaint fields computed from a cohort that has not been recomputed after removal."],"normalization":{"field_separator":"|","record_separator":",","schema":["Cluster","Month","MonthComplaints","ExcludedTop2Companies","ExcludedTop2PeakMonthComplaints","TopState","StateComplaints","TopCompany","CompanyComplaints","EarliestComplaintID","EarliestDate","Issue","SubIssue"],"cluster_order":["AllCompanies","ResidualAfterTop2"],"date_format":{"Month":"YYYY-MM","EarliestDate":"YYYY-MM-DD"},"ExcludedTop2Companies":"join the two excluded company names with `+` in source-peak complaint-count descending order, breaking ties alphabetically","TopState":"use the uppercase two-letter state abbreviation","TopCompany":"use the company display name as shown in the source data","tie_breaks":"for the earliest complaint use EarliestDate ascending then Complaint ID ascending","SubIssue":"emit `NONE` when the complaint row has no sub-issue value"}}} +{"task_id":"consumerfinance_007","domain":"CFPB_COMPLAINT_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"I am drafting a layered analysis report on the core factors behind a batch of cryptocurrency complaints. I need your help to verify the true causes of this complaint surge step by step using the CFPB complaint database.\n\nFirst, define the base scope of the analysis. Using the current CFPB product and issue taxonomy documentation, confirm the product bucket that \"Virtual currency\" falls under. Once the bucket is determined, strictly restrict the time range to between 2020-01-01 and 2022-08-26, and only for the \"Virtual currency\" subcategory under that product bucket, extract the original peak month (BaselinePeak) and its total complaint count for this initial complaint cohort.\n\nSecond, determine the shift in peaks by progressively removing core influencing factors. Round 1: In the original peak month identified above, identify the most frequent \"Company public response\" value, then completely remove all complaints with that value from the entire initial cohort to obtain the recalculated second peak month (AfterDominantPublicResponse). Round 2: In the second peak month, identify the most frequent \"Issue\" type, remove it from the residual data of the previous round to lock in the third emerging peak month (AfterDominantPublicResponseAndIssue). Round 3: In the third peak month, identify the single most complained-about company (Company), remove that company, and perform the final round of statistics to obtain the final residual peak month (AfterDominantPublicResponseIssueAndCompany).\n\nThird, for each of the identified characteristic months, extract detailed data. For these four complaint clusters, besides obtaining the total complaint count for that month, also determine the newly added removal dimension and its specific excluded value, and the count of that excluded value in the month that served as its reference source. Additionally, identify the state with the highest complaint count in that month and its complaint count, the most complained-about company within that state and its complaint volume, and the complete information of the earliest complaint received by the highest-complaint company in that state during that characteristic month, including complaint ID, date, Issue, and Sub-issue.\n\nFinally, after completing the investigation and information collation for all the above dimensions, concatenate all extracted parameters for these four complaint clusters strictly in the order of BaselinePeak, AfterDominantPublicResponse, AfterDominantPublicResponseAndIssue, and AfterDominantPublicResponseIssueAndCompany into four strings with no spaces. Each line's field order is strictly fixed as: |||||||||||||. In case of ties, always select by lexicographic ascending order; for the earliest complaint with the same date, select by ascending Complaint ID numeric value. Normalize all empty values to NONE before sorting.","start_url":"https://www.consumerfinance.gov/data-research/consumer-complaints/","output_format":"Concatenate into four strings with no spaces, strictly in the order of BaselinePeak, AfterDominantPublicResponse, AfterDominantPublicResponseAndIssue, AfterDominantPublicResponseIssueAndCompany; each line's field order is strictly fixed as: |||||||||||||. In case of ties, always select by lexicographic ascending order; for the earliest complaint with the same date, select by ascending Complaint ID numeric value. Normalize all empty values to NONE before sorting.","oracle_answer":"BaselinePeak|2021-05|336|NONE|NONE|0|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,AfterDominantPublicResponse|2022-07|31|Company public response|NONE|321|CA|6|BANK OF AMERICA, NATIONAL ASSOCIATION|4|5735227|2022-07-05|Other transaction problem|NONE,AfterDominantPublicResponseAndIssue|2021-10|13|Issue|Fraud or scam|26|TX|2|BANK OF AMERICA, NATIONAL ASSOCIATION|1|4821611|2021-10-18|Other transaction problem|NONE,AfterDominantPublicResponseIssueAndCompany|2021-06|8|Company|Foris DAX, Inc.|5|NC|3|TRUIST FINANCIAL CORPORATION|2|4462160|2021-06-15|Money was not available when promised|NONE","metadata":{"State-Gated Retrieval":["Only consider Complaint Database records under the current product bucket's Virtual currency subcategory with a received date between 2020-01-01 and 2022-08-26.","Determine the peak months for the four stages BaselinePeak, AfterDominantPublicResponse, AfterDominantIssue, and AfterDominantCompany sequentially as required.","Each round's identified dominant Company public response, dominant Issue, and dominant Company must be written back and globally deleted from the corresponding upstream residual cohort before running the next round of statistics."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["current complaint-form taxonomy yields the product bucket for Virtual currency","complaint records yield the baseline peak plus the dominant Company public response, dominant Issue, and dominant Company at successive residual-peak states","final rows are produced only after each dominant value is applied to the full upstream residual cohort and then used to determine the next peak"],"control_dependency":["dominant values found in a peak month cannot be deleted only inside that month; each must be propagated to the full upstream cohort","each new residual peak depends on the prior round's global rewrite, so local month-by-month deletion gives the wrong chain","downstream counts and exemplar complaints are valid only after the full three-stage waterfall is executed"],"freeze":{"historical_window":"Complaint Database records received from 2020-01-01 through 2022-08-26 under the current product-bucket mapping for Virtual currency"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only consider Complaint Database records under the current product bucket's Virtual currency subcategory with a received date between 2020-01-01 and 2022-08-26.","Determine the peak months for the four stages BaselinePeak, AfterDominantPublicResponse, AfterDominantIssue, and AfterDominantCompany sequentially as required.","Each round's identified dominant Company public response, dominant Issue, and dominant Company must be written back and globally deleted from the corresponding upstream residual cohort before running the next round of statistics."],"exclusion_conditions":["Exclude results that only delete records locally within the current peak month without writing back to the entire upstream cohort.","Exclude results that do not re-find the next peak month on each round's residual cohort.","Exclude intermediate or final fields based on downstream statistics that were not fully re-run."],"normalization":{"field_separator":"|","record_separator":",","schema":["Cluster","Month","MonthComplaints","NewExclusionType","NewExclusionValue","NewExclusionCountInSourcePeak","TopState","StateComplaints","TopCompany","CompanyComplaints","EarliestComplaintID","EarliestDate","Issue","SubIssue"],"cluster_order":["BaselinePeak","AfterDominantPublicResponse","AfterDominantPublicResponseAndIssue","AfterDominantPublicResponseIssueAndCompany"],"date_format":{"Month":"YYYY-MM","EarliestDate":"YYYY-MM-DD"},"NewExclusionType":"emit the canonical exclusion-type label from the source workflow; when no new exclusion is applied, emit NONE","NewExclusionValue":"emit the canonical excluded value; when no value exists, emit NONE","TopState":"use the uppercase two-letter state abbreviation","TopCompany":"use the company display name as shown in the source data","tie_breaks":"normalize empty values to NONE before sorting; for other ties use lexicographic order ascending, and for the earliest complaint use EarliestDate ascending then Complaint ID ascending","SubIssue":"emit NONE when the complaint row has no sub-issue value"}}} +{"task_id":"europemc_001","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":21,"instruction":"I want to consolidate the admission variables actually used by several prediction schemes in this 2020 COVID-19 mortality risk prediction paper into a single line, to make it easy to see which variables overlap and which appear only in the comparison schemes.\nPlease follow the steps below. First, locate the target paper — a 2020 open-access review whose title contains all of \"prognosis model\", \"mortality risk\", and \"COVID-19\", and whose main text discusses hospitalized patients in Wuhan.\nThen, retain only two types of variables:\n- Type 1: admission variables that appear in both the Random Forest and XGBoost variable importance rankings.\n- Type 2: additional admission variables that do not appear in both rankings but are present in the CURB-65 or NEWS schemes used by the authors for comparison.\nNext, for each retained variable, record it in the following format:\nvariable~RF_rank_or_0~XGB_rank_or_0~F~C~N~X\nWhere:\n- RF_rank_or_0: the rank of this variable in the Random Forest ranking; write 0 if it is not included.\n- XGB_rank_or_0: the rank of this variable in the XGBoost ranking used in the paper; write 0 if it is not included.\n- F: whether this variable entered the authors' final logistic regression model.\n- C: whether this variable belongs to CURB-65.\n- N: whether this variable belongs to NEWS.\n- X: whether this variable belongs to the XGBoost model used as a comparison in the paper.\nFinally, sort all variables alphabetically by variable name, join them with | into a single line; if the paper cannot be found, output NONE.","start_url":"https://europepmc.org/advancesearch","output_format":"Next, for each retained variable, record it in the following format:\nvariable~RF_rank_or_0~XGB_rank_or_0~F~C~N~X\nWhere:\n- RF_rank_or_0: the rank of this variable in the Random Forest ranking; write 0 if it is not included.\n- XGB_rank_or_0: the rank of this variable in the XGBoost ranking used in the paper; write 0 if it is not included.\n- F: whether this variable entered the authors' final logistic regression model.\n- C: whether this variable belongs to CURB-65.\n- N: whether this variable belongs to NEWS.\n- X: whether this variable belongs to the XGBoost model used as a comparison in the paper.\nFinally, sort all variables alphabetically by variable name, join them with | into a single line; if the paper cannot be found, output NONE.","oracle_answer":"Age~4~2~1~1~0~0|Alanine aminotransferase~17~11~0~0~0~0|Aspartate transaminase~6~4~0~0~0~0|Blood urea nitrogen~5~7~0~1~0~0|Confusion~0~0~0~1~1~0|CRP~2~6~1~0~0~1|Creatinine~9~13~0~0~0~0|Diastolic pressure~16~17~0~1~0~0|Heart rate~15~14~0~0~1~0|LDH~1~1~1~0~0~1|Lymphocyte count~3~5~0~0~0~1|Monocytes~12~16~0~0~0~0|Neutrophil~7~3~0~0~0~0|Normal platelet~10~9~0~0~0~0|Oxygen inhalation~0~0~0~0~1~0|Respiratory rate~11~10~0~1~1~0|SPO2~0~0~0~0~1~0|Systolic pressure~13~12~0~1~1~0|Temperature~18~18~0~0~1~0|Total bilirubin~14~15~0~0~0~0|White blood cell~8~8~0~0~0~0","metadata":{"State-Gated Retrieval":["First, locate the target paper: a 2020 open-access review whose title contains all of \"prognosis model\", \"mortality risk\", and \"COVID-19\", and whose main text discusses hospitalized patients in Wuhan.","Retain only two types of variables: admission variables that appear in both the Random Forest and XGBoost rankings; or variables that do not appear in both rankings but are additional items belonging to CURB-65 or NEWS.","For each variable, annotate it as required with RF rank, XGB rank, and whether it belongs to the final logistic regression, CURB-65, NEWS, and the comparison XGBoost model, then output in alphabetical order by variable name."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Europe PMC search results and the target open-access article yield the candidate Wuhan COVID mortality-risk review","article tables and discussion sections yield RF/XGBoost rankings, final logistic-regression inclusion, and comparator-variable memberships for CURB-65 / NEWS / external XGBoost","final rows are produced only after overlapping variables and comparator-only variables are merged into one normalized variable table"],"control_dependency":["comparator-only variables must be captured from the discussion definitions rather than from Table 2 + Table 3 alone","comparator membership must be read from the article's explicit scheme definitions rather than inferred from common clinical usage","variable normalization must wait until RF/XGBoost overlap and comparator-only additions are both complete"],"freeze":{"historical_window":"the 2020 open-access COVID-19 mortality-risk review about Wuhan inpatients; variable inclusion and comparator definitions are taken from the article's current full-text tables and discussion"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["First, locate the target paper: a 2020 open-access review whose title contains all of \"prognosis model\", \"mortality risk\", and \"COVID-19\", and whose main text discusses hospitalized patients in Wuhan.","Retain only two types of variables: admission variables that appear in both the Random Forest and XGBoost rankings; or variables that do not appear in both rankings but are additional items belonging to CURB-65 or NEWS.","For each variable, annotate it as required with RF rank, XGB rank, and whether it belongs to the final logistic regression, CURB-65, NEWS, and the comparison XGBoost model, then output in alphabetical order by variable name."],"exclusion_conditions":["Exclude admission variables that do not appear in both RF and XGB rankings and also do not belong to CURB-65 / NEWS additional variables.","Exclude results that stop at Table 2 + Table 3 and do not proceed to the discussion to read the comparator definitions.","Exclude results that infer comparator variables by common sense rather than verifying against the paper's explicit definitions."],"normalization":{"field_separator":"~","record_separator":"|","schema":["variable","RF_rank_or_0","XGB_rank_or_0","F","C","N","X"],"variable":"use the variable wording normalized in the article tables; keep `Systolic pressure` and `Diastolic pressure` as separate variables","rank_fields":"RF_rank_or_0 and XGB_rank_or_0 are positive integer ranks when present, otherwise 0","boolean_fields":"F, C, N, and X are emitted as 1 or 0 only","sorting_or_selection":"variable name alphabetical ascending","stop_condition":["the shared variable set from Table 2 and Table 3 is fully resolved","the comparator definitions for CURB-65, NEWS, and the comparison XGBoost model are fixed before the final line is emitted"]}}} +{"task_id":"europemc_002","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":6,"instruction":"Track studies that were Phase 1 in the 2021 Alzheimer's disease drug development pipeline review by their ClinicalTrials.gov identifier, and check whether they continue to appear in the 2022 and 2023 pipeline reviews.\nFollow these steps. First, locate the three articles: the 2021 review titled \"Alzheimer's disease drug development pipeline\", and the 2022 and 2023 open-access reviews in the same series.\nIn the 2021 review, retain only the studies that were listed as Phase 1 at that time.\nThen, in the 2022 and 2023 reviews, check each of these studies one by one, but match them by the same ClinicalTrials.gov identifier rather than by drug name alone, because drug names can change across years.\nFinally, keep only those studies that can still be found under the same ClinicalTrials.gov identifier in both 2022 and 2023. Format the result as a single line: NCT~2021_agent~2022_phase~2022_agent~2023_phase~2023_agent. Sort by NCT in ascending order and join records with |. If the set of three articles cannot be found, output NONE.","start_url":"https://europepmc.org/advancesearch","output_format":"Finally, keep only those studies that can still be found under the same ClinicalTrials.gov identifier in both 2022 and 2023. Format the result as a single line: NCT~2021_agent~2022_phase~2022_agent~2023_phase~2023_agent. Sort by NCT in ascending order and join records with |. If the set of three articles cannot be found, output NONE.","oracle_answer":"NCT03277573~Salsalate~P1~Salsalate~P1~Salsalate|NCT03634007~AAVrh.10hAPOE2~P1~LX1001~P2~LX1001|NCT03748303~Allopregnanolone (Allo)~P1~Allopregnanolone~P1~Allopregnanolone|NCT04149860~Lu AF87908~P1~Lu AF87908~P1~Lu AF87908|NCT04451408~LY3372993~P1~LY3372993~P1~LY3372993|NCT04500847~Emtricitabine~P1~Emtricitabine~P1~Emtricitabine","metadata":{"State-Gated Retrieval":["Use only the Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline article as the baseline.","Retention in 2022 and 2023 must be determined by exact match on the ClinicalTrials.gov NCT identifier, not by drug name alone.","Keep only studies that are found under the same NCT in both 2022 and 2023, and output them sorted by NCT in ascending order."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the 2021, 2022, and 2023 pipeline reviews yield the 2021 Phase 1 baseline cohort and the later-year lookup tables","article tables yield exact ClinicalTrials.gov NCT IDs, yearly phase labels, and yearly drug names for the same study","final rows are produced only after 2021 baseline studies are re-identified in both later reviews by exact NCT matching"],"control_dependency":["continuation must be matched by exact NCT rather than by drug name, because drug names drift across years","2022 and 2023 lookups must use the fixed 2021 Phase 1 NCT set as the starting cohort rather than later-year table membership alone","yearly phase/name fields are only valid after the same NCT is confirmed across all three reviews"],"freeze":{"historical_window":"the 2021, 2022, and 2023 open-access Alzheimer's disease drug development pipeline reviews; the baseline is the 2021 Phase 1 cohort and continuation is matched by exact ClinicalTrials.gov NCT"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Use only the Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline article as the baseline.","Retention in 2022 and 2023 must be determined by exact match on the ClinicalTrials.gov NCT identifier, not by drug name alone.","Keep only studies that are found under the same NCT in both 2022 and 2023, and output them sorted by NCT in ascending order."],"exclusion_conditions":["Exclude results that are continued by drug name alone without an exact match on the same ClinicalTrials.gov identifier.","Exclude studies found only in 2022 or only in 2023, not continuously retained in both years.","Exclude studies not in the 2021 baseline Phase 1 set."],"normalization":{"field_separator":"~","record_separator":"|","schema":["NCT","agent_2021","phase_2022","agent_2022","phase_2023","agent_2023"],"NCT":"use the exact ClinicalTrials.gov identifier as the cross-year identity key","phase_fields":"normalize phases to P1, P2, or P3; if the same NCT appears multiple times in a year, keep the highest phase for that year","agent_fields":"keep the agent text as shown in each year-specific table","sorting_or_selection":"NCT ascending"}}} +{"task_id":"europemc_003","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"I want to see which candidate molecules predicted in the 2023 \"Antibodies to Watch\" article as expected to submit their first marketing applications in 2022–2023 have actually been approved or entered first regulatory review in the 2024 installment of the same series.\nFollow the steps below. First, find the open-access full texts of both the 2023 and 2024 \"Antibodies to Watch\" articles in Europe PMC.\nThen, in the 2023 article, identify all candidate molecules listed as **\"expected to submit first marketing applications in 2022–2023\"**.\nNext, check each of these molecules against the 2024 article and retain only those that have been approved or have entered first regulatory review.\nFinally, format each qualifying molecule as follows:\nINN~2023 category~2023 prediction label~2024 status~2024 indication~2024 region\nwhere:\n\t•\t2023 category uses NC/CA for non-cancer/cancer;\n\t•\t2024 status uses A/R for first approval/first regulatory review.\nSort by INN alphabetically and output as a single line joined by |; if neither article is found, output NONE.","start_url":"https://europepmc.org/advancesearch","output_format":"Finally, format each qualifying molecule as follows:\nINN~2023 category~2023 prediction label~2024 status~2024 indication~2024 region\nwhere:\n\t•\t2023 category uses NC/CA for non-cancer/cancer;\n\t•\t2024 status uses A/R for first approval/first regulatory review.\nSort by INN alphabetically and output as a single line joined by |; if neither article is found, output NONE.","oracle_answer":"Cosibelimab~CA~MAA,Q2 2023~R~Squamous cell carcinoma~US|Elranatamab~CA~2023~A~Multiple myeloma~US,EU,Switzerland,Brazil|Garadacimab~NC~BLA,2023~R~Hereditary angioedema~EU|Odronextamab~CA~BLA,H2 2022~R~Diffuse large B-cell lymphoma~US,EU|Pozelimab~NC~BLA,H2 2022~A~CHAPLE disease~US|Suciraslimab~NC~NDA,2023~R~Rheumatoid arthritis~China|Talquetamab~CA~2023–25~A~Multiple myeloma~US,EU,UK,Switzerland|Zolbetuximab~CA~BLA,2023~R~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China","metadata":{"State-Gated Retrieval":["First, identify all candidate molecules in the 2023 Antibodies to Watch article that are predicted to submit first marketing applications in 2022-2023.","Then, check each of these molecules against the 2024 article and retain only those that have been first approved or have entered first regulatory review.","The 2024 status must distinguish A=first approval from R=first regulatory review, and include the 2024 indication and region."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the 2023 Antibodies to Watch article yields the forecast baseline of candidates expected to file in 2022-2023","the 2024 article tables yield first-approval outcomes, first-regulatory-review outcomes, indications, and regions for the same INNs","final rows are produced only after Table 1 approvals and Table 2 first-review candidates are merged back onto the 2023 forecast cohort"],"control_dependency":["both 2024 Table 1 and Table 2 must be read so that first-review-but-not-yet-approved candidates are retained","2024 status coding must distinguish approval from first regulatory review instead of collapsing both into a single positive match","region and indication fields are valid only after the 2023 forecast cohort is reconciled against both 2024 tables"],"freeze":{"historical_window":"the 2023 and 2024 open-access Antibodies to Watch articles; baseline candidates come from the 2023 forecast set and 2024 outcomes come from current Table 1 plus Table 2"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["First, identify all candidate molecules in the 2023 Antibodies to Watch article that are predicted to submit first marketing applications in 2022-2023.","Then, check each of these molecules against the 2024 article and retain only those that have been first approved or have entered first regulatory review.","The 2024 status must distinguish A=first approval from R=first regulatory review, and include the 2024 indication and region."],"exclusion_conditions":["Exclude results that only check approvals in 2024 Table 1 without also consulting Table 2 for first regulatory review candidates.","Exclude molecules not in the 2023 forecast baseline.","Exclude candidates that were neither first approved nor entered first regulatory review in 2024."],"normalization":{"field_separator":"~","record_separator":"|","schema":["INN","category_2023","prediction_label_2023","status_2024","indication_2024","region_2024"],"category_2023":"emit `NC` or `CA` exactly","prediction_label_2023":"keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H2 2022`","status_2024":"emit `A` for first approval and `R` for first regulatory review","region_2024":"preserve the raw region string but remove spaces after commas, for example `US,EU`","sorting_or_selection":"INN alphabetical ascending"}}} +{"task_id":"europemc_004","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":9,"instruction":"I am evaluating the accuracy of annual antibody drug watchlist predictions and want to trace whether the 2022 cohort of candidates from the Antibodies to Watch series simply experienced delays in development progress. I need you to use the Europe PMC database to systematically map the year-over-year status changes for these candidates.\n\nFirst, establish the literature baseline and initial candidate set. Precisely locate the three open-access full-text Antibodies to Watch articles published in 2022, 2023, and 2024 in Europe PMC. Once all three articles are found, identify a set of antibodies (INN) with a specific delay pattern: those that were explicitly listed in the 2022 article under a category such as \"expected to file soon\" (identified by INN, drug code, project name, or other recognizable name) but, due to slower progress, still remained as watchlist candidates in the 2023 article.\n\nSecond, determine the latest status of these consecutively delayed candidates. For the identified antibody group, ascertain their final status in the 2024 article: whether they finally received first approval, are in first regulatory review, remain on the 2024 watchlist, or have completely disappeared from the 2024 main article list.\n\nFinally, after completing the cross-year literature review and status confirmation, aggregate the extracted parameters into a specific formatted single-line record. If all three target articles cannot be found, output NONE. If all three are successfully located, concatenate the internal parameters for each qualifying antibody in the fixed order \"INN~2022 category~2022 phase~2023 prediction label~2024 status~2024 phase or NA~2024 indication or NA~2024 region or NA\". Then join all identified candidates in strict alphabetical order by INN using the \"|\" symbol into a single string with no spaces.","start_url":"https://europepmc.org/advancesearch","output_format":"If all three target articles cannot be found, output NONE. If all three are successfully located, concatenate the internal parameters for each qualifying antibody in the fixed order \"INN~2022 category~2022 phase~2023 prediction label~2024 status~2024 phase or NA~2024 indication or NA~2024 region or NA\". Then, join all identified candidates in strict alphabetical order by INN using the \"|\" symbol into a single string with no spaces.","oracle_answer":"Apamistamab-I-131~CA~P3~BLA,H1 2023~F~P3~Ablation of bone marrow prior to transplantation in AML patients~NA|Bentracimab~NC~P3~BLA,Q4 2022~F~P3~Reversal of the antiplatelet effects of ticagrelor~NA|Cosibelimab~CA~P3~MAA,Q2 2023~R~NA~Squamous cell carcinoma~US|Erfonrilimab~CA~P3~NDA~F~P3~Pancreatic ductal adenocarcinoma~NA|Odronextamab~CA~P2~BLA,H2 2022~R~NA~Diffuse large B-cell lymphoma~US,EU|Talquetamab~CA~P2~2023-25~A~NA~Multiple myeloma~US,EU,UK,Switzerland|Tiragolumab~CA~P3~2023~F~P3~NSCLC~NA|Zanidatamab~CA~P2~2023~D~NA~NA~NA|Zolbetuximab~CA~P3~BLA,2023~R~NA~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China","metadata":{"State-Gated Retrieval":["Start with the 2022 Antibodies to Watch candidates listed as \"expected to file soon\", but retain only those molecules that still remain as watchlist candidates in the 2023 article of the same series.","For these consecutively delayed candidates, determine their final status in the 2024 article: first approved, in first regulatory review, or completely absent from Tables 1-4.","Name matching must handle the Apamistamab naming drift; complete absence in 2024 must be explicitly encoded as D."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the 2022, 2023, and 2024 Antibodies to Watch articles yield the 2022 soon-to-file baseline, 2023 carry-over membership, and 2024 status tables","article tables and full-text naming context yield name normalizations, 2024 table presence/absence, and final status labels for each carried-over INN","final rows are produced only after 2022 candidates are filtered by 2023 carry-over status and then resolved against 2024 Tables 1-4 plus explicit absence"],"control_dependency":["2022 candidates must first be filtered by 2023 carry-over status before they are matched against the 2024 tables","Apamistamab naming drift forces explicit normalization before 2024 lookup","complete 2024 absence must be emitted as D rather than treated as a lookup failure"],"freeze":{"historical_window":"the 2022, 2023, and 2024 open-access Antibodies to Watch articles; the 2022 baseline is filtered by 2023 carry-over status and then checked against 2024 Tables 1-4, with explicit absence retained as a status"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Start with the 2022 Antibodies to Watch candidates listed as \"expected to file soon\", but retain only those molecules that still remain as watchlist candidates in the 2023 article of the same series.","For these consecutively delayed candidates, determine their final status in the 2024 article: first approved, in first regulatory review, or completely absent from Tables 1-4.","Name matching must handle the Apamistamab naming drift; complete absence in 2024 must be explicitly encoded as D."],"exclusion_conditions":["Exclude results that directly match the 2022 baseline against 2024 without applying the 2023 carry-over filter.","Exclude matching results that do not handle the Apamistamab naming drift.","Exclude cases where complete 2024 absence is treated as a lookup failure rather than a status that must be output."],"normalization":{"field_separator":"~","record_separator":"|","schema":["INN","category_2022","phase_2022","prediction_label_2023","status_2024","phase_or_NA_2024","indication_or_NA_2024","region_or_NA_2024"],"category_2022":"emit `NC` or `CA` exactly","phase_2022":"normalize stage labels such as `Phase 3` to `P3` and `Pivotal Phase 2` to `P2`","prediction_label_2023":"keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H1 2023`","status_2024":"emit one of `A`, `R`, `F`, or `D` exactly","conditional_fields_2024":"if status is A or R, phase_or_NA_2024 must be `NA` and region_or_NA_2024 must carry the raw region string; if status is F, region_or_NA_2024 is `NA` and phase_or_NA_2024 carries the normalized phase; if status is D, all three trailing 2024 fields are `NA`","naming_exception":"preserve the fixed source exception around the Apamistamab-I-131 naming variant instead of over-normalizing the INN","sorting_or_selection":"INN alphabetical ascending"}}} +{"task_id":"europemc_005","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":20,"instruction":"I am compiling a cross-platform correspondence checklist for core predictors of COVID-19 hospitalization prognosis. Using the Europe PMC database, I need to work through the process of identifying the variables each specific model actually used, together with their matching attributes.\n\nFirst, establish the literature baseline. In Europe PMC, precisely locate the 2024 WHO global individual patient data validation paper and identify the four prognostic models that were successfully externally validated in low- and middle-income country data. Then trace back to the three original model papers corresponding to these four models.\n\nAfter locating these four target papers, the core task is to extract and verify the specific characteristics of the predictors. Determine which distinct admission variables each of the four models actually used in the evaluation. For each identified variable, clarify its acquisition pathway in the WHO platform baseline table: either a direct match under the same or a substantively equivalent name (marked as E), or a fixed mapped conversion (marked as M). Also trace the model-source attributes of these variables: whether they belong to the model with the strongest external validation performance (TopAUC), the model with calibration closest to the ideal (BestCal), or an original model that explicitly used dynamic data (Dyn).\n\nTo ensure consistent judgment criteria, model attribution, performance attribution, and variable conflicts must all be based on the verifiable model descriptions, performance summaries, and field definitions in the target papers. When the same concept has multiple naming or mapping methods, prioritize conservative mappings that maintain cross-model interpretability consistency, and flag mapping differences that may affect interpretability consistency.\n\nAfter completing the above literature tracing and variable characteristic extraction, finally extract these parameters to generate a formatted single-line summary record. For status flags, uniformly use 1 for yes and 0 for no for all boolean types. If the search fails to locate the one validation paper and the three original model papers, output NONE. If all are successfully located, after arranging all distinct variables strictly in alphabetical order by variable name, concatenate the parameters within each variable in the fixed order \"variable~category~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict\", then join all variables with \"|\" into a single string with no spaces.","start_url":"https://europepmc.org/advancesearch","output_format":"If the search fails to locate the one validation paper and the three original model papers, output NONE. If all are successfully located, after arranging all distinct variables strictly in alphabetical order by variable name, concatenate the parameters within each variable in the fixed order \"variable~category~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict\", then join all variables with \"|\" into a single string with no spaces. For all boolean types, uniformly use 1 for yes and 0 for no.","oracle_answer":"Age~DEM~1~1~1~1~Age~E~1~1~1~0|Cancer~COM~0~0~1~0~Cancer~E~1~0~0~0|Chronic kidney disease~COM~0~0~0~1~CKD~M~0~0~0~1|Chronic lung disease~COM~0~0~1~0~Pulmonary disease~M~1~0~0~0|Chronic renal disease~COM~0~0~1~0~CKD~M~1~0~0~1|Coronary heart disease~COM~0~1~0~0~CHD~M~0~0~0~1|Cough~SYM~0~0~1~0~Cough~E~1~0~0~0|Diabetes mellitus~COM~0~0~1~0~Diabetes~M~1~0~0~0|Diarrhea~SYM~0~0~1~0~Diarrhea~E~1~0~0~0|Dyspnea~SYM~0~0~1~0~Dyspnea~E~1~0~0~0|Fever~VIT~0~0~0~1~Body temperature~M~0~0~0~0|Heart disease~COM~0~0~1~0~CHD~M~1~0~0~1|Hypertension~COM~0~1~1~0~Hypertension~E~1~0~0~0|Immunocompromised status~COM~0~0~1~0~Immunosuppression~M~1~0~0~0|O2 saturation~VIT~1~0~0~0~Oxygen saturation~M~0~1~1~0|Respiratory rate~VIT~1~0~0~1~Respiratory rate~E~0~1~1~0|Sex~DEM~0~0~1~0~Men~M~1~0~0~0|Smoking~DEM~1~0~0~0~Smoking~E~0~1~1~1|Smoking status~DEM~0~0~0~1~Smoking~M~0~0~0~1|Systolic blood pressure~VIT~0~0~0~1~Systolic blood pressure~E~0~0~0~0","metadata":{"State-Gated Retrieval":["First, in the 2024 WHO global individual patient data validation paper, identify the four prognostic models that were successfully externally validated in LMIC data, and trace back to the three corresponding original model papers.","For each predictor, retain the original wording from WHO Table 1, annotate its matching method (E/M) in the WHO baseline table, and indicate whether it comes from the TopAUC, BestCal, or Dyn model.","When encountering a predictor that was conceptually merged on the WHO side, trace back to the original Wang/Zhou papers to split it apart and then recalculate the relevant fields."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the 2024 WHO global validation paper yields the four externally validated models and the WHO-side predictor wording/mapping baseline","the three original model papers yield model-specific predictor wordings, dynamic-data flags, and conflicts hidden by WHO-side conceptual merging","final rows are produced only after WHO predictors are kept separate, traced back to the original papers, and then re-annotated for mapping and model provenance"],"control_dependency":["conceptually merged WHO predictors must be split back out when the original Wang/Zhou papers expose distinct variables","Table 2 mapping decisions are not valid until Table 1 wording and original-paper predictor sets are reconciled","TopAUC / BestCal / Dyn flags must be determined after the predictor split is applied correctly"],"freeze":{"historical_window":"the 2024 WHO global IPD validation paper and the three linked original COVID prognosis-model papers, using their current open-access full texts and tables"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["First, in the 2024 WHO global individual patient data validation paper, identify the four prognostic models that were successfully externally validated in LMIC data, and trace back to the three corresponding original model papers.","For each predictor, retain the original wording from WHO Table 1, annotate its matching method (E/M) in the WHO baseline table, and indicate whether it comes from the TopAUC, BestCal, or Dyn model.","When encountering a predictor that was conceptually merged on the WHO side, trace back to the original Wang/Zhou papers to split it apart and then recalculate the relevant fields."],"exclusion_conditions":["Exclude results that directly merged conceptually similar predictors after WHO Table 1 without tracing back to the original papers for splitting.","Exclude results that relied solely on loose mapping from WHO Table 2 without incorporating the original paper wording.","Exclude results that fixed TopAUC/BestCal/Dyn annotations before applying the predictor split correction."],"normalization":{"field_separator":"~","record_separator":"|","schema":["variable","category","B","W","Zh","Zo","WHOfield","WHOx","TopAUC","BestCal","Dyn","Conflict"],"variable_set":"the candidate variable set comes only from the WHO validation Table 1 and remains at the original 20 predictors","conflict_groups":"do not pre-merge the three source conflict groups `Smoking`/`Smoking status`, `Chronic renal disease`/`Chronic kidney disease`, and `Coronary heart disease`/`Heart disease` before applying the conflict flag","boolean_fields":"B, W, Zh, Zo, TopAUC, BestCal, Dyn, and Conflict are emitted as 1 or 0 only","WHOx":"emit `E` for exact WHO matches or direct matches under a substantively equivalent name, `M` for the fixed mapped match, and `NA` when no WHO field matches","sorting_or_selection":"variable name alphabetical ascending"}}} +{"task_id":"genome_001","domain":"KEGG_BRITE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am compiling a reference list of medications for ulcerative colitis for in-hospital use. From the immunosuppressants cataloged in KEGG, I want to select those drug entries that have been approved in Japan by the end of June 2025 and that carry explicit CYP-related metabolism information or CYP inhibition indications. Please proceed in the following order: first, within the scope of KEGG immunosuppressants for ulcerative colitis, screen for drug entries approved in Japan by the end of June 2025; then check whether each entry has explicit CYP-related metabolism information or CYP inhibition indications, retaining only qualifying entries. Next, record each entry's Japanese therapeutic classification code, ATC code, corresponding target branch, and Japan first approval date. Finally, output a single-line string sorted by Japan first approval date from earliest to latest, in the format ||||; separate entries with commas; if no qualifying entries exist, output NONE.","start_url":"https://www.genome.jp/kegg/brite.html","output_format":"Output a single-line string sorted by Japan first approval date from earliest to latest, in the format ||||; separate entries with commas; if no qualifying entries exist, output NONE.","oracle_answer":"D09783|3999|L04AF01|JAK1/JAK2/JAK3/TYK2|2013/3/25,D11048|3999|L04AF03|JAK1|2020/1/23,D10931|2399|L04AE05|S1PR1/S1PR4/S1PR5|2025/6/24","metadata":{"State-Gated Retrieval":["Within the scope of KEGG immunosuppressants for ulcerative colitis, retain only entries approved in Japan by 2025-06-30 and that carry explicit CYP-related metabolism information or CYP inhibition indications.","Candidate drugs must be re-verified against the corrected UC drug list for Japanese therapeutic classification, ATC, target branch, CYP evidence, and Japan first approval date.","Finally, output sorted by Japan first approval date from earliest to latest."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["KEGG disease H01466 and linked drug entries yield the ulcerative-colitis immunosuppressant candidate set","each candidate drug entry yields Japanese class, ATC, target branch, CYP metabolism/inhibition evidence, and Japan approval date","final rows are produced only after the full UC candidate set is determined and every candidate is checked against CYP evidence and PMDA timing"],"control_dependency":["the candidate set must include Japanese class 3999 UC drugs when the disease page exposes them rather than being limited to 2399 alone","target / CYP / PMDA validation must be applied across the full candidate set rather than only the old 2399 subset","entries without explicit CYP evidence may be dropped only after the full candidate set has been established"],"freeze":{"historical_window":"KEGG ulcerative-colitis drug candidates with Japan approvals on or before 2025-06-30; current drug-entry annotations provide target, CYP, and Japan-class metadata"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Within the scope of KEGG immunosuppressants for ulcerative colitis, retain only entries approved in Japan by 2025-06-30 and that carry explicit CYP-related metabolism information or CYP inhibition indications.","Candidate drugs must be re-verified against the corrected UC drug list for Japanese therapeutic classification, ATC, target branch, CYP evidence, and Japan first approval date.","Finally, output sorted by Japan first approval date from earliest to latest."],"exclusion_conditions":["Exclude results that incorrectly lock the upstream scope to the 2399 digestive branch without falling back to the full UC drug list.","Exclude entries without explicit CYP-related metabolism information or CYP inhibition indications.","Exclude entries with a Japan approval date after 2025-06-30 or that are not within the KEGG UC immunosuppressant scope."],"normalization":{"field_separator":"|","record_separator":",","schema":["DRUG_ID","JP_class","ATC","Target_branch","JP_date"],"dedup_key":"DRUG_ID","JP_date":"use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value","Target_branch":"emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`","sorting_or_selection":{"primary":"JP_date ascending","secondary":"DRUG_ID ascending"}}}} +{"task_id":"genome_002","domain":"KEGG_GENOME","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am preparing a lecture page on classic animal endosymbiosis cases and want to find, among KEGG's host-symbiont examples, the case that meets the following conditions: it was already recorded by the end of 2005, its bacterial symbiont genome contains named extra replicons, and the names of those replicons directly correspond to amino acid synthesis modules on the host-symbiont joint pathway map. Process in the following order: first, among KEGG's host-symbiont examples, select those combinations whose bacterial symbiont KEGG GENOME entry has a Created year on or before 2005; then retain cases where the bacterial symbiont genome carries named extra replicons; next, verify that the replicon names directly correspond to amino acid synthesis modules on the host-symbiont joint pathway map; finally, within the joint pathway map for that host-symbiont combination, list all qualifying pathway-module pairs for that case and output a single-line string: ||||| (sorted by pathway ID in ascending order, separated by commas; output NONE if no qualifying items exist).","start_url":"https://www.genome.jp/kegg/genome/","output_format":"Output a single-line string: ||||| (sorted by pathway ID in ascending order, separated by commas; output NONE if no qualifying items exist).","oracle_answer":"api+buc|buc|00290|M00432|pLeu|2000,api+buc|buc|00400|M00023|pTrp|2000","metadata":{"State-Gated Retrieval":["Retain only those host-symbiont examples where the bacterial symbiont KEGG GENOME Created year is on or before 2005 and the genome carries named extra replicons.","The replicon names must directly correspond to amino acid synthesis modules on the host-symbiont joint pathway page.","Finally, output all qualifying pathway-module-replicon records from the surviving case, sorted by pathway ID in ascending order."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["KEGG host-symbiont examples and symbiont genome pages yield the pre-2006 candidate pairs and named extra replicons","Joint pathway maps, module pages, and genome annotations yield the pathway-module-replicon links attributable to the symbiont side","Final rows are produced only after the surviving host-symbiont pair is validated against both replicon existence and module support on the joint pathway page"],"control_dependency":["Only branches satisfying the named-plasmid requirement may be retained, so the bmy+wbm branch must be excluded when the wbm genome page fails that requirement","Module retrieval must use the api+buc pathway state and the 00400 view, because that view is the one that actually exposes M00023","Module support is valid only after symbiont-side evidence for both M00023 and M00432 is validated in the selected pathway state"],"freeze":{"historical_window":"KEGG host-symbiont examples whose symbiont GENOME Created year is on or before 2005; current joint pathway, module, and genome replicon annotations"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Retain only those host-symbiont examples where the bacterial symbiont KEGG GENOME Created year is on or before 2005 and the genome carries named extra replicons.","The replicon names must directly correspond to amino acid synthesis modules on the host-symbiont joint pathway page.","Finally, output all qualifying pathway-module-replicon records from the surviving case, sorted by pathway ID in ascending order."],"exclusion_conditions":["Exclude cases like bmy+wbm where the symbiont genome page does not satisfy the named-plasmid requirement.","Exclude results that only follow pathway names along pages such as 00380 without returning to the joint pathway page to verify module evidence.","Exclude records where the relationship between replicon name and module cannot be directly established on the joint pathway map."],"normalization":{"field_separator":"|","record_separator":",","schema":["group","symbiont","pathway","module","replicon","created_year"],"group":"Use the canonical host-symbiont group label from the source workflow, such as `api+buc`","symbiont":"Use the bare lowercase KEGG organism code","pathway":"Emit the numeric KEGG pathway ID without a `map` prefix","module":"Normalize the KEGG module identifier to the `Mxxxxx` form","replicon":"Preserve the named extra replicon exactly as displayed in the source, such as `pLeu` or `pTrp`","created_year":"Emit the four-digit created year","sorting_or_selection":"Pathway numeric ascending"}}} +{"task_id":"genome_003","domain":"KEGG_BRITE","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"I am compiling a table of the approval order of systemic drugs for plaque psoriasis in Japan. Process as follows: first, within the scope of systemic drugs for plaque psoriasis approved in Japan by the end of 2024, identify the active ingredients that act on the IL-17/IL-23 signaling axis; then exclude all topical drugs and systemic drugs acting on other axes. Next, sort these active ingredients by their first approval date in Japan from earliest to latest; if approved on the same day, sort by DRUG_ID in ascending order. Finally, output a multi-row table with each row formatted as ||||.","start_url":"https://www.kegg.jp/brite/br08301","output_format":"Output a multi-row table with each row formatted as ||||.","oracle_answer":"D09967|Secukinumab|L04AC10|IL17A|2014/12/26\nD10061|Brodalumab|L04AC12|IL17RA|2016/7/4\nD10071|Ixekizumab|L04AC13|IL17A|2016/7/4\nD10438|Guselkumab|L04AC16|IL23A|2018/3/23\nD11052|Risankizumab|L04AC18|IL23A|2019/3/26\nD10400|Tildrakizumab|L04AC17|IL23A|2020/6/29\nD11550|Bimekizumab|L04AC21|IL17A/IL17F|2022/1/20\nD11817|Deucravacitinib|L04AF07|TYK2|2022/9/26","metadata":{"State-Gated Retrieval":["Retain only the active ingredients that truly act on the IL-17/IL-23 signaling axis among systemic drugs for plaque psoriasis approved in Japan by 2024-12-31.","The candidate set must cover the ligand side, receptor side, and TYK2 kinase side, not just the interleukin ligand side.","Sort final entries by Japan first approval date in ascending order; if on the same day, sort by DRUG_ID in ascending order."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["KEGG disease/drug entry points yield the Japan-approved systemic plaque-psoriasis drug cohort through 2024-12-31","each drug entry yields target branch, ATC, systemic-use validity, and Japan approval date for IL-17/IL-23-axis candidates","final rows are produced only after ligand-side, receptor-side, and kinase-side candidates are jointly reconciled and re-sorted by Japan approval date"],"control_dependency":["entry-point coverage must include receptor-side IL17RA and kinase-side TYK2 mechanisms when downstream drug pages expose them, rather than staying ligand-only","Ustekinumab must be removed only when target interpretation shows IL12 + IL23A rather than the IL-17/IL-23-axis criterion required here","systemic-use, Japanese 3999, and PMDA-date filtering must be applied after each expansion of the candidate set rather than attached to the earlier ligand-only state"],"freeze":{"historical_window":"Japanese plaque-psoriasis systemic drugs approved on or before 2024-12-31; current KEGG drug-entry annotations supply target branches and Japan approval dates"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Retain only the active ingredients that truly act on the IL-17/IL-23 signaling axis among systemic drugs for plaque psoriasis approved in Japan by 2024-12-31.","The candidate set must cover the ligand side, receptor side, and TYK2 kinase side, not just the interleukin ligand side.","Sort final entries by Japan first approval date in ascending order; if on the same day, sort by DRUG_ID in ascending order."],"exclusion_conditions":["Exclude topical drugs, non-systemic drugs, or entries outside the specified historical freeze window.","Exclude entries such as Ustekinumab whose actual target is IL12 + IL23A and which do not meet the IL-17/IL-23 axis criterion required here.","Exclude results that miss Brodalumab or Deucravacitinib due to looking only at the ligand side."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["DRUG_ID","Name","ATC","Target_branch","PMDA_date"],"PMDA_date":"use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value","Target_branch":"emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`","sorting_or_selection":{"primary":"PMDA_date ascending","secondary":"DRUG_ID ascending"}}}} +{"task_id":"genome_004","domain":"KEGG_GENOME","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am preparing a handout for a primate evolution course and want to summarize, in a two-row comparison table, the anomalous pattern behind why this lineage must obtain vitamin C from the diet. Among primate genome entries established by the end of 2022, identify the anomalous lower-level clade in which the upstream glucuronate module M00014 is still retained but the animal-type vitamin C biosynthesis module M00129 has been lost. Then verify the corresponding sister branch and confirm that it still retains M00129. Finally, output a two-row comparison table with columns rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year. The first row should be EXCEPTION_CLADE and the second row RETAINED_SISTER_CLADE. In all rows, vitamin_c_synthesis_module is fixed as M00129; vitamin_c_module_status should be LOST for the first row and RETAINED for the second. Use KEGG organism codes for the example species.","start_url":"https://www.genome.jp/kegg/kegg2.html","output_format":"Output a two-row comparison table with columns rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year.","oracle_answer":"1|EXCEPTION_CLADE|Primates|Haplorrhini|map00053|map00040|M00014|M00129|LOST|csyr|2022\n2|RETAINED_SISTER_CLADE|Primates|Strepsirrhini|map00053|map00040|M00014|M00129|RETAINED|oga|2022","metadata":{"State-Gated Retrieval":["Search only among primate genome entries established by the end of 2022, and isolate the anomalous lower-level clade that retains the upstream glucuronate module M00014 but lacks the animal-type vitamin C biosynthesis module M00129.","That anomalous clade must be paired with a sister branch under the same higher-level split, and the sister branch must still retain M00129.","The final output must place the anomalous branch and the retained sister branch into a two-row comparison table, including the required pathway, module, and example-species fields."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the KEGG primate clade pages and genome entries yield candidate subclades and example species established through the cutoff year","the pathway and module views yield M00014 and M00129 presence/absence evidence for the exception clade and its sister branch","final rows are produced only after the exception clade and retained sister branch are jointly validated under the same parent split and paired with example organisms"],"control_dependency":["the exception clade remains provisional until both the sister-branch contrast and the example-species checks succeed","the comparison view must make retained M00014 and missing M00129 visible together","the two output rows are emitted together only after the exception clade and retained sister branch are fixed under the same parent split"],"freeze":{"historical_window":"primate genome entries established on or before 2022, with current KEGG clade, pathway, and module pages used as relatively stable reference information for comparing retained M00014 against lost M00129"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Search only among primate genome entries established by the end of 2022, and isolate the anomalous lower-level clade that retains the upstream glucuronate module M00014 but lacks the animal-type vitamin C biosynthesis module M00129.","That anomalous clade must have a contrastable sister branch, and that sister branch must still retain M00129.","The final output must place the anomalous branch and the retained sister branch into a two-row comparison table, including the required pathway, module, and example-species fields."],"exclusion_conditions":["Exclude results that stop at Simiiformes without checking the broader boundary and therefore miss Haplorrhini.","Exclude pathway views that do not make the M00014 versus M00129 contrast visible together.","Exclude candidate clades that have not been validated against a retained sister branch."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","clade_role","parent_clade","clade","anomaly_pathway","contrast_pathway","retained_upstream_module","vitamin_c_synthesis_module","vitamin_c_module_status","example_org","cutoff_year"],"rank":"emit 1 for EXCEPTION_CLADE and 2 for RETAINED_SISTER_CLADE","clade_role":["EXCEPTION_CLADE","RETAINED_SISTER_CLADE"],"pathway_normalization":"emit KEGG pathway ids with the map prefix","module_normalization":"emit KEGG module ids with the leading M","vitamin_c_module_status":["LOST","RETAINED"],"organism_code":"use bare KEGG organism codes in lowercase, not species names","cutoff_year":"use a four-digit year; this task is frozen at 2022","sorting_or_selection":"emit rows in the fixed order EXCEPTION_CLADE then RETAINED_SISTER_CLADE"}}} +{"task_id":"nvd_001","domain":"NVD","autonomy_type":"ordered table","instruction":"We are cleaning up a batch of old SBOM matching rules for the Duplicator product line. Some rules still rely on legacy vendor lineage and outdated product labeling, so we need to identify Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator but can still be traced back to snapcreek:duplicator in the deprecated vendor chain. Search NVD records for Duplicator-related CVEs published from 2018-01-01 through 2024-12-31. Retain only CVEs that satisfy all of the following conditions in Change History: the Initial Analysis is not yet lite or lite+pro; the first change to lite or lite+pro occurs in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurs on 2026-02-02. Exclude CVEs whose Initial Analysis already contained lite/lite+pro, as well as records that lack the required vendor-remap event or do not belong to the Duplicator product line. Finally, output a single-line ordered table with columns: CVE | lite_upper_version | lite_vs_lite+pro | analysis_event@date | snapcreek_to_awesomemotive@date.","start_url":"https://nvd.nist.gov/vuln/search#/nvd/home?resultType=records","output_format":"Output a single-line ordered table with columns: CVE | lite_upper_version | lite_vs_lite+pro | analysis_event@date | snapcreek_to_awesomemotive@date. Join rows with commas and sort by NVD published date ascending, then by CVE ascending.","oracle_output_cardinality":3,"oracle_answer":"CVE:2018-7543|1.2.32|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2018-17207|1.2.42|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2020-11738|1.3.28|lite+pro|ModifiedAnalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02","metadata":{"State-Gated Retrieval":["Retain only Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator and that can be traced back to snapcreek:duplicator in the deprecated old vendor chain.","Each candidate CVE must simultaneously satisfy the following in its Change History: the Initial Analysis is not yet lite/lite+pro; the first change to lite or lite+pro occurs in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurs on 2026-02-02.","The final output retains only CVE rows that satisfy all three conditions above."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["NVD product/CPE search pages yield the current awesomemotive:duplicator family and the deprecated snapcreek:duplicator lineage","each target CVE detail page and Change History yield the Initial Analysis state, the first lite/lite+pro analysis event, and the 2026-02-02 vendor-remap event","final rows are produced only after candidate CVEs are intersected on both snapcreek -> awesomemotive migration and later introduction of lite/lite+pro in NIST analysis history"],"control_dependency":["the search must include the deprecated snapcreek lineage rather than only the current product state","vendor migration alone is insufficient until detail-level history confirms that lite/lite+pro was introduced after Initial Analysis","candidate CVEs must be filtered against the full change-history chronology, excluding any whose Initial Analysis already contained lite"],"freeze":{"historical_window":"Duplicator CVEs published from 2018-01-01 through 2024-12-31, evaluated against NVD analysis history up to the 2026-02-02 snapcreek -> awesomemotive vendor-remap events"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Retain only Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator and that can be traced back to snapcreek:duplicator in the deprecated old vendor chain.","Each candidate CVE must simultaneously satisfy the following in its Change History: the Initial Analysis is not yet lite/lite+pro; the first change to lite or lite+pro occurs in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurs on 2026-02-02.","The final output retains only CVE rows that satisfy all three conditions above."],"exclusion_conditions":["Exclude results that only look at the current description or current product state without falling back to the deprecated snapcreek chain and Change History.","Exclude CVEs whose Initial Analysis was already lite/lite+pro.","Exclude records without a 2026-02-02 vendor remap, or that do not belong to the Duplicator product line."],"normalization":{"field_separator":"|","record_separator":",","schema_note":"the checked oracle rowset uses the Duplicator CVE schema below, and normalization follows that verified schema throughout this task","schema":["CVE","lite_upper_version","lite_vs_lite+pro","analysis_event@date","snapcreek_to_awesomemotive@date"],"CVE":"emit the identifier in the canonical `CVE:YYYY-NNNN` form used by the oracle","lite_vs_lite+pro":"emit `lite` or `lite+pro` exactly","analysis_event@date":"emit `Reanalysis@YYYY-MM-DD` or `ModifiedAnalysis@YYYY-MM-DD` exactly as supported by the source record","snapcreek_to_awesomemotive@date":"emit the ownership-transfer event as `snapcreek->awesomemotive@YYYY-MM-DD`","sorting_or_selection":{"primary":"NVD published date ascending","secondary":"CVE ascending"}}}} +{"task_id":"nvd_002","instruction":"Identify which CPE 2.3 product identifiers using the legacy vendor name mysql:mysql within the MySQL 5.1 branch were explicitly migrated by NIST to the corresponding oracle:mysql CPE 2.3 product identifiers in the NVD (National Vulnerability Database) records for the four InnoDB denial-of-service vulnerabilities CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680. Migration here refers only to the vendor field in the CPE changing from the old vendor mysql to the new vendor oracle; it does not include cases where the identifier remains under the old vendor name and only version aliases are normalized. Retain only entries from the MySQL 5.1 branch that meet this criterion. Exclude entries from the MySQL 5.0 branch, as well as all entries that did not undergo a vendor migration and only had internal version-alias normalization under the old vendor. Output a multi-row ordered table with columns version_update | legacy_cpe | current_cpe | remap_time_nvd, sorted by numeric version in ascending order; within the same version, entries without an update suffix come before entries with an update suffix.","domain":"NVD","autonomy_type":"ordered table","oracle_output_cardinality":44,"start_url":"https://nvd.nist.gov/products/cpe/search","output_format":"Output a multi-row ordered table with columns version_update | legacy_cpe | current_cpe | remap_time_nvd, sorted by numeric version in ascending order; within the same version, entries without an update suffix come before entries with an update suffix.","oracle_answer":"version_update|legacy_cpe|current_cpe|remap_time_nvd\n5.1.1|cpe:2.3:a:mysql:mysql:5.1.1:::::::*|cpe:2.3:a:oracle:mysql:5.1.1:::::::*|2019-12-17 15:04:33\n5.1.2|cpe:2.3:a:mysql:mysql:5.1.2:::::::*|cpe:2.3:a:oracle:mysql:5.1.2:::::::*|2019-12-17 15:04:39\n5.1.3|cpe:2.3:a:mysql:mysql:5.1.3:::::::*|cpe:2.3:a:oracle:mysql:5.1.3:::::::*|2019-12-17 15:04:46\n5.1.4|cpe:2.3:a:mysql:mysql:5.1.4:::::::*|cpe:2.3:a:oracle:mysql:5.1.4:::::::*|2019-12-17 15:04:53\n5.1.10|cpe:2.3:a:mysql:mysql:5.1.10:::::::*|cpe:2.3:a:oracle:mysql:5.1.10:::::::*|2019-12-17 15:05:30\n5.1.11|cpe:2.3:a:mysql:mysql:5.1.11:::::::*|cpe:2.3:a:oracle:mysql:5.1.11:::::::*|2019-12-17 15:05:37\n5.1.12|cpe:2.3:a:mysql:mysql:5.1.12:::::::*|cpe:2.3:a:oracle:mysql:5.1.12:::::::*|2019-12-17 15:05:45\n5.1.13|cpe:2.3:a:mysql:mysql:5.1.13:::::::*|cpe:2.3:a:oracle:mysql:5.1.13:::::::*|2019-12-17 15:05:52\n5.1.14|cpe:2.3:a:mysql:mysql:5.1.14:::::::*|cpe:2.3:a:oracle:mysql:5.1.14:::::::*|2019-12-17 15:05:59\n5.1.15|cpe:2.3:a:mysql:mysql:5.1.15:::::::*|cpe:2.3:a:oracle:mysql:5.1.15:::::::*|2019-12-17 15:06:07\n5.1.16|cpe:2.3:a:mysql:mysql:5.1.16:::::::*|cpe:2.3:a:oracle:mysql:5.1.16:::::::*|2019-12-17 15:06:14\n5.1.17|cpe:2.3:a:mysql:mysql:5.1.17:::::::*|cpe:2.3:a:oracle:mysql:5.1.17:::::::*|2019-12-17 15:06:21\n5.1.18|cpe:2.3:a:mysql:mysql:5.1.18:::::::*|cpe:2.3:a:oracle:mysql:5.1.18:::::::*|2019-12-17 15:06:27\n5.1.19|cpe:2.3:a:mysql:mysql:5.1.19:::::::*|cpe:2.3:a:oracle:mysql:5.1.19:::::::*|2019-12-17 15:06:34\n5.1.20|cpe:2.3:a:mysql:mysql:5.1.20:::::::*|cpe:2.3:a:oracle:mysql:5.1.20:::::::*|2019-12-17 15:06:42\n5.1.21|cpe:2.3:a:mysql:mysql:5.1.21:::::::*|cpe:2.3:a:oracle:mysql:5.1.21:::::::*|2019-12-17 15:06:50\n5.1.22|cpe:2.3:a:mysql:mysql:5.1.22:::::::*|cpe:2.3:a:oracle:mysql:5.1.22:::::::*|2019-12-17 15:06:56\n5.1.23:a|cpe:2.3:a:mysql:mysql:5.1.23:a::::::|cpe:2.3:a:oracle:mysql:5.1.23:a::::::|2019-12-17 15:23:28\n5.1.24|cpe:2.3:a:mysql:mysql:5.1.24:::::::*|cpe:2.3:a:oracle:mysql:5.1.24:::::::*|2019-12-17 15:07:03\n5.1.25|cpe:2.3:a:mysql:mysql:5.1.25:::::::*|cpe:2.3:a:oracle:mysql:5.1.25:::::::*|2019-12-17 15:07:10\n5.1.26|cpe:2.3:a:mysql:mysql:5.1.26:::::::*|cpe:2.3:a:oracle:mysql:5.1.26:::::::*|2019-12-17 15:07:17\n5.1.27|cpe:2.3:a:mysql:mysql:5.1.27:::::::*|cpe:2.3:a:oracle:mysql:5.1.27:::::::*|2019-12-17 15:07:24\n5.1.28|cpe:2.3:a:mysql:mysql:5.1.28:::::::*|cpe:2.3:a:oracle:mysql:5.1.28:::::::*|2019-12-17 15:07:31\n5.1.29|cpe:2.3:a:mysql:mysql:5.1.29:::::::*|cpe:2.3:a:oracle:mysql:5.1.29:::::::*|2019-12-17 15:07:38\n5.1.30|cpe:2.3:a:mysql:mysql:5.1.30:::::::*|cpe:2.3:a:oracle:mysql:5.1.30:::::::*|2019-12-17 15:07:46\n5.1.31:sp1|cpe:2.3:a:mysql:mysql:5.1.31:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.31:sp1::::::|2019-12-17 15:23:35\n5.1.33|cpe:2.3:a:mysql:mysql:5.1.33:::::::*|cpe:2.3:a:oracle:mysql:5.1.33:::::::*|2019-12-17 15:07:55\n5.1.34:sp1|cpe:2.3:a:mysql:mysql:5.1.34:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.34:sp1::::::|2019-12-17 15:23:42\n5.1.35|cpe:2.3:a:mysql:mysql:5.1.35:::::::*|cpe:2.3:a:oracle:mysql:5.1.35:::::::*|2019-12-17 15:08:03\n5.1.36|cpe:2.3:a:mysql:mysql:5.1.36:::::::*|cpe:2.3:a:oracle:mysql:5.1.36:::::::*|2019-12-17 15:08:10\n5.1.37:sp1|cpe:2.3:a:mysql:mysql:5.1.37:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.37:sp1::::::|2019-12-17 15:23:49\n5.1.38|cpe:2.3:a:mysql:mysql:5.1.38:::::::*|cpe:2.3:a:oracle:mysql:5.1.38:::::::*|2019-12-17 15:08:17\n5.1.39|cpe:2.3:a:mysql:mysql:5.1.39:::::::*|cpe:2.3:a:oracle:mysql:5.1.39:::::::*|2019-12-17 10:22:31\n5.1.40|cpe:2.3:a:mysql:mysql:5.1.40:::::::*|cpe:2.3:a:oracle:mysql:5.1.40:::::::*|2019-12-17 10:22:46\n5.1.40:sp1|cpe:2.3:a:mysql:mysql:5.1.40:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.40:sp1::::::|2019-12-17 10:22:39\n5.1.41|cpe:2.3:a:mysql:mysql:5.1.41:::::::*|cpe:2.3:a:oracle:mysql:5.1.41:::::::*|2019-12-17 10:22:52\n5.1.42|cpe:2.3:a:mysql:mysql:5.1.42:::::::*|cpe:2.3:a:oracle:mysql:5.1.42:::::::*|2019-12-17 10:22:59\n5.1.43|cpe:2.3:a:mysql:mysql:5.1.43:::::::*|cpe:2.3:a:oracle:mysql:5.1.43:::::::*|2019-12-17 10:23:06\n5.1.43:sp1|cpe:2.3:a:mysql:mysql:5.1.43:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.43:sp1::::::|2019-12-17 10:23:11\n5.1.44|cpe:2.3:a:mysql:mysql:5.1.44:::::::*|cpe:2.3:a:oracle:mysql:5.1.44:::::::*|2019-12-17 10:23:17\n5.1.45|cpe:2.3:a:mysql:mysql:5.1.45:::::::*|cpe:2.3:a:oracle:mysql:5.1.45:::::::*|2019-12-17 10:23:24\n5.1.46|cpe:2.3:a:mysql:mysql:5.1.46:::::::*|cpe:2.3:a:oracle:mysql:5.1.46:::::::*|2019-12-17 10:23:38\n5.1.46:sp1|cpe:2.3:a:mysql:mysql:5.1.46:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.46:sp1::::::|2019-12-17 10:23:31\n5.1.47|cpe:2.3:a:mysql:mysql:5.1.47:::::::*|cpe:2.3:a:oracle:mysql:5.1.47:::::::*|2019-12-17 10:23:45","metadata":{"State-Gated Retrieval":["Retain only CPE 2.3 entries from the MySQL 5.1 branch for which the NVD Change History of all four vulnerabilities CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680 clearly shows a mysql:mysql -> oracle:mysql vendor migration.","Every result must provide version_update, legacy_cpe, current_cpe, and remap_time_nvd.","Within the same version, entries without an update suffix come before entries with an update suffix, and output is sorted by numeric version in ascending order."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Current and deprecated MySQL 5.1 CPE search results yield candidate legacy/current CPE strings.","The four target CVE pages and their Change History entries yield vendor-migration evidence, exact version_update strings, and remap timestamps.","Final rows are produced only after taking the common mysql:mysql 5.1 -> oracle:mysql 5.1 migrations across all four CVEs and removing alias-only or 5.0 entries."],"control_dependency":["Legacy vendor mapping must be determined from Analysis Description plus Change History rather than from the current description/current CPE view.","Include-deprecated results cannot be accepted wholesale because alias-only remaps must be filtered out.","5.1-branch membership and sort order must be determined after the vendor-migration filter removes 5.0 and non-migration rows."],"freeze":{"historical_window":"The MySQL 5.1 branches visible in CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680, restricted to explicit mysql:mysql -> oracle:mysql vendor-migration events."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Retain only CPE 2.3 entries from the MySQL 5.1 branch for which the NVD Change History of all four vulnerabilities CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680 clearly shows a mysql:mysql -> oracle:mysql vendor migration.","Every result must provide version_update, legacy_cpe, current_cpe, and remap_time_nvd.","Within the same version, entries without an update suffix come before entries with an update suffix, and output is sorted by numeric version in ascending order."],"exclusion_conditions":["Exclude entries from the MySQL 5.0 branch.","Exclude entries that remain under the old vendor mysql:mysql, only have internal version-alias normalization, and did not undergo a vendor migration.","Exclude results that are read only from the current Oracle MySQL 5.1 CPE state without using legacy mapping and Change History."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"required literal first row `version_update|legacy_cpe|current_cpe|remap_time_nvd`","schema":["version_update","legacy_cpe","current_cpe","remap_time_nvd"],"version_update":"sort by numeric MySQL version ascending; within the same base version, the empty update comes before any non-empty update suffix","legacy_cpe":"preserve the exact legacy CPE 2.3 string","current_cpe":"preserve the exact current CPE 2.3 string","remap_time_nvd":"emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form","dedup_key":"(legacy_cpe, current_cpe)"}}} +{"task_id":"nvd_003","domain":"NVD","autonomy_type":"ordered table","instruction":"We are cleaning up a batch of old SBOM matching rules that still represent Apache Tomcat 9.0.0 pre-release milestone versions using the legacy CPE form 9.0.0.Mx. We need to identify which milestone versions satisfy both of the following conditions: (1) they appear in the current NVD affected-product version ranges for the four historical vulnerabilities CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797; and (2) the NVD change history shows that the CPE for these versions was remapped from the old short form (e.g., m1, m2) to the full form (e.g., milestone1, milestone2). Start from the Apache Tomcat 9.0.0 milestone versions, check each against the current NVD affected-product version ranges for these four CVEs, then examine the corresponding change history records. Retain only those milestone versions that satisfy both conditions. Exclude milestones that are included only because of other Tomcat 9.0.0 pre-release vulnerabilities, and do not include Tomcat 6, 7, 8, 8.5, or any non-Tomcat products. Finally, output an ordered multi-row table sorted by milestone number in ascending order, with columns: milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd.","start_url":"https://nvd.nist.gov/products/cpe/search","output_format":"Output as a Markdown multi-row table with fixed column names: milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd. Sort by milestone number in ascending order (M1, M2, ..., M9).","oracle_output_cardinality":9,"oracle_answer":"milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd\nM1|cpe:2.3:a:apache:tomcat:9.0.0:m1:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone1:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM2|cpe:2.3:a:apache:tomcat:9.0.0:m2:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone2:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM3|cpe:2.3:a:apache:tomcat:9.0.0:m3:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone3:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM4|cpe:2.3:a:apache:tomcat:9.0.0:m4:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone4:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM5|cpe:2.3:a:apache:tomcat:9.0.0:m5:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone5:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM6|cpe:2.3:a:apache:tomcat:9.0.0:m6:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone6:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM7|cpe:2.3:a:apache:tomcat:9.0.0:m7:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone7:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM8|cpe:2.3:a:apache:tomcat:9.0.0:m8:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone8:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM9|cpe:2.3:a:apache:tomcat:9.0.0:m9:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone9:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18","metadata":{"State-Gated Retrieval":["Retain only Apache Tomcat 9.0.0 milestone versions that appear in the current affected-product ranges for all four target CVEs: CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797.","These versions must also have a CPE Deprecation Remap from mN to milestoneN visible in the NVD Change History.","Finally, output sorted by milestone number in ascending order, and the required_cves field must list these four specific CVEs."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the current milestoneN CPE search and detail pages yield the Tomcat milestone family and the legacy mN mapping anchors","the four target CVE pages and Change History entries yield the exact mN -> milestoneN deprecation remaps and the required-CVE intersection","final rows are produced only after taking the remaps common to all four target CVEs and sorting by numeric milestone"],"control_dependency":["the candidate milestone set must be determined from the four-target-CVE intersection rather than from all prerelease Tomcat CVEs","later remapped milestones such as M10+ must be excluded by applying the specified four-CVE boundary","only explicit NVD CPE Deprecation Remap events from mN to milestoneN count, so generic Tomcat prerelease visibility cannot be accepted as evidence"],"freeze":{"historical_window":"the Tomcat 9.0.0 prerelease milestones jointly covered by CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797, with remap evidence fixed to the 2023-12-08 11:41:18 NVD deprecation events"},"answer_type":"multi-row ordered table"},"all_involved_urls":{"fixed_entry_and_docs":["https://nvd.nist.gov/products/cpe/search","https://nvd.nist.gov/vuln/vulnerability-detail-pages"],"cpe_search_result_pages":["https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL","https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED","https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20m&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED","https://nvd.nist.gov/products/cpe/search/results?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED"],"representative_cpe_detail_pages":["https://nvd.nist.gov/products/cpe/detail/615922?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED","https://nvd.nist.gov/products/cpe/detail/615947?keyword=cpe%3A2.3%3Aa%3Aapache&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED"],"row_level_cpe_api_urls_m1_to_m9":["https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone2%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone3%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone4%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone5%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone6%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone7%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone8%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone9%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A"],"target_cve_detail_pages":["https://nvd.nist.gov/vuln/detail/CVE-2016-5018","https://nvd.nist.gov/vuln/detail/CVE-2016-6794","https://nvd.nist.gov/vuln/detail/CVE-2016-6796","https://nvd.nist.gov/vuln/detail/CVE-2016-6797"],"negative_control_cve_detail_pages":["https://nvd.nist.gov/vuln/detail/CVE-2016-6816","https://nvd.nist.gov/vuln/detail/CVE-2016-6817","https://nvd.nist.gov/vuln/detail/CVE-2019-0221"],"cve_change_history_api":["https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-5018&eventName=CPE%20Deprecation%20Remap","https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6794&eventName=CPE%20Deprecation%20Remap","https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6796&eventName=CPE%20Deprecation%20Remap","https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6797&eventName=CPE%20Deprecation%20Remap","https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6816&eventName=CPE%20Deprecation%20Remap","https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6817&eventName=CPE%20Deprecation%20Remap","https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2019-0221&eventName=CPE%20Deprecation%20Remap"],"representative_change_record_pages":["https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=04%2F18%2F2022T13%3A57%3A03.500-0400","https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=08%2F24%2F2017T09%3A11%3A40.690-0400"]},"rubric":{"inclusion_conditions":["Retain only Apache Tomcat 9.0.0 milestone versions that appear in the current affected-product ranges for all four target CVEs: CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797.","These versions must also have a CPE Deprecation Remap from mN to milestoneN visible in the NVD Change History.","Finally, output sorted by milestone number in ascending order, and the required_cves field must list these four specific CVEs."],"exclusion_conditions":["Exclude milestones that are included only because of other Tomcat 9.0.0 pre-release vulnerabilities, such as M10/M11 and later milestones.","Exclude Tomcat 6, 7, 8, 8.5, or any non-Tomcat products.","Exclude records that lack explicit NVD remap evidence and are only visible on the current milestone page."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"required literal first row `milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd`","schema":["milestone","legacy_cpe","current_cpe","required_cves","remap_time_nvd"],"milestone":"emit the canonical milestone label `M1` through `M9` and sort by the numeric suffix ascending","legacy_cpe":"preserve the exact legacy CPE 2.3 string containing the short milestone token such as `m1`","current_cpe":"preserve the exact current CPE 2.3 string containing the full milestone token such as `milestone1`","required_cves":"emit the fixed literal `CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797`","remap_time_nvd":"emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form"}}} +{"task_id":"reptile_001","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"I am compiling a name concordance for early museum specimens of Indian snakes recorded in George A. Boulenger's 1890 work *The Fauna of British India, Including Ceylon and Burma*. Proceed as follows: first, using this specimen set as the scope, look up each corresponding current species page in the Reptile Database and retain only entries that simultaneously satisfy the following conditions: the species has since been reassigned to a different genus; the page still retains BMNH type specimen information; and the type locality still corresponds to India. For each qualifying entry, identify from the names listed on that page the oldest binomial that is closest to the present but has not yet been updated to the current genus name. Then, search again using this full old name and determine whether the search result points to only this single record. Finally, output the results as a single line sorted alphabetically by current accepted name, in the format |||; separate entries with semicolons. If no qualifying entries exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output the results as a single line sorted alphabetically by current accepted name, in the format |||; separate entries with semicolons. If no qualifying entries exist, output NONE.","oracle_answer":"Argyrophis oatesii|Typhlops oatesii|UNIQUE|SYNTYPES;Dendrelaphis grandoculis|Ahaetulla grandoculis|UNIQUE|LECTOTYPE;Fowlea sanctijohannis|Xenochrophis sanctijohannis|UNIQUE|HOLOTYPE;Gerrhopilus beddomii|Typhlops beddomii|UNIQUE|SYNTYPES;Hebius khasiensis|Amphiesma khasiense|UNIQUE|LECTOTYPE;Hebius parallelus|Amphiesma parallelum|AMBIG|LECTOTYPE;Indotyphlops jerdoni|Typhlops jerdoni|UNIQUE|SYNTYPES;Myriopholis blanfordii|Leptotyphlops blanfordi|AMBIG|SYNTYPES","metadata":{"State-Gated Retrieval":["Candidates must come from the historical museum entries of Indian snakes in Boulenger 1890 *Fauna of British India*.","The current Reptile Database species page must simultaneously satisfy: the species has been reassigned to a different genus; the page still retains BMNH type specimen information; the type locality still corresponds to India.","On each qualifying page, select the oldest binomial that is closest to the present but has not yet been updated to the current genus name, then perform an exact back-search using this old name and label it UNIQUE or AMBIG."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the Boulenger 1890 historical sample and current accepted-species pages yield candidates that changed genus while retaining BMNH type data and India-compatible type locality","each accepted page yields the nearest pre-current-genus old label, the BMNH type status, and the historical/type-locality evidence anchoring the entity","final rows are produced only after the old-label exact back-search is evaluated for uniqueness without losing the original entity anchor"],"control_dependency":["when an exact old-label back-search now hits multiple species, the original anchored entity must be kept and the uniqueness label must be set to AMBIG","once a candidate has passed the historical-cluster, genus-shift, BMNH, and India-locality gates, later old-label ambiguity can only rewrite the uniqueness field, not the entity itself","candidate anchoring must be preserved across the two-stage workflow so that old-label search noise does not redirect the accepted-species row"],"freeze":{"historical_window":"the George A. Boulenger 1890 British India sample, evaluated against current Reptile Database accepted pages, synonym labels, BMNH type data, and present type-locality text"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Candidates must come from the historical museum entries of Indian snakes in Boulenger 1890 *Fauna of British India*.","The current Reptile Database species page must simultaneously satisfy: the species has been reassigned to a different genus; the page still retains BMNH type specimen information; the type locality still corresponds to India.","On each qualifying page, select the oldest binomial that is closest to the present but has not yet been updated to the current genus name, then perform an exact back-search using this old name and label it UNIQUE or AMBIG."],"exclusion_conditions":["Exclude entries where the current accepted name has not undergone a genus change, or where the page no longer retains BMNH type specimen information.","Exclude entries whose type locality does not correspond to India.","Do not discard candidates whose exact old-name back-search is non-unique; such candidates should be retained and labeled AMBIG."],"normalization":{"field_separator":"|","record_separator":";","schema":["accepted name","old label","UNIQUE/AMBIG","BMNH status"],"accepted_name":"emit the current accepted binomial exactly as shown in the reconciled source","old_label":"preserve the historical label exactly as used on the legacy branch","UNIQUE/AMBIG":"emit `UNIQUE` or `AMBIG` in uppercase","BMNH_status":"normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or SYNTYPES","sorting_or_selection":"accepted name alphabetical ascending"}}} +{"task_id":"reptile_002","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am compiling current name correspondences for early museum specimens of Southeast Asian Lygosoma. The old labels correspond to Riopa combinations attributed to Smith (1935/1937) in the Synonym section of each species page, but some of these old names now map to multiple current species under the current classification. Process as follows: first, within the current Lygosoma checklist, examine each current species page and locate these Smith (1935/1937) Riopa combinations in the Synonym section; then compare these old names, identify those that point to multiple current species, and list all involved current species. Next, for each qualifying current species, record the first-listed type specimen number, type category, and the region ultimately corresponding to the type locality on that page. Finally, output the results as a single line with entries sorted alphabetically by current accepted name, in the format ||||; separate entries with semicolons; if no qualifying entries exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output the results as a single line with entries sorted alphabetically by current accepted name, in the format ||||; separate entries with semicolons; if no qualifying entries exist, output NONE.","oracle_answer":"Lygosoma bampfyldei|Riopa bampfyldei|BMNH 1946.8.10.84|SYNTYPES|East Malaysia;Lygosoma peninsulare|Riopa bampfyldei|LSUHC 13857|HOLOTYPE|Peninsular Malaysia;Lygosoma schneideri|Riopa bampfyldei|NMBA 4743|HOLOTYPE|Indonesia","metadata":{"State-Gated Retrieval":["Retain only those accepted species that can be traced from the Smith 1937 old-name chain to a current Lygosoma record and for which the type accession, type status, and locality can be read on the current page.","For each accepted record, output the accepted name, the corresponding old label, the type accession, the type status, and the locality.","If the same exact old name is attached to multiple accepted species, retain them as separate chains."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the Smith 1937 old-name chain yields the three current Lygosoma accepted pages connected to Riopa bampfyldei / Lygosoma bampfyldei","each accepted page yields its own type accession, type status, and type locality needed to separate the homonymous old-name paths","final rows are produced only after the one-to-many old-name split is rebuilt and the three paths are re-anchored to their own type evidence"],"control_dependency":["same-specific-epithet matching cannot establish a one-to-one mapping when the same Smith 1937 old name appears on multiple accepted pages","once literal old-name reuse is exposed, the workflow must keep the original parallel three-chain state rather than collapsing to a one-to-one mapping","type accession and locality evidence must be read separately for each chain rather than patched onto the first stopping page"],"freeze":{"historical_window":"the current Reptile Database accepted pages linked to the Smith 1937 old-name cluster around Riopa bampfyldei, using current type accessions, statuses, and localities"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Retain only those accepted species that can be traced from the Smith 1937 old-name chain to a current Lygosoma record and for which the type accession, type status, and locality can be read on the current page.","For each accepted record, output the accepted name, the corresponding old label, the type accession, the type status, and the locality.","If the same exact old name is attached to multiple accepted species, retain them as separate chains."],"exclusion_conditions":["Exclude results that assume the same species based solely on the old name and current specific epithet being identical.","Exclude results that retain only the first chain after discovering the same exact old name on multiple accepted pages.","Exclude results that do not return to each accepted page to re-verify the type accession and locality."],"normalization":{"field_separator":"|","record_separator":";","schema":["accepted","Smith-era Riopa label","first type code","type status","region"],"accepted":"emit the current accepted binomial exactly as shown in the reconciled source","Smith-era_Riopa_label":"preserve the Smith-era Riopa label exactly as used on the legacy branch","first_type_code":"emit the first accession code that follows the selected type-status statement","type_status":"normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES","region":"emit the modern geographic region label from the source reconciliation, such as East Malaysia or Peninsular Malaysia","sorting_or_selection":"accepted name alphabetical ascending"}}} +{"task_id":"reptile_003","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":10,"instruction":"I am organizing current-name cross-references for a batch of early museum catalog cards that were still filed under Mabuya or Mabuia around 1980, and need to map them into the current Eutropis checklist. Process as follows: first, examine each species page in the current Eutropis checklist one by one, and on each page identify the first synonym label that is both in Mabuya or Mabuia form and tagged with the 1980 citation year. Then, perform an exact name search using that 1980 old label, and retain only those species for which the back-search result points to more than one current Eutropis entry. For each qualifying entry, record its current accepted name, the 1980 old label, the qualifier annotation for that old label on the page, and the first type category and code listed on the current page. Finally, output a single line per entry in the format |<1980 label>|||, sorted alphabetically by old label and, within the same old label, by accepted name. Join entries with semicolons. If no qualifying entries exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output a single line per entry in the format |<1980 label>|||, sorted alphabetically by old label and, within the same old label, by accepted name. Join entries with semicolons. If no qualifying entries exist, output NONE.","oracle_answer":"Eutropis indeprensa|Mabuya indeprensa|NONE|HOLOTYPE|CAS 85664;Eutropis sahulinghangganan|Mabuya indeprensa|PART-MISID|HOLOTYPE|PNM 9867;Eutropis multifasciata|Mabuya multifasciata|NONE|NEOTYPE|MZB 11912;Eutropis multicarinata|Mabuya multicarinata|NONE|HOLOTYPE|BMNH 1946.8.15.13-15;Eutropis borealis|Mabuya multicarinata borealis|NONE|HOLOTYPE|CAS 15447;Eutropis islamaliit|Mabuya multicarinata borealis|PART-MISID|HOLOTYPE|PNM 9847;Eutropis caraga|Mabuya multicarinata multicarinata|PART-MISID|HOLOTYPE|PNM 9845;Eutropis palauensis|Mabuya multicarinata multicarinata|PART-BYIMPL|HOLOTYPE|CAS 248251;Eutropis dattaroyi|Mabuya rudis|PART|HOLOTYPE|ZSI 25118;Eutropis rudis|Mabuya rudis|NONE|LECTOTYPE|BMNH 1946.8.15.26","metadata":{"State-Gated Retrieval":["Retain only those current Eutropis accepted species for which the synonym block contains, scanning top-down, a first synonym label that begins with Mabuya or Mabuia and has the year 1980.","Then, perform an exact name search using that 1980 old label, and output the accepted name, old label, back-search qualifier, type status, and type specimen.","If the subsequent back-search reveals additional matching entries, revisit the earlier results and include them in the final output."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["current Eutropis detail pages yield the first 1980-tagged Mabuya/Mabuia synonym label for each accepted species","exact back-search on that 1980 old label yields the present accepted page, type status, and type specimen needed for the output row","final rows are produced only after the 1980-specific old-label anchor is rebuilt and the accepted-species set is expanded when back-search evidence reveals omitted entries"],"control_dependency":["the workflow must identify the first Mabuya/Mabuia label carrying the 1980 year rather than stopping at the first old label on the page","when old-label back-search reveals missing entries such as Eutropis dattaroyi, the accepted-species set must be expanded to include them rather than patched in place","accepted-page synonym parsing and back-search interpretation must stay coupled so that 1980 labels are not replaced by older but irrelevant names"],"freeze":{"historical_window":"current Reptile Database Eutropis pages, restricted to the first synonym label that is both Mabuya/Mabuia-form and tagged with the 1980 citation year"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Retain only those current Eutropis accepted species for which the synonym block contains, scanning top-down, a first synonym label that begins with Mabuya or Mabuia and has the year 1980.","Then, perform an exact name search using that 1980 old label, and output the accepted name, old label, back-search qualifier, type status, and type specimen.","If the subsequent back-search reveals additional matching entries, revisit the earlier results and include them in the final output."],"exclusion_conditions":["Exclude results that mistakenly treat the first old name on the page as the first 1980 old label.","Exclude results whose exact back-search on the 1980 old label points to only a single current Eutropis entry.","Exclude results that, when subsequent evidence reveals omitted entries, do not revisit the earlier results and rebuild the accepted-species set."],"normalization":{"field_separator":"|","record_separator":";","schema":["accepted","1980 label","qualifier","type status","first type code"],"accepted":"emit the current accepted binomial exactly as shown in the reconciled source","1980_label":"preserve the 1980-era label exactly as used on the legacy branch","qualifier":"normalize to one of `NONE`, `PART`, `PART-MISID`, or `PART-BYIMPL`","type_status":"normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES","first_type_code":"emit the first accession code that follows the selected type-status statement","sorting_or_selection":{"primary":"1980 label alphabetical ascending","secondary":"accepted name alphabetical ascending"}}}} +{"task_id":"reptile_004","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":6,"instruction":"I am organizing a batch of early museum catalog cards for half-toed geckos that still use the old labels listed in the comments section of the Hemidactylus brookii species page. Process as follows: first examine the old labels listed in the comments section of the current Hemidactylus brookii species page, and select those that are no longer placed in Hemidactylus brookii and for which the database has clearly provided their current assignment. Then, for each qualifying label, determine the current species it should ultimately be assigned to; if merging from that label to the current species must pass through an intermediate old name, write that intermediate name, otherwise write DIRECT. At the same time, record the type status, type code, and the country of the type locality for that label itself. Finally, output a single line with entries sorted alphabetically by legacy label: |||||; separate entries with semicolons; if no qualifying entries exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output a single line with entries sorted alphabetically by legacy label: |||||; separate entries with semicolons; if no qualifying entries exist, output NONE.","oracle_answer":"Hemidactylus brooki leightoni|Hemidactylus angulatus|DIRECT|HOLOTYPE|BMNH 1946.8.25.65|Colombia;Hemidactylus brookii haitianus|Hemidactylus angulatus|DIRECT|LECTOTYPE|ZMH R22378|Haiti;Hemidactylus brookii parvimaculatus|Hemidactylus parvimaculatus|DIRECT|HOLOTYPE|NMSL No. RG. 15|Sri Lanka;Hemidactylus brookii subtriedroides|Hemidactylus murrayi|Hemidactylus tenkatei|LECTOTYPE|BMNH [subtriedroides] [tenkatei]|Myanmar;Hemidactylus gleadowi|Hemidactylus gleadowi|DIRECT|NEOTYPE|BMNH 1884.7.25.8|Pakistan;Hemidactylus tenkatei|Hemidactylus murrayi|DIRECT|LECTOTYPE|RMNH 4353|Indonesia","metadata":{"State-Gated Retrieval":["Each result must start from the old-label chain specified in the task and ultimately determine the accepted name, bridge status, type status, type accession, and locality from the current accepted page.","For the subtriedroides branch, continue along tenkatei to murrayi, output the final accepted name as Hemidactylus murrayi, and retain bridge=Hemidactylus tenkatei.","For branches such as haitianus and leightoni, read their own locality/type lines rather than borrowing header information from the wrong page."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["The old-label chains from Hemidactylus angulatus and related names yield accepted pages, bridge names, and the type/locality lines for each path.","Comment, Types, and type-comment blocks yield the later evidence that tenkatei is further sunk into H. murrayi.","Final rows are produced only after each old-label path is re-anchored to its own locality/type line and the subtriedroides -> tenkatei -> murrayi bridge chain is completed."],"control_dependency":["Type data must be taken from the locality/type line belonging to the actual old-label branch rather than from the header block of the wrong accepted page.","Stopping at the intermediate tenkatei bridge is insufficient; the workflow must continue to the later murrayi evidence and rewrite both tenkatei and subtriedroides final accepted names.","Bridge labels remain useful, but final accepted names and type lines must be determined from the deeper synonym chain."],"freeze":{"historical_window":"Current Reptile Database pages for the Hemidactylus angulatus / brookii / murrayi complex, using present locality, type, comment, and type-comment blocks."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Each result must start from the old-label chain specified in the task and ultimately determine the accepted name, bridge status, type status, type accession, and locality from the current accepted page.","For the subtriedroides branch, continue along tenkatei to murrayi, output the final accepted name as Hemidactylus murrayi, and retain bridge=Hemidactylus tenkatei.","For branches such as haitianus and leightoni, read their own locality/type lines rather than borrowing header information from the wrong page."],"exclusion_conditions":["Exclude results that follow the wrong page hierarchy and apply the Holotype/locality from the H. angulatus page header to other branches.","Exclude results that stop early on the subtriedroides -> tenkatei chain without continuing to read the murrayi evidence.","Exclude results that fail to align the locality/type line with each specific old-label branch."],"normalization":{"field_separator":"|","record_separator":";","schema":["legacy label","accepted","bridge","type status","type code","country"],"legacy_label":"Preserve the legacy label exactly as used on the source branch.","accepted":"Emit the current accepted binomial exactly as shown in the reconciled source.","bridge":"Emit `DIRECT` when no intermediate legacy bridge name is needed; otherwise emit the intermediate legacy name that links the branches.","type_status":"Normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or NEOTYPE.","type_code":"Take the type accession from the legacy-label branch rather than from a generic type line elsewhere on the page.","country":"Emit the modern English country name from the reconciled source branch.","sorting_or_selection":"Legacy label alphabetical ascending."}}} +{"task_id":"reptile_005","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am checking a synonymization record in the current Naja species list that involves an early Sri Lankan museum name, and I want to organize the key information from the accepted side and the contested-name side into a two-row comparison table. First, in the current Naja list, locate the contested-name record associated with Sri Lanka. Then verify its recent-use evidence, the database's final treatment, the correction concerning lectotype assignment, the restricted type locality, and the holotype information for the contested name itself. Finally, output a two-row comparison table with columns rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note. Row 1 should be ACCEPTED_NAME and give the accepted name, final status, valid lectotype, and restricted type locality. Row 2 should be CONTESTED_NAME and give the contested name, recent-use evidence, holotype, and the corrected invalid lectotype claim.","start_url":"https://reptile-database.reptarium.cz/advanced_search?genus=Naja&submit=Search","output_format":"Output a two-row comparison table with columns rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note.","oracle_answer":"1|ACCEPTED_NAME|Naja naja|SUBJECTIVE_JUNIOR_SYNONYM_OF_NAJA_NAJA|VALID_LECTOTYPE|ZMB 2796|restricted type locality: Sri Lanka\n2|CONTESTED_NAME|Naja polyocellata|SHI et al. 2022+SILVA et al. 2023|HOLOTYPE|BMNH 1946.1.18.50|invalid lectotype claim: NRM (= NHR) Lin-90","metadata":{"State-Gated Retrieval":["Within the current Naja list, identify the Sri Lanka contested-name branch: the name was recently reused as a distinct valid name, but the database now explicitly merges it back into the accepted name.","On the current Naja naja page, read the recent-use evidence, final synonym status, lectotype correction, restricted type locality, and the holotype information for the contested name itself.","The final output must organize the ACCEPTED_NAME side and the CONTESTED_NAME side into a two-row comparison table."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the current Naja species list and the Naja naja page yield the Sri Lanka contested-name branch, recent-use citations, and the accepted-name context","comment, Types, and type-comment blocks yield the final synonym treatment plus the valid and invalid lectotype assignments and the contested-name holotype","final rows are produced only after the accepted-name side and the contested-name side are reconciled on the current Naja naja page"],"control_dependency":["recent-use evidence for Naja polyocellata must be interpreted together with the current final synonym treatment shown on that page","lectotype status must be fixed from the combined Types and type-comment evidence rather than from a single provisional assignment","the accepted-name and contested-name rows are emitted together only after final status, type locality, and specimen roles are fixed"],"freeze":{"historical_window":"the objectively existing taxa in the Sri Lanka Naja branch, using current Reptile Database comment, Types, and type-comment blocks as nearly objective and highly stable reference information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Within the current Naja list, identify the Sri Lanka contested-name record: the name was recently reused in the literature as a distinct valid name, but the database now explicitly states that it should still be merged into the accepted name.","On the current Naja naja page, the result must jointly recover the recent-use evidence, final synonym status, lectotype correction, restricted type locality, and the holotype information for the contested name itself.","The final output must organize the ACCEPTED_NAME side and the CONTESTED_NAME side into a two-row comparison table."],"exclusion_conditions":["Exclude results that treat the recently revived contested name as the current accepted name.","Exclude results that stop at the Wallach 2014 lectotype designation and do not continue to the later comment and type-comment correction.","Exclude results that fail to output both the restricted type locality and the contested-name holotype."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","name_role","name","status_or_evidence","specimen_role","specimen_code","supporting_note"],"rank":"emit 1 for ACCEPTED_NAME and 2 for CONTESTED_NAME","name_role":["ACCEPTED_NAME","CONTESTED_NAME"],"name_fields":"use the current binomial spellings exactly","specimen_code_normalization":"preserve museum abbreviations, spaces, parentheses, and specimen punctuation exactly as the page shows","sorting_or_selection":"emit rows in the fixed order ACCEPTED_NAME then CONTESTED_NAME"}}} +{"task_id":"wateroffice_001","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am compiling historical daily flow comparison data for the Saint John River spring freshet period and want to determine, along the mainstem, which station in the current monitoring network is the last one that still allows daily flow comparisons for March–April 1973 and March–April 2018, and which mainstem station downstream of it is the first one that no longer satisfies that condition. First, use the current monitoring network shown on the Wateroffice real-time page as of April 16, 2026, and retain only stations on the Saint John River mainstem. Then, for each station, check the historical availability page, distinguish Flow Data Availability from Daily Water Level Data Availability, and determine whether March–April 1973 and March–April 2018 both have complete daily flow records. If the target windows satisfy the complete daily flow condition, set target_window_status to PASS and final_verdict to KEEP. If the target years have only water level records and no daily flow records, set target_window_status to LEVEL_ONLY and final_verdict to REJECT. If daily flow records exist but any target month in March–April 1973 or March–April 2018 is missing or incomplete, set target_window_status to FLOW_GAP and final_verdict to REJECT. Finally, output a two-row breakpoint table with columns rank|station_number|breakpoint_role|target_window_status|final_verdict. In the first row, give the last usable station and set breakpoint_role to LAST_USABLE. In the second row, give the first failing station encountered downstream and set breakpoint_role to FIRST_DOWNSTREAM_FAIL.","start_url":"https://wateroffice.ec.gc.ca/search/real_time_e.html","output_format":"Output a two-row breakpoint table with columns rank|station_number|breakpoint_role|target_window_status|final_verdict.","oracle_answer":"1|01AF002|LAST_USABLE|PASS|KEEP\n2|01AK003|FIRST_DOWNSTREAM_FAIL|LEVEL_ONLY|REJECT","metadata":{"State-Gated Retrieval":["Determine the last station still usable for the target historical-window comparison only within the Saint John River mainstem stations in the current monitoring network.","On the historical availability page, Flow Data Availability must be distinguished from Daily Water Level Data Availability, and completeness for March–April 1973 and March–April 2018 must be checked.","The final output must provide both breakpoint rows, LAST_USABLE and FIRST_DOWNSTREAM_FAIL, under the same validation rule."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the current Saint John River mainstem station sequence provides the downstream order in which the breakpoints must be checked","per-station historical availability pages yield Flow Data Availability, Daily Water Level Data Availability, and target-month completeness for 1973 and 2018","the final breakpoint rows are produced only after the availability-page checks identify the last usable station and the first downstream failure under the same rule"],"control_dependency":["the breakpoint pair must be determined from historical availability that distinguishes flow from level-only evidence","target-year/month completeness must be checked on the availability page rather than inferred from the station list","the second row is emitted only after the first downstream failing mainstem station is fixed under the same validation rule"],"freeze":{"historical_window":"mainstem candidate stations evaluated by historical daily availability, with the target completeness rule applied to the specified 1973 and 2018 March/April windows"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Search for the final station only within the mainstem station set specified in the task, and continue downstream along the mainstem to identify the first station after it that no longer meets the condition.","The historical daily availability page must distinguish Flow Data Availability from Daily Water Level Data Availability, and must verify the completeness of the required March–April windows for 1973 and 2018.","The final output must provide both breakpoint rows, LAST_USABLE and FIRST_DOWNSTREAM_FAIL, under the same validation rule."],"exclusion_conditions":["Exclude results that rely only on the current Saint John River mainstem station sequence and directly take the most downstream station by reference index.","Exclude results that mistakenly treat level-only evidence as satisfying the flow condition.","Exclude results that do not check each station's availability page to verify target-month completeness."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","station_number","breakpoint_role","target_window_status","final_verdict"],"rank":"emit `1` for LAST_USABLE and `2` for FIRST_DOWNSTREAM_FAIL","station_number":"preserve the station number exactly","breakpoint_role":"emit `LAST_USABLE` and `FIRST_DOWNSTREAM_FAIL` exactly","target_window_status":"emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly","final_verdict":"emit `KEEP` for the usable breakpoint row and `REJECT` for the downstream failing breakpoint row","stop_condition":["the last usable mainstem station is fixed under the availability-page validation rule","the first downstream failing mainstem station is fixed under the same validation rule before the two-row output is emitted"]}}} +{"task_id":"wateroffice_002","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"I am compiling historical daily flow records for the Bulkley River reach from Houston to Hazelton and want to verify, station by station, whether candidate mainstem stations on the Bulkley River truly have complete daily flow records for April–July 1948 and April–July 1950. First, from the Historical Results list, select candidate stations that lie on the Bulkley River mainstem, fall within the Houston-to-Hazelton reach, appear to cover both 1948 and 1950, and carry a Flow label. Then open each station's availability page and check whether the target years fall within the Flow section and whether April-July is marked C throughout. If the target windows satisfy the complete daily flow condition, set target_window_status to PASS and final_verdict to KEEP. If the target years have only water level records and no daily flow records, set target_window_status to LEVEL_ONLY and final_verdict to REJECT. If daily flow records exist but any month from April to July is not complete, set target_window_status to FLOW_GAP and final_verdict to REJECT. Finally, output a table in downstream-to-upstream order with columns rank|station_number|target_window_status|final_verdict.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a table in downstream-to-upstream order with columns rank|station_number|target_window_status|final_verdict.","oracle_answer":"1|08EE004|PASS|KEEP\n2|08EE001|LEVEL_ONLY|REJECT\n3|08EE005|FLOW_GAP|REJECT\n4|08EE003|FLOW_GAP|REJECT","metadata":{"State-Gated Retrieval":["First identify mainstem candidate stations on the Historical Results list that appear to cover 1948/1950 and carry a Flow label.","A station qualifies only if its availability page shows the target years in the Flow section and all of April-July marked C.","The final output must report target_window_status and final_verdict for each station in the same station set, ordered from downstream to upstream."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the Historical Results list yields four downstream-to-upstream mainstem candidates whose result rows span the target years and include Flow labels","each candidate's availability page yields whether the target years are in the Flow table and whether April-July is complete","the final ordered rows are produced only after all four stations are classified under the full Flow-table-and-Apr-Jul-C rule"],"control_dependency":["list-level year spans and coarse Flow tags must be confirmed by explicit target-month checks on the availability page","Hazelton, Smithers, and Houston candidate statuses must be fixed before the downstream-most KEEP row can be confirmed","row order and KEEP/REJECT labels must be emitted only after the full availability-page rule is applied to all four stations"],"freeze":{"historical_window":"the target mainstem stations tested against 1948 and 1950 daily Flow availability, with April-July requiring complete C coverage"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["First, from the Historical Results list, identify mainstem candidate stations that superficially appear to cover 1948/1950 and have a Flow label.","A truly qualified station must satisfy, on its availability page, that the target years are in the Flow section and that April–July are all marked C.","Finally, report target_window_status and final_verdict for each station in the same station set, ordered from downstream to upstream."],"exclusion_conditions":["Exclude stations deemed usable based solely on list-level year span and coarse Flow label.","Exclude retaining LEVEL_ONLY or FLOW_GAP stations in the final answer.","Exclude results that do not apply the full availability-page rule to all initially screened stations."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","station_number","target_window_status","final_verdict"],"rank":"emit 1 through 4 in downstream-to-upstream order within the validated station set","station_number":"preserve the station number exactly","target_window_status":"emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly","final_verdict":"emit `KEEP` or `REJECT` exactly","sorting_or_selection":"downstream to upstream within the validated Bulkley River mainstem station set","stop_condition":["all four initially screened stations are classified under the full availability-page rule","the ordered table is emitted only after the downstream-to-upstream sequence is fixed"]}}} +{"task_id":"wateroffice_003","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"I am compiling historical snowmelt daily flow data for the Thompson River from Chase to Spences Bridge. I need to verify, station by station, whether the mainstem stations along this reach actually have daily flow records for May–July of 1958 and 1971. First, in downstream order from Chase to Spences Bridge, select stations from the list that show coverage for 1958 and 1971 and have flow records for the Thompson River mainstem. Then, for each selected station, check whether it provides complete daily flow records for May–July of both 1958 and 1971. If a station has only water level records (no daily flow) for a target year, mark it LEVEL_ONLY. If daily flow records exist but the May–July window is missing or any target month is incomplete, mark it FLOW_GAP. Only when both years' May–July daily flow records are complete should the final_verdict be KEEP; otherwise, REJECT. Finally, output a table with columns rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict, ordered downstream from Chase to Spences Bridge.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a table with columns rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict, ordered downstream from Chase to Spences Bridge.","oracle_answer":"1|08LE031|SOUTH THOMPSON RIVER AT CHASE|PASS|PASS|KEEP\n2|08LE069|SOUTH THOMPSON RIVER AT MONTE CREEK|FLOW_GAP|LEVEL_ONLY|REJECT\n3|08LF023|THOMPSON RIVER AT KAMLOOPS|LEVEL_ONLY|LEVEL_ONLY|REJECT\n4|08LF033|THOMPSON RIVER NEAR SAVONA|FLOW_GAP|FLOW_GAP|REJECT\n5|08LF051|THOMPSON RIVER NEAR SPENCES BRIDGE|PASS|PASS|KEEP","metadata":{"State-Gated Retrieval":["All five candidate stations must be verified on the availability page to confirm that the target years are present in the Flow table and that May–July is entirely marked C.","Each station must output a PASS / LEVEL_ONLY / FLOW_GAP judgment for both target years, and then be marked KEEP or REJECT accordingly.","The result order must follow the river-path ordering specified in the task."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the river-path ordering yields five South Thompson / Thompson mainstem candidates","each station's availability page yields whether 1958 and 1971 are present in the Flow table and whether May-July is complete","final rows are produced only after every candidate is classified under the stricter target-year and target-month Flow rule"],"control_dependency":["overall year coverage on the results list must be confirmed by the availability page inside the Flow table","Monte Creek, Savona, and Kamloops must be rejected by LEVEL_ONLY / FLOW_GAP evidence before the KEEP rows are final","the river-order sequence remains fixed, but station statuses must be assigned only after the availability-page rule is applied to all five stations"],"freeze":{"historical_window":"the ordered South Thompson / Thompson mainstem candidates tested against 1958 and 1971 Flow availability, with May-July requiring complete C coverage"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["All five candidate stations must be verified on the availability page to confirm that the target years are present in the Flow table and that May–July is entirely marked C.","Each station must output a PASS / LEVEL_ONLY / FLOW_GAP judgment for both target years, and then be marked KEEP or REJECT accordingly.","The result order must follow the river-path ordering specified in the task."],"exclusion_conditions":["Exclude results that treat overall year coverage on the list as sufficient evidence.","Exclude results that fail to distinguish between Flow table target-year and month completeness versus Level-only evidence.","Exclude results that do not apply the same availability-page rule uniformly to all five stations."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","station_number","station_name","1958_MayJul","1971_MayJul","final_verdict"],"rank":"use the fixed Chase-to-Spences-Bridge mainstem order from the reference index, not the transient search-result order","year_window_fields":"the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP","final_verdict":"emit `KEEP` or `REJECT` exactly"}}} +{"task_id":"wateroffice_004","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":13,"instruction":"I am compiling historical daily flow records for the mainstem Columbia River from Fairmont Hot Springs to the International Boundary. I want to check, station by station in Wateroffice, which stations have complete daily flow records for May–October of 1955 and 1956. First, locate stations on the Columbia River mainstem between Fairmont Hot Springs and the International Boundary whose records span both 1955 and 1956. Then, proceeding from upstream to downstream, check the availability of daily flow for May–October of 1955 and 1956 at each station. If a station has only water-level records and no daily flow records for a given target year, mark that year as LEVEL_ONLY. If daily flow for May–October of that year is complete, mark it as PASS. Otherwise, if the year has no usable daily flow records or any month within May–October is incomplete, mark it as FLOW_GAP. Only when both years satisfy the PASS condition should the final_verdict be KEEP; otherwise write REJECT. Finally, output a table in upstream-to-downstream order with columns: rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a table in upstream-to-downstream order with columns: rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict.","oracle_answer":"1|08NA045|COLUMBIA RIVER NEAR FAIRMONT HOT SPRINGS|PASS|PASS|KEEP\n2|08NA004|COLUMBIA RIVER AT ATHALMER|LEVEL_ONLY|LEVEL_ONLY|REJECT\n3|08NA052|COLUMBIA RIVER NEAR EDGEWATER|PASS|FLOW_GAP|REJECT\n4|08NA002|COLUMBIA RIVER AT NICHOLSON|PASS|PASS|KEEP\n5|08NB005|COLUMBIA RIVER AT DONALD|PASS|PASS|KEEP\n6|08NB006|COLUMBIA RIVER AT SURPRISE RAPIDS|PASS|PASS|KEEP\n7|08ND007|COLUMBIA RIVER ABOVE NAGLE CREEK|PASS|PASS|KEEP\n8|08ND011|COLUMBIA RIVER ABOVE STEAMBOAT RAPIDS|FLOW_GAP|PASS|REJECT\n9|08ND006|COLUMBIA RIVER AT TWELVE MILE FERRY|PASS|PASS|KEEP\n10|08NE002|COLUMBIA RIVER AT CASTLEGAR|LEVEL_ONLY|LEVEL_ONLY|REJECT\n11|08NE049|COLUMBIA RIVER AT BIRCHBANK|PASS|PASS|KEEP\n12|08NE003|COLUMBIA RIVER AT TRAIL|LEVEL_ONLY|LEVEL_ONLY|REJECT\n13|08NE058|COLUMBIA RIVER AT INTERNATIONAL BOUNDARY|PASS|PASS|KEEP","metadata":{"State-Gated Retrieval":["Every candidate Columbia River station must be checked on its availability page to confirm that the target years appear in the Flow table and that May–October is fully marked C.","For each station, provide the KEEP/REJECT basis for both 1955 and 1956, distinguishing LEVEL_ONLY and FLOW_GAP cases from stations that only appear eligible from their overall year span.","The final table must preserve the order and fields specified in the task."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the Columbia River candidate ordering yields fourteen stations spanning the target years","each availability page yields whether 1955 and 1956 are present in the Flow table and whether May-October is complete","final rows are produced only after every station is classified under the stricter Flow-table-and-May-Oct-C rule"],"control_dependency":["list-level year spans must be confirmed by the availability page inside the Flow table","LEVEL_ONLY and FLOW_GAP evidence must be applied to each station before the KEEP/REJECT table is finalized","station-by-station verdicts and rejection reasons must be determined only after the full availability-page rule replaces the initial year-span screen"],"freeze":{"historical_window":"the ordered Columbia River candidates tested against 1955 and 1956 Flow availability, with May-October requiring complete C coverage"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Every candidate Columbia River station must be checked on its availability page to confirm that the target years appear in the Flow table and that May–October is fully marked C.","For each station, provide the KEEP/REJECT basis for both 1955 and 1956, distinguishing LEVEL_ONLY and FLOW_GAP cases from stations that only appear eligible from their overall year span.","The final table must preserve the order and fields specified in the task."],"exclusion_conditions":["Exclude results that retain a station solely because its overall record spans 1955/1956.","Exclude results that fail to distinguish, station by station, between Flow availability, Level-only, and incomplete months.","Exclude results that do not apply the full availability-page rule uniformly to all 14 stations."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","station_number","station_name","1955_MayOct","1956_MayOct","final_verdict"],"rank":"use the fixed upstream-to-downstream Columbia mainstem order from the reference index, not the transient search-result order","year_window_fields":"the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP","final_verdict":"emit `KEEP` or `REJECT` exactly"}}} +{"task_id":"wateroffice_005","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am organizing historical daily-flow records for the Peace River reach from Dunvegan Bridge to Fifth Meridian and want to verify three things at once: the true furthest-downstream reusable station on the mainstem, the first failing station encountered after it, and the provisional terminal station that a station-level screen based only on year coverage and record type would mistakenly treat as the downstream winner. Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian. First, from the station list, identify provisional candidates that appear to cover both 1966 and 1967 and show a daily-flow record type. Then open each availability page and verify whether May through September in both 1966 and 1967 appears in the Flow table and is complete for every month. If both target years satisfy the complete daily-flow condition, write PASS in target_window_status. If a target year has only level records and no daily-flow records, write LEVEL_ONLY. If daily-flow records exist but any target month from May through September is incomplete, write FLOW_GAP. If the target year has neither daily-flow nor level records, write NO_TARGET_RECORD. Finally, output a three-row diagnostic table with columns rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count. The rows must be FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION in that order, and the last two columns must repeat the global provisional_count and final_count in every row.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a three-row diagnostic table with columns rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count.","oracle_answer":"1|07HA001|FINAL_STATION|PASS|5|2\n2|07HD001|FIRST_BREAK_AFTER_FINAL|FLOW_GAP|5|2\n3|07KA002|PROVISIONAL_STATION|FLOW_GAP|5|2","metadata":{"State-Gated Retrieval":["Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian.","A genuinely reusable station must satisfy the availability-page rule that both 1966 and 1967 appear in the Flow table and that every month from May through September is complete.","The final output must jointly report FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION, while repeating provisional_count and final_count in every row."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the Peace River mainstem chain between Dunvegan Bridge and Fifth Meridian yields the initial station list and the downstream breakpoint positions that need revalidation","each availability page yields whether 1966 and 1967 are present in the Flow or Level tables and whether May-September is complete","final rows are produced only after the final station, the first downstream failure, and the provisional downstream winner are all fixed under the same availability-page validation rule"],"control_dependency":["station-level target-year Flow evidence must be validated by explicit May-September completeness checks on the availability page","the final downstream reusable station and the first downstream failure must be determined under the same validation rule rather than from the initial station screen","the provisional downstream winner is kept in the output only for reference after its FLOW_GAP status is confirmed on the availability page"],"freeze":{"historical_window":"Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian, evaluated within the fixed historical 1966 and 1967 Flow-availability windows, with May-September complete-C coverage used as nearly stable reference information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian.","A genuinely reusable station must satisfy the availability-page rule that both 1966 and 1967 appear in the Flow table and that every month from May through September is complete.","The final output must jointly report FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION, while repeating provisional_count and final_count in every row."],"exclusion_conditions":["Exclude results that treat a station as usable simply because the target years have Flow records.","Exclude results that do not verify completeness month by month from May through September.","Exclude results that mark a station such as 07KA002 as FINAL_STATION when availability-page evidence shows FLOW_GAP."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","station_number","diagnosis_role","target_window_status","provisional_count","final_count"],"rank":"emit the fixed order 1, 2, 3 for FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION","station_number":"use uppercase WSC station codes exactly as the Reference Index and availability pages show","diagnosis_role":["FINAL_STATION","FIRST_BREAK_AFTER_FINAL","PROVISIONAL_STATION"],"target_window_status":["PASS","LEVEL_ONLY","FLOW_GAP","NO_TARGET_RECORD"],"count_fields":"repeat the global provisional_count and final_count in every row as plain integers","sorting_or_selection":"emit rows in the fixed diagnostic order FINAL_STATION, FIRST_BREAK_AFTER_FINAL, PROVISIONAL_STATION"}}} +{"task_id":"waterquality_001","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am reviewing historical monitoring records for a reach of the middle Rio Grande and need to select two monitoring stations suitable for observing wastewater impacts on the main channel. Starting from RIO GRANDE AT EMBUDO, NM and proceeding downstream, retain only stations that are confirmed to lie on the Rio Grande mainstem. Then, find the first mainstem monitoring station downstream of the Town of Bernalillo wastewater treatment plant outfall that meets the following conditions; continuing further downstream, find the first mainstem monitoring station that has passed both the Town of Bernalillo WWTP outfall and the Rio Rancho No. 2 WWTP outfall and meets the same conditions. Both stations must satisfy: the station itself is not an outfall, facility, well, canal, or drainage ditch; the type on the station detail page is labeled as River/Stream; records for the four characteristic groups Microbiological, Nutrient, Organics, Other, and Physical fully cover 2015–2020; and the start years for both Microbiological and Physical records are earlier than 2010. Finally, output a single-line string in upstream-to-downstream order: ||, with the two segments separated by a comma.","start_url":"https://www.waterqualitydata.us/","output_format":"Output a single-line string in upstream-to-downstream order: ||, with the two segments separated by a comma.","oracle_answer":"SANDIAWQ_WQX-RG003|2004|2004,SANDIAWQ_WQX-RG008|2004|2004","metadata":{"State-Gated Retrieval":["Select two target stations only from Rio Grande mainstem monitoring stations downstream of RIO GRANDE AT EMBUDO, NM, and both must have passed the specified outfall locations.","The station detail page must explicitly show River/Stream, and records for the four characteristic groups Microbiological, Nutrient, Organics, Other, and Physical must fully cover 2015–2020, while the start years for both Microbiological and Physical must be earlier than 2010.","Output the two final stations in upstream-to-downstream order."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["provider/list views yield the Rio Grande mainstem candidates downstream of the Bernalillo and Rio Rancho No. 2 discharge points","detail pages yield flow position, location type, characteristic-group period-of-record coverage for 2015-2020, and the Microbiological/Physical baseline years","final rows are produced only after the corrected downstream sentry stations are fixed and ordered from upstream to downstream"],"control_dependency":["provider-list stream tags are only provisional and must be confirmed on the detail page by both mainstem placement and location type","target-window presence is insufficient until full 2015-2020 coverage is confirmed on the detail page for all four groups","once RG002/RG007 fail the full detail-page checks, the workflow must continue downstream from the discharge-point starting position to RG003/RG008"],"freeze":{"historical_window":"Rio Grande mainstem stations downstream of the Town of Bernalillo and Rio Rancho No. 2 WWTP outfalls, validated against 2015-2020 coverage for Microbiological, Nutrient, Organics, Other, and Physical"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Select two target stations only from Rio Grande mainstem monitoring stations downstream of RIO GRANDE AT EMBUDO, NM, and both must have passed the specified outfall locations.","The station detail page must explicitly show River/Stream, and records for the four characteristic groups Microbiological, Nutrient, Organics, Other, and Physical must fully cover 2015–2020, while the start years for both Microbiological and Physical must be earlier than 2010.","Output the two final stations in upstream-to-downstream order."],"exclusion_conditions":["Exclude stations that have only a superficial (Stream) tag on the provider list or have records near the target window, but whose detail page does not satisfy the flow position, location type, or complete period-of-record conditions.","Exclude locations that are outfalls, facilities, wells, canals, or drainage ditches.","Exclude candidates such as RG002 and RG007 that are not the qualifying sentry stations downstream of the corresponding outfalls."],"normalization":{"record_separator":",","field_separator":"|","schema_per_record":["MonitoringLocationIdentifier","Microbiological_start_year","Physical_start_year"],"ordering":"emit exactly two records from upstream to downstream","station_id":"use uppercase MonitoringLocationIdentifier","year_fields":"emit four-digit years as plain integers","selection":{"record_1":"the first qualifying mainstem station below the Bernalillo outfall","record_2":"the first qualifying mainstem station below both the Bernalillo and Rio Rancho No. 2 outfalls"},"stop_condition":["the Bernalillo branch stops only after its first qualifying mainstem station is fixed","the Rio Rancho No. 2 branch stops only after its first qualifying mainstem station is fixed","the two segments are emitted as one comma-joined line in upstream-to-downstream order"]}}} +{"task_id":"waterquality_002","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am analyzing trends in the lower Rio Grande from 2001 to 2010. From monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002, select one representative station for Hidalgo County and one for Cameron County. First, screen candidate stations for each county within the specified area. Retain only stations whose detail page lists the type as River/Stream and that have records covering 2001–2010 for all four characteristic groups: Microbiological, Nutrient, Organics, Other, and Physical. If multiple stations in the same county qualify, select the station with the earliest year in which all four groups are simultaneously present. Then record the MonitoringLocationIdentifier of the selected station, the earliest year all four groups are simultaneously present, and the start year for each of Microbiological, Nutrient, Organics, Other, and Physical. Finally, output a single-line string in the order Hidalgo then Cameron: :|||||, with the two segments separated by a comma.","start_url":"https://www.waterqualitydata.us/","output_format":"Output a single-line string in the order Hidalgo then Cameron: :|||||, with the two segments separated by a comma.","oracle_answer":"Hidalgo:TCEQMAIN-15808|1998|1998|1998|1998|1998,Cameron:TCEQMAIN-13177|1995|1981|1981|1995|1981","metadata":{"State-Gated Retrieval":["Select one representative station for Hidalgo County and one for Cameron County from monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002.","Candidate detail pages must list the type as River/Stream, and records for all four characteristic groups (Microbiological, Nutrient, Organics, Other, Physical) must cover 2001–2010.","If multiple stations in the same county qualify, select the station with the earliest year in which all four groups are simultaneously present."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the fixed downstream starting point and county split yield Hidalgo and Cameron candidate mainstem stations within HUC 13090002","detail pages yield River/Stream validity, the four characteristic-group start years, and the earliest year when all four groups are simultaneously present for 2001-2010 coverage","final rows are produced only after the county-specific searches are rerun from the fixed downstream starting point and then ranked by common-start year"],"control_dependency":["the Hidalgo search must preserve the \"below TCEQMAIN-13664\" downstream starting point rather than returning to the anchor station itself","a station is only provisional until all four characteristic groups are confirmed for the same MonitoringLocationIdentifier and tidal/intake conflicts are excluded on the detail page","county winners are valid only after late-start and non-river candidates are removed and the common-start-year tie-break is recomputed"],"freeze":{"historical_window":"stations below RIO GRANDE BELOW ANZALDUAS within HUC 13090002, split by Hidalgo and Cameron County, with Microbiological, Nutrient, Organics, Other, and Physical coverage over 2001-2010"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Select one representative station for Hidalgo County and one for Cameron County from monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002.","Candidate detail pages must list the type as River/Stream, and records for all four characteristic groups (Microbiological, Nutrient, Organics, Other, Physical) must cover 2001–2010.","If multiple stations in the same county qualify, select the station with the earliest year in which all four groups are simultaneously present."],"exclusion_conditions":["Exclude results where the Hidalgo search loses the downstream starting point and brings the starting station itself back into the candidate set.","Exclude results that treat a single multi-select of the four characteristic groups as sufficient without verifying that all four belong to the same station ID.","Exclude stations with tidal, intake, late-start, or other conflicts clearly indicated on the detail page."],"normalization":{"record_separator":",","field_separator":"|","schema_per_record":["County:MonitoringLocationIdentifier","common_start_year","Microbiological_start_year","Nutrient_start_year","Organics_Other_start_year","Physical_start_year"],"ordering":"emit exactly two records, with Hidalgo first and Cameron second","county_prefix":"use the county label in title case, followed by : and the uppercase MonitoringLocationIdentifier","year_fields":"emit four-digit years as plain integers","common_start_year":"the earliest year in which all four required groups are simultaneously present for the chosen county station","stop_condition":["each county branch is rerun until one River/Stream station survives all four group checks","the county winner is fixed only after late-start and non-river candidates are excluded after checking the detail page","the two county segments are emitted on one line in the fixed Hidalgo-then-Cameron order"]}}} +{"task_id":"waterquality_003","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am compiling 2012–2018 water quality reference data for the Brazos River mainstem downstream of Brazos Rv at Waco, TX. I want to select one TCEQ monitoring station suitable as a long-term reference point in each of the three HUCs (12060202, 12070101, 12070104) that the mainstem passes through. Process as follows: first, within the Brazos River mainstem reach downstream of Brazos Rv at Waco, TX, screen candidate stations in HUCs 12060202, 12070101, and 12070104 respectively; retain only monitoring locations whose detail page labels them as River/Stream and whose station name still corresponds to the Brazos River mainstem rather than another named waterbody. Next, check the record categories for these stations, retaining only those that cover 2012–2018 for all five categories: Inorganics, Major, Non-metals; Microbiological; Nutrient; Organics, Other; and Physical. Specifically, the station start year must be no later than 2012 and the end year no earlier than 2018. Finally, list the 3 results in order from upstream to downstream, each row formatted as: |||||||.","start_url":"https://www.waterqualitydata.us/","output_format":"List the 3 results in order from upstream to downstream, each row formatted as: |||||||.","oracle_answer":"12060202|TCEQMAIN-12037|2000|1991|2000|1991|1999|1991\n12070101|TCEQMAIN-12030|2006|1972|1972|1972|2006|1972\n12070104|TCEQMAIN-11848|1975|1974|1975|1974|1975|1974","metadata":{"State-Gated Retrieval":["The search must stay anchored downstream of Waco and look for Brazos mainstem monitoring stations within the three HUCs specified in the task.","Each candidate station must be checked separately across the five characteristic groups and then matched back to the same station ID, after which the detail page must verify full 2012–2018 coverage and mainstem semantics.","For each HUC, retain only the qualifying station with the earliest common start year, and output the start-year fields required by the task."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the fixed downstream starting point below Waco and the three target HUC searches yield the Brazos mainstem candidate stations","detail pages yield true downstream position, mainstem-vs-tributary semantics, and five-group period-of-record coverage across 2012-2018","final rows are produced only after the three HUC-specific searches are carried out, matched by station ID, and ranked by the earliest year when all five groups are jointly available"],"control_dependency":["the workflow must stay anchored downstream of Waco rather than reintroducing upstream stations such as TCEQMAIN-12044","name-based waterbody matches must be validated on the detail page by excluding tributaries such as LITTLE BRAZOS RIVER and confirming full-window coverage","station ranking must be determined after false positives from partial-window records are removed"],"freeze":{"historical_window":"Brazos River mainstem stations downstream of the Waco anchor, split across HUC 12060202, 12070101, and 12070104, with five characteristic groups covering 2012-2018"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["The search must stay anchored downstream of Waco and look for Brazos mainstem monitoring stations within the three HUCs specified in the task.","Each candidate station must be checked separately across the five characteristic groups and then matched back to the same station ID, after which the detail page must verify full 2012–2018 coverage and mainstem semantics.","For each HUC, retain only the qualifying station with the earliest common start year, and output the start-year fields required by the task."],"exclusion_conditions":["Exclude results that lose the downstream starting point below Waco and bring upstream stations back into the candidate set.","Exclude results that mistake tributaries such as LITTLE BRAZOS RIVER for the Brazos mainstem.","Exclude stations that have data near the query window but do not cover the entire 2012–2018 window."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["HUC","MonitoringLocationIdentifier","common_start_year","Inorganics_start","Microbiological_start","Nutrient_start","Organics_Other_start","Physical_start"],"HUC":"preserve the HUC exactly as emitted in the source result","MonitoringLocationIdentifier":"preserve the monitoring-location identifier exactly, for example `TCEQMAIN-12037`","common_start_year":"emit the maximum of the five per-group start years","selection_rule":"only keep mainstem river/stream sites whose five required groups all cover the target 2012-2018 window","sorting_or_selection":"upstream to downstream along the mainstem"}}} +{"task_id":"waterquality_004","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am reviewing toxic-pollutant-related water quality monitoring data for 1993–2001 along the Trinity River mainstem, bounded upstream by the reach near FM 85 and downstream by the reach near Interstate 10. I need to select one TCEQ long-term reference station for each of the upper, middle, and lower segments.\n\nStarting from the Trinity River mainstem between the reach near FM 85 and the reach near Interstate 10, screen candidate monitoring locations in the upper, middle, and lower segments. Retain only stations whose record is tagged as River/Stream and whose name still refers to the Trinity River mainstem, not to other named water bodies or distributaries. Then check the record categories for these stations; keep only those that have all six record categories covering 1993–2001 (i.e., the start year is no later than 1993 and the end year is no earlier than 2001). Output the results from upstream to downstream.\n\nFinally, list three rows from upstream to downstream along the river, each in the format: ||||||||.","start_url":"https://www.waterqualitydata.us/","output_format":"List three rows from upstream to downstream along the river, each in the format: ||||||||.","oracle_answer":"12030105|TCEQMAIN-10924|1983|1982|1983|1982|1983|1983|1982\n12030202|TCEQMAIN-10897|1993|1969|1972|1972|1993|1974|1969\n12030203|TCEQMAIN-10892|1976|1969|1971|1972|1974|1976|1969","metadata":{"State-Gated Retrieval":["Screen only among candidate stations where Trinity River mainstem semantics hold, and require all six characteristic groups to cover 1993–2001.","The six groups must be searched separately and then matched back to the same station ID, after which the detail page must verify full-window coverage and legacy toxics group completeness.","For each target segment, retain only the station that meets all group requirements and has the best common start year."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Trinity River mainstem candidate stations are generated from the target HUC searches and the six characteristic-group searches","detail pages yield River/Stream validity, 1993–2001 full-window coverage, and the group-specific start years needed for ranking","final rows are produced only after all six groups have been matched by station ID and detail-page validation removes partial-group and non-mainstem false positives"],"control_dependency":["each of the six characteristic groups must be evaluated separately and confirmed against the same station ID before a multi-select result can be retained","station names and River/Stream tags are insufficient until the detail page confirms Trinity mainstem semantics and 1993–2001 full-window coverage","candidate rejection and final ranking must be determined after applying the PCBs / Organics, Other gap checks"],"freeze":{"historical_window":"Trinity River mainstem stations validated against six characteristic groups over 1993–2001, with ranking based on the earliest joint availability and group start years"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Screen only among candidate stations where Trinity River mainstem semantics hold, and require all six characteristic groups to cover 1993–2001.","The six groups must be searched separately and then matched back to the same station ID, after which the detail page must verify full-window coverage and legacy toxics group completeness.","For each target segment, retain only the station that meets all group requirements and has the best common start year."],"exclusion_conditions":["Exclude results that mistakenly treat a single multi-select of characteristic groups as sufficient to satisfy the requirement.","Exclude results that only check station names and River/Stream tags without verifying 1993–2001 full-window coverage.","Exclude stations that ignore missing PCBs or Organics, Other groups."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["HUC","MonitoringLocationIdentifier","common_start_year","Inorganics_start","Microbiological_start","Nutrient_start","Organics_Other_start","Organics_PCBs_start","Physical_start"],"HUC":"preserve the HUC exactly as emitted in the source result","MonitoringLocationIdentifier":"preserve the monitoring-location identifier exactly, for example `TCEQMAIN-10924`","common_start_year":"emit the maximum of the six per-group start years","selection_rule":"only keep mainstem river/stream sites whose six required groups all cover the target window","sorting_or_selection":"upstream to downstream along the mainstem"}}} +{"task_id":"waterquality_005","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":9,"instruction":"I am organizing integrated water-quality records for the lower Neches River during 1978-1984. Starting downstream from NECHES RIVER AT CR 4915, I want to identify the nearest TCEQ long-term reference station that still represents the inland Neches River mainstem, and then tabulate the start year of nine Characteristic Groups at that station. Search downstream along the mainstem and retain only monitoring stations whose detail page labels the site type as River/Stream. Exclude stations located in lake or reservoir waters or in the Sabine-Neches outlet boundary reach. Among stations that satisfy these location conditions, identify the nearest qualifying station for which all nine record categories cover 1978-1984: Biological, Algae, Phytoplankton; Inorganics, Major, Non-metals; Inorganics, Minor, Metals; Microbiological; Nutrient; Organics, Other; Organics, PCBs; Organics, Pesticide; and Physical. Finally, output a table for that final station, one row per Characteristic Group, with columns rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year. The row order is fixed as Biological, Algae, Phytoplankton; Inorganics, Major, Non-metals; Inorganics, Minor, Metals; Microbiological; Nutrient; Organics, Other; Organics, PCBs; Organics, Pesticide; Physical.","start_url":"https://www.waterqualitydata.us/provider/STORET/TCEQMAIN/TCEQMAIN-10598/","output_format":"Output a 9-row table with columns rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year.","oracle_answer":"1|TCEQMAIN-10580|12020003|Hardin County|Biological, Algae, Phytoplankton|1972|1977\n2|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Major, Non-metals|1971|1977\n3|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Minor, Metals|1974|1977\n4|TCEQMAIN-10580|12020003|Hardin County|Microbiological|1972|1977\n5|TCEQMAIN-10580|12020003|Hardin County|Nutrient|1972|1977\n6|TCEQMAIN-10580|12020003|Hardin County|Organics, Other|1974|1977\n7|TCEQMAIN-10580|12020003|Hardin County|Organics, PCBs|1974|1977\n8|TCEQMAIN-10580|12020003|Hardin County|Organics, Pesticide|1977|1977\n9|TCEQMAIN-10580|12020003|Hardin County|Physical|1971|1977","metadata":{"State-Gated Retrieval":["Search only among TCEQ monitoring stations downstream of NECHES RIVER AT CR 4915 that still represent the inland Neches River mainstem.","A candidate station must cover 1978-1984 in all nine Characteristic Groups and, on the detail page, must still qualify as River/Stream, outside lake or reservoir waters, and outside the Sabine-Neches outlet boundary reach.","The final output must be centered on the single winning station and list group_start_year plus common_start_year row by row in the fixed nine-group order."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the fixed downstream starting point at NECHES RIVER AT CR 4915 yields candidate inland mainstem stations across successive downstream HUCs","detail pages yield River/Stream validity, inland-vs-boundary semantics, and nine-group period-of-record coverage across 1978-1984","final rows are produced only after one winning station survives the inland-mainstem checks and the requirement that all nine groups match the same station, after which its nine group start years are emitted in the required order"],"control_dependency":["the nearest downstream mainstem station remains provisional until all nine characteristic groups have been checked separately and matched back to the same station ID","the downstream search must continue to the next mainstem HUC when the first candidate fails the nine-group coverage requirement","location semantics remain valid only after detail-page exclusion of lake/reservoir and Sabine-Neches boundary stations"],"freeze":{"historical_window":"Neches River inland mainstem stations downstream of NECHES RIVER AT CR 4915, validated within the fixed 1978-1984 window against nine characteristic groups as largely stable reference information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Search only among TCEQ monitoring stations downstream of NECHES RIVER AT CR 4915 that still represent the inland Neches River mainstem.","A candidate station must cover 1978-1984 in all nine Characteristic Groups and, on the detail page, must still qualify as River/Stream, outside lake or reservoir waters, and outside the Sabine-Neches outlet boundary reach.","The final output must be centered on the single winning station and list group_start_year plus common_start_year row by row in the fixed nine-group order."],"exclusion_conditions":["Exclude results that retain TCEQMAIN-10591 merely because it appears to be the nearest downstream mainstem station.","Exclude results that do not check the nine Characteristic Groups separately and verify that they all belong to the same station ID.","Exclude stations located in lake or reservoir waters or in the Sabine-Neches outlet boundary reach."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","MonitoringLocationIdentifier","HUC","County","characteristic_group","group_start_year","common_start_year"],"rank":"emit 1 through 9 in the fixed characteristic-group order required by the task","MonitoringLocationIdentifier":"use uppercase MonitoringLocationIdentifier","HUC":"emit the HUC as an 8-digit string with no separators","County":"use the county name exactly as shown on the detail page","characteristic_group":"preserve the group label exactly as listed in the task","year_fields":"emit four-digit years as plain integers","common_start_year":"repeat the earliest year in which all nine required groups are simultaneously present for the chosen station","sorting_or_selection":"emit rows in the fixed nine-group order stated in the task"}}} +{"task_id":"wonder_001","domain":"CDC_WONDER","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"I am preparing a public health brief on changes in U.S. home births in 2020. I need to identify months where the home-birth rate among all mothers increased by at least 25% compared to the same month in 2019, and also examine the corresponding changes for non-Hispanic Black mothers and Hispanic mothers in those months. First, compare the home-birth rates for all mothers by calendar month between 2019 and 2020, retaining only months in 2020 where the rate increased by at least 25% relative to the same month in 2019. Then, for those months, add the 2020 home-birth rates for non-Hispanic Black mothers and Hispanic mothers, along with their changes relative to the same month in 2019. Finally, output a multi-row pipe-delimited table in calendar month order with the fixed header: month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel. All numeric values should be plain numbers without percent signs.","start_url":"https://wonder.cdc.gov/natality-expanded-current.html","output_format":"Output a multi-row pipe-delimited table in calendar month order with the fixed header: month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel. All numeric values should be plain numbers without percent signs.","oracle_answer":"month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel\nMay|1.03|1.49|45|0.74|54|0.55|57\nJune|1.04|1.31|26|0.66|20|0.48|30\nJuly|1.03|1.30|26|0.68|42|0.48|30\nAugust|1.02|1.29|26|0.69|50|0.48|26\nSeptember|1.01|1.31|30|0.73|43|0.54|54\nOctober|1.00|1.28|28|0.75|50|0.47|27\nNovember|0.99|1.30|31|0.73|43|0.55|67\nDecember|0.92|1.28|39|0.80|63|0.53|61","metadata":{"State-Gated Retrieval":["First, compare the home-birth rates for all mothers by calendar month between 2019 and 2020, retaining only months in 2020 where the rate increased by at least 25% relative to the same month in 2019.","The home-birth numerator must use the full home category, not Home intended alone.","For those months, add the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, along with their changes relative to the same month in 2019."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Monthly natality queries yield the 2019 vs 2020 home-birth rates for all mothers and the candidate month set.","Follow-up race/ethnicity queries yield the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, plus their same-month changes versus 2019.","Final rows are produced only after qualifying months are determined from rate growth, and the resulting month set is reused for both subgroup backfill chains."],"control_dependency":["Month selection must be based on relative rate increase rather than counts alone.","The home-birth numerator must use Residence or an equivalent full-home measure rather than Home intended alone before downstream subgroup queries run.","Subgroup columns must be generated from the resulting month set rather than appended to earlier rows."],"freeze":{"historical_window":"2019 and 2020 U.S. natality monthly home-birth rates for all mothers, non-Hispanic Black mothers, and Hispanic mothers."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["First, compare the home-birth rates for all mothers by calendar month between 2019 and 2020, retaining only months in 2020 where the rate increased by at least 25% relative to the same month in 2019.","The home-birth numerator must use the full home category, not Home intended alone.","For those months, add the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, along with their changes relative to the same month in 2019."],"exclusion_conditions":["Exclude month-row sets that misinterpret \"rate increase of at least 25%\" as \"count increase of at least 25%.\"","Exclude results that use only the Home intended category instead of the full home numerator.","Exclude results that add subgroup columns to an incorrect month set."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"Required literal first row: month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel","schema":["month","all_2019","all_2020","all_rel","black_2020","black_rel","hispanic_2020","hispanic_rel"],"month":"Use the English month name and keep calendar order.","numeric_fields":"All numeric outputs are plain numbers without a percent sign.","relative_change_fields":"all_rel, black_rel, and hispanic_rel are emitted as integer percentages without the `%` character."}}} +{"task_id":"wonder_002","domain":"CDC_WONDER","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am preparing a one-page public health brief on 2021 U.S. infant mortality disparities. I want to identify groups that are separately listed in the report by mother's race and Hispanic origin, have an infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death. First, from the separately listed groups in the report, select those with an infant mortality rate above the U.S. overall rate and a clearly identifiable leading cause of death. Then, for each qualifying group, record the full-year infant mortality rate, the neonatal rate (under 28 days), and the postneonatal rate (28 days and older), along with the group's leading cause of death, its cause-specific rate, and the rank of that cause among all infant causes. Finally, output a multi-row pipe-delimited table sorted by full-year infant mortality rate from high to low: group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank.","start_url":"https://wonder.cdc.gov/lbd-current-expanded.html","output_format":"Finally, output a multi-row pipe-delimited table sorted by full-year infant mortality rate from high to low: group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank.","oracle_answer":"group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank\nnon-Hispanic Black|10.55|6.35|4.19|Short gestation and low birth weight|196.4|2\nnon-Hispanic American Indian or Alaska Native|7.46|3.83|3.67|Congenital malformations|134.0|1\nPuerto Rican|6.05|3.93|2.13|Short gestation and low birth weight|108.9|2","metadata":{"State-Gated Retrieval":["Retain only groups that are separately listed in the 2021 U.S. infant mortality statistics, have a full-year infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death.","For each qualifying group, provide the infant rate, neonatal rate, postneonatal rate, top cause, cause rate, and the rank of that cause among all infant causes.","The leading cause must be determined by a group-level leading-cause query and verified for availability using notes/reliability markers."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["infant-mortality queries yield group-level overall, neonatal, and postneonatal rates for reportable mother race/Hispanic-origin groups","leading-cause queries and reliability notes yield each eligible group's top cause, cause-specific rate, and U.S. rank","final rows are produced only after the eligible-group set is rebuilt using both overall-rate and cause-specific-identifiability criteria"],"control_dependency":["groups above the U.S. overall rate cannot be accepted until cause-specific reliability checks are run, which removes NHOPI","leading cause must be queried at the group level rather than inherited from an all-infants cause table","the cause-rate multiplier must be defined as per 100,000 live births before downstream ranking/output"],"freeze":{"historical_window":"2021 U.S. infant mortality by mother race and Hispanic origin, including the group-level leading-cause tables and reliability notes"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Retain only groups that are separately listed in the 2021 U.S. infant mortality statistics, have a full-year infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death.","For each qualifying group, provide the infant rate, neonatal rate, postneonatal rate, top cause, cause rate, and the rank of that cause among all infant causes.","The leading cause must be determined by a group-level leading-cause query and verified for availability using notes/reliability markers."],"exclusion_conditions":["Exclude groups that, despite having a full-year mortality rate above the U.S. overall rate, cannot provide a clearly identifiable leading cause due to cause-specific reliability issues.","Exclude results that only inherit the top cause from the all-infants cause table without performing a group-level leading-cause query.","Exclude results where the cause_rate uses an incorrect rate multiplier and is not read at the per-100,000-live-births denominator."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"required literal first row `group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank`","schema":["group","infant_rate","neonatal_rate","postneonatal_rate","top_cause","cause_rate","us_rank"],"sorting_or_selection":"infant_rate descending","rate_fields":"infant_rate, neonatal_rate, and postneonatal_rate are per 1,000 live births; cause_rate is per 100,000 live births, but all four are emitted as plain numbers without unit text","top_cause":"emit the short cause label used in the oracle, not an expanded prose description","us_rank":"emit the integer rank of that same cause in the overall infant leading-cause list"}}} diff --git a/constraint_hf.jsonl b/constraint_hf.jsonl new file mode 100644 index 0000000000000000000000000000000000000000..6f62150e9a1133dd12d41040e59de5936f3b9db0 --- /dev/null +++ b/constraint_hf.jsonl @@ -0,0 +1,50 @@ +{"task_id":"arxiv_001","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"I am organizing the research trajectory of dataset distillation and dataset condensation on arXiv from 2019 to 2021, aiming to identify machine learning papers that discuss replacing large-scale training sets with a small number of synthetic training data points. Search arXiv records from 2019 to 2021 for both the phrases \"dataset distillation\" and \"dataset condensation\". Retain only entries whose primary category is Machine Learning; do not include records that are only cross-listed into Machine Learning by other primary-category papers. From these, further select papers that had a version update in the calendar year following their initial submission and whose current arXiv record still clearly indicates a subsequent publication venue. Finally, output a table sorted by v1 submitted in ascending order, with columns: arXiv ID, term family, cue location, v1 submitted, first next-year version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying items exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Finally, output a table sorted by v1 submitted in ascending order, with columns: arXiv ID, term family, cue location, v1 submitted, first next-year version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying items exist, output NONE.","oracle_answer":"arXiv ID|term family|cue location|v1 submitted|first next-year version|date of that version|primary category|publication-trail source|current publication clue\n1910.02551|Distillation|Title|2019-10-06|v3|2020-05-05|cs.LG|Related DOI|10.1109/IJCNN52387.2021.9533769\n2011.00050|Distillation|Abstract-only|2020-10-30|v2|2021-03-02|cs.LG|Comments|Accepted to ICLR 2021\n2107.13034|Distillation|Title|2021-07-27|v3|2022-01-17|cs.LG|Comments|NeurIPS 2021\n2110.04181|Condensation|Title|2021-10-08|v2|2022-04-21|cs.LG|Journal reference|Proceedings of the IEEE/CVF Winter Conference on Applications of Computer Vision 2023 (WACV)","metadata":"{\"State-Gated Retrieval\":[\"Only include arXiv records where v1 submitted falls between 2019-01-01 and 2021-12-31.\",\"The title or abstract must explicitly use a phrase from the \\\"dataset distillation\\\" or \\\"dataset condensation\\\" family, and the semantics must refer to replacing large-scale training sets with a small number of synthetic training data points.\",\"The current primary category must be cs.LG. Do not include records that are only cross-listed into Machine Learning by other primary-category papers.\",\"The paper must have a version update in the calendar year following its initial submission, and the current record must still clearly indicate a subsequent publication venue.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Root searches yield candidate arXiv IDs\",\"Each candidate abstract page yields primary category, v1 date, first next-year version, cue location, and publication-trail source\",\"Answer rows are produced only after deduplication and detail-page validation\"],\"control_dependency\":[\"Records must be filtered by original submission year, with per-record validation that a next-calendar-year version exists\",\"Cross-listed-only hits must be excluded, and the current primary category must be validated on abstract pages\",\"Searches must cover both Title and Abstract because valid distillation hits can appear only in the abstract\",\"Topic matches without a current publication trail still fail until the Comments, Journal reference, or Related DOI field is checked on the record page\"],\"freeze\":{\"historical_window\":\"v1 year in {2019, 2020, 2021}\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only include arXiv records where v1 submitted falls between 2019-01-01 and 2021-12-31.\",\"The title or abstract must explicitly use a phrase from the \\\"dataset distillation\\\" or \\\"dataset condensation\\\" family, and the semantics must refer to replacing large-scale training sets with a small number of synthetic training data points.\",\"The current primary category must be cs.LG. Do not include records that are only cross-listed into Machine Learning by other primary-category papers.\",\"The paper must have a version update in the calendar year following its initial submission, and the current record must still clearly indicate a subsequent publication venue.\"],\"exclusion_conditions\":[\"Exclude records whose current primary category is not cs.LG and are only cross-listed to cs.LG.\",\"Exclude records where the title or abstract contains the words \\\"distillation\\\" or \\\"condensation\\\" but does not correspond to the dataset distillation or dataset condensation research line.\",\"Exclude records that have no next-calendar-year version update, or whose current record contains no clearly visible publication clue.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"required literal first row shown in the oracle\",\"schema\":[\"arXiv ID\",\"term family\",\"cue location\",\"v1 submitted\",\"first next-year version\",\"date of that version\",\"primary category\",\"publication-trail source\",\"current publication clue\"],\"dedup_key\":\"bare arXiv ID without version suffix\",\"date_format\":\"YYYY-MM-DD\",\"term_family_extraction\":{\"allowed_families\":[\"Distillation\",\"Condensation\"],\"tie_break\":\"if both families appear, prefer the title hit; if both appear only in the abstract, keep the first abstract occurrence\"},\"cue_location\":{\"Title\":\"qualifying cue appears only in the title\",\"Abstract-only\":\"qualifying cue appears only in the abstract\",\"Title + Abstract\":\"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name\"},\"publication_trail_source\":[\"Comments\",\"Journal reference\",\"Related DOI\"],\"current_publication_clue\":\"keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue\",\"sorting_or_selection\":{\"primary\":\"v1 submitted ascending\",\"secondary\":\"arXiv ID ascending\"},\"stop_condition\":[\"all four corrected result pages are exhausted\",\"all unique candidate IDs are opened to abstract-page depth\",\"for every surviving candidate, the abstract page, current browse context, and publication-trail fields are checked before emitting the final ordered table\"]}}","all_involved_urls":"null"} +{"task_id":"arxiv_002","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":10,"instruction":"I am compiling a reading list of 2022 research on reasoning prompts for large language models. I want to find arXiv papers whose first version was submitted in 2022 and that explicitly focus on chain-of-thought or self-consistency reasoning methods. Start with arXiv records first submitted in 2022. First, check whether the title or abstract explicitly contains clues related to chain-of-thought or self-consistency. Then, retain only papers whose primary category is Computation and Language; do not include records that are only cross-listed from other primary categories. Next, verify that these papers actually had a version update in 2023, and confirm that the current arXiv record's comments field clearly indicates subsequent publication information. Finally, output a table sorted in ascending order by the date of each paper's earliest 2023 version update, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2023 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Finally, output a table sorted in ascending order by the date of each paper's earliest 2023 version update, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2023 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.","oracle_answer":"arXiv ID|cue family|cue location|v1 submitted|first 2023 version|date of that version|primary category|publication clue\n2210.01240|Chain-of-thought|Title + Abstract|2022-10-03|v2|2023-01-25|cs.CL|Published as a conference paper at ICLR 2023\n2205.11916|Chain-of-thought|Abstract-only|2022-05-24|v4|2023-01-29|cs.CL|Accepted to NeurIPS2022\n2203.11171|Self-consistency; Chain-of-thought|Title + Abstract|2022-03-21|v4|2023-03-07|cs.CL|Published at ICLR 2023; camera ready version at ICLR 2023\n2210.03629|Chain-of-thought|Abstract-only|2022-10-06|v3|2023-03-10|cs.CL|v3 is the ICLR camera ready version\n2210.03350|Chain-of-thought|Abstract-only|2022-10-07|v2|2023-05-23|cs.CL|To appear at Findings of EMNLP 2023\n2212.10001|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-01|cs.CL|ACL-23 Camera Ready\n2212.08061|Chain-of-thought|Abstract-only|2022-12-15|v2|2023-06-04|cs.CL|ACL 2023 Main Conference\n2212.10071|Chain-of-thought|Abstract-only|2022-12-20|v2|2023-06-13|cs.CL|ACL 2023 camera-ready\n2212.10509|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-23|cs.CL|ACL'23 Camera Ready\n2211.12588|Chain-of-thought; Self-consistency|Abstract-only|2022-11-22|v4|2023-10-23|cs.CL|Published at TMLR 2023","metadata":"{\"State-Gated Retrieval\":[\"Only include arXiv papers whose v1 was submitted in 2022.\",\"The title or abstract must explicitly contain clues related to chain-of-thought or self-consistency.\",\"The current primary category must be cs.CL; do not include records that are only cross-listed from other primary categories.\",\"Must have had a version update in 2023, and the current comments field must clearly indicate subsequent publication information.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"root searches yield candidate arXiv IDs\",\"each candidate abstract page yields primary category, v1 date, first 2023 version, comments/publication clue\",\"answer rows are produced only after deduplication and detail-page validation\"],\"control_dependency\":[\"searches must cover both Title and Abstract fields because valid rows can appear only in the abstract\",\"cross-listed hits whose primary category is not cs.CL must be excluded, and the primary category must be validated on the abstract page\",\"topic-matched hits must be validated against a current Comments publication clue before they can be accepted\",\"2023 candidates must be identified by original submission year and full version-history checks, rather than by latest-date proxies\"],\"freeze\":{\"historical_window\":\"v1 submitted in 2022; version-history event in 2023\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only include arXiv papers whose v1 was submitted in 2022.\",\"The title or abstract must explicitly contain clues related to chain-of-thought or self-consistency.\",\"The current primary category must be cs.CL; do not include records that are only cross-listed from other primary categories.\",\"Must have had a version update in 2023, and the current comments field must clearly indicate subsequent publication information.\"],\"exclusion_conditions\":[\"Exclude records whose current primary category is not cs.CL, even if they appear in relevant search results.\",\"Exclude records that contain only vague abbreviations or weakly related hints, but whose title and abstract lack explicit CoT/self-consistency semantics.\",\"Exclude records that have no 2023 version update, or whose current record lacks a direct publication clue.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"required literal first row shown in the oracle\",\"schema\":[\"arXiv ID\",\"cue family\",\"cue location\",\"v1 submitted\",\"first 2023 version\",\"date of that version\",\"primary category\",\"publication clue\"],\"dedup_key\":\"bare arXiv ID without version suffix\",\"date_format\":\"YYYY-MM-DD\",\"cue_family\":[\"Chain-of-thought\",\"Self-consistency\"],\"cue_location\":{\"Title\":\"qualifying cue appears only in the title\",\"Abstract-only\":\"qualifying cue appears only in the abstract\",\"Title + Abstract\":\"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name\"},\"publication_clue\":{\"source\":\"Comments field only\",\"extraction\":\"keep the shortest phrase that still preserves the current publication-status clue\"},\"sorting_or_selection\":{\"primary\":\"date of the earliest 2023 version ascending\",\"secondary\":\"arXiv ID ascending\"},\"stop_condition\":[\"all corrected result pages are exhausted\",\"all unique candidate IDs are opened to abstract-page depth\",\"for every surviving candidate, the current browse context, Comments field, and full Submission history are checked before emitting the final ordered table\"]}}","all_involved_urls":"null"} +{"task_id":"arxiv_003","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"I am compiling a reading list of early vision Transformer research. Identify arXiv papers whose first version was submitted in Q4 2020 and whose title or abstract explicitly uses vision- or image-domain Transformer terminology. First, filter for papers with a first-submission date in Q4 2020. Then check whether the title or abstract explicitly contains vision- or image-related Transformer expressions. Retain only papers whose primary category is Computer Vision and Pattern Recognition. Next, confirm that the paper had at least one version update in 2021, and check whether the current arXiv record clearly indicates subsequent publication information. Finally, output a table sorted in ascending order by the date of each paper's earliest 2021 version. Columns: arXiv ID, cue family, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying items exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Output a table sorted in ascending order by the date of each paper's earliest 2021 version. Columns: arXiv ID, cue family, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying items exist, output NONE.","oracle_answer":"arXiv ID|cue family|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication-trail source|current publication clue\n2101.01097|Vision Transformer|Abstract-only|2020-12-30|v2|2021-01-08|cs.CV|Journal reference|IEEE Int. Conf. on Image Processing (ICIP) 2021\n2012.12556|Visual Transformer; Vision Transformer|Title + Abstract|2020-12-23|v2|2021-01-15|cs.CV|Comments; Related DOI|Accepted by TPAMI 2022; 10.1109/TPAMI.2022.3152247\n2012.00364|Image Processing Transformer|Title + Abstract|2020-12-01|v3|2021-05-28|cs.CV|Comments|CVPR 2021\n2011.08019|Vision Transformer|Title + Abstract|2020-11-16|v2|2021-06-02|cs.CV|Comments|Accepted for Publication in IJCB2021\n2010.11929|Vision Transformer|Abstract-only|2020-10-22|v2|2021-06-03|cs.CV|Comments|ICLR camera-ready version","metadata":"{\"State-Gated Retrieval\":[\"Only include arXiv papers whose v1 submitted date falls in Q4 2020.\",\"The title or abstract must explicitly contain vision- or image-domain Transformer-related expressions.\",\"The current primary category must be cs.CV.\",\"The paper must have had a version update in 2021, and the current record must clearly indicate a subsequent publication venue.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"root searches yield candidate arXiv IDs\",\"candidate abstract pages yield v1 submitted date, first 2021 version, primary category, cue location, and publication-trail source\",\"answer rows depend on deduplication plus detail-page validation\"],\"control_dependency\":[\"searches must cover both Title and Abstract because valid positives can appear only in the abstract\",\"candidate eligibility must be determined by the original-submission date window rather than by arXiv-ID or announcement intuition\",\"candidate filtering must use full Submission-history validation rather than most-recent-submission filtering\",\"searches must use the broader semantic cue state rather than a ViT-only entry point, because ViT-only hits can be false positives\",\"publication-trail false positives still require Comments / Journal reference / Related DOI validation before final inclusion\"],\"freeze\":{\"historical_window\":\"v1 submitted from 2020-10-01 through 2020-12-31; version-history event in 2021\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only include arXiv papers whose v1 submitted date falls in Q4 2020.\",\"The title or abstract must explicitly contain vision- or image-domain Transformer-related expressions.\",\"The current primary category must be cs.CV.\",\"The paper must have had a version update in 2021, and the current record must clearly indicate a subsequent publication venue.\"],\"exclusion_conditions\":[\"Exclude records whose current primary category is not cs.CV and are only cross-listed.\",\"Exclude records that contain only weak cues such as Transformer or ViT, but whose title and abstract lack explicit vision- or image-domain expressions.\",\"Exclude records that had no version update in 2021, or whose current record contains no direct publication clue.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"required literal first row shown in the oracle\",\"schema\":[\"arXiv ID\",\"cue family\",\"cue location\",\"v1 submitted\",\"first 2021 version\",\"date of that version\",\"primary category\",\"publication-trail source\",\"current publication clue\"],\"dedup_key\":\"bare arXiv ID without version suffix\",\"date_format\":\"YYYY-MM-DD\",\"cue_family_extraction\":\"record every qualifying family actually present and join multiple families with `; ` in the emitted field\",\"cue_location\":{\"Title\":\"qualifying cue appears only in the title\",\"Abstract-only\":\"qualifying cue appears only in the abstract\",\"Title + Abstract\":\"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name\"},\"publication_trail_source\":[\"Comments\",\"Journal reference\",\"Related DOI\"],\"current_publication_clue\":\"keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue\",\"sorting_or_selection\":{\"primary\":\"date of the earliest 2021 version ascending\",\"secondary\":\"arXiv ID ascending\"},\"stop_condition\":[\"all corrected result pages are exhausted\",\"all unique candidate IDs are opened to abstract-page depth\",\"for every surviving candidate, the abstract page, current browse context, Comments field, Journal reference, Related DOI, and full Submission history are checked before emitting the final ordered table\"]}}","all_involved_urls":"null"} +{"task_id":"arxiv_004","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"I am compiling a reading list of certified robustness defense research from the first half of 2020. I want to find arXiv papers whose first version was submitted between January and June 2020 and whose title or abstract explicitly focuses on smoothed classifiers, randomized smoothing and its variants, certified defenses against backdoor or poisoning attacks, or partition aggregation. Start with arXiv records whose first submission date falls between January and June 2020. Check whether the title or abstract explicitly mentions randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor/poisoning, or partition aggregation. Then retain only papers whose primary category is Machine Learning; do not include records that are only cross-listed from other primary categories. Next, confirm that these papers actually had a version update in 2021, and check whether the current arXiv record clearly indicates formal publication or acceptance information. Finally, output a table sorted by the date of each paper's earliest 2021 version in ascending order, with columns: arXiv ID, defense family, threat/topic cue, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Finally, output a table sorted by the date of each paper's earliest 2021 version in ascending order, with columns: arXiv ID, defense family, threat/topic cue, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.","oracle_answer":"arXiv ID|defense family|threat/topic cue|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication clue\n2002.10733|De-randomized smoothing; Randomized smoothing|patch attacks|Title + Abstract|2020-02-25|v3|2021-01-08|cs.LG|NeurIPS 2020\n2006.04062|Smoothed classifiers; Randomized smoothing|certified L2 robustness|Title + Abstract|2020-06-07|v4|2021-01-08|cs.LG|NeurIPS 2020\n2003.08904|RAB; Randomized smoothing|backdoor attacks|Title + Abstract|2020-03-19|v4|2021-02-26|cs.LG|IEEE Symposium on Security and Privacy 2023\n2006.14768|Deep Partition Aggregation|general poisoning attacks; label-flipping poisoning attacks|Title + Abstract|2020-06-26|v2|2021-03-18|cs.LG|ICLR 2021\n2002.12398|Transformation-specific smoothing; Randomized smoothing|semantic transformations|Title + Abstract|2020-02-27|v4|2021-09-17|cs.LG|2021 ACM SIGSAC Conference on Computer and Communications Security (CCS '21)","metadata":"{\"State-Gated Retrieval\":[\"Only include arXiv papers whose v1 submission date falls between 2020-01-01 and 2020-06-30.\",\"The title or abstract must explicitly focus on randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor or poisoning attacks, or partition aggregation.\",\"The current primary category must be cs.LG.\",\"The paper must have had a version update in 2021, and the current record must clearly indicate formal publication or acceptance information.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"root searches yield candidate arXiv IDs\",\"candidate abstract pages yield v1 date, primary category, full Submission history, cue location, and current publication clue\",\"final rows depend on deduplication plus detail-page validation\"],\"control_dependency\":[\"candidate filtering must use the original-submission window together with full 2021 version-history validation, because valid rows can have later newest versions\",\"cross-listed hits whose primary category is not the target category must be excluded, with category validation on detail pages\",\"searches must cover the broader certified-defense family, including partition-aggregation and backdoor/poisoning variants, rather than smoothing-only entries\",\"topic+venue hits must be confirmed by detail-history validation that a 2021 version actually exists\"],\"freeze\":{\"historical_window\":\"v1 submitted from 2020-01-01 through 2020-06-30; version-history event in 2021\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only include arXiv papers whose v1 submission date falls between 2020-01-01 and 2020-06-30.\",\"The title or abstract must explicitly focus on randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor or poisoning attacks, or partition aggregation.\",\"The current primary category must be cs.LG.\",\"The paper must have had a version update in 2021, and the current record must clearly indicate formal publication or acceptance information.\"],\"exclusion_conditions\":[\"Exclude records whose current primary category is not cs.LG, even if semantically related.\",\"Exclude records that are only broadly related to robustness, defense, or backdoor/poisoning but do not meet the required certified-defense semantics.\",\"Exclude records that have no version update in 2021 or no current publication clue.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"required literal first row shown in the oracle\",\"schema\":[\"arXiv ID\",\"defense family\",\"threat/topic cue\",\"cue location\",\"v1 submitted\",\"first 2021 version\",\"date of that version\",\"primary category\",\"publication clue\"],\"dedup_key\":\"bare arXiv ID without version suffix\",\"date_format\":\"YYYY-MM-DD\",\"defense_family_extraction\":\"record every qualifying defense family actually present and join multiple families with `; ` in the emitted field\",\"threat_topic_cue\":\"keep the shortest qualifying threat or topic cue that justifies inclusion\",\"cue_location\":{\"Title\":\"qualifying cue appears only in the title\",\"Abstract-only\":\"qualifying cue appears only in the abstract\",\"Title + Abstract\":\"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name\"},\"publication_clue\":\"keep the shortest phrase that still preserves venue or publication-status information\",\"sorting_or_selection\":{\"primary\":\"date of the earliest 2021 version ascending\",\"secondary\":\"arXiv ID ascending\"},\"stop_condition\":[\"all corrected result pages are exhausted\",\"all unique candidate IDs are opened to abstract-page depth\",\"for every surviving candidate, the abstract page, current browse context, Comments field, and full Submission history are checked before emitting the final ordered table\"]}}","all_involved_urls":"null"} +{"task_id":"census_001","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":20,"instruction":"Using the 2014–2018 American Community Survey 5-year estimates, identify counties with limited internet access, a high share of seniors living alone, weak transportation conditions, and low income. Scope the analysis to North Carolina counties from this dataset and use the North Carolina statewide values from the same release as the comparison baseline. First, select counties with at least 4,000 households lacking internet access. Then, retain only counties that simultaneously meet all of the following conditions: share of households without internet access higher than the statewide share; share of households with a householder aged 65 or older living alone higher than the statewide share; share of households without a vehicle higher than the statewide share; and median household income lower than the statewide median. Finally, output all qualifying counties as a single line, sorted alphabetically by county name. Each county should be formatted as County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome, with counties separated by commas. Percentage fields should be given to three decimal places without a percent sign.","start_url":"https://www.census.gov/data.html","output_format":"Output all qualifying counties as a single line, sorted alphabetically by county name. Each county should be formatted as County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome, with counties separated by commas. Percentage fields should be given to three decimal places without a percent sign.","oracle_answer":"Beaufort County|5988|30.986|16.083|7.664|43688,Bladen County|4194|30.026|13.681|10.417|32378,Cleveland County|11599|31.449|12.469|7.825|40393,Columbus County|7371|33.045|15.148|7.958|36398,Duplin County|7574|34.773|14.370|7.424|38850,Edgecombe County|7454|34.879|13.720|11.225|35516,Halifax County|7575|35.873|14.657|11.565|34251,Lenoir County|4923|21.292|15.614|11.699|38387,Nash County|8617|23.467|13.597|7.917|48362,Richmond County|5193|28.001|13.706|9.269|36091,Robeson County|19814|43.103|11.312|9.854|33679,Rockingham County|9938|26.714|14.166|7.164|42490,Rutherford County|7583|28.783|16.033|6.335|40347,Sampson County|8216|34.907|14.088|7.686|39068,Scotland County|4971|37.909|13.910|11.470|35617,Surry County|7595|26.203|13.762|6.779|41068,Vance County|5131|30.444|12.347|11.600|37282,Wayne County|9709|20.163|11.742|8.456|42192,Wilkes County|7046|24.849|14.773|5.992|40829,Wilson County|7652|23.817|13.322|9.540|42850","metadata":"{\"State-Gated Retrieval\":[\"Use only North Carolina county data from the 2014-2018 American Community Survey 5-year estimates, and use the North Carolina statewide values from the same release as the comparison baseline.\",\"Retain only counties with at least 4,000 households lacking internet access, and where the share of households without internet access, the share of households with a householder aged 65+ living alone, and the share of households without a vehicle are all higher than the statewide shares, and the median household income is lower than the statewide median.\",\"Output the final results sorted alphabetically by county name, retaining the six required fields.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the 2014-2018 ACS 5-year product and North Carolina county geography yield the full county candidate set plus the statewide baseline row\",\"the relevant ACS tables yield no-internet households, senior-living-alone share, no-vehicle share, and median household income for each county and the state baseline\",\"final rows are produced only after the 5-year product/geography setup is fixed consistently and the full county filtering chain is executed from B28002 through the downstream filters\"],\"control_dependency\":[\"the 2018 ACS 5-year Detailed Tables product must be used instead of the 2018 ACS 1-year product\",\"county coverage must be established under one consistent product-and-geography setup rather than by piecemeal fixes within the current table\",\"all downstream county comparisons must use the same 5-year statewide baseline and the same all-counties geography\"],\"freeze\":{\"historical_window\":\"2014-2018 American Community Survey 5-year estimates for North Carolina counties, using the North Carolina statewide row from the same release as the comparison baseline\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Use only North Carolina county data from the 2014-2018 American Community Survey 5-year estimates, and use the North Carolina statewide values from the same release as the comparison baseline.\",\"Retain only counties with at least 4,000 households lacking internet access, and where the share of households without internet access, the share of households with a householder aged 65+ living alone, and the share of households without a vehicle are all higher than the statewide shares, and the median household income is lower than the statewide median.\",\"Output the final results sorted alphabetically by county name, retaining the six required fields.\"],\"exclusion_conditions\":[\"Exclude results that incorrectly use the 2018 ACS 1-Year Estimates Detailed Tables or any other non-2014-2018 5-year release.\",\"Exclude results that do not use the North Carolina statewide row from the same release as the comparison baseline.\",\"Exclude any county that does not meet any one of the thresholds or statewide comparison conditions.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"County\",\"NoInternetHH\",\"NoInternetRatePct\",\"SeniorLivingAloneSharePct\",\"NoVehicleRatePct\",\"MedianIncome\"],\"county\":\"use the county display name including the word `County` and excluding a trailing state suffix\",\"dedup_key\":\"county FIPS / GEOID\",\"percentage_fields\":\"all percentage fields are plain numbers with exactly three decimal places and no percent sign\",\"numeric_fields\":\"household counts and median income are emitted as plain integers without commas\",\"sorting_or_selection\":\"county name alphabetical ascending\",\"stop_condition\":[\"the North Carolina statewide threshold is fixed once from the designated table\",\"all 100 North Carolina counties are covered under the same table/product settings\",\"every surviving county is validated against all four required tables before emission\"]}}","all_involved_urls":"null"} +{"task_id":"census_002","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"Using the 2015–2019 American Community Survey 5-year estimates, identify New Mexico counties that simultaneously have a large renter population, significant language barriers, limited internet access, transportation difficulties, low income, and rental stress. Use the New Mexico county-level data from this release and the New Mexico statewide values from the same release as the comparison baseline. First, retain counties with at least 2,500 renter households and at least 500 limited-English-proficient households. Then, keep only counties that meet all of the following conditions: the share of limited-English-proficient households is higher than the statewide share; the share of households with no internet access is higher than the statewide share; the share of households with no vehicle is higher than the statewide share; and the median household income is lower than the statewide median. Next, evaluate the rental housing stress indicators for renter households. Retain only counties that meet at least one of the following: the share of renter households with a rent-to-income ratio of 35% or more is higher than the statewide share, or the share of renter households with more than one occupant per room is higher than the statewide share. If both conditions are met, indicate both. Finally, output all qualifying counties as a single line, sorted alphabetically by county name. Each county should be formatted as County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath, with counties separated by commas. StressPath must be RENT, CROWD, or BOTH. Percentage fields should have three decimal places and no percent sign.","start_url":"https://data.census.gov/advanced","output_format":"Output all qualifying counties as a single line, sorted alphabetically by county name. Each county should be formatted as County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath, with counties separated by commas. StressPath must be RENT, CROWD, or BOTH. Percentage fields should have three decimal places and no percent sign.","oracle_answer":"Doña Ana County|28729|7883|10.127|22.612|6.079|44.172|6.391|40973|BOTH,Luna County|3482|1109|12.455|34.030|8.165|42.700|1.407|29360|RENT,McKinley County|6090|1610|7.688|50.587|10.978|27.568|16.256|33834|CROWD,San Miguel County|3443|1200|10.337|38.470|7.684|47.376|2.440|30946|RENT,Taos County|2854|652|5.387|28.844|5.726|48.823|4.555|38329|RENT","metadata":"{\"State-Gated Retrieval\":[\"Use only the 2015-2019 American Community Survey 5-year estimates for New Mexico counties, and use the New Mexico statewide values from the same release as the comparison baseline.\",\"Candidate counties must have at least 2,500 renter households and at least 500 limited-English-proficient households. Additionally, the LEP share, no-internet share, and no-vehicle share must all be higher than the statewide shares, and the median household income must be lower than the statewide median.\",\"LEPHH must be computed by summing all four limited-English language groups from C16002. Finally, retain only counties where at least one of Severe Rent Burden or Crowded Renter is higher than the statewide value, and write StressPath according to the rule.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the 2015-2019 ACS 5-year county geography yields New Mexico county candidates and the statewide baseline row\",\"C16002 and the downstream housing/income tables yield LEPHH, LEP share, no-internet share, no-vehicle share, severe rent burden, crowded-renter share, and median income for counties and the state baseline\",\"final rows are produced only after the LEPHH numerator is computed from all four limited-English language groups and the downstream stress-path filters are applied\"],\"control_dependency\":[\"the LEPHH numerator must be computed from all four limited-English language groups in C16002 rather than from Spanish-only counts\",\"county eligibility and StressPath labels must be determined from the LEPHH measure and statewide LEP baseline defined under that full four-group calculation\",\"the RENT / CROWD / BOTH classification must be determined by evaluating the same county set against both downstream housing-stress branches\"],\"freeze\":{\"historical_window\":\"2015-2019 American Community Survey 5-year estimates for New Mexico counties, using the New Mexico statewide row from the same release as the comparison baseline\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Use only the 2015-2019 American Community Survey 5-year estimates for New Mexico counties, and use the New Mexico statewide values from the same release as the comparison baseline.\",\"Candidate counties must have at least 2,500 renter households and at least 500 limited-English-proficient households. Additionally, the LEP share, no-internet share, and no-vehicle share must all be higher than the statewide shares, and the median household income must be lower than the statewide median.\",\"LEPHH must be computed by summing all four limited-English language groups from C16002. Finally, retain only counties where at least one of Severe Rent Burden or Crowded Renter is higher than the statewide value, and write StressPath according to the rule.\"],\"exclusion_conditions\":[\"Exclude results that treat Spanish-only limited-English households as the entire LEPHH count.\",\"Exclude results that do not use the statewide baseline from the same release or that do not recalculate LEPHH/LEPSharePct/LEPShare_state.\",\"Exclude counties that do not meet the final stress-path condition of RENT, CROWD, or BOTH.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"County\",\"RenterHH\",\"LEPHH\",\"LEPSharePct\",\"NoInternetPct\",\"NoVehiclePct\",\"SevereRentBurdenPct\",\"CrowdedRenterPct\",\"MedianIncome\",\"StressPath\"],\"county\":\"use the county display name including the word `County` and excluding a trailing state suffix\",\"dedup_key\":\"county FIPS / GEOID\",\"LEPHH\":\"sum the four designated limited-English-proficient renter-household cells before emitting the integer total\",\"percentage_fields\":\"all percentage fields are plain numbers with exactly three decimal places and no percent sign\",\"numeric_fields\":\"household counts and median income are emitted as plain integers without commas\",\"StressPath\":{\"allowed_values\":[\"RENT\",\"CROWD\",\"BOTH\"],\"rule\":\"emit BOTH only when both the severe-rent-burden and crowded-renter signals survive; otherwise emit the single surviving label\"},\"sorting_or_selection\":\"county name alphabetical ascending\",\"stop_condition\":[\"all candidate counties are validated under the same geography and product settings\",\"the renter scope and LEP aggregation are checked before the final line is emitted\"]}}","all_involved_urls":"null"} +{"task_id":"census_003","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"I am compiling a pre-pandemic county screening list for the California Department of Education to identify counties where, during annual school meal applications and parent data updates, schools cannot rely solely on English online portals and must still provide paper materials and in-person assistance. Use California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline. First, select counties with a population aged 5–17 of at least 75,000. Then, retain counties with at least 2,000 individuals aged 5–17 who speak English \"not well\" or \"not at all\" and whose share of the 5–17 population exceeds the statewide share. Next, check these counties' digital access and income conditions: the share of households with no internet access must exceed the statewide share, and the median household income must be below the statewide median. Finally, among three offline support signals, retain counties where at least two exceed the statewide share: the share of households with no vehicle, the share of minors in households that received SSI, cash public assistance, Food Stamps, or SNAP in the past 12 months, and the share of renter-occupied housing units with more than one occupant per room. Output all qualifying counties in a single line, sorted alphabetically by county name. Each county should be formatted as County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath, with counties separated by commas. SupportPath uses only the three labels BENEFITS, CROWD, and MOBILITY: the public assistance signal corresponds to BENEFITS, the crowded housing signal corresponds to CROWD, and the no-vehicle signal corresponds to MOBILITY. If multiple labels apply, join them with + in the fixed order BENEFITS+CROWD+MOBILITY.","start_url":"https://data.census.gov/advanced","output_format":"Output all qualifying counties in a single line, sorted alphabetically by county name. Each county should be formatted as County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath, with counties separated by commas. SupportPath uses only the three labels BENEFITS, CROWD, and MOBILITY: the public assistance signal corresponds to BENEFITS, the crowded housing signal corresponds to CROWD, and the no-vehicle signal corresponds to MOBILITY. If multiple labels apply, join them with + in the fixed order BENEFITS+CROWD+MOBILITY.","oracle_answer":"Fresno County|200205|5127|2.561|20.588|8.686|46.388|13.967|48730|BENEFITS+CROWD+MOBILITY,Kern County|185802|4130|2.223|21.739|7.058|37.285|14.394|50826|BENEFITS+CROWD,Los Angeles County|1641669|37540|2.287|16.338|9.204|27.238|16.741|61015|BENEFITS+CROWD+MOBILITY,Tulare County|104542|2703|2.586|25.738|6.274|49.347|14.535|44871|BENEFITS+CROWD","metadata":"{\"State-Gated Retrieval\":[\"Use only California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline.\",\"Retain only counties with a population aged 5–17 of at least 75,000, a SchoolAgeLEP of at least 2,000 with a share exceeding the statewide share, a no-internet share exceeding the statewide share, and a median household income below the statewide median.\",\"SchoolAgeLEP must be the sum of the eight \\\"not well\\\" and \\\"not at all\\\" cells across the four major language groups in B16004. The final county must also have at least two of the three offline support signals (Mobility, Benefits, Crowd) exceeding the statewide share.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"The 2013–2017 ACS 5-year county geography yields California county candidates and the statewide baseline row.\",\"B16004 and the downstream access/income/support tables yield SchoolAgeLEP, no-internet share, no-vehicle share, child-benefit share, crowded-renter share, and median income for counties and the statewide baseline.\",\"Final rows are produced only after the SchoolAgeLEP numerator is computed from all eight 1980-target language cells and the downstream support-path branches are applied.\"],\"control_dependency\":[\"The SchoolAgeLEP numerator must be computed from the full eight-cell language set in B16004 rather than from only two Spanish LEP cells.\",\"County eligibility and SupportPath labels must be determined from the LEP numerator and candidate set defined under that full eight-cell calculation.\",\"The BENEFITS / CROWD / MOBILITY path labels must be determined by applying all three downstream support branches to the same county set.\"],\"freeze\":{\"historical_window\":\"2013–2017 American Community Survey 5-year estimates for California counties, using the California statewide row from the same release as the comparison baseline.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Use only California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline.\",\"Retain only counties with a population aged 5–17 of at least 75,000, a SchoolAgeLEP of at least 2,000 with a share exceeding the statewide share, a no-internet share exceeding the statewide share, and a median household income below the statewide median.\",\"SchoolAgeLEP must be the sum of the eight \\\"not well\\\" and \\\"not at all\\\" cells across the four major language groups in B16004. The final county must also have at least two of the three offline support signals (Mobility, Benefits, Crowd) exceeding the statewide share.\"],\"exclusion_conditions\":[\"Exclude results that only take the two Spanish LEP rows and do not combine all eight target cells.\",\"Exclude results that do not re-run the B28011, B19013, B08201, B09010, and B25014 branches.\",\"Exclude counties whose final SupportPath does not have at least two signals exceeding the statewide share.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"County\",\"SchoolAgePop\",\"SchoolAgeLEP\",\"LEPSharePct\",\"NoInternetPct\",\"NoVehiclePct\",\"ChildBenefitSharePct\",\"CrowdedRenterPct\",\"MedianIncome\",\"SupportPath\"],\"county\":\"Use the county display name including the word `County` and excluding a trailing state suffix.\",\"dedup_key\":\"county FIPS / GEOID\",\"SchoolAgeLEP\":\"Sum the eight designated school-age LEP cells before emitting the integer total.\",\"percentage_fields\":\"All percentage fields are plain numbers with exactly three decimal places and no percent sign.\",\"numeric_fields\":\"Population counts and median income are emitted as plain integers without commas.\",\"SupportPath\":\"Use only BENEFITS, CROWD, and MOBILITY, and when multiple labels apply join them with `+` in the fixed order BENEFITS+CROWD+MOBILITY.\",\"sorting_or_selection\":\"County name alphabetical ascending.\",\"stop_condition\":[\"All candidate counties are validated under the same geography and product settings.\",\"The school-age LEP aggregation and all three support-signal gates are checked before the final line is emitted.\"]}}","all_involved_urls":"null"} +{"task_id":"census_004","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":7,"instruction":"Using 2012–2016 American Community Survey 5-year estimates, identify Pennsylvania counties with high senior evacuation support needs that warrant proactive in-person outreach before winter storms. Use Pennsylvania county-level data from the 2012–2016 American Community Survey 5-year estimates, with Pennsylvania statewide values from the same release as the comparison baseline. First, retain counties with a population aged 65 and over of at least 15,000. Then, among those, keep counties with at least 4,000 people aged 65 and over who have ambulatory difficulty, and whose share exceeds the statewide share. Additionally, the county median household income must be below the statewide median. Next, evaluate four evacuation support barriers: share of households with a householder aged 65+ living alone, share of households with no vehicle, share of renter households with no vehicle, and share of mobile homes among all housing units. Retain only counties where at least two of these barriers exceed the statewide values. Finally, output all qualifying counties in a single line, sorted alphabetically by county name. Each county should be formatted as County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath, with counties separated by commas. For BarrierPath, use only the labels ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE. If multiple labels apply, join them with + in the fixed order ALONE+MOBILE_HOME+NO_VEHICLE+RENTER_NO_VEHICLE.","start_url":"https://www.census.gov/data.html","output_format":"Output all qualifying counties in a single line, sorted alphabetically by county name. Each county should be formatted as County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath, with counties separated by commas. For BarrierPath, use only the labels ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE. If multiple labels apply, join them with + in the fixed order ALONE+MOBILE_HOME+NO_VEHICLE+RENTER_NO_VEHICLE.","oracle_answer":"Blair County|23013|5576|24.230|14.917|9.440|24.316|6.388|44033|ALONE+MOBILE_HOME, Cambria County|27058|6308|23.313|15.243|10.309|26.627|4.070|42917|ALONE+MOBILE_HOME+RENTER_NO_VEHICLE, Fayette County|25186|5886|23.370|14.961|9.302|22.290|10.489|40511|ALONE+MOBILE_HOME, Lycoming County|19486|4311|22.124|12.164|9.257|23.312|6.726|48731|ALONE+MOBILE_HOME, Mercer County|21537|4799|22.283|14.090|9.572|24.413|7.912|45831|ALONE+MOBILE_HOME, Philadelphia County|188185|56935|30.255|11.553|30.954|44.924|0.250|39770|NO_VEHICLE+RENTER_NO_VEHICLE, Schuylkill County|26613|6465|24.293|14.357|9.676|23.652|4.080|46573|ALONE+MOBILE_HOME","metadata":"{\"State-Gated Retrieval\":[\"Use only Pennsylvania county-level data from the 2012-2016 American Community Survey 5-year estimates, and use Pennsylvania statewide values from the same release as the comparison baseline.\",\"Retain only counties with a population aged 65 and over of at least 15,000, at least 4,000 people aged 65 and over with ambulatory difficulty and a share higher than the statewide share, and a median household income below the statewide median.\",\"The 65+ ambulatory difficulty numerator must combine the four target cells from B18105 for ages 65-74 and 75+, male and female. The final county must also have at least two of the four barriers—Alone, No Vehicle, Renter No Vehicle, Mobile Home—higher than the statewide values.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"ACS tables B01001 and B18105 yield county senior-population totals and the full 65+ ambulatory-difficulty numerator.\",\"Statewide comparison tables yield Pennsylvania baselines plus county barrier metrics for living alone, no vehicle, renter no vehicle, mobile home, and median income.\",\"Final rows are produced only after the county candidate set is defined from the full ambulatory-difficulty numerator and the downstream six-table filters are applied.\"],\"control_dependency\":[\"The ambulatory-difficulty numerator must include the full 65+ population across 65-74 and 75+ and male and female cells, rather than only the 75+ cells.\",\"Downstream county eligibility and barrier labels must be determined from the county candidate set defined under that full ambulatory numerator.\",\"The at-least-two-barriers test must compare every county metric against the same Pennsylvania statewide baselines from the same ACS release.\"],\"freeze\":{\"historical_window\":\"2012-2016 American Community Survey 5-year estimates for Pennsylvania counties, with Pennsylvania statewide baselines taken from the same release.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Use only Pennsylvania county-level data from the 2012-2016 American Community Survey 5-year estimates, and use Pennsylvania statewide values from the same release as the comparison baseline.\",\"Retain only counties with a population aged 65 and over of at least 15,000, at least 4,000 people aged 65 and over with ambulatory difficulty and a share higher than the statewide share, and a median household income below the statewide median.\",\"The 65+ ambulatory difficulty numerator must combine the four target cells from B18105 for ages 65-74 and 75+, male and female. The final county must also have at least two of the four barriers—Alone, No Vehicle, Renter No Vehicle, Mobile Home—higher than the statewide values.\"],\"exclusion_conditions\":[\"Exclude results that take only the 75 years and over ambulatory difficulty cells and mistakenly treat them as the full 65+ value.\",\"Exclude results that do not use the Pennsylvania statewide baselines from the same release.\",\"Exclude counties whose final BarrierPath does not satisfy the condition of at least two barriers higher than the statewide values.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"County\",\"SeniorPop\",\"AmbulatoryDifficulty65Plus\",\"AmbDiffPct\",\"SeniorLivingAloneSharePct\",\"NoVehiclePct\",\"RenterNoVehiclePct\",\"MobileHomePct\",\"MedianIncome\",\"BarrierPath\"],\"county\":\"Use the county display name including the word `County` and excluding a trailing state suffix.\",\"dedup_key\":\"county FIPS / GEOID\",\"percentage_fields\":\"All percentage fields are plain numbers with exactly three decimal places and no percent sign.\",\"numeric_fields\":\"Population counts and median income are emitted as plain integers without commas.\",\"BarrierPath\":\"Use only ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE. When multiple labels apply, join them with `+` in the fixed order ALONE+MOBILE_HOME+NO_VEHICLE+RENTER_NO_VEHICLE.\",\"sorting_or_selection\":\"county name alphabetical ascending\",\"stop_condition\":[\"All candidate counties are validated under the same geography and product settings.\",\"The senior ambulatory-difficulty gate and all barrier-signal gates are checked before the final line is emitted.\"]}}","all_involved_urls":"null"} +{"task_id":"climategov_001","domain":"NOAA_NCEI_CLIMATE_AT_A_GLANCE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"Screen the four South Texas climate divisions (South Central, Upper Coast, South, and Lower Valley) to identify divisions that remained near-normal to wet over two longer periods yet still had low heating demand in March 1966. Restrict the search strictly to these four divisions; use the official Texas climate-division page for their exact names and numbers.\n\nRetain only divisions that meet all three of the following criteria:\n- The 10-month Palmer Z-Index anomaly ending February 1966 must be at least -0.05.\n- The 24-month Palmer Z-Index anomaly ending December 1966 must be at least -0.10.\n- The March 1966 single-month Heating Degree Days actual value must be below 200°Df.\n\nAfter identifying qualifying divisions, sort them as follows:\n- Primary: sum of the February 1966 10-month Z anomaly and the December 1966 24-month Z anomaly, in descending order.\n- Secondary: March 1966 Heating Degree Days actual value, in ascending order.\n- Tertiary: Texas division number, in ascending order.\n\nOutput a single-line string with qualifying entries separated by commas. Each entry must follow this exact format:\n|||||\n\nThe moisture score is the sum of the February 1966 10-month Z anomaly and the December 1966 24-month Z anomaly, formatted to two decimal places. If no division qualifies, output NONE.","start_url":"https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national","output_format":"Output a single-line string with qualifying entries separated by commas. Each entry must follow this exact format:\n|||||\nThe moisture score is the sum of the February 1966 10-month Z anomaly and the December 1966 24-month Z anomaly, formatted to two decimal places. If no division qualifies, output NONE.","oracle_answer":"7|South Central|0.72|0.35|194°Df|1.07,10|Lower Valley|0.28|0.67|106°Df|0.95,9|South|0.03|0.37|148°Df|0.40","metadata":"{\"State-Gated Retrieval\":[\"Screen only within the four South Texas divisions defined on the Texas divisional page: South Central, Upper Coast, South, Lower Valley.\",\"Retain divisions that simultaneously satisfy: 1966-02 10-month Palmer Z-Index anomaly >= -0.05; 1966-12 24-month anomaly >= -0.10; 1966-03 1-month Heating Degree Days Value < 200°Df.\",\"Sort by sum of the two Z anomalies descending, then by 1966-03 HDD Value ascending, then by division number ascending.\"],\"dependency_type\":\"Data\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"The official Texas climate-division reference fixes the four South Texas division IDs and names that must be tracked across all later pages.\",\"The 1966-02 10-month Palmer Z-Index anomaly page and the 1966-12 24-month Palmer Z-Index anomaly page jointly identify the four target South Texas divisions.\",\"The 1966-03 1-month Heating Degree Days Value page supplies the last filter; final rows are produced only after intersecting the three divisional screens and then sorting by summed Z-anomaly score, HDD value, and division number.\"],\"freeze\":{\"historical_window\":\"Texas climate divisions South Central, Upper Coast, South, and Lower Valley; metrics are fixed to the 1966-02 10-month Palmer Z-Index anomaly, 1966-12 24-month anomaly, and 1966-03 1-month Heating Degree Days Value pages.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Screen only within the four South Texas divisions defined on the Texas divisional page: South Central, Upper Coast, South, Lower Valley.\",\"Retain divisions that simultaneously satisfy: 1966-02 10-month Palmer Z-Index anomaly >= -0.05; 1966-12 24-month anomaly >= -0.10; 1966-03 1-month Heating Degree Days Value < 200°Df.\",\"Sort by sum of the two Z anomalies descending, then by 1966-03 HDD Value ascending, then by division number ascending.\"],\"exclusion_conditions\":[\"Exclude any Texas divisional results outside the four specified South Texas divisions.\",\"Exclude results that misread the 1966-03 HDD page filter field as Anomaly instead of Value.\",\"Exclude any division that fails any time window or threshold condition.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"texas_division_no\",\"division_name\",\"feb_1966_10mo_z_text\",\"dec_1966_24mo_z_text\",\"mar_1966_hdd_text\",\"moisture_score\"],\"texas_division_no\":\"Canonical output uses the short Texas climate-division number; the scorer may accept an equivalent four-digit form, but the emitted oracle uses the short number.\",\"raw_text_fields\":\"The two Z-index anomaly fields and the March 1966 HDD field preserve the raw displayed text; comparison may ignore optional trailing HDD unit text such as `°Df`.\",\"moisture_score\":\"Compute as February 1966 10-month Z-index anomaly plus December 1966 24-month Z-index anomaly, formatted with exactly two decimal places.\",\"sorting_or_selection\":{\"primary\":\"moisture_score descending\",\"secondary\":\"March 1966 HDD actual value ascending after numeric normalization\",\"tertiary\":\"Texas division number ascending\"},\"eligibility_rule\":\"Each Texas division is counted once per requested window; if any required window value is missing, exclude the division.\",\"stop_condition\":[\"All candidate Texas divisions are checked under the same base period and anomaly windows.\",\"The unique ordered output string is resolved before emission.\"]}}","all_involved_urls":"null"} +{"task_id":"climategov_002","domain":"NOAA_NCEI_CLIMATE_AT_A_GLANCE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am researching historical climate patterns in Texas and want to find similar historical years to reference for shoulder-season operational planning. I am particularly interested in regions that recovered from a dry state to near-normal or wet conditions in the early 20th century and had light heating loads during both shoulder-season windows.\n\nIdentify the divisions in NOAA's Climate at a Glance database that meet these criteria. A division is retained only if it satisfies all four hard constraints: the 10-month Palmer Z-Index anomaly ending April 1907 is no higher than -0.30; the 10-month Z-Index anomaly ending April 1923 is no lower than -0.20; the 2-month Heating Degree Days (HDD) actual value ending May 1915 is below 50°Df; and the 5-month HDD actual value ending October 1922 is below 20°Df.\n\nAfter identifying the qualifying divisions, sort them. First compute each division's \"rebound score\" as the April 1923 10-month Z-Index anomaly minus the April 1907 10-month Z-Index anomaly. Sort primarily by rebound score in descending order. If scores are tied, place the division with the smaller October 1922 5-month HDD actual value first. If still tied, give priority to the smaller Texas official division number.\n\nFinally, output the results as a single-line string with divisions joined by commas. Each entry must strictly follow this format: \"|<4-digit division ID>||<1907-04 10-month Z-Index anomaly raw text>|<1923-04 10-month Z-Index anomaly raw text>|<1915-05 2-month HDD actual value raw text>|<1922-10 5-month HDD actual value raw text>|\". If no division meets all conditions, output NONE in uppercase.","start_url":"https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national","output_format":"Output the results as a single-line string with divisions joined by commas. Each entry must strictly follow this format: \"|<4-digit division ID>||<1907-04 10-month Z-Index anomaly raw text>|<1923-04 10-month Z-Index anomaly raw text>|<1915-05 2-month HDD actual value raw text>|<1922-10 5-month HDD actual value raw text>|\". If no division meets all conditions, output NONE in uppercase.","oracle_answer":"10|4110|Lower Valley|-0.36|1.46|10°Df|7°Df|1.82,9|4109|South|-0.33|0.53|23°Df|16°Df|0.86\n10|4110|Lower Valley|-0.36|1.46|10|7|1.82,9|4109|South|-0.33|0.53|23|16|0.86","metadata":"{\"State-Gated Retrieval\":[\"Retain only Texas divisions that satisfy all four historical conditions: the 10-month Palmer Z-Index anomaly ending April 1907 is no higher than -0.30; the 10-month anomaly ending April 1923 is no lower than -0.20; the 2-month HDD Value ending May 1915 is less than 50°Df; the 5-month HDD Value ending October 1922 is less than 20°Df.\",\"Rebound score is defined as the April 1923 10-month anomaly minus the April 1907 10-month anomaly.\",\"Sort by rebound score descending, then by October 1922 5-month HDD Value ascending, then by Texas division number ascending.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Texas divisional pages yield the 1907-04 and 1923-04 10-month Palmer Z-Index anomalies plus the 1915-05 2-month and 1922-10 5-month HDD values for each division.\",\"The rebound score and the two shoulder-season HDD values are computed only after the same set of candidate divisions survives all four historical filters.\",\"The final output is produced after sorting the surviving divisions by rebound score, then 1922-10 HDD value, then division number.\"],\"control_dependency\":[\"The workflow must cover the 1907, 1923, and 1915 pages as well as the 1922-10 5-month HDD page.\",\"Both HDD pages must be read from Value rather than Anomaly.\",\"The final rebound ranking must be determined after the 1922-10 5-month HDD page excludes 7 South Central and 8 Upper Coast, using ReboundScore as the ordering basis.\"],\"freeze\":{\"historical_window\":\"Texas climate divisions evaluated on the 1907-04 and 1923-04 10-month Palmer Z-Index anomaly pages, the 1915-05 2-month HDD Value page, and the 1922-10 5-month HDD Value page.\"},\"answer_type\":\"mixed multi-line output\"}","rubric":"{\"inclusion_conditions\":[\"Retain only Texas divisions that satisfy all four historical conditions: the 10-month Palmer Z-Index anomaly ending April 1907 is no higher than -0.30; the 10-month anomaly ending April 1923 is no lower than -0.20; the 2-month HDD Value ending May 1915 is less than 50°Df; the 5-month HDD Value ending October 1922 is less than 20°Df.\",\"Rebound score is defined as the April 1923 10-month anomaly minus the April 1907 10-month anomaly.\",\"Sort by rebound score descending, then by October 1922 5-month HDD Value ascending, then by Texas division number ascending.\"],\"exclusion_conditions\":[\"Exclude results that stop after filtering only the 1907, 1923, and 1915 pages without also reading the 1922-10 5-month HDD page.\",\"Exclude results that incorrectly read the 1915 or 1922 HDD page as Anomaly instead of Value.\",\"Exclude any division that does not satisfy all historical window conditions.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"texas_division_no\",\"division_id_4digit\",\"division_name\",\"apr_1907_10mo_z_text\",\"apr_1923_10mo_z_text\",\"may_1915_2mo_hdd_text\",\"oct_1922_5mo_hdd_text\",\"rebound_score\"],\"texas_division_no\":\"Emit the short Texas climate-division number in field 1 and the four-digit division ID in field 2.\",\"raw_text_fields\":\"The two Z-index anomaly fields preserve the raw displayed text; the two HDD fields preserve the raw displayed text, but comparison may ignore an optional trailing `°Df` suffix.\",\"rebound_score\":\"Compute as the April 1923 10-month Z-index anomaly minus the April 1907 10-month Z-index anomaly, formatted with exactly two decimal places.\",\"sorting_or_selection\":{\"primary\":\"rebound_score descending\",\"secondary\":\"October 1922 HDD actual value ascending after numeric normalization\",\"tertiary\":\"Texas division number ascending\"},\"answer_set_note\":\"The current oracle stores two equivalent answer sets: one preserves the HDD unit suffixes and one strips them; treat the two HDD columns as equivalent after optional `°Df` removal.\",\"stop_condition\":[\"All candidate Texas divisions are checked under the same anomaly and HDD windows.\",\"The unique ordered output string is resolved before emission.\"]}}","all_involved_urls":"null"} +{"task_id":"comptox_001","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"Among the following five substances found in records related to European painted products—aniline, cobalt, chromium, 3,3’-dichlorobenzidine, and dibenz[a,h]anthracene—retain only those whose pages explicitly contain the record “Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe.” For each qualifying substance, produce a consolidated list that integrates historical keyword status and the deepest-level use categories. First, check whether each of the following five dated keywords appears (presence only, ignoring any leading numbers): Substances in Products - Canada (4/2014), Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children’s Safe Product Act (4/2020), OEHHA Proposition 65 (1/2023). Record the earliest and latest year-month among the hits. Then, separately from the painted-products record mentioned above, select two use-category routes: one from a daily-consumer perspective with priority order Formulation → Article → Occupation, and one from a production-material perspective with priority order Occupation → Article → Formulation. After selecting each category, drill down along the child category with the highest product count until no further subdivision is possible; if there is a tie at the same level, choose the one with the smaller PUC ID.","start_url":"https://comptox.epa.gov/chemexpo/","output_format":"Finally, sort results by hit count descending; for ties, sort by the consumer-side terminal node’s product count descending. Output format: |||||||||||||. Separate results with commas; if no qualifying items exist, output NONE.","oracle_answer":"DTXSID8020090|5|2014-04|2023-01|Formulation|272|295|type|4|Occupation|301|356|family|27,DTXSID1031040|3|2018-10|2023-01|Formulation|77|94|type|7|Occupation|301|400|family|308,DTXSID9020409|2|2019-03|2023-01|Occupation|321|321|general|11|Occupation|321|321|general|11,DTXSID6020432|2|2019-03|2023-01|Article|313|313|general|1|Occupation|301|356|family|27,DTXSID3031022|1|2023-01|2023-01|Formulation|77|95|type|4|Occupation|301|356|family|185","metadata":"{\"State-Gated Retrieval\":[\"Screen only the five substances specified in the task, and each target substance page must explicitly contain the record “Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe.”\",\"Check whether each of the five specified dated keywords appears, and record the earliest and latest year-month among the hits.\",\"Then independently select one daily-consumer route and one production-material route, the former following Formulation → Article → Occupation and the latter following Occupation → Article → Formulation, and refine each route separately to its deepest level.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"each chemical page yields the five dated historical keywords, the Europe body-paint/tattoo-ink qualifying record, and the earliest/latest dated-hit months\",\"PUC category paths yield one consumer-side route chosen by Formulation -> Article -> Occupation and one source-side route chosen independently by Occupation -> Article -> Formulation\",\"final rows are produced only after the consumer-side and source-side routes are selected and refined separately for each chemical\"],\"control_dependency\":[\"the source-side route must be selected independently from the consumer-side route\",\"for each chemical, the second route refinement must follow the production-material priority order rather than the daily-consumer route\",\"family/type/general outputs must be determined only after both route selections are made independently\"],\"freeze\":{\"historical_window\":\"current ChemExpo chemical pages and PUC category paths for the five named substances, using the dated keyword states through 2023-01 and the current Europe body-paint/tattoo-ink record\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Screen only the five substances specified in the task, and each target substance page must explicitly contain the record “Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe.”\",\"Check whether each of the five specified dated keywords appears, and record the earliest and latest year-month among the hits.\",\"Then independently select one daily-consumer route and one production-material route, the former following Formulation → Article → Occupation and the latter following Occupation → Article → Formulation, and refine each route separately to its deepest level.\"],\"exclusion_conditions\":[\"Exclude substances that do not contain the specified Europe body-paint/tattoo-ink record.\",\"Exclude results that directly reuse the same daily-consumer route for the production-material side.\",\"Exclude results that do not independently select and refine both routes according to the specified priority orders.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"DTXSID\",\"hit_count\",\"earliest\",\"latest\",\"consumer_kind\",\"consumer_general_puc_id\",\"consumer_terminal_puc_id\",\"consumer_level\",\"consumer_products\",\"material_kind\",\"material_general_puc_id\",\"material_terminal_puc_id\",\"material_level\",\"material_products\"],\"dated_hits\":\"count only the exact dated keyword strings defined in the source rubric\",\"date_format\":\"YYYY-MM\",\"kind\":\"the kind fields use the canonical labels Article, Formulation, or Occupation\",\"level\":\"the level fields use the canonical labels general, family, or type\",\"products_source\":\"the Products counts come from the local chemical-detail node for the selected branch, not from an overall aggregate shown elsewhere on the site\",\"sorting_or_selection\":{\"primary\":\"hit_count descending\",\"secondary\":\"consumer_products descending\",\"tertiary\":\"DTXSID ascending\"}}}","all_involved_urls":"null"} +{"task_id":"comptox_002","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":6,"instruction":"In ChemExpo, I want to check whether each of these six substances currently appears more often in material-contact-related uses or in manufacturing-source-related uses, and then select the most representative use category from the corresponding direction. Follow the steps below. First, restrict the scope to these six substances: Di(2-Ethylhexyl) Phthalate, Melamine, Tris(2-Ethylhexyl) Phosphate, 4,5-Dihydro-2-Mercaptoimidazole, Phthalic Acid, Triphenyl Phosphates Tert-Butylated. Then, for each substance, first check whether any of the five material-contact-related label categories appear; score 1 point for each category that appears: Indirect additives food contact (10/2018); Europe, Food contact items; Food contact items, Japan; any keyword containing \"Toys and children's products\"; any keyword containing \"artificial_saliva\" or \"artificial_sweat\". Next, check whether any of the two manufacturing-source-related label categories appear; score 1 point for each category that appears: drinking_water, Europe, manufacturing, plastic_additive; Europe, plastic_additive. Additionally, separately count how many of the following four dated keywords appear: Indirect additives food contact (10/2018); OEHHA Proposition 65 (3/2019); WA Children's Safe Product Act (4/2020); OEHHA Proposition 65 (1/2023). Record the number of hits and the earliest and latest year-month among the hits. Then determine the direction based on which side has a higher score: if the material-contact score is strictly greater than the manufacturing-source score, search for the most representative category for this substance in the order Article → Formulation → Occupation; otherwise, search in the order Occupation → Article → Formulation. After determining the category, from this level onward, at each level only follow the subcategory with the highest product count, continuing until no further subdivision is possible; if there is a tie at the same level, choose the one with the smaller PUC ID.","start_url":"https://comptox.epa.gov/chemexpo/","output_format":"Finally, sort all substances by dated hit count descending; for ties, sort by product count of the selected node descending. Output format: |||||||||||||. Separate results with commas. If datedHits is 0, write NA for both earliest and latest.","oracle_answer":"DTXSID5020607|5|2|4|2018-10|2023-01|contact|Article|309|493|family|1|23|58,DTXSID5020601|4|1|3|2018-10|2023-01|contact|Article|309|309|general|1|5836|1827,DTXSID6020802|4|2|1|2018-10|2018-10|contact|Article|313|313|general|15|1104|675,DTXSID8021484|3|1|1|2018-10|2018-10|contact|Occupation|321|321|general|8|28313|4200,DTXSID0021414|5|0|1|2018-10|2018-10|contact|Article|309|309|general|3|5836|1827,DTXSID20872645|0|1|0|NA|NA|source|Occupation|318|381|family|5|274|107","metadata":"{\"State-Gated Retrieval\":[\"Only consider the six specified substances, and first compute contactHits, sourceHits, and datedHits on the chemical page.\",\"prioritySide must first be determined by these historical signals, and then a most representative current use category is selected along the corresponding direction.\",\"The current route selection must follow the given kind priority and the same-level smaller PUC ID tie-break rule for further drill-down.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"each chemical page yields contactHits, sourceHits, datedHits, and the earliest/latest dated-hit months from the historical keyword set\",\"after the priority side is chosen, the corresponding current PUC category path yields the representative kind, PUC path, product counts, and curated-chemical counts\",\"final rows are produced only after the historical hit scores determine the side first and the current route is then chosen with the side-specific priority and tie-break rules\"],\"control_dependency\":[\"historical contact/source signal scores must take priority over current maximum-Products paths\",\"the priority side must be determined from contactHits, sourceHits, and datedHits rather than from current visibility alone\",\"PUC path tie-breaks are valid only after the correct side has been fixed and the route has been traced under that side's rules\"],\"freeze\":{\"historical_window\":\"current ChemExpo chemical pages and PUC category paths for the six named substances, using the stated historical keyword families and dated hits through 2023-01\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only consider the six specified substances, and first compute contactHits, sourceHits, and datedHits on the chemical page.\",\"prioritySide must first be determined by these historical signals, and then a most representative current use category is selected along the corresponding direction.\",\"The current route selection must follow the given kind priority and the same-level smaller PUC ID tie-break rule for further drill-down.\"],\"exclusion_conditions\":[\"Exclude results that ignore historical signals and directly select the path with the maximum current visible Products on the chemical page.\",\"Exclude results that start PUC route selection without first determining the contact/source direction.\",\"Exclude results that do not apply the smaller PUC ID tie-break rule for same-level ties.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"DTXSID\",\"contactHits\",\"sourceHits\",\"datedHits\",\"earliest\",\"latest\",\"prioritySide\",\"PUCkind\",\"generalPUCID\",\"terminalPUCID\",\"level\",\"Products\",\"PUCDocuments\",\"PUCCuratedChemicals\"],\"dated_hits\":\"count only the exact dated keyword strings defined in the source rubric\",\"date_format\":\"YYYY-MM; if datedHits is 0, earliest and latest are both `NA`\",\"prioritySide\":\"emit `contact` when contactHits > sourceHits; otherwise emit `source`\",\"kind\":\"the PUCkind field uses the canonical labels Article, Formulation, or Occupation\",\"level\":\"the level field uses the canonical labels general, family, or type\",\"products_source\":\"Products comes from the selected terminal chemical-detail node\",\"terminal_statistics\":\"PUCDocuments and PUCCuratedChemicals come from the selected terminal PUC detail page Additional Statistics block\",\"sorting_or_selection\":{\"primary\":\"datedHits descending\",\"secondary\":\"Products descending\",\"tertiary\":\"DTXSID ascending\"}}}","all_involved_urls":"null"} +{"task_id":"comptox_003","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"In ChemExpo, first select Formulation categories with a total product count of 15,000 or more. Then, within each category, following the website's default display order, identify the first product family that meets these criteria: the family itself has no assumed attributes and its total product count is at least 3,000; additionally, the family must have at least two distinct specific product types, one with allowed attributes including aerosol and the other including child, and both types must have empty assumed attributes. Next, within each of these two specific product types, compute the product share (type product count divided by family cumulative product count). If shares are equal, compare their Curated Chemicals counts and select the higher one; if still equal, select the type with the smaller PUC ID. After completing the selection on both sides, retain only the better of the two candidate types: first prioritize the type with the higher product share; if shares are equal, compare Product Count (higher wins); if still equal, compare Curated Chemicals (higher wins); if still equal, select the type with the smaller PUC ID.","start_url":"https://comptox.epa.gov/chemexpo/visualizations/","output_format":"Output results sorted by final share in descending order, formatted as: |||||. Join records with commas and no spaces. If no qualifying items exist, output NONE.","oracle_answer":"48|42|62|child|2160/3531|583,137|197|210|child|6934/16904|1135","metadata":"{\"State-Gated Retrieval\":[\"First, retain only Formulation categories with a total product count of 15,000 or more.\",\"Within each candidate family, both an aerosol-side type and a child-side type must be found: the family itself must have no assumed attributes and a total product count of at least 3,000; both types must also have empty assumed attributes.\",\"All final selections within a family and between the two sides must follow the specified tie-break rules: share, Product Count, Curated Chemicals, and PUC ID.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"The Formulation summary yields the high-product candidate families whose total product count is at least 15,000\",\"Within each family, lower-level type pages yield the aerosol and child candidates, their assumed/allowed attributes, product counts, shares, and curated-chemical counts\",\"Final rows are produced only after a family survives both aerosol and child branches and the winning type is selected by the layered share/product/chemical/PUC tie-break rules\"],\"control_dependency\":[\"Both the aerosol and child branches within the same family must be fully checked before that family can be retained\",\"If one side is missing, the workflow must reject the family and continue to the next sibling family rather than stop at the first partial hit\",\"The final winner can be selected only after both sides have been independently optimized within the family and then compared against each other\"],\"freeze\":{\"historical_window\":\"Current ChemExpo Formulation families with total product count >= 15,000, evaluated on family/type attributes and current product/chemical counts\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"First, retain only Formulation categories with a total product count of 15,000 or more.\",\"Within each candidate family, both an aerosol-side type and a child-side type must be found: the family itself must have no assumed attributes and a total product count of at least 3,000; both types must also have empty assumed attributes.\",\"All final selections within a family and between the two sides must follow the specified tie-break rules: share, Product Count, Curated Chemicals, and PUC ID.\"],\"exclusion_conditions\":[\"Exclude results that stop as soon as a usable type is found on either side without requiring the same family to cover both aerosol and child sides.\",\"Exclude results that stop as soon as one side is missing instead of continuing to check sibling families at the same level.\",\"Exclude results that do not follow the specified layered tie-break rules to select the winning type within a family and overall.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"generalPUCID\",\"familyPUCID\",\"typePUCID\",\"side\",\"share\",\"CuratedChemicals\"],\"dedup_key\":\"(generalPUCID, familyPUCID, typePUCID, side)\",\"side\":\"Emit the lower-case branch label exactly as determined in the source workflow\",\"share\":\"Canonical output uses the raw fraction `type Products / family Cumulative Products` rather than a decimal\",\"CuratedChemicals\":\"Emit the integer count from the selected type-level node\",\"sorting_or_selection\":{\"primary\":\"Share descending by numeric fraction value\",\"secondary\":\"Type-level Products descending\",\"tertiary\":\"CuratedChemicals descending, then PUC IDs ascending as tie-breaks\"}}}","all_involved_urls":"null"} +{"task_id":"comptox_004","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"In ChemExpo, for the five substances Di(2-Ethylhexyl) Phthalate, Melamine, Phthalic Acid, Tris(2-Ethylhexyl) Phosphate, and Triphenyl Phosphates Tert-Butylated, check whether their historical labels align with their current uses. Follow the steps below. First, restrict the scope to these five substances. For each substance, collect three sets of baseline assessment data. The first set is the \"material contact\" score: check for the presence of the following five label categories, scoring 1 point for each category hit: Indirect additives food contact (10/2018); Europe, Food contact items; Food contact items, Japan; any keyword containing \"Toys and children's products\"; and any keyword containing \"artificial_saliva\" or \"artificial_sweat\". The second set is the \"production source\" score: check for the presence of the following two label categories, scoring 1 point for each category hit: \"drinking_water, Europe, manufacturing, plastic_additive\" and \"Europe, plastic_additive\". The third set is the regulatory profile for specific dates: separately count the total hits for the four exact keywords Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children's Safe Product Act (4/2020), and OEHHA Proposition 65 (1/2023), and record the earliest and latest year-month among all hits. After obtaining these three sets of data, determine the historical side by comparing scores: if the material contact score is strictly greater than the production source score, select a historically recommended kind in the order Article → Formulation → Occupation; otherwise, select in the order Occupation → Article → Formulation. After determining the kind, drill down along the subcategory with the most products at each level until no further subdivision is possible; if there is a tie at the same level, choose the one with the smaller PUC ID. Separately, independently identify the current dominant category for the same substance, ignoring historical clues: directly find the path with the most products among all use categories, drilling down to the terminal level using the same tie-breaking rule (smaller PUC ID). Finally, compare the two results: if the current dominant kind is Article or Formulation and the historical side is material, mark ALIGNED; if the current dominant kind is Occupation and the historical side is source, also mark ALIGNED; otherwise, mark MISALIGNED.","start_url":"https://comptox.epa.gov/chemexpo/","output_format":"Output MISALIGNED records first; within the same group, sort by datedHits descending; if datedHits are equal, sort by currentProducts descending. Format: |||||||||||||||||. Separate records with commas. If datedHits is 0, write NA for both earliest and latest.","oracle_answer":"DTXSID6020802|4|2|1|2018-10|2018-10|material|Article|Furniture and furnishings|Furniture and furnishings|general|15|Occupation|Raw materials|fireproof coatings|type|24|MISALIGNED,DTXSID8021484|3|1|1|2018-10|2018-10|material|Occupation|Laboratory supplies|Laboratory supplies|general|8|Occupation|Laboratory supplies|Laboratory supplies|general|8|MISALIGNED,DTXSID5020607|5|2|4|2018-10|2023-01|material|Article|Construction and building materials|flooring|family|1|Formulation|Home maintenance|paint|type|112|ALIGNED,DTXSID0021414|5|0|1|2018-10|2018-10|material|Article|Construction and building materials|Construction and building materials|general|3|Article|Construction and building materials|Construction and building materials|general|3|ALIGNED,DTXSID20872645|0|1|0|NA|NA|source|Occupation|Industrial products|hydraulic fluid|family|5|Occupation|Industrial products|hydraulic fluid|family|5|ALIGNED","metadata":"{\"State-Gated Retrieval\":[\"Operate only on the five specified substances, and first compute materialHits, sourceHits, and datedHits from the keyword-set block.\",\"The historically recommended category must be derived independently from these historical signals; the current dominant category must be derived separately from the current use path.\",\"Finally, compare only whether the historically recommended category and the current dominant category align at the coarse side level, and mark ALIGNED or MISALIGNED accordingly.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"each chemical page yields materialHits, sourceHits, datedHits, and the historical recommendation side implied by the keyword set\",\"an independent current PUC category path yields the current dominant category, path labels, and classification counts for the same chemical\",\"final rows are produced only after the historical recommendation and current dominant category are computed independently and then compared at the coarse side level\"],\"control_dependency\":[\"the historical recommendation must be determined from the keyword-set evidence rather than from the current largest category\",\"historical recommendation must be computed from the keyword-set evidence before alignment is judged\",\"ALIGNED / MISALIGNED status is valid only after the historical and current category directions have been derived independently and then compared\"],\"freeze\":{\"historical_window\":\"current ChemExpo chemical pages and PUC category paths for the five named substances, using the specified historical keyword-set evidence through 2023-01\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Operate only on the five specified substances, and first compute materialHits, sourceHits, and datedHits from the keyword-set block.\",\"The historically recommended category must be derived independently from these historical signals; the current dominant category must be derived separately from the current use path.\",\"Finally, compare only whether the historically recommended category and the current dominant category align at the coarse side level, and mark ALIGNED or MISALIGNED accordingly.\"],\"exclusion_conditions\":[\"Exclude results that simply take the current largest category and treat it as the historically recommended category.\",\"Exclude results that default to ALIGNED without independently deriving the historically recommended category.\",\"Exclude results that fail to compute the historical and current paths separately, instead mixing signals in a single path.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"DTXSID\",\"materialHits\",\"sourceHits\",\"datedHits\",\"earliest\",\"latest\",\"historySide\",\"recommendedKind\",\"recommendedGeneral\",\"recommendedTerminal\",\"recommendedLevel\",\"recommendedProducts\",\"currentKind\",\"currentGeneral\",\"currentTerminal\",\"currentLevel\",\"currentProducts\",\"status\"],\"dated_hits\":\"count only the exact dated keyword strings defined in the source rubric\",\"date_format\":\"YYYY-MM; if datedHits is 0, earliest and latest are both `NA`\",\"historySide\":\"emit the lower-case historical winner `material` or `source`\",\"recommended_fields\":\"these fields describe the historically suggested path\",\"current_fields\":\"these fields describe the current dominant path\",\"kind\":\"the kind fields use the canonical labels Article, Formulation, or Occupation\",\"level\":\"the level fields use the canonical labels general, family, or type\",\"status\":\"emit `ALIGNED` or `MISALIGNED` exactly\",\"sorting_or_selection\":{\"primary\":\"status with MISALIGNED before ALIGNED\",\"secondary\":\"datedHits descending\",\"tertiary\":\"currentProducts descending\",\"quaternary\":\"DTXSID ascending\"}}}","all_involved_urls":"null"} +{"task_id":"consumerfinance_001","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"On the CFPB enforcement actions page, for the period 2022 to 2024, find one qualifying administrative enforcement action for each of the three product categories: Deposits, Furnishing, and Prepaid. Then, in the corresponding Consent Order for that action, locate the first occurrence of the consumer redress amount and the civil money penalty amount, along with their page numbers.\n\nSpecifically, first restrict the search to actions on the CFPB enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.\n\nThen, search separately for each of the three product categories: Deposits, Furnishing, and Prepaid. For each category, follow the current default case order on the CFPB website from top to bottom, and select the first action that simultaneously meets all of the following conditions:\n1. The action page provides both a Consent Order and a press release.\n2. The product category label corresponds one-to-one with the target category.\n3. The page explicitly states consumer redress, and the redress amount exceeds $5,000,000.\n4. In addition to consumer redress, the page also explicitly states a civil money penalty.\n\nAfter finding such an action for each product category, open its corresponding Consent Order and locate the two types of monetary information:\n- The specific amount of consumer redress when it first appears in the text, and the page number where it appears.\n- The specific amount of civil money penalty when it first appears in the text, and the page number where it appears.\n\nPage numbers should be based on the physical page numbering of the Consent Order PDF, i.e., the first page is p1, the second page is p2, and so on.","start_url":"https://www.consumerfinance.gov/enforcement/actions/","output_format":"Finally, output the results for the three product categories sorted alphabetically by product name. Output one segment per category in the following format:\n|||||p||p\nIf no qualifying case is found for a category, output:\n|NONE\nJoin the three results with commas, with no spaces.","oracle_answer":"Deposits|Bank of America, N.A.|2023-CFPB-0006|2023-07-11|$80,400,000|p11|$60,000,000|p14,Furnishing|Hyundai Capital America|2022-CFPB-0005|2022-07-26|$13,200,000|p31|$6,000,000|p35,Prepaid|U.S. Bank National Association|2023-CFPB-0019|2023-12-19|$5,700,000|p22|$15,000,000|p26","metadata":"{\"State-Gated Retrieval\":[\"Only consider administrative enforcement actions on the CFPB Enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.\",\"For each of the three product categories (Deposits, Furnishing, Prepaid), search in the current default order from top to bottom for the first action that simultaneously satisfies: the page provides a Consent Order and a Press release; the Products label corresponds one-to-one with the target category; the action detail page explicitly states consumer redress > $5,000,000 and also states a civil money penalty.\",\"Finally, extract the first-occurrence amounts and page numbers of consumer redress and civil money penalty from the correct Consent Order.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Enforcement-action list pages yield product-branch candidate actions in current default order.\",\"Each action detail page and linked consent-order PDF yield product singularity, document-stack presence, redress/civil-money-penalty amounts, and first-occurrence pages.\",\"Final rows are emitted only after identifying, for each product, the first action that survives detail-page and PDF validation.\"],\"control_dependency\":[\"List-level \\\"has Consent Order + Press release\\\" hits must be validated on the detail page for product singularity and money thresholds.\",\"Prepaid candidates force document-level disambiguation among Consent Order, Stipulation, and terminating-order PDFs.\",\"Per-product first-match selection must explicitly skip rejected candidates and validate downstream PDFs before it is finalized.\"],\"freeze\":{\"historical_window\":\"Administrative enforcement actions with Initial filing date from 2022-01-01 through 2024-12-31; current default case ordering and currently linked action documents.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only consider administrative enforcement actions on the CFPB Enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.\",\"For each of the three product categories (Deposits, Furnishing, Prepaid), search in the current default order from top to bottom for the first action that simultaneously satisfies: the page provides a Consent Order and a Press release; the Products label corresponds one-to-one with the target category; the action detail page explicitly states consumer redress > $5,000,000 and also states a civil money penalty.\",\"Finally, extract the first-occurrence amounts and page numbers of consumer redress and civil money penalty from the correct Consent Order.\"],\"exclusion_conditions\":[\"Exclude actions where the Products label is not a single target category, or where the action appears relevant only at the list level but the detail page does not confirm it.\",\"Exclude actions that do not clearly satisfy the redress > $5M and independent civil money penalty conditions.\",\"Exclude cases where a Stipulation or Order Terminating the Consent Order is mistakenly used in place of the required Consent Order.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"Product\",\"Respondent\",\"Docket\",\"FilingDate\",\"RedressUSD\",\"RedressPage\",\"PenaltyUSD\",\"PenaltyPage\"],\"product_order\":\"Alphabetical by Product name\",\"fallback_row\":\"If a product has no qualifying case, emit `|NONE`\",\"date_format\":\"FilingDate uses YYYY-MM-DD\",\"money_fields\":\"Canonical output preserves the dollar sign and commas from the oracle, but equivalent comparison may ignore `$` and commas and compare the numeric USD amount.\",\"page_fields\":\"Page fields use the canonical `pN` form.\",\"document_scope\":\"Extract both money amounts from the Consent Order PDF only; do not substitute a stipulation, termination order, or other companion document.\",\"selection_rule\":\"For each product, keep the first action in the default filtered order that fully satisfies every gate in the source rubric.\"}}","all_involved_urls":"null"} +{"task_id":"consumerfinance_002","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I want to organize the annual household financial stability survey report series in CFPB Reports, whose latest version page still links directly to the 2023 and 2022 editions. Some topics that appeared in the 2022 edition were later dropped from subsequent annual reports, and I want to see which other reports on the site are associated with these dropped topics. First, locate this series within the CFPB Reports section and confirm that the latest version links directly to the two previous editions (2023 and 2022). Then, using the 2022 edition as the baseline, identify topics that appear in the 2022 edition but are no longer retained in subsequent annual reports. Note: exclude the topic specifically used to mark \"belongs to the same survey series.\" Next, for each identified topic, confirm the following one by one: first, the year in which this topic first disappeared from subsequent annual reports; second, when searching for this topic within the CFPB Reports section, among results from 2022 and earlier, which report that does not belong to this series appears first; third, open that report, count how many related resources are listed on the page, how many of those explicitly link to the same survey series, and among those reports that link to the same survey series, how many have appendices labeled alphabetically with at least three sections (e.g., Appendix A, B, C or more); fourth, for the report that survives this multi-level screening, provide its title, publication date, and the alphabetical range of its appendices.","start_url":"https://www.consumerfinance.gov/data-research/research-reports/","output_format":"Finally, output a single-line string sorted alphabetically by topic name: |||||||||","oracle_answer":"Saving|2023|Consumer Savings App Strategies and Savings Outcomes|2022-12-07|4|2|1|Emergency Savings and Financial Security: Insights from the Making Ends Meet Survey and Consumer Credit Panel|2022-03-23|A-D,Student loans|2023|Report of the CFPB Education Loan Ombudsman|2022-10-20|0|0|0|NONE|NONE|NONE","metadata":"{\"State-Gated Retrieval\":[\"First, locate the CFPB household financial well-being annual report series whose latest version links directly to 2023 and 2022.\",\"Using the 2022 edition as the baseline, retain only topics that appear in 2022 but are no longer retained in subsequent annual reports, and exclude the topic specifically marked as \\\"belongs to the same survey series.\\\"\",\"For each topic, find the earliest non-series pivot report from 2022 or earlier, then count its directly listed related resources, how many link back to the same survey series, how many qualify under the appendix rule, and the appendix span of the final qualifying report.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"current CFPB Reports pages yield the 2024 -> 2023 -> 2022 annual-survey chain and the 2022 topic baseline\",\"report detail pages and report-search results yield first-disappearance year, pivot report title/date, related-resource counts, and links back to the annual-survey series\",\"final rows are produced only after separating the first jump target from later return-to-series counting\"],\"control_dependency\":[\"requiring the pivot report itself to link back to the same survey series incorrectly rules out valid topic rows\",\"title extraction must use the pivot detail page rather than search-result snippets\",\"related-resource expansion must continue even when the pivot report itself does not link back to the same survey series\"],\"freeze\":{\"historical_window\":\"currently linked 2024, 2023, and 2022 CFPB household financial well-being annual reports; topic disappearance is judged over that three-year chain, and pivot-report search is restricted to 2022-and-earlier reports\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"First, locate the CFPB household financial well-being annual report series whose latest version links directly to 2023 and 2022.\",\"Using the 2022 edition as the baseline, retain only topics that appear in 2022 but are no longer retained in subsequent annual reports, and exclude the topic specifically marked as \\\"belongs to the same survey series.\\\"\",\"For each topic, find the earliest non-series pivot report from 2022 or earlier, then count its directly listed related resources, how many link back to the same survey series, how many qualify under the appendix rule, and the appendix span of the final qualifying report.\"],\"exclusion_conditions\":[\"Exclude topics that are still retained in subsequent annual reports.\",\"Exclude results that incorrectly treat \\\"the pivot report itself must link back to the same survey series\\\" as a hard condition for column 3.\",\"Exclude search results that directly belong to the same survey series or reports from after 2022.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"topic\",\"first-missing-year\",\"pivot-report-or-NONE\",\"pivot-date-or-NONE\",\"direct-related-count\",\"same-series-count\",\"qualified-count\",\"representative-report-or-NONE\",\"publication-date-or-NONE\",\"appendix-span-or-NONE\"],\"topic_order\":\"alphabetical by topic name\",\"date_format\":\"pivot-date and publication-date use YYYY-MM-DD when present\",\"appendix_span\":\"canonical span uses compact labels such as `A-D`\",\"none_rule\":\"if qualified-count is 0, representative-report, publication-date, and appendix-span are all `NONE`\"}}","all_involved_urls":"null"} +{"task_id":"consumerfinance_003","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I want to clearly sort out the CFPB's 2020 Debt Collection Rules, including proposal sources, delayed effective date arrangements, final effective dates, and the accompanying quick-reference PDF information on the implementation page. Follow the steps below. First, confirm when each of the two 2020 Debt Collection Rule final rules was issued. Then separately confirm the following for each wave: 1. The issue date of this final rule; 2. Which proposal(s) it developed from, and the public comment deadline for each proposal; 3. Whether the 2021 proposed rule on delaying the effective date covers this wave, and the comment deadline for that proposal; 4. The actual final effective date; 5. Which quick-reference PDF corresponds to this wave on the implementation page; 6. The first heading in the PDF body after skipping the introductory paragraph.","start_url":"https://www.consumerfinance.gov/rules-policy/final-rules/","output_format":"Output a single-line string with results sorted by final-rule issue date in ascending order. Identify each wave by its final rule issue month (YYYY-MM). Use the following format: ||||||||","oracle_answer":"2020-10|2020-10-30|2019-05-07 main|2019-09-18|YES|2021-05-19|2021-11-30|Executive summary of the October 2020 final rule|Coverage and Definitions,2020-12|2020-12-18|2019-05-07 main+2020-02-21 supplemental|2019-09-18+2020-08-04|YES|2021-05-19|2021-11-30|Executive summary of the December 2020 final rule|Validation Information Requirements and Disclosures","metadata":"{\"State-Gated Retrieval\":[\"Must process the two 2020 Debt Collection Practices (Regulation F) final rules separately, not merge them into one.\",\"For each wave, separately confirm: issue date, corresponding proposal chain and public comment deadlines, whether the 2021 delayed-effective-date proposed rule covers it and its deadline, final effective date, corresponding implementation quick-reference PDF, and the first heading after the introduction in that PDF.\",\"The detail page, proposal chain, and summary PDF for the October wave and the December wave must each be independently verified.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"final-rules index pages and rule-development pages yield the two 2020 Regulation F final-rule waves and their proposal branches\",\"each final-rule detail page, delayed-effective-date proposal page, and implementation quick-reference PDF yields the wave-specific dates, linked proposals, comment deadlines, and first summary heading\",\"final rows are produced only after the October and December waves are traced separately end to end\"],\"control_dependency\":[\"two same-title final rules force correction from name-based collapsing to issue-date branching\",\"proposal-chain validation must be done per wave; otherwise the later December chain contaminates the October row\",\"implementation PDFs must be matched back to the correct wave rather than accepting the latest quick-reference page\"],\"freeze\":{\"historical_window\":\"the 2020-10 and 2020-12 Debt Collection Rule final-rule waves, their linked 2020 proposal pages, the 2021 delayed-effective-date proposal, and the current implementation-page quick-reference PDFs\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Must process the two 2020 Debt Collection Practices (Regulation F) final rules separately, not merge them into one.\",\"For each wave, separately confirm: issue date, corresponding proposal chain and public comment deadlines, whether the 2021 delayed-effective-date proposed rule covers it and its deadline, final effective date, corresponding implementation quick-reference PDF, and the first heading after the introduction in that PDF.\",\"The detail page, proposal chain, and summary PDF for the October wave and the December wave must each be independently verified.\"],\"exclusion_conditions\":[\"Exclude results that merge the two identically named 2020 final rules into one.\",\"Exclude results that project the December wave's proposal chain or executive-summary heading onto the October wave.\",\"Exclude results that do not independently verify each final-rule detail page and its corresponding PDF.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"wave\",\"final-rule-date\",\"proposal-chain\",\"proposal-comment-closes\",\"delay-proposal-applied\",\"delay-proposal-comments-close\",\"controlling-effective-date\",\"quick-reference-pdf\",\"summary-heading\"],\"wave\":\"wave is the final-rule issue month in YYYY-MM\",\"date_format\":\"all standalone date fields use YYYY-MM-DD\",\"proposal_chain\":\"canonical chain joins proposal milestones with `+`, using pieces such as `2019-05-07 main` or `2020-02-21 supplemental` in chronological order\",\"proposal_comment_closes\":\"join multiple comment-close dates with `+` in the same order as proposal_chain\",\"delay_proposal_applied\":\"emit `YES` when a delay proposal is part of the chain; otherwise emit `NO`\",\"quick_reference_pdf\":\"use the displayed quick-reference PDF title, not the filename\",\"summary_heading\":\"use the first substantive heading from the final-rule PDF\",\"sorting_or_selection\":\"final-rule-date ascending\"}}","all_involved_urls":"null"} +{"task_id":"consumerfinance_004","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"On the CFPB Enforcement Actions page, identify administrative enforcement actions filed in 2024 and subsequently closed, separately for the product categories Credit Cards and Deposits. Then extract the corresponding clause information linking the terminating order to the original Consent Order. Specifically, first restrict the search to administrative enforcement actions on the CFPB Enforcement Actions page whose initial filing date falls between 2024-01-01 and 2024-12-31. Then filter separately for the two product categories: Credit Cards and Deposits. For each category, retain only cases that simultaneously meet the following conditions: the case page shows the case has been closed, with a status of Expired, Terminated, or Vacated; the case page provides all four of these document types: Consent Order, Stipulation, Order Terminating the Consent Order, and Press Release; the page lists exactly one product category, and that single category is the one you are currently targeting. That is, if you are searching for Credit Cards, the page must list only that item and no other categories; the same requirement applies when searching for Deposits. After filtering, each product category may still have more than one case. For each category, retain only the case with the latest initial filing date; if multiple cases share the same filing date, select the one with the smaller docket number. Next, open the Order Terminating the Consent Order for the selected case and record the following three pieces of information: the termination date on this document; the passage in the document that states the legal authority for terminating the consent order, i.e., the termination authority, recording only the original text of its first occurrence; the PDF physical page number where this termination authority first appears. Also, within the text of this terminating order, find the first explicit reference to a paragraph number from the original Consent Order; if it reads \"Paragraphs X and Y,\" take only X. Then, return to the original Consent Order document for this case, locate the referenced paragraph, and record the section heading under which it falls.","start_url":"https://www.consumerfinance.gov/enforcement/actions/","output_format":"Finally, output a single-line string in alphabetical order by product name: ||||||p||. If a product has no qualifying case, output: |NONE","oracle_answer":"Credit Cards|Apple Inc.|2024-CFPB-0012|2024-10-23|2025-09-22|12 U.S.C. § 5563(b)(3)|p1|83|ADMINISTRATIVE PROVISIONS,Deposits|Navy Federal Credit Union|2024-CFPB-0014|2024-11-07|2025-07-01|12 U.S.C. § 5563(b)(3)|p1|106|ADMINISTRATIVE PROVISIONS","metadata":"{\"State-Gated Retrieval\":[\"Consider only administrative enforcement actions with an Initial filing date in 2024, and search separately in the Credit Cards and Deposits categories.\",\"Cases must have a status of Expired, Terminated, or Vacated, and the page must simultaneously provide a Consent Order, Stipulation, Order Terminating the Consent Order, and Press Release, and the Products field must correspond one-to-one with the target category.\",\"Finally, for each category retain only the most recent qualifying case determined by Initial filing date, and compile the corresponding clause information linking the terminating order to the original Consent Order.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"enforcement-action list pages yield 2024 candidate actions by product branch\",\"each action detail page and linked Consent Order / Stipulation / Order Terminating the Consent Order / Press Release documents yield status, initial filing date, single-product validity, and clause references\",\"final rows are selected only after per-product comparison on Initial filing date and document-stack validation\"],\"control_dependency\":[\"\\\"latest\\\" must be determined by Initial filing date rather than termination date\",\"product filters on the list page are insufficient until the action detail page confirms a single matching product\",\"clause extraction in the terminating order must stay aligned with the original Consent Order rather than a superficially similar section\"],\"freeze\":{\"historical_window\":\"administrative enforcement actions with Initial filing date from 2024-01-01 through 2024-12-31; current action status and currently linked Consent Order / Stipulation / terminating-order / Press Release documents\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Consider only administrative enforcement actions with an Initial filing date in 2024, and search separately in the Credit Cards and Deposits categories.\",\"Cases must have a status of Expired, Terminated, or Vacated, and the page must simultaneously provide a Consent Order, Stipulation, Order Terminating the Consent Order, and Press Release, and the Products field must correspond one-to-one with the target category.\",\"Finally, for each category retain only the most recent qualifying case determined by Initial filing date, and compile the corresponding clause information linking the terminating order to the original Consent Order.\"],\"exclusion_conditions\":[\"Exclude results that use termination date instead of Initial filing date to determine \\\"latest.\\\"\",\"Exclude cases with an incomplete document stack or where Products is not a single target category.\",\"Exclude cases where the required clause correspondence between the terminating order and the original Consent Order cannot be established.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"Product\",\"Respondent\",\"Docket\",\"InitialFilingDate\",\"TerminationDate\",\"TerminationAuthority\",\"TermAuthorityPage\",\"ReferencedParagraph\",\"ConsentSectionHeading\"],\"product_order\":\"alphabetical by Product name\",\"fallback_row\":\"if a product has no qualifying case, emit `|NONE`\",\"date_format\":\"InitialFilingDate and TerminationDate use YYYY-MM-DD\",\"termination_authority\":\"use the canonical statute string extracted from the termination order\",\"page_fields\":\"TermAuthorityPage uses the canonical `pN` form\",\"ReferencedParagraph\":\"emit the paragraph number as a plain numeric string\",\"ConsentSectionHeading\":\"emit the uppercase heading of the consent-order section containing the referenced paragraph\"}}","all_involved_urls":"null"} +{"task_id":"consumerfinance_005","domain":"CFPB_COMPLAINT_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am preparing an internal outreach memo on historical complaint clusters and need to track a specific set of complaints: from the CFPB Complaint Database, within the current product bucket covering credit reporting and other personal consumer reports, between 2018-01-01 and 2021-12-31, tagged as Servicemember, with a public narrative, and where the text explicitly mentions medical bills or doctors. Please provide two representative complaint clusters: the first is the peak month of this cohort; the second is the latest month in this cohort whose complaint count is still at least half of the peak. For each cluster, report the total complaints for that month, the state with the highest complaint count and its count, the company with the highest complaint count within that state and month and its count, and the earliest complaint received by that company in that state and month, including its ID, date, Issue, and Sub-issue. Output a single line with Peak first, then LatestHalfPeak, using the format: ||||||||||.","start_url":"https://www.consumerfinance.gov/data-research/consumer-complaints/","output_format":"Output a single line with Peak first, then LatestHalfPeak, using the format: ||||||||||. Join the Peak and LatestHalfPeak clusters with a comma. For ties: months are ordered chronologically; states are ordered alphabetically by state abbreviation; companies are ordered alphabetically by company name; for the earliest complaint, use the earliest date, then the smallest Complaint ID if dates are identical.","oracle_answer":"Peak|2018-02|46|CA|28|TRANSUNION INTERMEDIATE HOLDINGS, INC.|9|2806154|2018-02-07|Improper use of your report|Reporting company used your report improperly,LatestHalfPeak|2021-11|23|CA|12|EQUIFAX, INC.|3|4928768|2021-11-19|Problem with a credit reporting company's investigation into an existing problem|Their investigation did not fix an error on your report","metadata":"{\"State-Gated Retrieval\":[\"Only consider complaints within the current product bucket covering credit reporting and other personal consumer reports, from 2018-01-01 to 2021-12-31, tagged as Servicemember, with a public narrative, and where the text explicitly mentions medical bills or doctors.\",\"The first cluster must be the peak month of the cohort; the second cluster must be the latest month in the cohort whose complaint count is still at least half of the peak.\",\"For each cluster, recompute the top company within the corresponding month + state subset, then locate the earliest complaint received by that company in that state and month.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"current complaint-form taxonomy yields the product bucket that contains credit reporting / other personal consumer reports\",\"filtered complaint records yield month counts, month-state subsets, top companies, and earliest complaint details inside each chosen subset\",\"final rows are produced only after peak month and latest-half-peak month are determined, and each downstream aggregate is computed inside its narrower month-state cohort\"],\"control_dependency\":[\"the latest month must be defined as the latest month whose count is at least ceil(PeakCount / 2)\",\"overall top-company counts cannot be projected into a month-state subset without recomputation\",\"earliest complaint selection is only valid after the month, state, and company filters are all frozen\"],\"freeze\":{\"historical_window\":\"Complaint Database records received from 2018-01-01 through 2021-12-31 under the current product-bucket mapping for the credit-reporting / other personal consumer reports family; Servicemember + public narrative + medical bills/doctors text cohort\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only consider complaints within the current product bucket covering credit reporting and other personal consumer reports, from 2018-01-01 to 2021-12-31, tagged as Servicemember, with a public narrative, and where the text explicitly mentions medical bills or doctors.\",\"The first cluster must be the peak month of the cohort; the second cluster must be the latest month in the cohort whose complaint count is still at least half of the peak.\",\"For each cluster, recompute the top company within the corresponding month + state subset, then locate the earliest complaint received by that company in that state and month.\"],\"exclusion_conditions\":[\"Exclude results that directly use the latest month with any complaints as the second cluster.\",\"Exclude results that first find the overall top company across the full cohort and then project it onto the month-state subset.\",\"Exclude results that do not first derive the half-peak threshold from PeakCount.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"Cluster\",\"Month\",\"MonthComplaints\",\"TopState\",\"StateComplaints\",\"TopCompany\",\"CompanyComplaints\",\"EarliestComplaintID\",\"EarliestDate\",\"Issue\",\"SubIssue\"],\"cluster_order\":[\"Peak\",\"LatestHalfPeak\"],\"date_format\":{\"Month\":\"YYYY-MM\",\"EarliestDate\":\"YYYY-MM-DD\"},\"TopState\":\"use the uppercase two-letter state abbreviation\",\"TopCompany\":\"use the company display name as shown in the source data\",\"tie_breaks\":\"for tied months use chronological order; for tied states use state-code alphabetical order; for tied companies use company-name alphabetical order; for the earliest complaint use EarliestDate ascending then Complaint ID ascending\",\"SubIssue\":\"emit `NONE` when the complaint row has no sub-issue value\"}}","all_involved_urls":"null"} +{"task_id":"consumerfinance_006","domain":"CFPB_COMPLAINT_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am writing a crypto-complaint concentration memo. To verify whether complaint peaks within a fixed three-year window are driven only by a few top platforms, I need you to step through the CFPB complaint database and extract relevant data.\n\nFirst, define the underlying data scope. Using the current CFPB complaint form product taxonomy, determine which product bucket Virtual currency currently falls under. Once the bucket is confirmed, strictly limit the time range to 2019-08-26 through 2022-08-26 and retain only complaint records classified under the Virtual currency subcategory within that product bucket. This forms the initial cohort.\n\nSecond, identify two characteristic peak months within this cohort. Step 1: Aggregate complaints by month across the full cohort (with no companies removed) and identify the original peak month (AllCompanies). Step 2: Identify the top two companies by complaint count in that original peak month. Remove all complaint records of these two companies from the entire three-year cohort (not just from the single peak month). Then re-aggregate complaints by month on the remaining data to find the residual peak month (ResidualAfterTop2).\n\nThird, for each of these two peak months, extract detailed data. For each cluster, obtain the total complaint count for that month, the names of the two excluded top companies, and their combined complaint count in the original peak month. Also identify the state with the highest complaint count in that feature month and its complaint count, the most complained-about company within that state and its complaint count, and the full details of the earliest complaint received by that company in that state during that feature month (including Complaint ID, date, Issue, and Sub-issue).\n\nFinally, after completing all the above steps, format the two sets of core parameters into a single string with no spaces. The two rows must be ordered AllCompanies first, ResidualAfterTop2 second. The field order for each row is fixed as: ||||||||||||. To ensure a unique answer: output the two records in AllCompanies then ResidualAfterTop2 order; list ExcludedTop2Companies in descending order of their complaint count in the original peak month, breaking ties alphabetically; for any tie in sorting indicators, sort by field value in ascending alphabetical order; if the earliest complaint date is tied, select the one with the smallest Complaint ID.","start_url":"https://www.consumerfinance.gov/data-research/consumer-complaints/","output_format":"Output the two rows in AllCompanies first, ResidualAfterTop2 second order, joined into a formatted string with no spaces. The field order for each row is fixed as: ||||||||||||.","oracle_answer":"AllCompanies|2021-05|336|Coinbase, Inc.+BAM Management US Holdings Inc.|226|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,ResidualAfterTop2|2020-06|180|Coinbase, Inc.+BAM Management US Holdings Inc.|226|OH|28|PNC Bank N.A.|22|3687376|2020-06-07|Other transaction problem|NONE","metadata":"{\"State-Gated Retrieval\":[\"Only consider Complaint Database records under the current product bucket for Virtual currency subcategory, with a received date between 2019-08-26 and 2022-08-26.\",\"First determine the AllCompanies original peak month, then identify the top two companies by complaint count in that peak month.\",\"These two companies must be removed entirely from the full three-year cohort, then recompute the residual peak month and all downstream fields based on the remaining cohort.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"current complaint-form taxonomy yields the product bucket for Virtual currency\",\"complaint records within the fixed three-year cohort yield the all-company peak month, per-month top companies, and residual-cohort recomputations after company removal\",\"final rows are produced only after the top-2 companies from the original peak month are removed from the full cohort and downstream aggregates are computed on the resulting cohort\"],\"control_dependency\":[\"peak-month top companies must be removed from the entire cohort, not only from the original peak month\",\"residual peak detection must be computed from the rewritten cohort rather than by local patching of the original month\",\"downstream state / company / earliest-complaint fields are valid only after the global company-removal step is locked\"],\"freeze\":{\"historical_window\":\"Complaint Database records received from 2019-08-26 through 2022-08-26 under the current product-bucket mapping for Virtual currency\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only consider Complaint Database records under the current product bucket for Virtual currency subcategory, with a received date between 2019-08-26 and 2022-08-26.\",\"First determine the AllCompanies original peak month, then identify the top two companies by complaint count in that peak month.\",\"These two companies must be removed entirely from the full three-year cohort, then recompute the residual peak month and all downstream fields based on the remaining cohort.\"],\"exclusion_conditions\":[\"Exclude results that only locally delete top-2 company records from the original peak month.\",\"Exclude results that do not write the top-2 company set back into the full cohort before recomputing the residual peak.\",\"Exclude results that use downstream state, company, or earliest complaint fields computed from a cohort that has not been recomputed after removal.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"Cluster\",\"Month\",\"MonthComplaints\",\"ExcludedTop2Companies\",\"ExcludedTop2PeakMonthComplaints\",\"TopState\",\"StateComplaints\",\"TopCompany\",\"CompanyComplaints\",\"EarliestComplaintID\",\"EarliestDate\",\"Issue\",\"SubIssue\"],\"cluster_order\":[\"AllCompanies\",\"ResidualAfterTop2\"],\"date_format\":{\"Month\":\"YYYY-MM\",\"EarliestDate\":\"YYYY-MM-DD\"},\"ExcludedTop2Companies\":\"join the two excluded company names with `+` in source-peak complaint-count descending order, breaking ties alphabetically\",\"TopState\":\"use the uppercase two-letter state abbreviation\",\"TopCompany\":\"use the company display name as shown in the source data\",\"tie_breaks\":\"for the earliest complaint use EarliestDate ascending then Complaint ID ascending\",\"SubIssue\":\"emit `NONE` when the complaint row has no sub-issue value\"}}","all_involved_urls":"null"} +{"task_id":"consumerfinance_007","domain":"CFPB_COMPLAINT_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"I am drafting a layered analysis report on the core factors behind a batch of cryptocurrency complaints. I need your help to verify the true causes of this complaint surge step by step using the CFPB complaint database.\n\nFirst, define the base scope of the analysis. Using the current CFPB product and issue taxonomy documentation, confirm the product bucket that \"Virtual currency\" falls under. Once the bucket is determined, strictly restrict the time range to between 2020-01-01 and 2022-08-26, and only for the \"Virtual currency\" subcategory under that product bucket, extract the original peak month (BaselinePeak) and its total complaint count for this initial complaint cohort.\n\nSecond, determine the shift in peaks by progressively removing core influencing factors. Round 1: In the original peak month identified above, identify the most frequent \"Company public response\" value, then completely remove all complaints with that value from the entire initial cohort to obtain the recalculated second peak month (AfterDominantPublicResponse). Round 2: In the second peak month, identify the most frequent \"Issue\" type, remove it from the residual data of the previous round to lock in the third emerging peak month (AfterDominantPublicResponseAndIssue). Round 3: In the third peak month, identify the single most complained-about company (Company), remove that company, and perform the final round of statistics to obtain the final residual peak month (AfterDominantPublicResponseIssueAndCompany).\n\nThird, for each of the identified characteristic months, extract detailed data. For these four complaint clusters, besides obtaining the total complaint count for that month, also determine the newly added removal dimension and its specific excluded value, and the count of that excluded value in the month that served as its reference source. Additionally, identify the state with the highest complaint count in that month and its complaint count, the most complained-about company within that state and its complaint volume, and the complete information of the earliest complaint received by the highest-complaint company in that state during that characteristic month, including complaint ID, date, Issue, and Sub-issue.\n\nFinally, after completing the investigation and information collation for all the above dimensions, concatenate all extracted parameters for these four complaint clusters strictly in the order of BaselinePeak, AfterDominantPublicResponse, AfterDominantPublicResponseAndIssue, and AfterDominantPublicResponseIssueAndCompany into four strings with no spaces. Each line's field order is strictly fixed as: |||||||||||||. In case of ties, always select by lexicographic ascending order; for the earliest complaint with the same date, select by ascending Complaint ID numeric value. Normalize all empty values to NONE before sorting.","start_url":"https://www.consumerfinance.gov/data-research/consumer-complaints/","output_format":"Concatenate into four strings with no spaces, strictly in the order of BaselinePeak, AfterDominantPublicResponse, AfterDominantPublicResponseAndIssue, AfterDominantPublicResponseIssueAndCompany; each line's field order is strictly fixed as: |||||||||||||. In case of ties, always select by lexicographic ascending order; for the earliest complaint with the same date, select by ascending Complaint ID numeric value. Normalize all empty values to NONE before sorting.","oracle_answer":"BaselinePeak|2021-05|336|NONE|NONE|0|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,AfterDominantPublicResponse|2022-07|31|Company public response|NONE|321|CA|6|BANK OF AMERICA, NATIONAL ASSOCIATION|4|5735227|2022-07-05|Other transaction problem|NONE,AfterDominantPublicResponseAndIssue|2021-10|13|Issue|Fraud or scam|26|TX|2|BANK OF AMERICA, NATIONAL ASSOCIATION|1|4821611|2021-10-18|Other transaction problem|NONE,AfterDominantPublicResponseIssueAndCompany|2021-06|8|Company|Foris DAX, Inc.|5|NC|3|TRUIST FINANCIAL CORPORATION|2|4462160|2021-06-15|Money was not available when promised|NONE","metadata":"{\"State-Gated Retrieval\":[\"Only consider Complaint Database records under the current product bucket's Virtual currency subcategory with a received date between 2020-01-01 and 2022-08-26.\",\"Determine the peak months for the four stages BaselinePeak, AfterDominantPublicResponse, AfterDominantIssue, and AfterDominantCompany sequentially as required.\",\"Each round's identified dominant Company public response, dominant Issue, and dominant Company must be written back and globally deleted from the corresponding upstream residual cohort before running the next round of statistics.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"current complaint-form taxonomy yields the product bucket for Virtual currency\",\"complaint records yield the baseline peak plus the dominant Company public response, dominant Issue, and dominant Company at successive residual-peak states\",\"final rows are produced only after each dominant value is applied to the full upstream residual cohort and then used to determine the next peak\"],\"control_dependency\":[\"dominant values found in a peak month cannot be deleted only inside that month; each must be propagated to the full upstream cohort\",\"each new residual peak depends on the prior round's global rewrite, so local month-by-month deletion gives the wrong chain\",\"downstream counts and exemplar complaints are valid only after the full three-stage waterfall is executed\"],\"freeze\":{\"historical_window\":\"Complaint Database records received from 2020-01-01 through 2022-08-26 under the current product-bucket mapping for Virtual currency\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only consider Complaint Database records under the current product bucket's Virtual currency subcategory with a received date between 2020-01-01 and 2022-08-26.\",\"Determine the peak months for the four stages BaselinePeak, AfterDominantPublicResponse, AfterDominantIssue, and AfterDominantCompany sequentially as required.\",\"Each round's identified dominant Company public response, dominant Issue, and dominant Company must be written back and globally deleted from the corresponding upstream residual cohort before running the next round of statistics.\"],\"exclusion_conditions\":[\"Exclude results that only delete records locally within the current peak month without writing back to the entire upstream cohort.\",\"Exclude results that do not re-find the next peak month on each round's residual cohort.\",\"Exclude intermediate or final fields based on downstream statistics that were not fully re-run.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"Cluster\",\"Month\",\"MonthComplaints\",\"NewExclusionType\",\"NewExclusionValue\",\"NewExclusionCountInSourcePeak\",\"TopState\",\"StateComplaints\",\"TopCompany\",\"CompanyComplaints\",\"EarliestComplaintID\",\"EarliestDate\",\"Issue\",\"SubIssue\"],\"cluster_order\":[\"BaselinePeak\",\"AfterDominantPublicResponse\",\"AfterDominantPublicResponseAndIssue\",\"AfterDominantPublicResponseIssueAndCompany\"],\"date_format\":{\"Month\":\"YYYY-MM\",\"EarliestDate\":\"YYYY-MM-DD\"},\"NewExclusionType\":\"emit the canonical exclusion-type label from the source workflow; when no new exclusion is applied, emit NONE\",\"NewExclusionValue\":\"emit the canonical excluded value; when no value exists, emit NONE\",\"TopState\":\"use the uppercase two-letter state abbreviation\",\"TopCompany\":\"use the company display name as shown in the source data\",\"tie_breaks\":\"normalize empty values to NONE before sorting; for other ties use lexicographic order ascending, and for the earliest complaint use EarliestDate ascending then Complaint ID ascending\",\"SubIssue\":\"emit NONE when the complaint row has no sub-issue value\"}}","all_involved_urls":"null"} +{"task_id":"europemc_001","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":21,"instruction":"I want to consolidate the admission variables actually used by several prediction schemes in this 2020 COVID-19 mortality risk prediction paper into a single line, to make it easy to see which variables overlap and which appear only in the comparison schemes.\nPlease follow the steps below. First, locate the target paper — a 2020 open-access review whose title contains all of \"prognosis model\", \"mortality risk\", and \"COVID-19\", and whose main text discusses hospitalized patients in Wuhan.\nThen, retain only two types of variables:\n- Type 1: admission variables that appear in both the Random Forest and XGBoost variable importance rankings.\n- Type 2: additional admission variables that do not appear in both rankings but are present in the CURB-65 or NEWS schemes used by the authors for comparison.\nNext, for each retained variable, record it in the following format:\nvariable~RF_rank_or_0~XGB_rank_or_0~F~C~N~X\nWhere:\n- RF_rank_or_0: the rank of this variable in the Random Forest ranking; write 0 if it is not included.\n- XGB_rank_or_0: the rank of this variable in the XGBoost ranking used in the paper; write 0 if it is not included.\n- F: whether this variable entered the authors' final logistic regression model.\n- C: whether this variable belongs to CURB-65.\n- N: whether this variable belongs to NEWS.\n- X: whether this variable belongs to the XGBoost model used as a comparison in the paper.\nFinally, sort all variables alphabetically by variable name, join them with | into a single line; if the paper cannot be found, output NONE.","start_url":"https://europepmc.org/advancesearch","output_format":"Next, for each retained variable, record it in the following format:\nvariable~RF_rank_or_0~XGB_rank_or_0~F~C~N~X\nWhere:\n- RF_rank_or_0: the rank of this variable in the Random Forest ranking; write 0 if it is not included.\n- XGB_rank_or_0: the rank of this variable in the XGBoost ranking used in the paper; write 0 if it is not included.\n- F: whether this variable entered the authors' final logistic regression model.\n- C: whether this variable belongs to CURB-65.\n- N: whether this variable belongs to NEWS.\n- X: whether this variable belongs to the XGBoost model used as a comparison in the paper.\nFinally, sort all variables alphabetically by variable name, join them with | into a single line; if the paper cannot be found, output NONE.","oracle_answer":"Age~4~2~1~1~0~0|Alanine aminotransferase~17~11~0~0~0~0|Aspartate transaminase~6~4~0~0~0~0|Blood urea nitrogen~5~7~0~1~0~0|Confusion~0~0~0~1~1~0|CRP~2~6~1~0~0~1|Creatinine~9~13~0~0~0~0|Diastolic pressure~16~17~0~1~0~0|Heart rate~15~14~0~0~1~0|LDH~1~1~1~0~0~1|Lymphocyte count~3~5~0~0~0~1|Monocytes~12~16~0~0~0~0|Neutrophil~7~3~0~0~0~0|Normal platelet~10~9~0~0~0~0|Oxygen inhalation~0~0~0~0~1~0|Respiratory rate~11~10~0~1~1~0|SPO2~0~0~0~0~1~0|Systolic pressure~13~12~0~1~1~0|Temperature~18~18~0~0~1~0|Total bilirubin~14~15~0~0~0~0|White blood cell~8~8~0~0~0~0","metadata":"{\"State-Gated Retrieval\":[\"First, locate the target paper: a 2020 open-access review whose title contains all of \\\"prognosis model\\\", \\\"mortality risk\\\", and \\\"COVID-19\\\", and whose main text discusses hospitalized patients in Wuhan.\",\"Retain only two types of variables: admission variables that appear in both the Random Forest and XGBoost rankings; or variables that do not appear in both rankings but are additional items belonging to CURB-65 or NEWS.\",\"For each variable, annotate it as required with RF rank, XGB rank, and whether it belongs to the final logistic regression, CURB-65, NEWS, and the comparison XGBoost model, then output in alphabetical order by variable name.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Europe PMC search results and the target open-access article yield the candidate Wuhan COVID mortality-risk review\",\"article tables and discussion sections yield RF/XGBoost rankings, final logistic-regression inclusion, and comparator-variable memberships for CURB-65 / NEWS / external XGBoost\",\"final rows are produced only after overlapping variables and comparator-only variables are merged into one normalized variable table\"],\"control_dependency\":[\"comparator-only variables must be captured from the discussion definitions rather than from Table 2 + Table 3 alone\",\"comparator membership must be read from the article's explicit scheme definitions rather than inferred from common clinical usage\",\"variable normalization must wait until RF/XGBoost overlap and comparator-only additions are both complete\"],\"freeze\":{\"historical_window\":\"the 2020 open-access COVID-19 mortality-risk review about Wuhan inpatients; variable inclusion and comparator definitions are taken from the article's current full-text tables and discussion\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"First, locate the target paper: a 2020 open-access review whose title contains all of \\\"prognosis model\\\", \\\"mortality risk\\\", and \\\"COVID-19\\\", and whose main text discusses hospitalized patients in Wuhan.\",\"Retain only two types of variables: admission variables that appear in both the Random Forest and XGBoost rankings; or variables that do not appear in both rankings but are additional items belonging to CURB-65 or NEWS.\",\"For each variable, annotate it as required with RF rank, XGB rank, and whether it belongs to the final logistic regression, CURB-65, NEWS, and the comparison XGBoost model, then output in alphabetical order by variable name.\"],\"exclusion_conditions\":[\"Exclude admission variables that do not appear in both RF and XGB rankings and also do not belong to CURB-65 / NEWS additional variables.\",\"Exclude results that stop at Table 2 + Table 3 and do not proceed to the discussion to read the comparator definitions.\",\"Exclude results that infer comparator variables by common sense rather than verifying against the paper's explicit definitions.\"],\"normalization\":{\"field_separator\":\"~\",\"record_separator\":\"|\",\"schema\":[\"variable\",\"RF_rank_or_0\",\"XGB_rank_or_0\",\"F\",\"C\",\"N\",\"X\"],\"variable\":\"use the variable wording normalized in the article tables; keep `Systolic pressure` and `Diastolic pressure` as separate variables\",\"rank_fields\":\"RF_rank_or_0 and XGB_rank_or_0 are positive integer ranks when present, otherwise 0\",\"boolean_fields\":\"F, C, N, and X are emitted as 1 or 0 only\",\"sorting_or_selection\":\"variable name alphabetical ascending\",\"stop_condition\":[\"the shared variable set from Table 2 and Table 3 is fully resolved\",\"the comparator definitions for CURB-65, NEWS, and the comparison XGBoost model are fixed before the final line is emitted\"]}}","all_involved_urls":"null"} +{"task_id":"europemc_002","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":6,"instruction":"Track studies that were Phase 1 in the 2021 Alzheimer's disease drug development pipeline review by their ClinicalTrials.gov identifier, and check whether they continue to appear in the 2022 and 2023 pipeline reviews.\nFollow these steps. First, locate the three articles: the 2021 review titled \"Alzheimer's disease drug development pipeline\", and the 2022 and 2023 open-access reviews in the same series.\nIn the 2021 review, retain only the studies that were listed as Phase 1 at that time.\nThen, in the 2022 and 2023 reviews, check each of these studies one by one, but match them by the same ClinicalTrials.gov identifier rather than by drug name alone, because drug names can change across years.\nFinally, keep only those studies that can still be found under the same ClinicalTrials.gov identifier in both 2022 and 2023. Format the result as a single line: NCT~2021_agent~2022_phase~2022_agent~2023_phase~2023_agent. Sort by NCT in ascending order and join records with |. If the set of three articles cannot be found, output NONE.","start_url":"https://europepmc.org/advancesearch","output_format":"Finally, keep only those studies that can still be found under the same ClinicalTrials.gov identifier in both 2022 and 2023. Format the result as a single line: NCT~2021_agent~2022_phase~2022_agent~2023_phase~2023_agent. Sort by NCT in ascending order and join records with |. If the set of three articles cannot be found, output NONE.","oracle_answer":"NCT03277573~Salsalate~P1~Salsalate~P1~Salsalate|NCT03634007~AAVrh.10hAPOE2~P1~LX1001~P2~LX1001|NCT03748303~Allopregnanolone (Allo)~P1~Allopregnanolone~P1~Allopregnanolone|NCT04149860~Lu AF87908~P1~Lu AF87908~P1~Lu AF87908|NCT04451408~LY3372993~P1~LY3372993~P1~LY3372993|NCT04500847~Emtricitabine~P1~Emtricitabine~P1~Emtricitabine","metadata":"{\"State-Gated Retrieval\":[\"Use only the Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline article as the baseline.\",\"Retention in 2022 and 2023 must be determined by exact match on the ClinicalTrials.gov NCT identifier, not by drug name alone.\",\"Keep only studies that are found under the same NCT in both 2022 and 2023, and output them sorted by NCT in ascending order.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the 2021, 2022, and 2023 pipeline reviews yield the 2021 Phase 1 baseline cohort and the later-year lookup tables\",\"article tables yield exact ClinicalTrials.gov NCT IDs, yearly phase labels, and yearly drug names for the same study\",\"final rows are produced only after 2021 baseline studies are re-identified in both later reviews by exact NCT matching\"],\"control_dependency\":[\"continuation must be matched by exact NCT rather than by drug name, because drug names drift across years\",\"2022 and 2023 lookups must use the fixed 2021 Phase 1 NCT set as the starting cohort rather than later-year table membership alone\",\"yearly phase/name fields are only valid after the same NCT is confirmed across all three reviews\"],\"freeze\":{\"historical_window\":\"the 2021, 2022, and 2023 open-access Alzheimer's disease drug development pipeline reviews; the baseline is the 2021 Phase 1 cohort and continuation is matched by exact ClinicalTrials.gov NCT\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Use only the Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline article as the baseline.\",\"Retention in 2022 and 2023 must be determined by exact match on the ClinicalTrials.gov NCT identifier, not by drug name alone.\",\"Keep only studies that are found under the same NCT in both 2022 and 2023, and output them sorted by NCT in ascending order.\"],\"exclusion_conditions\":[\"Exclude results that are continued by drug name alone without an exact match on the same ClinicalTrials.gov identifier.\",\"Exclude studies found only in 2022 or only in 2023, not continuously retained in both years.\",\"Exclude studies not in the 2021 baseline Phase 1 set.\"],\"normalization\":{\"field_separator\":\"~\",\"record_separator\":\"|\",\"schema\":[\"NCT\",\"agent_2021\",\"phase_2022\",\"agent_2022\",\"phase_2023\",\"agent_2023\"],\"NCT\":\"use the exact ClinicalTrials.gov identifier as the cross-year identity key\",\"phase_fields\":\"normalize phases to P1, P2, or P3; if the same NCT appears multiple times in a year, keep the highest phase for that year\",\"agent_fields\":\"keep the agent text as shown in each year-specific table\",\"sorting_or_selection\":\"NCT ascending\"}}","all_involved_urls":"null"} +{"task_id":"europemc_003","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"I want to see which candidate molecules predicted in the 2023 \"Antibodies to Watch\" article as expected to submit their first marketing applications in 2022–2023 have actually been approved or entered first regulatory review in the 2024 installment of the same series.\nFollow the steps below. First, find the open-access full texts of both the 2023 and 2024 \"Antibodies to Watch\" articles in Europe PMC.\nThen, in the 2023 article, identify all candidate molecules listed as **\"expected to submit first marketing applications in 2022–2023\"**.\nNext, check each of these molecules against the 2024 article and retain only those that have been approved or have entered first regulatory review.\nFinally, format each qualifying molecule as follows:\nINN~2023 category~2023 prediction label~2024 status~2024 indication~2024 region\nwhere:\n\t•\t2023 category uses NC/CA for non-cancer/cancer;\n\t•\t2024 status uses A/R for first approval/first regulatory review.\nSort by INN alphabetically and output as a single line joined by |; if neither article is found, output NONE.","start_url":"https://europepmc.org/advancesearch","output_format":"Finally, format each qualifying molecule as follows:\nINN~2023 category~2023 prediction label~2024 status~2024 indication~2024 region\nwhere:\n\t•\t2023 category uses NC/CA for non-cancer/cancer;\n\t•\t2024 status uses A/R for first approval/first regulatory review.\nSort by INN alphabetically and output as a single line joined by |; if neither article is found, output NONE.","oracle_answer":"Cosibelimab~CA~MAA,Q2 2023~R~Squamous cell carcinoma~US|Elranatamab~CA~2023~A~Multiple myeloma~US,EU,Switzerland,Brazil|Garadacimab~NC~BLA,2023~R~Hereditary angioedema~EU|Odronextamab~CA~BLA,H2 2022~R~Diffuse large B-cell lymphoma~US,EU|Pozelimab~NC~BLA,H2 2022~A~CHAPLE disease~US|Suciraslimab~NC~NDA,2023~R~Rheumatoid arthritis~China|Talquetamab~CA~2023–25~A~Multiple myeloma~US,EU,UK,Switzerland|Zolbetuximab~CA~BLA,2023~R~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China","metadata":"{\"State-Gated Retrieval\":[\"First, identify all candidate molecules in the 2023 Antibodies to Watch article that are predicted to submit first marketing applications in 2022-2023.\",\"Then, check each of these molecules against the 2024 article and retain only those that have been first approved or have entered first regulatory review.\",\"The 2024 status must distinguish A=first approval from R=first regulatory review, and include the 2024 indication and region.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the 2023 Antibodies to Watch article yields the forecast baseline of candidates expected to file in 2022-2023\",\"the 2024 article tables yield first-approval outcomes, first-regulatory-review outcomes, indications, and regions for the same INNs\",\"final rows are produced only after Table 1 approvals and Table 2 first-review candidates are merged back onto the 2023 forecast cohort\"],\"control_dependency\":[\"both 2024 Table 1 and Table 2 must be read so that first-review-but-not-yet-approved candidates are retained\",\"2024 status coding must distinguish approval from first regulatory review instead of collapsing both into a single positive match\",\"region and indication fields are valid only after the 2023 forecast cohort is reconciled against both 2024 tables\"],\"freeze\":{\"historical_window\":\"the 2023 and 2024 open-access Antibodies to Watch articles; baseline candidates come from the 2023 forecast set and 2024 outcomes come from current Table 1 plus Table 2\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"First, identify all candidate molecules in the 2023 Antibodies to Watch article that are predicted to submit first marketing applications in 2022-2023.\",\"Then, check each of these molecules against the 2024 article and retain only those that have been first approved or have entered first regulatory review.\",\"The 2024 status must distinguish A=first approval from R=first regulatory review, and include the 2024 indication and region.\"],\"exclusion_conditions\":[\"Exclude results that only check approvals in 2024 Table 1 without also consulting Table 2 for first regulatory review candidates.\",\"Exclude molecules not in the 2023 forecast baseline.\",\"Exclude candidates that were neither first approved nor entered first regulatory review in 2024.\"],\"normalization\":{\"field_separator\":\"~\",\"record_separator\":\"|\",\"schema\":[\"INN\",\"category_2023\",\"prediction_label_2023\",\"status_2024\",\"indication_2024\",\"region_2024\"],\"category_2023\":\"emit `NC` or `CA` exactly\",\"prediction_label_2023\":\"keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H2 2022`\",\"status_2024\":\"emit `A` for first approval and `R` for first regulatory review\",\"region_2024\":\"preserve the raw region string but remove spaces after commas, for example `US,EU`\",\"sorting_or_selection\":\"INN alphabetical ascending\"}}","all_involved_urls":"null"} +{"task_id":"europemc_004","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":9,"instruction":"I am evaluating the accuracy of annual antibody drug watchlist predictions and want to trace whether the 2022 cohort of candidates from the Antibodies to Watch series simply experienced delays in development progress. I need you to use the Europe PMC database to systematically map the year-over-year status changes for these candidates.\n\nFirst, establish the literature baseline and initial candidate set. Precisely locate the three open-access full-text Antibodies to Watch articles published in 2022, 2023, and 2024 in Europe PMC. Once all three articles are found, identify a set of antibodies (INN) with a specific delay pattern: those that were explicitly listed in the 2022 article under a category such as \"expected to file soon\" (identified by INN, drug code, project name, or other recognizable name) but, due to slower progress, still remained as watchlist candidates in the 2023 article.\n\nSecond, determine the latest status of these consecutively delayed candidates. For the identified antibody group, ascertain their final status in the 2024 article: whether they finally received first approval, are in first regulatory review, remain on the 2024 watchlist, or have completely disappeared from the 2024 main article list.\n\nFinally, after completing the cross-year literature review and status confirmation, aggregate the extracted parameters into a specific formatted single-line record. If all three target articles cannot be found, output NONE. If all three are successfully located, concatenate the internal parameters for each qualifying antibody in the fixed order \"INN~2022 category~2022 phase~2023 prediction label~2024 status~2024 phase or NA~2024 indication or NA~2024 region or NA\". Then join all identified candidates in strict alphabetical order by INN using the \"|\" symbol into a single string with no spaces.","start_url":"https://europepmc.org/advancesearch","output_format":"If all three target articles cannot be found, output NONE. If all three are successfully located, concatenate the internal parameters for each qualifying antibody in the fixed order \"INN~2022 category~2022 phase~2023 prediction label~2024 status~2024 phase or NA~2024 indication or NA~2024 region or NA\". Then, join all identified candidates in strict alphabetical order by INN using the \"|\" symbol into a single string with no spaces.","oracle_answer":"Apamistamab-I-131~CA~P3~BLA,H1 2023~F~P3~Ablation of bone marrow prior to transplantation in AML patients~NA|Bentracimab~NC~P3~BLA,Q4 2022~F~P3~Reversal of the antiplatelet effects of ticagrelor~NA|Cosibelimab~CA~P3~MAA,Q2 2023~R~NA~Squamous cell carcinoma~US|Erfonrilimab~CA~P3~NDA~F~P3~Pancreatic ductal adenocarcinoma~NA|Odronextamab~CA~P2~BLA,H2 2022~R~NA~Diffuse large B-cell lymphoma~US,EU|Talquetamab~CA~P2~2023-25~A~NA~Multiple myeloma~US,EU,UK,Switzerland|Tiragolumab~CA~P3~2023~F~P3~NSCLC~NA|Zanidatamab~CA~P2~2023~D~NA~NA~NA|Zolbetuximab~CA~P3~BLA,2023~R~NA~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China","metadata":"{\"State-Gated Retrieval\":[\"Start with the 2022 Antibodies to Watch candidates listed as \\\"expected to file soon\\\", but retain only those molecules that still remain as watchlist candidates in the 2023 article of the same series.\",\"For these consecutively delayed candidates, determine their final status in the 2024 article: first approved, in first regulatory review, or completely absent from Tables 1-4.\",\"Name matching must handle the Apamistamab naming drift; complete absence in 2024 must be explicitly encoded as D.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the 2022, 2023, and 2024 Antibodies to Watch articles yield the 2022 soon-to-file baseline, 2023 carry-over membership, and 2024 status tables\",\"article tables and full-text naming context yield name normalizations, 2024 table presence/absence, and final status labels for each carried-over INN\",\"final rows are produced only after 2022 candidates are filtered by 2023 carry-over status and then resolved against 2024 Tables 1-4 plus explicit absence\"],\"control_dependency\":[\"2022 candidates must first be filtered by 2023 carry-over status before they are matched against the 2024 tables\",\"Apamistamab naming drift forces explicit normalization before 2024 lookup\",\"complete 2024 absence must be emitted as D rather than treated as a lookup failure\"],\"freeze\":{\"historical_window\":\"the 2022, 2023, and 2024 open-access Antibodies to Watch articles; the 2022 baseline is filtered by 2023 carry-over status and then checked against 2024 Tables 1-4, with explicit absence retained as a status\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Start with the 2022 Antibodies to Watch candidates listed as \\\"expected to file soon\\\", but retain only those molecules that still remain as watchlist candidates in the 2023 article of the same series.\",\"For these consecutively delayed candidates, determine their final status in the 2024 article: first approved, in first regulatory review, or completely absent from Tables 1-4.\",\"Name matching must handle the Apamistamab naming drift; complete absence in 2024 must be explicitly encoded as D.\"],\"exclusion_conditions\":[\"Exclude results that directly match the 2022 baseline against 2024 without applying the 2023 carry-over filter.\",\"Exclude matching results that do not handle the Apamistamab naming drift.\",\"Exclude cases where complete 2024 absence is treated as a lookup failure rather than a status that must be output.\"],\"normalization\":{\"field_separator\":\"~\",\"record_separator\":\"|\",\"schema\":[\"INN\",\"category_2022\",\"phase_2022\",\"prediction_label_2023\",\"status_2024\",\"phase_or_NA_2024\",\"indication_or_NA_2024\",\"region_or_NA_2024\"],\"category_2022\":\"emit `NC` or `CA` exactly\",\"phase_2022\":\"normalize stage labels such as `Phase 3` to `P3` and `Pivotal Phase 2` to `P2`\",\"prediction_label_2023\":\"keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H1 2023`\",\"status_2024\":\"emit one of `A`, `R`, `F`, or `D` exactly\",\"conditional_fields_2024\":\"if status is A or R, phase_or_NA_2024 must be `NA` and region_or_NA_2024 must carry the raw region string; if status is F, region_or_NA_2024 is `NA` and phase_or_NA_2024 carries the normalized phase; if status is D, all three trailing 2024 fields are `NA`\",\"naming_exception\":\"preserve the fixed source exception around the Apamistamab-I-131 naming variant instead of over-normalizing the INN\",\"sorting_or_selection\":\"INN alphabetical ascending\"}}","all_involved_urls":"null"} +{"task_id":"europemc_005","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":20,"instruction":"I am compiling a cross-platform correspondence checklist for core predictors of COVID-19 hospitalization prognosis. Using the Europe PMC database, I need to work through the process of identifying the variables each specific model actually used, together with their matching attributes.\n\nFirst, establish the literature baseline. In Europe PMC, precisely locate the 2024 WHO global individual patient data validation paper and identify the four prognostic models that were successfully externally validated in low- and middle-income country data. Then trace back to the three original model papers corresponding to these four models.\n\nAfter locating these four target papers, the core task is to extract and verify the specific characteristics of the predictors. Determine which distinct admission variables each of the four models actually used in the evaluation. For each identified variable, clarify its acquisition pathway in the WHO platform baseline table: either a direct match under the same or a substantively equivalent name (marked as E), or a fixed mapped conversion (marked as M). Also trace the model-source attributes of these variables: whether they belong to the model with the strongest external validation performance (TopAUC), the model with calibration closest to the ideal (BestCal), or an original model that explicitly used dynamic data (Dyn).\n\nTo ensure consistent judgment criteria, model attribution, performance attribution, and variable conflicts must all be based on the verifiable model descriptions, performance summaries, and field definitions in the target papers. When the same concept has multiple naming or mapping methods, prioritize conservative mappings that maintain cross-model interpretability consistency, and flag mapping differences that may affect interpretability consistency.\n\nAfter completing the above literature tracing and variable characteristic extraction, finally extract these parameters to generate a formatted single-line summary record. For status flags, uniformly use 1 for yes and 0 for no for all boolean types. If the search fails to locate the one validation paper and the three original model papers, output NONE. If all are successfully located, after arranging all distinct variables strictly in alphabetical order by variable name, concatenate the parameters within each variable in the fixed order \"variable~category~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict\", then join all variables with \"|\" into a single string with no spaces.","start_url":"https://europepmc.org/advancesearch","output_format":"If the search fails to locate the one validation paper and the three original model papers, output NONE. If all are successfully located, after arranging all distinct variables strictly in alphabetical order by variable name, concatenate the parameters within each variable in the fixed order \"variable~category~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict\", then join all variables with \"|\" into a single string with no spaces. For all boolean types, uniformly use 1 for yes and 0 for no.","oracle_answer":"Age~DEM~1~1~1~1~Age~E~1~1~1~0|Cancer~COM~0~0~1~0~Cancer~E~1~0~0~0|Chronic kidney disease~COM~0~0~0~1~CKD~M~0~0~0~1|Chronic lung disease~COM~0~0~1~0~Pulmonary disease~M~1~0~0~0|Chronic renal disease~COM~0~0~1~0~CKD~M~1~0~0~1|Coronary heart disease~COM~0~1~0~0~CHD~M~0~0~0~1|Cough~SYM~0~0~1~0~Cough~E~1~0~0~0|Diabetes mellitus~COM~0~0~1~0~Diabetes~M~1~0~0~0|Diarrhea~SYM~0~0~1~0~Diarrhea~E~1~0~0~0|Dyspnea~SYM~0~0~1~0~Dyspnea~E~1~0~0~0|Fever~VIT~0~0~0~1~Body temperature~M~0~0~0~0|Heart disease~COM~0~0~1~0~CHD~M~1~0~0~1|Hypertension~COM~0~1~1~0~Hypertension~E~1~0~0~0|Immunocompromised status~COM~0~0~1~0~Immunosuppression~M~1~0~0~0|O2 saturation~VIT~1~0~0~0~Oxygen saturation~M~0~1~1~0|Respiratory rate~VIT~1~0~0~1~Respiratory rate~E~0~1~1~0|Sex~DEM~0~0~1~0~Men~M~1~0~0~0|Smoking~DEM~1~0~0~0~Smoking~E~0~1~1~1|Smoking status~DEM~0~0~0~1~Smoking~M~0~0~0~1|Systolic blood pressure~VIT~0~0~0~1~Systolic blood pressure~E~0~0~0~0","metadata":"{\"State-Gated Retrieval\":[\"First, in the 2024 WHO global individual patient data validation paper, identify the four prognostic models that were successfully externally validated in LMIC data, and trace back to the three corresponding original model papers.\",\"For each predictor, retain the original wording from WHO Table 1, annotate its matching method (E/M) in the WHO baseline table, and indicate whether it comes from the TopAUC, BestCal, or Dyn model.\",\"When encountering a predictor that was conceptually merged on the WHO side, trace back to the original Wang/Zhou papers to split it apart and then recalculate the relevant fields.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the 2024 WHO global validation paper yields the four externally validated models and the WHO-side predictor wording/mapping baseline\",\"the three original model papers yield model-specific predictor wordings, dynamic-data flags, and conflicts hidden by WHO-side conceptual merging\",\"final rows are produced only after WHO predictors are kept separate, traced back to the original papers, and then re-annotated for mapping and model provenance\"],\"control_dependency\":[\"conceptually merged WHO predictors must be split back out when the original Wang/Zhou papers expose distinct variables\",\"Table 2 mapping decisions are not valid until Table 1 wording and original-paper predictor sets are reconciled\",\"TopAUC / BestCal / Dyn flags must be determined after the predictor split is applied correctly\"],\"freeze\":{\"historical_window\":\"the 2024 WHO global IPD validation paper and the three linked original COVID prognosis-model papers, using their current open-access full texts and tables\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"First, in the 2024 WHO global individual patient data validation paper, identify the four prognostic models that were successfully externally validated in LMIC data, and trace back to the three corresponding original model papers.\",\"For each predictor, retain the original wording from WHO Table 1, annotate its matching method (E/M) in the WHO baseline table, and indicate whether it comes from the TopAUC, BestCal, or Dyn model.\",\"When encountering a predictor that was conceptually merged on the WHO side, trace back to the original Wang/Zhou papers to split it apart and then recalculate the relevant fields.\"],\"exclusion_conditions\":[\"Exclude results that directly merged conceptually similar predictors after WHO Table 1 without tracing back to the original papers for splitting.\",\"Exclude results that relied solely on loose mapping from WHO Table 2 without incorporating the original paper wording.\",\"Exclude results that fixed TopAUC/BestCal/Dyn annotations before applying the predictor split correction.\"],\"normalization\":{\"field_separator\":\"~\",\"record_separator\":\"|\",\"schema\":[\"variable\",\"category\",\"B\",\"W\",\"Zh\",\"Zo\",\"WHOfield\",\"WHOx\",\"TopAUC\",\"BestCal\",\"Dyn\",\"Conflict\"],\"variable_set\":\"the candidate variable set comes only from the WHO validation Table 1 and remains at the original 20 predictors\",\"conflict_groups\":\"do not pre-merge the three source conflict groups `Smoking`/`Smoking status`, `Chronic renal disease`/`Chronic kidney disease`, and `Coronary heart disease`/`Heart disease` before applying the conflict flag\",\"boolean_fields\":\"B, W, Zh, Zo, TopAUC, BestCal, Dyn, and Conflict are emitted as 1 or 0 only\",\"WHOx\":\"emit `E` for exact WHO matches or direct matches under a substantively equivalent name, `M` for the fixed mapped match, and `NA` when no WHO field matches\",\"sorting_or_selection\":\"variable name alphabetical ascending\"}}","all_involved_urls":"null"} +{"task_id":"genome_001","domain":"KEGG_BRITE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am compiling a reference list of medications for ulcerative colitis for in-hospital use. From the immunosuppressants cataloged in KEGG, I want to select those drug entries that have been approved in Japan by the end of June 2025 and that carry explicit CYP-related metabolism information or CYP inhibition indications. Please proceed in the following order: first, within the scope of KEGG immunosuppressants for ulcerative colitis, screen for drug entries approved in Japan by the end of June 2025; then check whether each entry has explicit CYP-related metabolism information or CYP inhibition indications, retaining only qualifying entries. Next, record each entry's Japanese therapeutic classification code, ATC code, corresponding target branch, and Japan first approval date. Finally, output a single-line string sorted by Japan first approval date from earliest to latest, in the format ||||; separate entries with commas; if no qualifying entries exist, output NONE.","start_url":"https://www.genome.jp/kegg/brite.html","output_format":"Output a single-line string sorted by Japan first approval date from earliest to latest, in the format ||||; separate entries with commas; if no qualifying entries exist, output NONE.","oracle_answer":"D09783|3999|L04AF01|JAK1/JAK2/JAK3/TYK2|2013/3/25,D11048|3999|L04AF03|JAK1|2020/1/23,D10931|2399|L04AE05|S1PR1/S1PR4/S1PR5|2025/6/24","metadata":"{\"State-Gated Retrieval\":[\"Within the scope of KEGG immunosuppressants for ulcerative colitis, retain only entries approved in Japan by 2025-06-30 and that carry explicit CYP-related metabolism information or CYP inhibition indications.\",\"Candidate drugs must be re-verified against the corrected UC drug list for Japanese therapeutic classification, ATC, target branch, CYP evidence, and Japan first approval date.\",\"Finally, output sorted by Japan first approval date from earliest to latest.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"KEGG disease H01466 and linked drug entries yield the ulcerative-colitis immunosuppressant candidate set\",\"each candidate drug entry yields Japanese class, ATC, target branch, CYP metabolism/inhibition evidence, and Japan approval date\",\"final rows are produced only after the full UC candidate set is determined and every candidate is checked against CYP evidence and PMDA timing\"],\"control_dependency\":[\"the candidate set must include Japanese class 3999 UC drugs when the disease page exposes them rather than being limited to 2399 alone\",\"target / CYP / PMDA validation must be applied across the full candidate set rather than only the old 2399 subset\",\"entries without explicit CYP evidence may be dropped only after the full candidate set has been established\"],\"freeze\":{\"historical_window\":\"KEGG ulcerative-colitis drug candidates with Japan approvals on or before 2025-06-30; current drug-entry annotations provide target, CYP, and Japan-class metadata\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Within the scope of KEGG immunosuppressants for ulcerative colitis, retain only entries approved in Japan by 2025-06-30 and that carry explicit CYP-related metabolism information or CYP inhibition indications.\",\"Candidate drugs must be re-verified against the corrected UC drug list for Japanese therapeutic classification, ATC, target branch, CYP evidence, and Japan first approval date.\",\"Finally, output sorted by Japan first approval date from earliest to latest.\"],\"exclusion_conditions\":[\"Exclude results that incorrectly lock the upstream scope to the 2399 digestive branch without falling back to the full UC drug list.\",\"Exclude entries without explicit CYP-related metabolism information or CYP inhibition indications.\",\"Exclude entries with a Japan approval date after 2025-06-30 or that are not within the KEGG UC immunosuppressant scope.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"DRUG_ID\",\"JP_class\",\"ATC\",\"Target_branch\",\"JP_date\"],\"dedup_key\":\"DRUG_ID\",\"JP_date\":\"use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value\",\"Target_branch\":\"emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`\",\"sorting_or_selection\":{\"primary\":\"JP_date ascending\",\"secondary\":\"DRUG_ID ascending\"}}}","all_involved_urls":"null"} +{"task_id":"genome_002","domain":"KEGG_GENOME","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am preparing a lecture page on classic animal endosymbiosis cases and want to find, among KEGG's host-symbiont examples, the case that meets the following conditions: it was already recorded by the end of 2005, its bacterial symbiont genome contains named extra replicons, and the names of those replicons directly correspond to amino acid synthesis modules on the host-symbiont joint pathway map. Process in the following order: first, among KEGG's host-symbiont examples, select those combinations whose bacterial symbiont KEGG GENOME entry has a Created year on or before 2005; then retain cases where the bacterial symbiont genome carries named extra replicons; next, verify that the replicon names directly correspond to amino acid synthesis modules on the host-symbiont joint pathway map; finally, within the joint pathway map for that host-symbiont combination, list all qualifying pathway-module pairs for that case and output a single-line string: ||||| (sorted by pathway ID in ascending order, separated by commas; output NONE if no qualifying items exist).","start_url":"https://www.genome.jp/kegg/genome/","output_format":"Output a single-line string: ||||| (sorted by pathway ID in ascending order, separated by commas; output NONE if no qualifying items exist).","oracle_answer":"api+buc|buc|00290|M00432|pLeu|2000,api+buc|buc|00400|M00023|pTrp|2000","metadata":"{\"State-Gated Retrieval\":[\"Retain only those host-symbiont examples where the bacterial symbiont KEGG GENOME Created year is on or before 2005 and the genome carries named extra replicons.\",\"The replicon names must directly correspond to amino acid synthesis modules on the host-symbiont joint pathway page.\",\"Finally, output all qualifying pathway-module-replicon records from the surviving case, sorted by pathway ID in ascending order.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"KEGG host-symbiont examples and symbiont genome pages yield the pre-2006 candidate pairs and named extra replicons\",\"Joint pathway maps, module pages, and genome annotations yield the pathway-module-replicon links attributable to the symbiont side\",\"Final rows are produced only after the surviving host-symbiont pair is validated against both replicon existence and module support on the joint pathway page\"],\"control_dependency\":[\"Only branches satisfying the named-plasmid requirement may be retained, so the bmy+wbm branch must be excluded when the wbm genome page fails that requirement\",\"Module retrieval must use the api+buc pathway state and the 00400 view, because that view is the one that actually exposes M00023\",\"Module support is valid only after symbiont-side evidence for both M00023 and M00432 is validated in the selected pathway state\"],\"freeze\":{\"historical_window\":\"KEGG host-symbiont examples whose symbiont GENOME Created year is on or before 2005; current joint pathway, module, and genome replicon annotations\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Retain only those host-symbiont examples where the bacterial symbiont KEGG GENOME Created year is on or before 2005 and the genome carries named extra replicons.\",\"The replicon names must directly correspond to amino acid synthesis modules on the host-symbiont joint pathway page.\",\"Finally, output all qualifying pathway-module-replicon records from the surviving case, sorted by pathway ID in ascending order.\"],\"exclusion_conditions\":[\"Exclude cases like bmy+wbm where the symbiont genome page does not satisfy the named-plasmid requirement.\",\"Exclude results that only follow pathway names along pages such as 00380 without returning to the joint pathway page to verify module evidence.\",\"Exclude records where the relationship between replicon name and module cannot be directly established on the joint pathway map.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"group\",\"symbiont\",\"pathway\",\"module\",\"replicon\",\"created_year\"],\"group\":\"Use the canonical host-symbiont group label from the source workflow, such as `api+buc`\",\"symbiont\":\"Use the bare lowercase KEGG organism code\",\"pathway\":\"Emit the numeric KEGG pathway ID without a `map` prefix\",\"module\":\"Normalize the KEGG module identifier to the `Mxxxxx` form\",\"replicon\":\"Preserve the named extra replicon exactly as displayed in the source, such as `pLeu` or `pTrp`\",\"created_year\":\"Emit the four-digit created year\",\"sorting_or_selection\":\"Pathway numeric ascending\"}}","all_involved_urls":"null"} +{"task_id":"genome_003","domain":"KEGG_BRITE","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"I am compiling a table of the approval order of systemic drugs for plaque psoriasis in Japan. Process as follows: first, within the scope of systemic drugs for plaque psoriasis approved in Japan by the end of 2024, identify the active ingredients that act on the IL-17/IL-23 signaling axis; then exclude all topical drugs and systemic drugs acting on other axes. Next, sort these active ingredients by their first approval date in Japan from earliest to latest; if approved on the same day, sort by DRUG_ID in ascending order. Finally, output a multi-row table with each row formatted as ||||.","start_url":"https://www.kegg.jp/brite/br08301","output_format":"Output a multi-row table with each row formatted as ||||.","oracle_answer":"D09967|Secukinumab|L04AC10|IL17A|2014/12/26\nD10061|Brodalumab|L04AC12|IL17RA|2016/7/4\nD10071|Ixekizumab|L04AC13|IL17A|2016/7/4\nD10438|Guselkumab|L04AC16|IL23A|2018/3/23\nD11052|Risankizumab|L04AC18|IL23A|2019/3/26\nD10400|Tildrakizumab|L04AC17|IL23A|2020/6/29\nD11550|Bimekizumab|L04AC21|IL17A/IL17F|2022/1/20\nD11817|Deucravacitinib|L04AF07|TYK2|2022/9/26","metadata":"{\"State-Gated Retrieval\":[\"Retain only the active ingredients that truly act on the IL-17/IL-23 signaling axis among systemic drugs for plaque psoriasis approved in Japan by 2024-12-31.\",\"The candidate set must cover the ligand side, receptor side, and TYK2 kinase side, not just the interleukin ligand side.\",\"Sort final entries by Japan first approval date in ascending order; if on the same day, sort by DRUG_ID in ascending order.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"KEGG disease/drug entry points yield the Japan-approved systemic plaque-psoriasis drug cohort through 2024-12-31\",\"each drug entry yields target branch, ATC, systemic-use validity, and Japan approval date for IL-17/IL-23-axis candidates\",\"final rows are produced only after ligand-side, receptor-side, and kinase-side candidates are jointly reconciled and re-sorted by Japan approval date\"],\"control_dependency\":[\"entry-point coverage must include receptor-side IL17RA and kinase-side TYK2 mechanisms when downstream drug pages expose them, rather than staying ligand-only\",\"Ustekinumab must be removed only when target interpretation shows IL12 + IL23A rather than the IL-17/IL-23-axis criterion required here\",\"systemic-use, Japanese 3999, and PMDA-date filtering must be applied after each expansion of the candidate set rather than attached to the earlier ligand-only state\"],\"freeze\":{\"historical_window\":\"Japanese plaque-psoriasis systemic drugs approved on or before 2024-12-31; current KEGG drug-entry annotations supply target branches and Japan approval dates\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Retain only the active ingredients that truly act on the IL-17/IL-23 signaling axis among systemic drugs for plaque psoriasis approved in Japan by 2024-12-31.\",\"The candidate set must cover the ligand side, receptor side, and TYK2 kinase side, not just the interleukin ligand side.\",\"Sort final entries by Japan first approval date in ascending order; if on the same day, sort by DRUG_ID in ascending order.\"],\"exclusion_conditions\":[\"Exclude topical drugs, non-systemic drugs, or entries outside the specified historical freeze window.\",\"Exclude entries such as Ustekinumab whose actual target is IL12 + IL23A and which do not meet the IL-17/IL-23 axis criterion required here.\",\"Exclude results that miss Brodalumab or Deucravacitinib due to looking only at the ligand side.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"DRUG_ID\",\"Name\",\"ATC\",\"Target_branch\",\"PMDA_date\"],\"PMDA_date\":\"use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value\",\"Target_branch\":\"emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`\",\"sorting_or_selection\":{\"primary\":\"PMDA_date ascending\",\"secondary\":\"DRUG_ID ascending\"}}}","all_involved_urls":"null"} +{"task_id":"genome_004","domain":"KEGG_GENOME","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am preparing a handout for a primate evolution course and want to summarize, in a two-row comparison table, the anomalous pattern behind why this lineage must obtain vitamin C from the diet. Among primate genome entries established by the end of 2022, identify the anomalous lower-level clade in which the upstream glucuronate module M00014 is still retained but the animal-type vitamin C biosynthesis module M00129 has been lost. Then verify the corresponding sister branch and confirm that it still retains M00129. Finally, output a two-row comparison table with columns rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year. The first row should be EXCEPTION_CLADE and the second row RETAINED_SISTER_CLADE. In all rows, vitamin_c_synthesis_module is fixed as M00129; vitamin_c_module_status should be LOST for the first row and RETAINED for the second. Use KEGG organism codes for the example species.","start_url":"https://www.genome.jp/kegg/kegg2.html","output_format":"Output a two-row comparison table with columns rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year.","oracle_answer":"1|EXCEPTION_CLADE|Primates|Haplorrhini|map00053|map00040|M00014|M00129|LOST|csyr|2022\n2|RETAINED_SISTER_CLADE|Primates|Strepsirrhini|map00053|map00040|M00014|M00129|RETAINED|oga|2022","metadata":"{\"State-Gated Retrieval\":[\"Search only among primate genome entries established by the end of 2022, and isolate the anomalous lower-level clade that retains the upstream glucuronate module M00014 but lacks the animal-type vitamin C biosynthesis module M00129.\",\"That anomalous clade must be paired with a sister branch under the same higher-level split, and the sister branch must still retain M00129.\",\"The final output must place the anomalous branch and the retained sister branch into a two-row comparison table, including the required pathway, module, and example-species fields.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the KEGG primate clade pages and genome entries yield candidate subclades and example species established through the cutoff year\",\"the pathway and module views yield M00014 and M00129 presence/absence evidence for the exception clade and its sister branch\",\"final rows are produced only after the exception clade and retained sister branch are jointly validated under the same parent split and paired with example organisms\"],\"control_dependency\":[\"the exception clade remains provisional until both the sister-branch contrast and the example-species checks succeed\",\"the comparison view must make retained M00014 and missing M00129 visible together\",\"the two output rows are emitted together only after the exception clade and retained sister branch are fixed under the same parent split\"],\"freeze\":{\"historical_window\":\"primate genome entries established on or before 2022, with current KEGG clade, pathway, and module pages used as relatively stable reference information for comparing retained M00014 against lost M00129\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Search only among primate genome entries established by the end of 2022, and isolate the anomalous lower-level clade that retains the upstream glucuronate module M00014 but lacks the animal-type vitamin C biosynthesis module M00129.\",\"That anomalous clade must have a contrastable sister branch, and that sister branch must still retain M00129.\",\"The final output must place the anomalous branch and the retained sister branch into a two-row comparison table, including the required pathway, module, and example-species fields.\"],\"exclusion_conditions\":[\"Exclude results that stop at Simiiformes without checking the broader boundary and therefore miss Haplorrhini.\",\"Exclude pathway views that do not make the M00014 versus M00129 contrast visible together.\",\"Exclude candidate clades that have not been validated against a retained sister branch.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"clade_role\",\"parent_clade\",\"clade\",\"anomaly_pathway\",\"contrast_pathway\",\"retained_upstream_module\",\"vitamin_c_synthesis_module\",\"vitamin_c_module_status\",\"example_org\",\"cutoff_year\"],\"rank\":\"emit 1 for EXCEPTION_CLADE and 2 for RETAINED_SISTER_CLADE\",\"clade_role\":[\"EXCEPTION_CLADE\",\"RETAINED_SISTER_CLADE\"],\"pathway_normalization\":\"emit KEGG pathway ids with the map prefix\",\"module_normalization\":\"emit KEGG module ids with the leading M\",\"vitamin_c_module_status\":[\"LOST\",\"RETAINED\"],\"organism_code\":\"use bare KEGG organism codes in lowercase, not species names\",\"cutoff_year\":\"use a four-digit year; this task is frozen at 2022\",\"sorting_or_selection\":\"emit rows in the fixed order EXCEPTION_CLADE then RETAINED_SISTER_CLADE\"}}","all_involved_urls":"null"} +{"task_id":"nvd_001","domain":"NVD","autonomy_type":"ordered table","instruction":"We are cleaning up a batch of old SBOM matching rules for the Duplicator product line. Some rules still rely on legacy vendor lineage and outdated product labeling, so we need to identify Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator but can still be traced back to snapcreek:duplicator in the deprecated vendor chain. Search NVD records for Duplicator-related CVEs published from 2018-01-01 through 2024-12-31. Retain only CVEs that satisfy all of the following conditions in Change History: the Initial Analysis is not yet lite or lite+pro; the first change to lite or lite+pro occurs in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurs on 2026-02-02. Exclude CVEs whose Initial Analysis already contained lite/lite+pro, as well as records that lack the required vendor-remap event or do not belong to the Duplicator product line. Finally, output a single-line ordered table with columns: CVE | lite_upper_version | lite_vs_lite+pro | analysis_event@date | snapcreek_to_awesomemotive@date.","start_url":"https://nvd.nist.gov/vuln/search#/nvd/home?resultType=records","output_format":"Output a single-line ordered table with columns: CVE | lite_upper_version | lite_vs_lite+pro | analysis_event@date | snapcreek_to_awesomemotive@date. Join rows with commas and sort by NVD published date ascending, then by CVE ascending.","oracle_output_cardinality":3,"oracle_answer":"CVE:2018-7543|1.2.32|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2018-17207|1.2.42|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2020-11738|1.3.28|lite+pro|ModifiedAnalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02","metadata":"{\"State-Gated Retrieval\":[\"Retain only Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator and that can be traced back to snapcreek:duplicator in the deprecated old vendor chain.\",\"Each candidate CVE must simultaneously satisfy the following in its Change History: the Initial Analysis is not yet lite/lite+pro; the first change to lite or lite+pro occurs in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurs on 2026-02-02.\",\"The final output retains only CVE rows that satisfy all three conditions above.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"NVD product/CPE search pages yield the current awesomemotive:duplicator family and the deprecated snapcreek:duplicator lineage\",\"each target CVE detail page and Change History yield the Initial Analysis state, the first lite/lite+pro analysis event, and the 2026-02-02 vendor-remap event\",\"final rows are produced only after candidate CVEs are intersected on both snapcreek -> awesomemotive migration and later introduction of lite/lite+pro in NIST analysis history\"],\"control_dependency\":[\"the search must include the deprecated snapcreek lineage rather than only the current product state\",\"vendor migration alone is insufficient until detail-level history confirms that lite/lite+pro was introduced after Initial Analysis\",\"candidate CVEs must be filtered against the full change-history chronology, excluding any whose Initial Analysis already contained lite\"],\"freeze\":{\"historical_window\":\"Duplicator CVEs published from 2018-01-01 through 2024-12-31, evaluated against NVD analysis history up to the 2026-02-02 snapcreek -> awesomemotive vendor-remap events\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Retain only Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator and that can be traced back to snapcreek:duplicator in the deprecated old vendor chain.\",\"Each candidate CVE must simultaneously satisfy the following in its Change History: the Initial Analysis is not yet lite/lite+pro; the first change to lite or lite+pro occurs in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurs on 2026-02-02.\",\"The final output retains only CVE rows that satisfy all three conditions above.\"],\"exclusion_conditions\":[\"Exclude results that only look at the current description or current product state without falling back to the deprecated snapcreek chain and Change History.\",\"Exclude CVEs whose Initial Analysis was already lite/lite+pro.\",\"Exclude records without a 2026-02-02 vendor remap, or that do not belong to the Duplicator product line.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema_note\":\"the checked oracle rowset uses the Duplicator CVE schema below, and normalization follows that verified schema throughout this task\",\"schema\":[\"CVE\",\"lite_upper_version\",\"lite_vs_lite+pro\",\"analysis_event@date\",\"snapcreek_to_awesomemotive@date\"],\"CVE\":\"emit the identifier in the canonical `CVE:YYYY-NNNN` form used by the oracle\",\"lite_vs_lite+pro\":\"emit `lite` or `lite+pro` exactly\",\"analysis_event@date\":\"emit `Reanalysis@YYYY-MM-DD` or `ModifiedAnalysis@YYYY-MM-DD` exactly as supported by the source record\",\"snapcreek_to_awesomemotive@date\":\"emit the ownership-transfer event as `snapcreek->awesomemotive@YYYY-MM-DD`\",\"sorting_or_selection\":{\"primary\":\"NVD published date ascending\",\"secondary\":\"CVE ascending\"}}}","all_involved_urls":"null"} +{"task_id":"nvd_002","instruction":"Identify which CPE 2.3 product identifiers using the legacy vendor name mysql:mysql within the MySQL 5.1 branch were explicitly migrated by NIST to the corresponding oracle:mysql CPE 2.3 product identifiers in the NVD (National Vulnerability Database) records for the four InnoDB denial-of-service vulnerabilities CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680. Migration here refers only to the vendor field in the CPE changing from the old vendor mysql to the new vendor oracle; it does not include cases where the identifier remains under the old vendor name and only version aliases are normalized. Retain only entries from the MySQL 5.1 branch that meet this criterion. Exclude entries from the MySQL 5.0 branch, as well as all entries that did not undergo a vendor migration and only had internal version-alias normalization under the old vendor. Output a multi-row ordered table with columns version_update | legacy_cpe | current_cpe | remap_time_nvd, sorted by numeric version in ascending order; within the same version, entries without an update suffix come before entries with an update suffix.","domain":"NVD","autonomy_type":"ordered table","oracle_output_cardinality":44,"start_url":"https://nvd.nist.gov/products/cpe/search","output_format":"Output a multi-row ordered table with columns version_update | legacy_cpe | current_cpe | remap_time_nvd, sorted by numeric version in ascending order; within the same version, entries without an update suffix come before entries with an update suffix.","oracle_answer":"version_update|legacy_cpe|current_cpe|remap_time_nvd\n5.1.1|cpe:2.3:a:mysql:mysql:5.1.1:::::::*|cpe:2.3:a:oracle:mysql:5.1.1:::::::*|2019-12-17 15:04:33\n5.1.2|cpe:2.3:a:mysql:mysql:5.1.2:::::::*|cpe:2.3:a:oracle:mysql:5.1.2:::::::*|2019-12-17 15:04:39\n5.1.3|cpe:2.3:a:mysql:mysql:5.1.3:::::::*|cpe:2.3:a:oracle:mysql:5.1.3:::::::*|2019-12-17 15:04:46\n5.1.4|cpe:2.3:a:mysql:mysql:5.1.4:::::::*|cpe:2.3:a:oracle:mysql:5.1.4:::::::*|2019-12-17 15:04:53\n5.1.10|cpe:2.3:a:mysql:mysql:5.1.10:::::::*|cpe:2.3:a:oracle:mysql:5.1.10:::::::*|2019-12-17 15:05:30\n5.1.11|cpe:2.3:a:mysql:mysql:5.1.11:::::::*|cpe:2.3:a:oracle:mysql:5.1.11:::::::*|2019-12-17 15:05:37\n5.1.12|cpe:2.3:a:mysql:mysql:5.1.12:::::::*|cpe:2.3:a:oracle:mysql:5.1.12:::::::*|2019-12-17 15:05:45\n5.1.13|cpe:2.3:a:mysql:mysql:5.1.13:::::::*|cpe:2.3:a:oracle:mysql:5.1.13:::::::*|2019-12-17 15:05:52\n5.1.14|cpe:2.3:a:mysql:mysql:5.1.14:::::::*|cpe:2.3:a:oracle:mysql:5.1.14:::::::*|2019-12-17 15:05:59\n5.1.15|cpe:2.3:a:mysql:mysql:5.1.15:::::::*|cpe:2.3:a:oracle:mysql:5.1.15:::::::*|2019-12-17 15:06:07\n5.1.16|cpe:2.3:a:mysql:mysql:5.1.16:::::::*|cpe:2.3:a:oracle:mysql:5.1.16:::::::*|2019-12-17 15:06:14\n5.1.17|cpe:2.3:a:mysql:mysql:5.1.17:::::::*|cpe:2.3:a:oracle:mysql:5.1.17:::::::*|2019-12-17 15:06:21\n5.1.18|cpe:2.3:a:mysql:mysql:5.1.18:::::::*|cpe:2.3:a:oracle:mysql:5.1.18:::::::*|2019-12-17 15:06:27\n5.1.19|cpe:2.3:a:mysql:mysql:5.1.19:::::::*|cpe:2.3:a:oracle:mysql:5.1.19:::::::*|2019-12-17 15:06:34\n5.1.20|cpe:2.3:a:mysql:mysql:5.1.20:::::::*|cpe:2.3:a:oracle:mysql:5.1.20:::::::*|2019-12-17 15:06:42\n5.1.21|cpe:2.3:a:mysql:mysql:5.1.21:::::::*|cpe:2.3:a:oracle:mysql:5.1.21:::::::*|2019-12-17 15:06:50\n5.1.22|cpe:2.3:a:mysql:mysql:5.1.22:::::::*|cpe:2.3:a:oracle:mysql:5.1.22:::::::*|2019-12-17 15:06:56\n5.1.23:a|cpe:2.3:a:mysql:mysql:5.1.23:a::::::|cpe:2.3:a:oracle:mysql:5.1.23:a::::::|2019-12-17 15:23:28\n5.1.24|cpe:2.3:a:mysql:mysql:5.1.24:::::::*|cpe:2.3:a:oracle:mysql:5.1.24:::::::*|2019-12-17 15:07:03\n5.1.25|cpe:2.3:a:mysql:mysql:5.1.25:::::::*|cpe:2.3:a:oracle:mysql:5.1.25:::::::*|2019-12-17 15:07:10\n5.1.26|cpe:2.3:a:mysql:mysql:5.1.26:::::::*|cpe:2.3:a:oracle:mysql:5.1.26:::::::*|2019-12-17 15:07:17\n5.1.27|cpe:2.3:a:mysql:mysql:5.1.27:::::::*|cpe:2.3:a:oracle:mysql:5.1.27:::::::*|2019-12-17 15:07:24\n5.1.28|cpe:2.3:a:mysql:mysql:5.1.28:::::::*|cpe:2.3:a:oracle:mysql:5.1.28:::::::*|2019-12-17 15:07:31\n5.1.29|cpe:2.3:a:mysql:mysql:5.1.29:::::::*|cpe:2.3:a:oracle:mysql:5.1.29:::::::*|2019-12-17 15:07:38\n5.1.30|cpe:2.3:a:mysql:mysql:5.1.30:::::::*|cpe:2.3:a:oracle:mysql:5.1.30:::::::*|2019-12-17 15:07:46\n5.1.31:sp1|cpe:2.3:a:mysql:mysql:5.1.31:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.31:sp1::::::|2019-12-17 15:23:35\n5.1.33|cpe:2.3:a:mysql:mysql:5.1.33:::::::*|cpe:2.3:a:oracle:mysql:5.1.33:::::::*|2019-12-17 15:07:55\n5.1.34:sp1|cpe:2.3:a:mysql:mysql:5.1.34:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.34:sp1::::::|2019-12-17 15:23:42\n5.1.35|cpe:2.3:a:mysql:mysql:5.1.35:::::::*|cpe:2.3:a:oracle:mysql:5.1.35:::::::*|2019-12-17 15:08:03\n5.1.36|cpe:2.3:a:mysql:mysql:5.1.36:::::::*|cpe:2.3:a:oracle:mysql:5.1.36:::::::*|2019-12-17 15:08:10\n5.1.37:sp1|cpe:2.3:a:mysql:mysql:5.1.37:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.37:sp1::::::|2019-12-17 15:23:49\n5.1.38|cpe:2.3:a:mysql:mysql:5.1.38:::::::*|cpe:2.3:a:oracle:mysql:5.1.38:::::::*|2019-12-17 15:08:17\n5.1.39|cpe:2.3:a:mysql:mysql:5.1.39:::::::*|cpe:2.3:a:oracle:mysql:5.1.39:::::::*|2019-12-17 10:22:31\n5.1.40|cpe:2.3:a:mysql:mysql:5.1.40:::::::*|cpe:2.3:a:oracle:mysql:5.1.40:::::::*|2019-12-17 10:22:46\n5.1.40:sp1|cpe:2.3:a:mysql:mysql:5.1.40:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.40:sp1::::::|2019-12-17 10:22:39\n5.1.41|cpe:2.3:a:mysql:mysql:5.1.41:::::::*|cpe:2.3:a:oracle:mysql:5.1.41:::::::*|2019-12-17 10:22:52\n5.1.42|cpe:2.3:a:mysql:mysql:5.1.42:::::::*|cpe:2.3:a:oracle:mysql:5.1.42:::::::*|2019-12-17 10:22:59\n5.1.43|cpe:2.3:a:mysql:mysql:5.1.43:::::::*|cpe:2.3:a:oracle:mysql:5.1.43:::::::*|2019-12-17 10:23:06\n5.1.43:sp1|cpe:2.3:a:mysql:mysql:5.1.43:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.43:sp1::::::|2019-12-17 10:23:11\n5.1.44|cpe:2.3:a:mysql:mysql:5.1.44:::::::*|cpe:2.3:a:oracle:mysql:5.1.44:::::::*|2019-12-17 10:23:17\n5.1.45|cpe:2.3:a:mysql:mysql:5.1.45:::::::*|cpe:2.3:a:oracle:mysql:5.1.45:::::::*|2019-12-17 10:23:24\n5.1.46|cpe:2.3:a:mysql:mysql:5.1.46:::::::*|cpe:2.3:a:oracle:mysql:5.1.46:::::::*|2019-12-17 10:23:38\n5.1.46:sp1|cpe:2.3:a:mysql:mysql:5.1.46:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.46:sp1::::::|2019-12-17 10:23:31\n5.1.47|cpe:2.3:a:mysql:mysql:5.1.47:::::::*|cpe:2.3:a:oracle:mysql:5.1.47:::::::*|2019-12-17 10:23:45","metadata":"{\"State-Gated Retrieval\":[\"Retain only CPE 2.3 entries from the MySQL 5.1 branch for which the NVD Change History of all four vulnerabilities CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680 clearly shows a mysql:mysql -> oracle:mysql vendor migration.\",\"Every result must provide version_update, legacy_cpe, current_cpe, and remap_time_nvd.\",\"Within the same version, entries without an update suffix come before entries with an update suffix, and output is sorted by numeric version in ascending order.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Current and deprecated MySQL 5.1 CPE search results yield candidate legacy/current CPE strings.\",\"The four target CVE pages and their Change History entries yield vendor-migration evidence, exact version_update strings, and remap timestamps.\",\"Final rows are produced only after taking the common mysql:mysql 5.1 -> oracle:mysql 5.1 migrations across all four CVEs and removing alias-only or 5.0 entries.\"],\"control_dependency\":[\"Legacy vendor mapping must be determined from Analysis Description plus Change History rather than from the current description/current CPE view.\",\"Include-deprecated results cannot be accepted wholesale because alias-only remaps must be filtered out.\",\"5.1-branch membership and sort order must be determined after the vendor-migration filter removes 5.0 and non-migration rows.\"],\"freeze\":{\"historical_window\":\"The MySQL 5.1 branches visible in CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680, restricted to explicit mysql:mysql -> oracle:mysql vendor-migration events.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Retain only CPE 2.3 entries from the MySQL 5.1 branch for which the NVD Change History of all four vulnerabilities CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680 clearly shows a mysql:mysql -> oracle:mysql vendor migration.\",\"Every result must provide version_update, legacy_cpe, current_cpe, and remap_time_nvd.\",\"Within the same version, entries without an update suffix come before entries with an update suffix, and output is sorted by numeric version in ascending order.\"],\"exclusion_conditions\":[\"Exclude entries from the MySQL 5.0 branch.\",\"Exclude entries that remain under the old vendor mysql:mysql, only have internal version-alias normalization, and did not undergo a vendor migration.\",\"Exclude results that are read only from the current Oracle MySQL 5.1 CPE state without using legacy mapping and Change History.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"required literal first row `version_update|legacy_cpe|current_cpe|remap_time_nvd`\",\"schema\":[\"version_update\",\"legacy_cpe\",\"current_cpe\",\"remap_time_nvd\"],\"version_update\":\"sort by numeric MySQL version ascending; within the same base version, the empty update comes before any non-empty update suffix\",\"legacy_cpe\":\"preserve the exact legacy CPE 2.3 string\",\"current_cpe\":\"preserve the exact current CPE 2.3 string\",\"remap_time_nvd\":\"emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form\",\"dedup_key\":\"(legacy_cpe, current_cpe)\"}}","all_involved_urls":"null"} +{"task_id":"nvd_003","domain":"NVD","autonomy_type":"ordered table","instruction":"We are cleaning up a batch of old SBOM matching rules that still represent Apache Tomcat 9.0.0 pre-release milestone versions using the legacy CPE form 9.0.0.Mx. We need to identify which milestone versions satisfy both of the following conditions: (1) they appear in the current NVD affected-product version ranges for the four historical vulnerabilities CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797; and (2) the NVD change history shows that the CPE for these versions was remapped from the old short form (e.g., m1, m2) to the full form (e.g., milestone1, milestone2). Start from the Apache Tomcat 9.0.0 milestone versions, check each against the current NVD affected-product version ranges for these four CVEs, then examine the corresponding change history records. Retain only those milestone versions that satisfy both conditions. Exclude milestones that are included only because of other Tomcat 9.0.0 pre-release vulnerabilities, and do not include Tomcat 6, 7, 8, 8.5, or any non-Tomcat products. Finally, output an ordered multi-row table sorted by milestone number in ascending order, with columns: milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd.","start_url":"https://nvd.nist.gov/products/cpe/search","output_format":"Output as a Markdown multi-row table with fixed column names: milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd. Sort by milestone number in ascending order (M1, M2, ..., M9).","oracle_output_cardinality":9,"oracle_answer":"milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd\nM1|cpe:2.3:a:apache:tomcat:9.0.0:m1:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone1:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM2|cpe:2.3:a:apache:tomcat:9.0.0:m2:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone2:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM3|cpe:2.3:a:apache:tomcat:9.0.0:m3:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone3:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM4|cpe:2.3:a:apache:tomcat:9.0.0:m4:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone4:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM5|cpe:2.3:a:apache:tomcat:9.0.0:m5:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone5:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM6|cpe:2.3:a:apache:tomcat:9.0.0:m6:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone6:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM7|cpe:2.3:a:apache:tomcat:9.0.0:m7:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone7:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM8|cpe:2.3:a:apache:tomcat:9.0.0:m8:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone8:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM9|cpe:2.3:a:apache:tomcat:9.0.0:m9:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone9:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18","metadata":"{\"State-Gated Retrieval\":[\"Retain only Apache Tomcat 9.0.0 milestone versions that appear in the current affected-product ranges for all four target CVEs: CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797.\",\"These versions must also have a CPE Deprecation Remap from mN to milestoneN visible in the NVD Change History.\",\"Finally, output sorted by milestone number in ascending order, and the required_cves field must list these four specific CVEs.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the current milestoneN CPE search and detail pages yield the Tomcat milestone family and the legacy mN mapping anchors\",\"the four target CVE pages and Change History entries yield the exact mN -> milestoneN deprecation remaps and the required-CVE intersection\",\"final rows are produced only after taking the remaps common to all four target CVEs and sorting by numeric milestone\"],\"control_dependency\":[\"the candidate milestone set must be determined from the four-target-CVE intersection rather than from all prerelease Tomcat CVEs\",\"later remapped milestones such as M10+ must be excluded by applying the specified four-CVE boundary\",\"only explicit NVD CPE Deprecation Remap events from mN to milestoneN count, so generic Tomcat prerelease visibility cannot be accepted as evidence\"],\"freeze\":{\"historical_window\":\"the Tomcat 9.0.0 prerelease milestones jointly covered by CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797, with remap evidence fixed to the 2023-12-08 11:41:18 NVD deprecation events\"},\"answer_type\":\"multi-row ordered table\"}","all_involved_urls":"{\"fixed_entry_and_docs\":[\"https://nvd.nist.gov/products/cpe/search\",\"https://nvd.nist.gov/vuln/vulnerability-detail-pages\"],\"cpe_search_result_pages\":[\"https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL\",\"https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED\",\"https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20m&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED\",\"https://nvd.nist.gov/products/cpe/search/results?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED\"],\"representative_cpe_detail_pages\":[\"https://nvd.nist.gov/products/cpe/detail/615922?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED\",\"https://nvd.nist.gov/products/cpe/detail/615947?keyword=cpe%3A2.3%3Aa%3Aapache&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED\"],\"row_level_cpe_api_urls_m1_to_m9\":[\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone2%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone3%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone4%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone5%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone6%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone7%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone8%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone9%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\"],\"target_cve_detail_pages\":[\"https://nvd.nist.gov/vuln/detail/CVE-2016-5018\",\"https://nvd.nist.gov/vuln/detail/CVE-2016-6794\",\"https://nvd.nist.gov/vuln/detail/CVE-2016-6796\",\"https://nvd.nist.gov/vuln/detail/CVE-2016-6797\"],\"negative_control_cve_detail_pages\":[\"https://nvd.nist.gov/vuln/detail/CVE-2016-6816\",\"https://nvd.nist.gov/vuln/detail/CVE-2016-6817\",\"https://nvd.nist.gov/vuln/detail/CVE-2019-0221\"],\"cve_change_history_api\":[\"https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-5018&eventName=CPE%20Deprecation%20Remap\",\"https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6794&eventName=CPE%20Deprecation%20Remap\",\"https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6796&eventName=CPE%20Deprecation%20Remap\",\"https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6797&eventName=CPE%20Deprecation%20Remap\",\"https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6816&eventName=CPE%20Deprecation%20Remap\",\"https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6817&eventName=CPE%20Deprecation%20Remap\",\"https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2019-0221&eventName=CPE%20Deprecation%20Remap\"],\"representative_change_record_pages\":[\"https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=04%2F18%2F2022T13%3A57%3A03.500-0400\",\"https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=08%2F24%2F2017T09%3A11%3A40.690-0400\"]}","rubric":"{\"inclusion_conditions\":[\"Retain only Apache Tomcat 9.0.0 milestone versions that appear in the current affected-product ranges for all four target CVEs: CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797.\",\"These versions must also have a CPE Deprecation Remap from mN to milestoneN visible in the NVD Change History.\",\"Finally, output sorted by milestone number in ascending order, and the required_cves field must list these four specific CVEs.\"],\"exclusion_conditions\":[\"Exclude milestones that are included only because of other Tomcat 9.0.0 pre-release vulnerabilities, such as M10/M11 and later milestones.\",\"Exclude Tomcat 6, 7, 8, 8.5, or any non-Tomcat products.\",\"Exclude records that lack explicit NVD remap evidence and are only visible on the current milestone page.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"required literal first row `milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd`\",\"schema\":[\"milestone\",\"legacy_cpe\",\"current_cpe\",\"required_cves\",\"remap_time_nvd\"],\"milestone\":\"emit the canonical milestone label `M1` through `M9` and sort by the numeric suffix ascending\",\"legacy_cpe\":\"preserve the exact legacy CPE 2.3 string containing the short milestone token such as `m1`\",\"current_cpe\":\"preserve the exact current CPE 2.3 string containing the full milestone token such as `milestone1`\",\"required_cves\":\"emit the fixed literal `CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797`\",\"remap_time_nvd\":\"emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form\"}}"} +{"task_id":"reptile_001","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"I am compiling a name concordance for early museum specimens of Indian snakes recorded in George A. Boulenger's 1890 work *The Fauna of British India, Including Ceylon and Burma*. Proceed as follows: first, using this specimen set as the scope, look up each corresponding current species page in the Reptile Database and retain only entries that simultaneously satisfy the following conditions: the species has since been reassigned to a different genus; the page still retains BMNH type specimen information; and the type locality still corresponds to India. For each qualifying entry, identify from the names listed on that page the oldest binomial that is closest to the present but has not yet been updated to the current genus name. Then, search again using this full old name and determine whether the search result points to only this single record. Finally, output the results as a single line sorted alphabetically by current accepted name, in the format |||; separate entries with semicolons. If no qualifying entries exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output the results as a single line sorted alphabetically by current accepted name, in the format |||; separate entries with semicolons. If no qualifying entries exist, output NONE.","oracle_answer":"Argyrophis oatesii|Typhlops oatesii|UNIQUE|SYNTYPES;Dendrelaphis grandoculis|Ahaetulla grandoculis|UNIQUE|LECTOTYPE;Fowlea sanctijohannis|Xenochrophis sanctijohannis|UNIQUE|HOLOTYPE;Gerrhopilus beddomii|Typhlops beddomii|UNIQUE|SYNTYPES;Hebius khasiensis|Amphiesma khasiense|UNIQUE|LECTOTYPE;Hebius parallelus|Amphiesma parallelum|AMBIG|LECTOTYPE;Indotyphlops jerdoni|Typhlops jerdoni|UNIQUE|SYNTYPES;Myriopholis blanfordii|Leptotyphlops blanfordi|AMBIG|SYNTYPES","metadata":"{\"State-Gated Retrieval\":[\"Candidates must come from the historical museum entries of Indian snakes in Boulenger 1890 *Fauna of British India*.\",\"The current Reptile Database species page must simultaneously satisfy: the species has been reassigned to a different genus; the page still retains BMNH type specimen information; the type locality still corresponds to India.\",\"On each qualifying page, select the oldest binomial that is closest to the present but has not yet been updated to the current genus name, then perform an exact back-search using this old name and label it UNIQUE or AMBIG.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the Boulenger 1890 historical sample and current accepted-species pages yield candidates that changed genus while retaining BMNH type data and India-compatible type locality\",\"each accepted page yields the nearest pre-current-genus old label, the BMNH type status, and the historical/type-locality evidence anchoring the entity\",\"final rows are produced only after the old-label exact back-search is evaluated for uniqueness without losing the original entity anchor\"],\"control_dependency\":[\"when an exact old-label back-search now hits multiple species, the original anchored entity must be kept and the uniqueness label must be set to AMBIG\",\"once a candidate has passed the historical-cluster, genus-shift, BMNH, and India-locality gates, later old-label ambiguity can only rewrite the uniqueness field, not the entity itself\",\"candidate anchoring must be preserved across the two-stage workflow so that old-label search noise does not redirect the accepted-species row\"],\"freeze\":{\"historical_window\":\"the George A. Boulenger 1890 British India sample, evaluated against current Reptile Database accepted pages, synonym labels, BMNH type data, and present type-locality text\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Candidates must come from the historical museum entries of Indian snakes in Boulenger 1890 *Fauna of British India*.\",\"The current Reptile Database species page must simultaneously satisfy: the species has been reassigned to a different genus; the page still retains BMNH type specimen information; the type locality still corresponds to India.\",\"On each qualifying page, select the oldest binomial that is closest to the present but has not yet been updated to the current genus name, then perform an exact back-search using this old name and label it UNIQUE or AMBIG.\"],\"exclusion_conditions\":[\"Exclude entries where the current accepted name has not undergone a genus change, or where the page no longer retains BMNH type specimen information.\",\"Exclude entries whose type locality does not correspond to India.\",\"Do not discard candidates whose exact old-name back-search is non-unique; such candidates should be retained and labeled AMBIG.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\";\",\"schema\":[\"accepted name\",\"old label\",\"UNIQUE/AMBIG\",\"BMNH status\"],\"accepted_name\":\"emit the current accepted binomial exactly as shown in the reconciled source\",\"old_label\":\"preserve the historical label exactly as used on the legacy branch\",\"UNIQUE/AMBIG\":\"emit `UNIQUE` or `AMBIG` in uppercase\",\"BMNH_status\":\"normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or SYNTYPES\",\"sorting_or_selection\":\"accepted name alphabetical ascending\"}}","all_involved_urls":"null"} +{"task_id":"reptile_002","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am compiling current name correspondences for early museum specimens of Southeast Asian Lygosoma. The old labels correspond to Riopa combinations attributed to Smith (1935/1937) in the Synonym section of each species page, but some of these old names now map to multiple current species under the current classification. Process as follows: first, within the current Lygosoma checklist, examine each current species page and locate these Smith (1935/1937) Riopa combinations in the Synonym section; then compare these old names, identify those that point to multiple current species, and list all involved current species. Next, for each qualifying current species, record the first-listed type specimen number, type category, and the region ultimately corresponding to the type locality on that page. Finally, output the results as a single line with entries sorted alphabetically by current accepted name, in the format ||||; separate entries with semicolons; if no qualifying entries exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output the results as a single line with entries sorted alphabetically by current accepted name, in the format ||||; separate entries with semicolons; if no qualifying entries exist, output NONE.","oracle_answer":"Lygosoma bampfyldei|Riopa bampfyldei|BMNH 1946.8.10.84|SYNTYPES|East Malaysia;Lygosoma peninsulare|Riopa bampfyldei|LSUHC 13857|HOLOTYPE|Peninsular Malaysia;Lygosoma schneideri|Riopa bampfyldei|NMBA 4743|HOLOTYPE|Indonesia","metadata":"{\"State-Gated Retrieval\":[\"Retain only those accepted species that can be traced from the Smith 1937 old-name chain to a current Lygosoma record and for which the type accession, type status, and locality can be read on the current page.\",\"For each accepted record, output the accepted name, the corresponding old label, the type accession, the type status, and the locality.\",\"If the same exact old name is attached to multiple accepted species, retain them as separate chains.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the Smith 1937 old-name chain yields the three current Lygosoma accepted pages connected to Riopa bampfyldei / Lygosoma bampfyldei\",\"each accepted page yields its own type accession, type status, and type locality needed to separate the homonymous old-name paths\",\"final rows are produced only after the one-to-many old-name split is rebuilt and the three paths are re-anchored to their own type evidence\"],\"control_dependency\":[\"same-specific-epithet matching cannot establish a one-to-one mapping when the same Smith 1937 old name appears on multiple accepted pages\",\"once literal old-name reuse is exposed, the workflow must keep the original parallel three-chain state rather than collapsing to a one-to-one mapping\",\"type accession and locality evidence must be read separately for each chain rather than patched onto the first stopping page\"],\"freeze\":{\"historical_window\":\"the current Reptile Database accepted pages linked to the Smith 1937 old-name cluster around Riopa bampfyldei, using current type accessions, statuses, and localities\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Retain only those accepted species that can be traced from the Smith 1937 old-name chain to a current Lygosoma record and for which the type accession, type status, and locality can be read on the current page.\",\"For each accepted record, output the accepted name, the corresponding old label, the type accession, the type status, and the locality.\",\"If the same exact old name is attached to multiple accepted species, retain them as separate chains.\"],\"exclusion_conditions\":[\"Exclude results that assume the same species based solely on the old name and current specific epithet being identical.\",\"Exclude results that retain only the first chain after discovering the same exact old name on multiple accepted pages.\",\"Exclude results that do not return to each accepted page to re-verify the type accession and locality.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\";\",\"schema\":[\"accepted\",\"Smith-era Riopa label\",\"first type code\",\"type status\",\"region\"],\"accepted\":\"emit the current accepted binomial exactly as shown in the reconciled source\",\"Smith-era_Riopa_label\":\"preserve the Smith-era Riopa label exactly as used on the legacy branch\",\"first_type_code\":\"emit the first accession code that follows the selected type-status statement\",\"type_status\":\"normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES\",\"region\":\"emit the modern geographic region label from the source reconciliation, such as East Malaysia or Peninsular Malaysia\",\"sorting_or_selection\":\"accepted name alphabetical ascending\"}}","all_involved_urls":"null"} +{"task_id":"reptile_003","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":10,"instruction":"I am organizing current-name cross-references for a batch of early museum catalog cards that were still filed under Mabuya or Mabuia around 1980, and need to map them into the current Eutropis checklist. Process as follows: first, examine each species page in the current Eutropis checklist one by one, and on each page identify the first synonym label that is both in Mabuya or Mabuia form and tagged with the 1980 citation year. Then, perform an exact name search using that 1980 old label, and retain only those species for which the back-search result points to more than one current Eutropis entry. For each qualifying entry, record its current accepted name, the 1980 old label, the qualifier annotation for that old label on the page, and the first type category and code listed on the current page. Finally, output a single line per entry in the format |<1980 label>|||, sorted alphabetically by old label and, within the same old label, by accepted name. Join entries with semicolons. If no qualifying entries exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output a single line per entry in the format |<1980 label>|||, sorted alphabetically by old label and, within the same old label, by accepted name. Join entries with semicolons. If no qualifying entries exist, output NONE.","oracle_answer":"Eutropis indeprensa|Mabuya indeprensa|NONE|HOLOTYPE|CAS 85664;Eutropis sahulinghangganan|Mabuya indeprensa|PART-MISID|HOLOTYPE|PNM 9867;Eutropis multifasciata|Mabuya multifasciata|NONE|NEOTYPE|MZB 11912;Eutropis multicarinata|Mabuya multicarinata|NONE|HOLOTYPE|BMNH 1946.8.15.13-15;Eutropis borealis|Mabuya multicarinata borealis|NONE|HOLOTYPE|CAS 15447;Eutropis islamaliit|Mabuya multicarinata borealis|PART-MISID|HOLOTYPE|PNM 9847;Eutropis caraga|Mabuya multicarinata multicarinata|PART-MISID|HOLOTYPE|PNM 9845;Eutropis palauensis|Mabuya multicarinata multicarinata|PART-BYIMPL|HOLOTYPE|CAS 248251;Eutropis dattaroyi|Mabuya rudis|PART|HOLOTYPE|ZSI 25118;Eutropis rudis|Mabuya rudis|NONE|LECTOTYPE|BMNH 1946.8.15.26","metadata":"{\"State-Gated Retrieval\":[\"Retain only those current Eutropis accepted species for which the synonym block contains, scanning top-down, a first synonym label that begins with Mabuya or Mabuia and has the year 1980.\",\"Then, perform an exact name search using that 1980 old label, and output the accepted name, old label, back-search qualifier, type status, and type specimen.\",\"If the subsequent back-search reveals additional matching entries, revisit the earlier results and include them in the final output.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"current Eutropis detail pages yield the first 1980-tagged Mabuya/Mabuia synonym label for each accepted species\",\"exact back-search on that 1980 old label yields the present accepted page, type status, and type specimen needed for the output row\",\"final rows are produced only after the 1980-specific old-label anchor is rebuilt and the accepted-species set is expanded when back-search evidence reveals omitted entries\"],\"control_dependency\":[\"the workflow must identify the first Mabuya/Mabuia label carrying the 1980 year rather than stopping at the first old label on the page\",\"when old-label back-search reveals missing entries such as Eutropis dattaroyi, the accepted-species set must be expanded to include them rather than patched in place\",\"accepted-page synonym parsing and back-search interpretation must stay coupled so that 1980 labels are not replaced by older but irrelevant names\"],\"freeze\":{\"historical_window\":\"current Reptile Database Eutropis pages, restricted to the first synonym label that is both Mabuya/Mabuia-form and tagged with the 1980 citation year\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Retain only those current Eutropis accepted species for which the synonym block contains, scanning top-down, a first synonym label that begins with Mabuya or Mabuia and has the year 1980.\",\"Then, perform an exact name search using that 1980 old label, and output the accepted name, old label, back-search qualifier, type status, and type specimen.\",\"If the subsequent back-search reveals additional matching entries, revisit the earlier results and include them in the final output.\"],\"exclusion_conditions\":[\"Exclude results that mistakenly treat the first old name on the page as the first 1980 old label.\",\"Exclude results whose exact back-search on the 1980 old label points to only a single current Eutropis entry.\",\"Exclude results that, when subsequent evidence reveals omitted entries, do not revisit the earlier results and rebuild the accepted-species set.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\";\",\"schema\":[\"accepted\",\"1980 label\",\"qualifier\",\"type status\",\"first type code\"],\"accepted\":\"emit the current accepted binomial exactly as shown in the reconciled source\",\"1980_label\":\"preserve the 1980-era label exactly as used on the legacy branch\",\"qualifier\":\"normalize to one of `NONE`, `PART`, `PART-MISID`, or `PART-BYIMPL`\",\"type_status\":\"normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES\",\"first_type_code\":\"emit the first accession code that follows the selected type-status statement\",\"sorting_or_selection\":{\"primary\":\"1980 label alphabetical ascending\",\"secondary\":\"accepted name alphabetical ascending\"}}}","all_involved_urls":"null"} +{"task_id":"reptile_004","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":6,"instruction":"I am organizing a batch of early museum catalog cards for half-toed geckos that still use the old labels listed in the comments section of the Hemidactylus brookii species page. Process as follows: first examine the old labels listed in the comments section of the current Hemidactylus brookii species page, and select those that are no longer placed in Hemidactylus brookii and for which the database has clearly provided their current assignment. Then, for each qualifying label, determine the current species it should ultimately be assigned to; if merging from that label to the current species must pass through an intermediate old name, write that intermediate name, otherwise write DIRECT. At the same time, record the type status, type code, and the country of the type locality for that label itself. Finally, output a single line with entries sorted alphabetically by legacy label: |||||; separate entries with semicolons; if no qualifying entries exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output a single line with entries sorted alphabetically by legacy label: |||||; separate entries with semicolons; if no qualifying entries exist, output NONE.","oracle_answer":"Hemidactylus brooki leightoni|Hemidactylus angulatus|DIRECT|HOLOTYPE|BMNH 1946.8.25.65|Colombia;Hemidactylus brookii haitianus|Hemidactylus angulatus|DIRECT|LECTOTYPE|ZMH R22378|Haiti;Hemidactylus brookii parvimaculatus|Hemidactylus parvimaculatus|DIRECT|HOLOTYPE|NMSL No. RG. 15|Sri Lanka;Hemidactylus brookii subtriedroides|Hemidactylus murrayi|Hemidactylus tenkatei|LECTOTYPE|BMNH [subtriedroides] [tenkatei]|Myanmar;Hemidactylus gleadowi|Hemidactylus gleadowi|DIRECT|NEOTYPE|BMNH 1884.7.25.8|Pakistan;Hemidactylus tenkatei|Hemidactylus murrayi|DIRECT|LECTOTYPE|RMNH 4353|Indonesia","metadata":"{\"State-Gated Retrieval\":[\"Each result must start from the old-label chain specified in the task and ultimately determine the accepted name, bridge status, type status, type accession, and locality from the current accepted page.\",\"For the subtriedroides branch, continue along tenkatei to murrayi, output the final accepted name as Hemidactylus murrayi, and retain bridge=Hemidactylus tenkatei.\",\"For branches such as haitianus and leightoni, read their own locality/type lines rather than borrowing header information from the wrong page.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"The old-label chains from Hemidactylus angulatus and related names yield accepted pages, bridge names, and the type/locality lines for each path.\",\"Comment, Types, and type-comment blocks yield the later evidence that tenkatei is further sunk into H. murrayi.\",\"Final rows are produced only after each old-label path is re-anchored to its own locality/type line and the subtriedroides -> tenkatei -> murrayi bridge chain is completed.\"],\"control_dependency\":[\"Type data must be taken from the locality/type line belonging to the actual old-label branch rather than from the header block of the wrong accepted page.\",\"Stopping at the intermediate tenkatei bridge is insufficient; the workflow must continue to the later murrayi evidence and rewrite both tenkatei and subtriedroides final accepted names.\",\"Bridge labels remain useful, but final accepted names and type lines must be determined from the deeper synonym chain.\"],\"freeze\":{\"historical_window\":\"Current Reptile Database pages for the Hemidactylus angulatus / brookii / murrayi complex, using present locality, type, comment, and type-comment blocks.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Each result must start from the old-label chain specified in the task and ultimately determine the accepted name, bridge status, type status, type accession, and locality from the current accepted page.\",\"For the subtriedroides branch, continue along tenkatei to murrayi, output the final accepted name as Hemidactylus murrayi, and retain bridge=Hemidactylus tenkatei.\",\"For branches such as haitianus and leightoni, read their own locality/type lines rather than borrowing header information from the wrong page.\"],\"exclusion_conditions\":[\"Exclude results that follow the wrong page hierarchy and apply the Holotype/locality from the H. angulatus page header to other branches.\",\"Exclude results that stop early on the subtriedroides -> tenkatei chain without continuing to read the murrayi evidence.\",\"Exclude results that fail to align the locality/type line with each specific old-label branch.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\";\",\"schema\":[\"legacy label\",\"accepted\",\"bridge\",\"type status\",\"type code\",\"country\"],\"legacy_label\":\"Preserve the legacy label exactly as used on the source branch.\",\"accepted\":\"Emit the current accepted binomial exactly as shown in the reconciled source.\",\"bridge\":\"Emit `DIRECT` when no intermediate legacy bridge name is needed; otherwise emit the intermediate legacy name that links the branches.\",\"type_status\":\"Normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or NEOTYPE.\",\"type_code\":\"Take the type accession from the legacy-label branch rather than from a generic type line elsewhere on the page.\",\"country\":\"Emit the modern English country name from the reconciled source branch.\",\"sorting_or_selection\":\"Legacy label alphabetical ascending.\"}}","all_involved_urls":"null"} +{"task_id":"reptile_005","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am checking a synonymization record in the current Naja species list that involves an early Sri Lankan museum name, and I want to organize the key information from the accepted side and the contested-name side into a two-row comparison table. First, in the current Naja list, locate the contested-name record associated with Sri Lanka. Then verify its recent-use evidence, the database's final treatment, the correction concerning lectotype assignment, the restricted type locality, and the holotype information for the contested name itself. Finally, output a two-row comparison table with columns rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note. Row 1 should be ACCEPTED_NAME and give the accepted name, final status, valid lectotype, and restricted type locality. Row 2 should be CONTESTED_NAME and give the contested name, recent-use evidence, holotype, and the corrected invalid lectotype claim.","start_url":"https://reptile-database.reptarium.cz/advanced_search?genus=Naja&submit=Search","output_format":"Output a two-row comparison table with columns rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note.","oracle_answer":"1|ACCEPTED_NAME|Naja naja|SUBJECTIVE_JUNIOR_SYNONYM_OF_NAJA_NAJA|VALID_LECTOTYPE|ZMB 2796|restricted type locality: Sri Lanka\n2|CONTESTED_NAME|Naja polyocellata|SHI et al. 2022+SILVA et al. 2023|HOLOTYPE|BMNH 1946.1.18.50|invalid lectotype claim: NRM (= NHR) Lin-90","metadata":"{\"State-Gated Retrieval\":[\"Within the current Naja list, identify the Sri Lanka contested-name branch: the name was recently reused as a distinct valid name, but the database now explicitly merges it back into the accepted name.\",\"On the current Naja naja page, read the recent-use evidence, final synonym status, lectotype correction, restricted type locality, and the holotype information for the contested name itself.\",\"The final output must organize the ACCEPTED_NAME side and the CONTESTED_NAME side into a two-row comparison table.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the current Naja species list and the Naja naja page yield the Sri Lanka contested-name branch, recent-use citations, and the accepted-name context\",\"comment, Types, and type-comment blocks yield the final synonym treatment plus the valid and invalid lectotype assignments and the contested-name holotype\",\"final rows are produced only after the accepted-name side and the contested-name side are reconciled on the current Naja naja page\"],\"control_dependency\":[\"recent-use evidence for Naja polyocellata must be interpreted together with the current final synonym treatment shown on that page\",\"lectotype status must be fixed from the combined Types and type-comment evidence rather than from a single provisional assignment\",\"the accepted-name and contested-name rows are emitted together only after final status, type locality, and specimen roles are fixed\"],\"freeze\":{\"historical_window\":\"the objectively existing taxa in the Sri Lanka Naja branch, using current Reptile Database comment, Types, and type-comment blocks as nearly objective and highly stable reference information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Within the current Naja list, identify the Sri Lanka contested-name record: the name was recently reused in the literature as a distinct valid name, but the database now explicitly states that it should still be merged into the accepted name.\",\"On the current Naja naja page, the result must jointly recover the recent-use evidence, final synonym status, lectotype correction, restricted type locality, and the holotype information for the contested name itself.\",\"The final output must organize the ACCEPTED_NAME side and the CONTESTED_NAME side into a two-row comparison table.\"],\"exclusion_conditions\":[\"Exclude results that treat the recently revived contested name as the current accepted name.\",\"Exclude results that stop at the Wallach 2014 lectotype designation and do not continue to the later comment and type-comment correction.\",\"Exclude results that fail to output both the restricted type locality and the contested-name holotype.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"name_role\",\"name\",\"status_or_evidence\",\"specimen_role\",\"specimen_code\",\"supporting_note\"],\"rank\":\"emit 1 for ACCEPTED_NAME and 2 for CONTESTED_NAME\",\"name_role\":[\"ACCEPTED_NAME\",\"CONTESTED_NAME\"],\"name_fields\":\"use the current binomial spellings exactly\",\"specimen_code_normalization\":\"preserve museum abbreviations, spaces, parentheses, and specimen punctuation exactly as the page shows\",\"sorting_or_selection\":\"emit rows in the fixed order ACCEPTED_NAME then CONTESTED_NAME\"}}","all_involved_urls":"null"} +{"task_id":"wateroffice_001","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am compiling historical daily flow comparison data for the Saint John River spring freshet period and want to determine, along the mainstem, which station in the current monitoring network is the last one that still allows daily flow comparisons for March–April 1973 and March–April 2018, and which mainstem station downstream of it is the first one that no longer satisfies that condition. First, use the current monitoring network shown on the Wateroffice real-time page as of April 16, 2026, and retain only stations on the Saint John River mainstem. Then, for each station, check the historical availability page, distinguish Flow Data Availability from Daily Water Level Data Availability, and determine whether March–April 1973 and March–April 2018 both have complete daily flow records. If the target windows satisfy the complete daily flow condition, set target_window_status to PASS and final_verdict to KEEP. If the target years have only water level records and no daily flow records, set target_window_status to LEVEL_ONLY and final_verdict to REJECT. If daily flow records exist but any target month in March–April 1973 or March–April 2018 is missing or incomplete, set target_window_status to FLOW_GAP and final_verdict to REJECT. Finally, output a two-row breakpoint table with columns rank|station_number|breakpoint_role|target_window_status|final_verdict. In the first row, give the last usable station and set breakpoint_role to LAST_USABLE. In the second row, give the first failing station encountered downstream and set breakpoint_role to FIRST_DOWNSTREAM_FAIL.","start_url":"https://wateroffice.ec.gc.ca/search/real_time_e.html","output_format":"Output a two-row breakpoint table with columns rank|station_number|breakpoint_role|target_window_status|final_verdict.","oracle_answer":"1|01AF002|LAST_USABLE|PASS|KEEP\n2|01AK003|FIRST_DOWNSTREAM_FAIL|LEVEL_ONLY|REJECT","metadata":"{\"State-Gated Retrieval\":[\"Determine the last station still usable for the target historical-window comparison only within the Saint John River mainstem stations in the current monitoring network.\",\"On the historical availability page, Flow Data Availability must be distinguished from Daily Water Level Data Availability, and completeness for March–April 1973 and March–April 2018 must be checked.\",\"The final output must provide both breakpoint rows, LAST_USABLE and FIRST_DOWNSTREAM_FAIL, under the same validation rule.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the current Saint John River mainstem station sequence provides the downstream order in which the breakpoints must be checked\",\"per-station historical availability pages yield Flow Data Availability, Daily Water Level Data Availability, and target-month completeness for 1973 and 2018\",\"the final breakpoint rows are produced only after the availability-page checks identify the last usable station and the first downstream failure under the same rule\"],\"control_dependency\":[\"the breakpoint pair must be determined from historical availability that distinguishes flow from level-only evidence\",\"target-year/month completeness must be checked on the availability page rather than inferred from the station list\",\"the second row is emitted only after the first downstream failing mainstem station is fixed under the same validation rule\"],\"freeze\":{\"historical_window\":\"mainstem candidate stations evaluated by historical daily availability, with the target completeness rule applied to the specified 1973 and 2018 March/April windows\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Search for the final station only within the mainstem station set specified in the task, and continue downstream along the mainstem to identify the first station after it that no longer meets the condition.\",\"The historical daily availability page must distinguish Flow Data Availability from Daily Water Level Data Availability, and must verify the completeness of the required March–April windows for 1973 and 2018.\",\"The final output must provide both breakpoint rows, LAST_USABLE and FIRST_DOWNSTREAM_FAIL, under the same validation rule.\"],\"exclusion_conditions\":[\"Exclude results that rely only on the current Saint John River mainstem station sequence and directly take the most downstream station by reference index.\",\"Exclude results that mistakenly treat level-only evidence as satisfying the flow condition.\",\"Exclude results that do not check each station's availability page to verify target-month completeness.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"station_number\",\"breakpoint_role\",\"target_window_status\",\"final_verdict\"],\"rank\":\"emit `1` for LAST_USABLE and `2` for FIRST_DOWNSTREAM_FAIL\",\"station_number\":\"preserve the station number exactly\",\"breakpoint_role\":\"emit `LAST_USABLE` and `FIRST_DOWNSTREAM_FAIL` exactly\",\"target_window_status\":\"emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly\",\"final_verdict\":\"emit `KEEP` for the usable breakpoint row and `REJECT` for the downstream failing breakpoint row\",\"stop_condition\":[\"the last usable mainstem station is fixed under the availability-page validation rule\",\"the first downstream failing mainstem station is fixed under the same validation rule before the two-row output is emitted\"]}}","all_involved_urls":"null"} +{"task_id":"wateroffice_002","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"I am compiling historical daily flow records for the Bulkley River reach from Houston to Hazelton and want to verify, station by station, whether candidate mainstem stations on the Bulkley River truly have complete daily flow records for April–July 1948 and April–July 1950. First, from the Historical Results list, select candidate stations that lie on the Bulkley River mainstem, fall within the Houston-to-Hazelton reach, appear to cover both 1948 and 1950, and carry a Flow label. Then open each station's availability page and check whether the target years fall within the Flow section and whether April-July is marked C throughout. If the target windows satisfy the complete daily flow condition, set target_window_status to PASS and final_verdict to KEEP. If the target years have only water level records and no daily flow records, set target_window_status to LEVEL_ONLY and final_verdict to REJECT. If daily flow records exist but any month from April to July is not complete, set target_window_status to FLOW_GAP and final_verdict to REJECT. Finally, output a table in downstream-to-upstream order with columns rank|station_number|target_window_status|final_verdict.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a table in downstream-to-upstream order with columns rank|station_number|target_window_status|final_verdict.","oracle_answer":"1|08EE004|PASS|KEEP\n2|08EE001|LEVEL_ONLY|REJECT\n3|08EE005|FLOW_GAP|REJECT\n4|08EE003|FLOW_GAP|REJECT","metadata":"{\"State-Gated Retrieval\":[\"First identify mainstem candidate stations on the Historical Results list that appear to cover 1948/1950 and carry a Flow label.\",\"A station qualifies only if its availability page shows the target years in the Flow section and all of April-July marked C.\",\"The final output must report target_window_status and final_verdict for each station in the same station set, ordered from downstream to upstream.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the Historical Results list yields four downstream-to-upstream mainstem candidates whose result rows span the target years and include Flow labels\",\"each candidate's availability page yields whether the target years are in the Flow table and whether April-July is complete\",\"the final ordered rows are produced only after all four stations are classified under the full Flow-table-and-Apr-Jul-C rule\"],\"control_dependency\":[\"list-level year spans and coarse Flow tags must be confirmed by explicit target-month checks on the availability page\",\"Hazelton, Smithers, and Houston candidate statuses must be fixed before the downstream-most KEEP row can be confirmed\",\"row order and KEEP/REJECT labels must be emitted only after the full availability-page rule is applied to all four stations\"],\"freeze\":{\"historical_window\":\"the target mainstem stations tested against 1948 and 1950 daily Flow availability, with April-July requiring complete C coverage\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"First, from the Historical Results list, identify mainstem candidate stations that superficially appear to cover 1948/1950 and have a Flow label.\",\"A truly qualified station must satisfy, on its availability page, that the target years are in the Flow section and that April–July are all marked C.\",\"Finally, report target_window_status and final_verdict for each station in the same station set, ordered from downstream to upstream.\"],\"exclusion_conditions\":[\"Exclude stations deemed usable based solely on list-level year span and coarse Flow label.\",\"Exclude retaining LEVEL_ONLY or FLOW_GAP stations in the final answer.\",\"Exclude results that do not apply the full availability-page rule to all initially screened stations.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"station_number\",\"target_window_status\",\"final_verdict\"],\"rank\":\"emit 1 through 4 in downstream-to-upstream order within the validated station set\",\"station_number\":\"preserve the station number exactly\",\"target_window_status\":\"emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly\",\"final_verdict\":\"emit `KEEP` or `REJECT` exactly\",\"sorting_or_selection\":\"downstream to upstream within the validated Bulkley River mainstem station set\",\"stop_condition\":[\"all four initially screened stations are classified under the full availability-page rule\",\"the ordered table is emitted only after the downstream-to-upstream sequence is fixed\"]}}","all_involved_urls":"null"} +{"task_id":"wateroffice_003","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"I am compiling historical snowmelt daily flow data for the Thompson River from Chase to Spences Bridge. I need to verify, station by station, whether the mainstem stations along this reach actually have daily flow records for May–July of 1958 and 1971. First, in downstream order from Chase to Spences Bridge, select stations from the list that show coverage for 1958 and 1971 and have flow records for the Thompson River mainstem. Then, for each selected station, check whether it provides complete daily flow records for May–July of both 1958 and 1971. If a station has only water level records (no daily flow) for a target year, mark it LEVEL_ONLY. If daily flow records exist but the May–July window is missing or any target month is incomplete, mark it FLOW_GAP. Only when both years' May–July daily flow records are complete should the final_verdict be KEEP; otherwise, REJECT. Finally, output a table with columns rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict, ordered downstream from Chase to Spences Bridge.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a table with columns rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict, ordered downstream from Chase to Spences Bridge.","oracle_answer":"1|08LE031|SOUTH THOMPSON RIVER AT CHASE|PASS|PASS|KEEP\n2|08LE069|SOUTH THOMPSON RIVER AT MONTE CREEK|FLOW_GAP|LEVEL_ONLY|REJECT\n3|08LF023|THOMPSON RIVER AT KAMLOOPS|LEVEL_ONLY|LEVEL_ONLY|REJECT\n4|08LF033|THOMPSON RIVER NEAR SAVONA|FLOW_GAP|FLOW_GAP|REJECT\n5|08LF051|THOMPSON RIVER NEAR SPENCES BRIDGE|PASS|PASS|KEEP","metadata":"{\"State-Gated Retrieval\":[\"All five candidate stations must be verified on the availability page to confirm that the target years are present in the Flow table and that May–July is entirely marked C.\",\"Each station must output a PASS / LEVEL_ONLY / FLOW_GAP judgment for both target years, and then be marked KEEP or REJECT accordingly.\",\"The result order must follow the river-path ordering specified in the task.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the river-path ordering yields five South Thompson / Thompson mainstem candidates\",\"each station's availability page yields whether 1958 and 1971 are present in the Flow table and whether May-July is complete\",\"final rows are produced only after every candidate is classified under the stricter target-year and target-month Flow rule\"],\"control_dependency\":[\"overall year coverage on the results list must be confirmed by the availability page inside the Flow table\",\"Monte Creek, Savona, and Kamloops must be rejected by LEVEL_ONLY / FLOW_GAP evidence before the KEEP rows are final\",\"the river-order sequence remains fixed, but station statuses must be assigned only after the availability-page rule is applied to all five stations\"],\"freeze\":{\"historical_window\":\"the ordered South Thompson / Thompson mainstem candidates tested against 1958 and 1971 Flow availability, with May-July requiring complete C coverage\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"All five candidate stations must be verified on the availability page to confirm that the target years are present in the Flow table and that May–July is entirely marked C.\",\"Each station must output a PASS / LEVEL_ONLY / FLOW_GAP judgment for both target years, and then be marked KEEP or REJECT accordingly.\",\"The result order must follow the river-path ordering specified in the task.\"],\"exclusion_conditions\":[\"Exclude results that treat overall year coverage on the list as sufficient evidence.\",\"Exclude results that fail to distinguish between Flow table target-year and month completeness versus Level-only evidence.\",\"Exclude results that do not apply the same availability-page rule uniformly to all five stations.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"station_number\",\"station_name\",\"1958_MayJul\",\"1971_MayJul\",\"final_verdict\"],\"rank\":\"use the fixed Chase-to-Spences-Bridge mainstem order from the reference index, not the transient search-result order\",\"year_window_fields\":\"the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP\",\"final_verdict\":\"emit `KEEP` or `REJECT` exactly\"}}","all_involved_urls":"null"} +{"task_id":"wateroffice_004","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":13,"instruction":"I am compiling historical daily flow records for the mainstem Columbia River from Fairmont Hot Springs to the International Boundary. I want to check, station by station in Wateroffice, which stations have complete daily flow records for May–October of 1955 and 1956. First, locate stations on the Columbia River mainstem between Fairmont Hot Springs and the International Boundary whose records span both 1955 and 1956. Then, proceeding from upstream to downstream, check the availability of daily flow for May–October of 1955 and 1956 at each station. If a station has only water-level records and no daily flow records for a given target year, mark that year as LEVEL_ONLY. If daily flow for May–October of that year is complete, mark it as PASS. Otherwise, if the year has no usable daily flow records or any month within May–October is incomplete, mark it as FLOW_GAP. Only when both years satisfy the PASS condition should the final_verdict be KEEP; otherwise write REJECT. Finally, output a table in upstream-to-downstream order with columns: rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a table in upstream-to-downstream order with columns: rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict.","oracle_answer":"1|08NA045|COLUMBIA RIVER NEAR FAIRMONT HOT SPRINGS|PASS|PASS|KEEP\n2|08NA004|COLUMBIA RIVER AT ATHALMER|LEVEL_ONLY|LEVEL_ONLY|REJECT\n3|08NA052|COLUMBIA RIVER NEAR EDGEWATER|PASS|FLOW_GAP|REJECT\n4|08NA002|COLUMBIA RIVER AT NICHOLSON|PASS|PASS|KEEP\n5|08NB005|COLUMBIA RIVER AT DONALD|PASS|PASS|KEEP\n6|08NB006|COLUMBIA RIVER AT SURPRISE RAPIDS|PASS|PASS|KEEP\n7|08ND007|COLUMBIA RIVER ABOVE NAGLE CREEK|PASS|PASS|KEEP\n8|08ND011|COLUMBIA RIVER ABOVE STEAMBOAT RAPIDS|FLOW_GAP|PASS|REJECT\n9|08ND006|COLUMBIA RIVER AT TWELVE MILE FERRY|PASS|PASS|KEEP\n10|08NE002|COLUMBIA RIVER AT CASTLEGAR|LEVEL_ONLY|LEVEL_ONLY|REJECT\n11|08NE049|COLUMBIA RIVER AT BIRCHBANK|PASS|PASS|KEEP\n12|08NE003|COLUMBIA RIVER AT TRAIL|LEVEL_ONLY|LEVEL_ONLY|REJECT\n13|08NE058|COLUMBIA RIVER AT INTERNATIONAL BOUNDARY|PASS|PASS|KEEP","metadata":"{\"State-Gated Retrieval\":[\"Every candidate Columbia River station must be checked on its availability page to confirm that the target years appear in the Flow table and that May–October is fully marked C.\",\"For each station, provide the KEEP/REJECT basis for both 1955 and 1956, distinguishing LEVEL_ONLY and FLOW_GAP cases from stations that only appear eligible from their overall year span.\",\"The final table must preserve the order and fields specified in the task.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the Columbia River candidate ordering yields fourteen stations spanning the target years\",\"each availability page yields whether 1955 and 1956 are present in the Flow table and whether May-October is complete\",\"final rows are produced only after every station is classified under the stricter Flow-table-and-May-Oct-C rule\"],\"control_dependency\":[\"list-level year spans must be confirmed by the availability page inside the Flow table\",\"LEVEL_ONLY and FLOW_GAP evidence must be applied to each station before the KEEP/REJECT table is finalized\",\"station-by-station verdicts and rejection reasons must be determined only after the full availability-page rule replaces the initial year-span screen\"],\"freeze\":{\"historical_window\":\"the ordered Columbia River candidates tested against 1955 and 1956 Flow availability, with May-October requiring complete C coverage\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Every candidate Columbia River station must be checked on its availability page to confirm that the target years appear in the Flow table and that May–October is fully marked C.\",\"For each station, provide the KEEP/REJECT basis for both 1955 and 1956, distinguishing LEVEL_ONLY and FLOW_GAP cases from stations that only appear eligible from their overall year span.\",\"The final table must preserve the order and fields specified in the task.\"],\"exclusion_conditions\":[\"Exclude results that retain a station solely because its overall record spans 1955/1956.\",\"Exclude results that fail to distinguish, station by station, between Flow availability, Level-only, and incomplete months.\",\"Exclude results that do not apply the full availability-page rule uniformly to all 14 stations.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"station_number\",\"station_name\",\"1955_MayOct\",\"1956_MayOct\",\"final_verdict\"],\"rank\":\"use the fixed upstream-to-downstream Columbia mainstem order from the reference index, not the transient search-result order\",\"year_window_fields\":\"the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP\",\"final_verdict\":\"emit `KEEP` or `REJECT` exactly\"}}","all_involved_urls":"null"} +{"task_id":"wateroffice_005","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am organizing historical daily-flow records for the Peace River reach from Dunvegan Bridge to Fifth Meridian and want to verify three things at once: the true furthest-downstream reusable station on the mainstem, the first failing station encountered after it, and the provisional terminal station that a station-level screen based only on year coverage and record type would mistakenly treat as the downstream winner. Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian. First, from the station list, identify provisional candidates that appear to cover both 1966 and 1967 and show a daily-flow record type. Then open each availability page and verify whether May through September in both 1966 and 1967 appears in the Flow table and is complete for every month. If both target years satisfy the complete daily-flow condition, write PASS in target_window_status. If a target year has only level records and no daily-flow records, write LEVEL_ONLY. If daily-flow records exist but any target month from May through September is incomplete, write FLOW_GAP. If the target year has neither daily-flow nor level records, write NO_TARGET_RECORD. Finally, output a three-row diagnostic table with columns rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count. The rows must be FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION in that order, and the last two columns must repeat the global provisional_count and final_count in every row.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a three-row diagnostic table with columns rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count.","oracle_answer":"1|07HA001|FINAL_STATION|PASS|5|2\n2|07HD001|FIRST_BREAK_AFTER_FINAL|FLOW_GAP|5|2\n3|07KA002|PROVISIONAL_STATION|FLOW_GAP|5|2","metadata":"{\"State-Gated Retrieval\":[\"Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian.\",\"A genuinely reusable station must satisfy the availability-page rule that both 1966 and 1967 appear in the Flow table and that every month from May through September is complete.\",\"The final output must jointly report FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION, while repeating provisional_count and final_count in every row.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the Peace River mainstem chain between Dunvegan Bridge and Fifth Meridian yields the initial station list and the downstream breakpoint positions that need revalidation\",\"each availability page yields whether 1966 and 1967 are present in the Flow or Level tables and whether May-September is complete\",\"final rows are produced only after the final station, the first downstream failure, and the provisional downstream winner are all fixed under the same availability-page validation rule\"],\"control_dependency\":[\"station-level target-year Flow evidence must be validated by explicit May-September completeness checks on the availability page\",\"the final downstream reusable station and the first downstream failure must be determined under the same validation rule rather than from the initial station screen\",\"the provisional downstream winner is kept in the output only for reference after its FLOW_GAP status is confirmed on the availability page\"],\"freeze\":{\"historical_window\":\"Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian, evaluated within the fixed historical 1966 and 1967 Flow-availability windows, with May-September complete-C coverage used as nearly stable reference information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian.\",\"A genuinely reusable station must satisfy the availability-page rule that both 1966 and 1967 appear in the Flow table and that every month from May through September is complete.\",\"The final output must jointly report FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION, while repeating provisional_count and final_count in every row.\"],\"exclusion_conditions\":[\"Exclude results that treat a station as usable simply because the target years have Flow records.\",\"Exclude results that do not verify completeness month by month from May through September.\",\"Exclude results that mark a station such as 07KA002 as FINAL_STATION when availability-page evidence shows FLOW_GAP.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"station_number\",\"diagnosis_role\",\"target_window_status\",\"provisional_count\",\"final_count\"],\"rank\":\"emit the fixed order 1, 2, 3 for FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION\",\"station_number\":\"use uppercase WSC station codes exactly as the Reference Index and availability pages show\",\"diagnosis_role\":[\"FINAL_STATION\",\"FIRST_BREAK_AFTER_FINAL\",\"PROVISIONAL_STATION\"],\"target_window_status\":[\"PASS\",\"LEVEL_ONLY\",\"FLOW_GAP\",\"NO_TARGET_RECORD\"],\"count_fields\":\"repeat the global provisional_count and final_count in every row as plain integers\",\"sorting_or_selection\":\"emit rows in the fixed diagnostic order FINAL_STATION, FIRST_BREAK_AFTER_FINAL, PROVISIONAL_STATION\"}}","all_involved_urls":"null"} +{"task_id":"waterquality_001","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am reviewing historical monitoring records for a reach of the middle Rio Grande and need to select two monitoring stations suitable for observing wastewater impacts on the main channel. Starting from RIO GRANDE AT EMBUDO, NM and proceeding downstream, retain only stations that are confirmed to lie on the Rio Grande mainstem. Then, find the first mainstem monitoring station downstream of the Town of Bernalillo wastewater treatment plant outfall that meets the following conditions; continuing further downstream, find the first mainstem monitoring station that has passed both the Town of Bernalillo WWTP outfall and the Rio Rancho No. 2 WWTP outfall and meets the same conditions. Both stations must satisfy: the station itself is not an outfall, facility, well, canal, or drainage ditch; the type on the station detail page is labeled as River/Stream; records for the four characteristic groups Microbiological, Nutrient, Organics, Other, and Physical fully cover 2015–2020; and the start years for both Microbiological and Physical records are earlier than 2010. Finally, output a single-line string in upstream-to-downstream order: ||, with the two segments separated by a comma.","start_url":"https://www.waterqualitydata.us/","output_format":"Output a single-line string in upstream-to-downstream order: ||, with the two segments separated by a comma.","oracle_answer":"SANDIAWQ_WQX-RG003|2004|2004,SANDIAWQ_WQX-RG008|2004|2004","metadata":"{\"State-Gated Retrieval\":[\"Select two target stations only from Rio Grande mainstem monitoring stations downstream of RIO GRANDE AT EMBUDO, NM, and both must have passed the specified outfall locations.\",\"The station detail page must explicitly show River/Stream, and records for the four characteristic groups Microbiological, Nutrient, Organics, Other, and Physical must fully cover 2015–2020, while the start years for both Microbiological and Physical must be earlier than 2010.\",\"Output the two final stations in upstream-to-downstream order.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"provider/list views yield the Rio Grande mainstem candidates downstream of the Bernalillo and Rio Rancho No. 2 discharge points\",\"detail pages yield flow position, location type, characteristic-group period-of-record coverage for 2015-2020, and the Microbiological/Physical baseline years\",\"final rows are produced only after the corrected downstream sentry stations are fixed and ordered from upstream to downstream\"],\"control_dependency\":[\"provider-list stream tags are only provisional and must be confirmed on the detail page by both mainstem placement and location type\",\"target-window presence is insufficient until full 2015-2020 coverage is confirmed on the detail page for all four groups\",\"once RG002/RG007 fail the full detail-page checks, the workflow must continue downstream from the discharge-point starting position to RG003/RG008\"],\"freeze\":{\"historical_window\":\"Rio Grande mainstem stations downstream of the Town of Bernalillo and Rio Rancho No. 2 WWTP outfalls, validated against 2015-2020 coverage for Microbiological, Nutrient, Organics, Other, and Physical\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Select two target stations only from Rio Grande mainstem monitoring stations downstream of RIO GRANDE AT EMBUDO, NM, and both must have passed the specified outfall locations.\",\"The station detail page must explicitly show River/Stream, and records for the four characteristic groups Microbiological, Nutrient, Organics, Other, and Physical must fully cover 2015–2020, while the start years for both Microbiological and Physical must be earlier than 2010.\",\"Output the two final stations in upstream-to-downstream order.\"],\"exclusion_conditions\":[\"Exclude stations that have only a superficial (Stream) tag on the provider list or have records near the target window, but whose detail page does not satisfy the flow position, location type, or complete period-of-record conditions.\",\"Exclude locations that are outfalls, facilities, wells, canals, or drainage ditches.\",\"Exclude candidates such as RG002 and RG007 that are not the qualifying sentry stations downstream of the corresponding outfalls.\"],\"normalization\":{\"record_separator\":\",\",\"field_separator\":\"|\",\"schema_per_record\":[\"MonitoringLocationIdentifier\",\"Microbiological_start_year\",\"Physical_start_year\"],\"ordering\":\"emit exactly two records from upstream to downstream\",\"station_id\":\"use uppercase MonitoringLocationIdentifier\",\"year_fields\":\"emit four-digit years as plain integers\",\"selection\":{\"record_1\":\"the first qualifying mainstem station below the Bernalillo outfall\",\"record_2\":\"the first qualifying mainstem station below both the Bernalillo and Rio Rancho No. 2 outfalls\"},\"stop_condition\":[\"the Bernalillo branch stops only after its first qualifying mainstem station is fixed\",\"the Rio Rancho No. 2 branch stops only after its first qualifying mainstem station is fixed\",\"the two segments are emitted as one comma-joined line in upstream-to-downstream order\"]}}","all_involved_urls":"null"} +{"task_id":"waterquality_002","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am analyzing trends in the lower Rio Grande from 2001 to 2010. From monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002, select one representative station for Hidalgo County and one for Cameron County. First, screen candidate stations for each county within the specified area. Retain only stations whose detail page lists the type as River/Stream and that have records covering 2001–2010 for all four characteristic groups: Microbiological, Nutrient, Organics, Other, and Physical. If multiple stations in the same county qualify, select the station with the earliest year in which all four groups are simultaneously present. Then record the MonitoringLocationIdentifier of the selected station, the earliest year all four groups are simultaneously present, and the start year for each of Microbiological, Nutrient, Organics, Other, and Physical. Finally, output a single-line string in the order Hidalgo then Cameron: :|||||, with the two segments separated by a comma.","start_url":"https://www.waterqualitydata.us/","output_format":"Output a single-line string in the order Hidalgo then Cameron: :|||||, with the two segments separated by a comma.","oracle_answer":"Hidalgo:TCEQMAIN-15808|1998|1998|1998|1998|1998,Cameron:TCEQMAIN-13177|1995|1981|1981|1995|1981","metadata":"{\"State-Gated Retrieval\":[\"Select one representative station for Hidalgo County and one for Cameron County from monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002.\",\"Candidate detail pages must list the type as River/Stream, and records for all four characteristic groups (Microbiological, Nutrient, Organics, Other, Physical) must cover 2001–2010.\",\"If multiple stations in the same county qualify, select the station with the earliest year in which all four groups are simultaneously present.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the fixed downstream starting point and county split yield Hidalgo and Cameron candidate mainstem stations within HUC 13090002\",\"detail pages yield River/Stream validity, the four characteristic-group start years, and the earliest year when all four groups are simultaneously present for 2001-2010 coverage\",\"final rows are produced only after the county-specific searches are rerun from the fixed downstream starting point and then ranked by common-start year\"],\"control_dependency\":[\"the Hidalgo search must preserve the \\\"below TCEQMAIN-13664\\\" downstream starting point rather than returning to the anchor station itself\",\"a station is only provisional until all four characteristic groups are confirmed for the same MonitoringLocationIdentifier and tidal/intake conflicts are excluded on the detail page\",\"county winners are valid only after late-start and non-river candidates are removed and the common-start-year tie-break is recomputed\"],\"freeze\":{\"historical_window\":\"stations below RIO GRANDE BELOW ANZALDUAS within HUC 13090002, split by Hidalgo and Cameron County, with Microbiological, Nutrient, Organics, Other, and Physical coverage over 2001-2010\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Select one representative station for Hidalgo County and one for Cameron County from monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002.\",\"Candidate detail pages must list the type as River/Stream, and records for all four characteristic groups (Microbiological, Nutrient, Organics, Other, Physical) must cover 2001–2010.\",\"If multiple stations in the same county qualify, select the station with the earliest year in which all four groups are simultaneously present.\"],\"exclusion_conditions\":[\"Exclude results where the Hidalgo search loses the downstream starting point and brings the starting station itself back into the candidate set.\",\"Exclude results that treat a single multi-select of the four characteristic groups as sufficient without verifying that all four belong to the same station ID.\",\"Exclude stations with tidal, intake, late-start, or other conflicts clearly indicated on the detail page.\"],\"normalization\":{\"record_separator\":\",\",\"field_separator\":\"|\",\"schema_per_record\":[\"County:MonitoringLocationIdentifier\",\"common_start_year\",\"Microbiological_start_year\",\"Nutrient_start_year\",\"Organics_Other_start_year\",\"Physical_start_year\"],\"ordering\":\"emit exactly two records, with Hidalgo first and Cameron second\",\"county_prefix\":\"use the county label in title case, followed by : and the uppercase MonitoringLocationIdentifier\",\"year_fields\":\"emit four-digit years as plain integers\",\"common_start_year\":\"the earliest year in which all four required groups are simultaneously present for the chosen county station\",\"stop_condition\":[\"each county branch is rerun until one River/Stream station survives all four group checks\",\"the county winner is fixed only after late-start and non-river candidates are excluded after checking the detail page\",\"the two county segments are emitted on one line in the fixed Hidalgo-then-Cameron order\"]}}","all_involved_urls":"null"} +{"task_id":"waterquality_003","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am compiling 2012–2018 water quality reference data for the Brazos River mainstem downstream of Brazos Rv at Waco, TX. I want to select one TCEQ monitoring station suitable as a long-term reference point in each of the three HUCs (12060202, 12070101, 12070104) that the mainstem passes through. Process as follows: first, within the Brazos River mainstem reach downstream of Brazos Rv at Waco, TX, screen candidate stations in HUCs 12060202, 12070101, and 12070104 respectively; retain only monitoring locations whose detail page labels them as River/Stream and whose station name still corresponds to the Brazos River mainstem rather than another named waterbody. Next, check the record categories for these stations, retaining only those that cover 2012–2018 for all five categories: Inorganics, Major, Non-metals; Microbiological; Nutrient; Organics, Other; and Physical. Specifically, the station start year must be no later than 2012 and the end year no earlier than 2018. Finally, list the 3 results in order from upstream to downstream, each row formatted as: |||||||.","start_url":"https://www.waterqualitydata.us/","output_format":"List the 3 results in order from upstream to downstream, each row formatted as: |||||||.","oracle_answer":"12060202|TCEQMAIN-12037|2000|1991|2000|1991|1999|1991\n12070101|TCEQMAIN-12030|2006|1972|1972|1972|2006|1972\n12070104|TCEQMAIN-11848|1975|1974|1975|1974|1975|1974","metadata":"{\"State-Gated Retrieval\":[\"The search must stay anchored downstream of Waco and look for Brazos mainstem monitoring stations within the three HUCs specified in the task.\",\"Each candidate station must be checked separately across the five characteristic groups and then matched back to the same station ID, after which the detail page must verify full 2012–2018 coverage and mainstem semantics.\",\"For each HUC, retain only the qualifying station with the earliest common start year, and output the start-year fields required by the task.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the fixed downstream starting point below Waco and the three target HUC searches yield the Brazos mainstem candidate stations\",\"detail pages yield true downstream position, mainstem-vs-tributary semantics, and five-group period-of-record coverage across 2012-2018\",\"final rows are produced only after the three HUC-specific searches are carried out, matched by station ID, and ranked by the earliest year when all five groups are jointly available\"],\"control_dependency\":[\"the workflow must stay anchored downstream of Waco rather than reintroducing upstream stations such as TCEQMAIN-12044\",\"name-based waterbody matches must be validated on the detail page by excluding tributaries such as LITTLE BRAZOS RIVER and confirming full-window coverage\",\"station ranking must be determined after false positives from partial-window records are removed\"],\"freeze\":{\"historical_window\":\"Brazos River mainstem stations downstream of the Waco anchor, split across HUC 12060202, 12070101, and 12070104, with five characteristic groups covering 2012-2018\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"The search must stay anchored downstream of Waco and look for Brazos mainstem monitoring stations within the three HUCs specified in the task.\",\"Each candidate station must be checked separately across the five characteristic groups and then matched back to the same station ID, after which the detail page must verify full 2012–2018 coverage and mainstem semantics.\",\"For each HUC, retain only the qualifying station with the earliest common start year, and output the start-year fields required by the task.\"],\"exclusion_conditions\":[\"Exclude results that lose the downstream starting point below Waco and bring upstream stations back into the candidate set.\",\"Exclude results that mistake tributaries such as LITTLE BRAZOS RIVER for the Brazos mainstem.\",\"Exclude stations that have data near the query window but do not cover the entire 2012–2018 window.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"HUC\",\"MonitoringLocationIdentifier\",\"common_start_year\",\"Inorganics_start\",\"Microbiological_start\",\"Nutrient_start\",\"Organics_Other_start\",\"Physical_start\"],\"HUC\":\"preserve the HUC exactly as emitted in the source result\",\"MonitoringLocationIdentifier\":\"preserve the monitoring-location identifier exactly, for example `TCEQMAIN-12037`\",\"common_start_year\":\"emit the maximum of the five per-group start years\",\"selection_rule\":\"only keep mainstem river/stream sites whose five required groups all cover the target 2012-2018 window\",\"sorting_or_selection\":\"upstream to downstream along the mainstem\"}}","all_involved_urls":"null"} +{"task_id":"waterquality_004","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am reviewing toxic-pollutant-related water quality monitoring data for 1993–2001 along the Trinity River mainstem, bounded upstream by the reach near FM 85 and downstream by the reach near Interstate 10. I need to select one TCEQ long-term reference station for each of the upper, middle, and lower segments.\n\nStarting from the Trinity River mainstem between the reach near FM 85 and the reach near Interstate 10, screen candidate monitoring locations in the upper, middle, and lower segments. Retain only stations whose record is tagged as River/Stream and whose name still refers to the Trinity River mainstem, not to other named water bodies or distributaries. Then check the record categories for these stations; keep only those that have all six record categories covering 1993–2001 (i.e., the start year is no later than 1993 and the end year is no earlier than 2001). Output the results from upstream to downstream.\n\nFinally, list three rows from upstream to downstream along the river, each in the format: ||||||||.","start_url":"https://www.waterqualitydata.us/","output_format":"List three rows from upstream to downstream along the river, each in the format: ||||||||.","oracle_answer":"12030105|TCEQMAIN-10924|1983|1982|1983|1982|1983|1983|1982\n12030202|TCEQMAIN-10897|1993|1969|1972|1972|1993|1974|1969\n12030203|TCEQMAIN-10892|1976|1969|1971|1972|1974|1976|1969","metadata":"{\"State-Gated Retrieval\":[\"Screen only among candidate stations where Trinity River mainstem semantics hold, and require all six characteristic groups to cover 1993–2001.\",\"The six groups must be searched separately and then matched back to the same station ID, after which the detail page must verify full-window coverage and legacy toxics group completeness.\",\"For each target segment, retain only the station that meets all group requirements and has the best common start year.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Trinity River mainstem candidate stations are generated from the target HUC searches and the six characteristic-group searches\",\"detail pages yield River/Stream validity, 1993–2001 full-window coverage, and the group-specific start years needed for ranking\",\"final rows are produced only after all six groups have been matched by station ID and detail-page validation removes partial-group and non-mainstem false positives\"],\"control_dependency\":[\"each of the six characteristic groups must be evaluated separately and confirmed against the same station ID before a multi-select result can be retained\",\"station names and River/Stream tags are insufficient until the detail page confirms Trinity mainstem semantics and 1993–2001 full-window coverage\",\"candidate rejection and final ranking must be determined after applying the PCBs / Organics, Other gap checks\"],\"freeze\":{\"historical_window\":\"Trinity River mainstem stations validated against six characteristic groups over 1993–2001, with ranking based on the earliest joint availability and group start years\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Screen only among candidate stations where Trinity River mainstem semantics hold, and require all six characteristic groups to cover 1993–2001.\",\"The six groups must be searched separately and then matched back to the same station ID, after which the detail page must verify full-window coverage and legacy toxics group completeness.\",\"For each target segment, retain only the station that meets all group requirements and has the best common start year.\"],\"exclusion_conditions\":[\"Exclude results that mistakenly treat a single multi-select of characteristic groups as sufficient to satisfy the requirement.\",\"Exclude results that only check station names and River/Stream tags without verifying 1993–2001 full-window coverage.\",\"Exclude stations that ignore missing PCBs or Organics, Other groups.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"HUC\",\"MonitoringLocationIdentifier\",\"common_start_year\",\"Inorganics_start\",\"Microbiological_start\",\"Nutrient_start\",\"Organics_Other_start\",\"Organics_PCBs_start\",\"Physical_start\"],\"HUC\":\"preserve the HUC exactly as emitted in the source result\",\"MonitoringLocationIdentifier\":\"preserve the monitoring-location identifier exactly, for example `TCEQMAIN-10924`\",\"common_start_year\":\"emit the maximum of the six per-group start years\",\"selection_rule\":\"only keep mainstem river/stream sites whose six required groups all cover the target window\",\"sorting_or_selection\":\"upstream to downstream along the mainstem\"}}","all_involved_urls":"null"} +{"task_id":"waterquality_005","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":9,"instruction":"I am organizing integrated water-quality records for the lower Neches River during 1978-1984. Starting downstream from NECHES RIVER AT CR 4915, I want to identify the nearest TCEQ long-term reference station that still represents the inland Neches River mainstem, and then tabulate the start year of nine Characteristic Groups at that station. Search downstream along the mainstem and retain only monitoring stations whose detail page labels the site type as River/Stream. Exclude stations located in lake or reservoir waters or in the Sabine-Neches outlet boundary reach. Among stations that satisfy these location conditions, identify the nearest qualifying station for which all nine record categories cover 1978-1984: Biological, Algae, Phytoplankton; Inorganics, Major, Non-metals; Inorganics, Minor, Metals; Microbiological; Nutrient; Organics, Other; Organics, PCBs; Organics, Pesticide; and Physical. Finally, output a table for that final station, one row per Characteristic Group, with columns rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year. The row order is fixed as Biological, Algae, Phytoplankton; Inorganics, Major, Non-metals; Inorganics, Minor, Metals; Microbiological; Nutrient; Organics, Other; Organics, PCBs; Organics, Pesticide; Physical.","start_url":"https://www.waterqualitydata.us/provider/STORET/TCEQMAIN/TCEQMAIN-10598/","output_format":"Output a 9-row table with columns rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year.","oracle_answer":"1|TCEQMAIN-10580|12020003|Hardin County|Biological, Algae, Phytoplankton|1972|1977\n2|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Major, Non-metals|1971|1977\n3|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Minor, Metals|1974|1977\n4|TCEQMAIN-10580|12020003|Hardin County|Microbiological|1972|1977\n5|TCEQMAIN-10580|12020003|Hardin County|Nutrient|1972|1977\n6|TCEQMAIN-10580|12020003|Hardin County|Organics, Other|1974|1977\n7|TCEQMAIN-10580|12020003|Hardin County|Organics, PCBs|1974|1977\n8|TCEQMAIN-10580|12020003|Hardin County|Organics, Pesticide|1977|1977\n9|TCEQMAIN-10580|12020003|Hardin County|Physical|1971|1977","metadata":"{\"State-Gated Retrieval\":[\"Search only among TCEQ monitoring stations downstream of NECHES RIVER AT CR 4915 that still represent the inland Neches River mainstem.\",\"A candidate station must cover 1978-1984 in all nine Characteristic Groups and, on the detail page, must still qualify as River/Stream, outside lake or reservoir waters, and outside the Sabine-Neches outlet boundary reach.\",\"The final output must be centered on the single winning station and list group_start_year plus common_start_year row by row in the fixed nine-group order.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the fixed downstream starting point at NECHES RIVER AT CR 4915 yields candidate inland mainstem stations across successive downstream HUCs\",\"detail pages yield River/Stream validity, inland-vs-boundary semantics, and nine-group period-of-record coverage across 1978-1984\",\"final rows are produced only after one winning station survives the inland-mainstem checks and the requirement that all nine groups match the same station, after which its nine group start years are emitted in the required order\"],\"control_dependency\":[\"the nearest downstream mainstem station remains provisional until all nine characteristic groups have been checked separately and matched back to the same station ID\",\"the downstream search must continue to the next mainstem HUC when the first candidate fails the nine-group coverage requirement\",\"location semantics remain valid only after detail-page exclusion of lake/reservoir and Sabine-Neches boundary stations\"],\"freeze\":{\"historical_window\":\"Neches River inland mainstem stations downstream of NECHES RIVER AT CR 4915, validated within the fixed 1978-1984 window against nine characteristic groups as largely stable reference information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Search only among TCEQ monitoring stations downstream of NECHES RIVER AT CR 4915 that still represent the inland Neches River mainstem.\",\"A candidate station must cover 1978-1984 in all nine Characteristic Groups and, on the detail page, must still qualify as River/Stream, outside lake or reservoir waters, and outside the Sabine-Neches outlet boundary reach.\",\"The final output must be centered on the single winning station and list group_start_year plus common_start_year row by row in the fixed nine-group order.\"],\"exclusion_conditions\":[\"Exclude results that retain TCEQMAIN-10591 merely because it appears to be the nearest downstream mainstem station.\",\"Exclude results that do not check the nine Characteristic Groups separately and verify that they all belong to the same station ID.\",\"Exclude stations located in lake or reservoir waters or in the Sabine-Neches outlet boundary reach.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"MonitoringLocationIdentifier\",\"HUC\",\"County\",\"characteristic_group\",\"group_start_year\",\"common_start_year\"],\"rank\":\"emit 1 through 9 in the fixed characteristic-group order required by the task\",\"MonitoringLocationIdentifier\":\"use uppercase MonitoringLocationIdentifier\",\"HUC\":\"emit the HUC as an 8-digit string with no separators\",\"County\":\"use the county name exactly as shown on the detail page\",\"characteristic_group\":\"preserve the group label exactly as listed in the task\",\"year_fields\":\"emit four-digit years as plain integers\",\"common_start_year\":\"repeat the earliest year in which all nine required groups are simultaneously present for the chosen station\",\"sorting_or_selection\":\"emit rows in the fixed nine-group order stated in the task\"}}","all_involved_urls":"null"} +{"task_id":"wonder_001","domain":"CDC_WONDER","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"I am preparing a public health brief on changes in U.S. home births in 2020. I need to identify months where the home-birth rate among all mothers increased by at least 25% compared to the same month in 2019, and also examine the corresponding changes for non-Hispanic Black mothers and Hispanic mothers in those months. First, compare the home-birth rates for all mothers by calendar month between 2019 and 2020, retaining only months in 2020 where the rate increased by at least 25% relative to the same month in 2019. Then, for those months, add the 2020 home-birth rates for non-Hispanic Black mothers and Hispanic mothers, along with their changes relative to the same month in 2019. Finally, output a multi-row pipe-delimited table in calendar month order with the fixed header: month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel. All numeric values should be plain numbers without percent signs.","start_url":"https://wonder.cdc.gov/natality-expanded-current.html","output_format":"Output a multi-row pipe-delimited table in calendar month order with the fixed header: month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel. All numeric values should be plain numbers without percent signs.","oracle_answer":"month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel\nMay|1.03|1.49|45|0.74|54|0.55|57\nJune|1.04|1.31|26|0.66|20|0.48|30\nJuly|1.03|1.30|26|0.68|42|0.48|30\nAugust|1.02|1.29|26|0.69|50|0.48|26\nSeptember|1.01|1.31|30|0.73|43|0.54|54\nOctober|1.00|1.28|28|0.75|50|0.47|27\nNovember|0.99|1.30|31|0.73|43|0.55|67\nDecember|0.92|1.28|39|0.80|63|0.53|61","metadata":"{\"State-Gated Retrieval\":[\"First, compare the home-birth rates for all mothers by calendar month between 2019 and 2020, retaining only months in 2020 where the rate increased by at least 25% relative to the same month in 2019.\",\"The home-birth numerator must use the full home category, not Home intended alone.\",\"For those months, add the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, along with their changes relative to the same month in 2019.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Monthly natality queries yield the 2019 vs 2020 home-birth rates for all mothers and the candidate month set.\",\"Follow-up race/ethnicity queries yield the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, plus their same-month changes versus 2019.\",\"Final rows are produced only after qualifying months are determined from rate growth, and the resulting month set is reused for both subgroup backfill chains.\"],\"control_dependency\":[\"Month selection must be based on relative rate increase rather than counts alone.\",\"The home-birth numerator must use Residence or an equivalent full-home measure rather than Home intended alone before downstream subgroup queries run.\",\"Subgroup columns must be generated from the resulting month set rather than appended to earlier rows.\"],\"freeze\":{\"historical_window\":\"2019 and 2020 U.S. natality monthly home-birth rates for all mothers, non-Hispanic Black mothers, and Hispanic mothers.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"First, compare the home-birth rates for all mothers by calendar month between 2019 and 2020, retaining only months in 2020 where the rate increased by at least 25% relative to the same month in 2019.\",\"The home-birth numerator must use the full home category, not Home intended alone.\",\"For those months, add the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, along with their changes relative to the same month in 2019.\"],\"exclusion_conditions\":[\"Exclude month-row sets that misinterpret \\\"rate increase of at least 25%\\\" as \\\"count increase of at least 25%.\\\"\",\"Exclude results that use only the Home intended category instead of the full home numerator.\",\"Exclude results that add subgroup columns to an incorrect month set.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"Required literal first row: month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel\",\"schema\":[\"month\",\"all_2019\",\"all_2020\",\"all_rel\",\"black_2020\",\"black_rel\",\"hispanic_2020\",\"hispanic_rel\"],\"month\":\"Use the English month name and keep calendar order.\",\"numeric_fields\":\"All numeric outputs are plain numbers without a percent sign.\",\"relative_change_fields\":\"all_rel, black_rel, and hispanic_rel are emitted as integer percentages without the `%` character.\"}}","all_involved_urls":"null"} +{"task_id":"wonder_002","domain":"CDC_WONDER","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am preparing a one-page public health brief on 2021 U.S. infant mortality disparities. I want to identify groups that are separately listed in the report by mother's race and Hispanic origin, have an infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death. First, from the separately listed groups in the report, select those with an infant mortality rate above the U.S. overall rate and a clearly identifiable leading cause of death. Then, for each qualifying group, record the full-year infant mortality rate, the neonatal rate (under 28 days), and the postneonatal rate (28 days and older), along with the group's leading cause of death, its cause-specific rate, and the rank of that cause among all infant causes. Finally, output a multi-row pipe-delimited table sorted by full-year infant mortality rate from high to low: group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank.","start_url":"https://wonder.cdc.gov/lbd-current-expanded.html","output_format":"Finally, output a multi-row pipe-delimited table sorted by full-year infant mortality rate from high to low: group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank.","oracle_answer":"group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank\nnon-Hispanic Black|10.55|6.35|4.19|Short gestation and low birth weight|196.4|2\nnon-Hispanic American Indian or Alaska Native|7.46|3.83|3.67|Congenital malformations|134.0|1\nPuerto Rican|6.05|3.93|2.13|Short gestation and low birth weight|108.9|2","metadata":"{\"State-Gated Retrieval\":[\"Retain only groups that are separately listed in the 2021 U.S. infant mortality statistics, have a full-year infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death.\",\"For each qualifying group, provide the infant rate, neonatal rate, postneonatal rate, top cause, cause rate, and the rank of that cause among all infant causes.\",\"The leading cause must be determined by a group-level leading-cause query and verified for availability using notes/reliability markers.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"infant-mortality queries yield group-level overall, neonatal, and postneonatal rates for reportable mother race/Hispanic-origin groups\",\"leading-cause queries and reliability notes yield each eligible group's top cause, cause-specific rate, and U.S. rank\",\"final rows are produced only after the eligible-group set is rebuilt using both overall-rate and cause-specific-identifiability criteria\"],\"control_dependency\":[\"groups above the U.S. overall rate cannot be accepted until cause-specific reliability checks are run, which removes NHOPI\",\"leading cause must be queried at the group level rather than inherited from an all-infants cause table\",\"the cause-rate multiplier must be defined as per 100,000 live births before downstream ranking/output\"],\"freeze\":{\"historical_window\":\"2021 U.S. infant mortality by mother race and Hispanic origin, including the group-level leading-cause tables and reliability notes\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Retain only groups that are separately listed in the 2021 U.S. infant mortality statistics, have a full-year infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death.\",\"For each qualifying group, provide the infant rate, neonatal rate, postneonatal rate, top cause, cause rate, and the rank of that cause among all infant causes.\",\"The leading cause must be determined by a group-level leading-cause query and verified for availability using notes/reliability markers.\"],\"exclusion_conditions\":[\"Exclude groups that, despite having a full-year mortality rate above the U.S. overall rate, cannot provide a clearly identifiable leading cause due to cause-specific reliability issues.\",\"Exclude results that only inherit the top cause from the all-infants cause table without performing a group-level leading-cause query.\",\"Exclude results where the cause_rate uses an incorrect rate multiplier and is not read at the per-100,000-live-births denominator.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"required literal first row `group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank`\",\"schema\":[\"group\",\"infant_rate\",\"neonatal_rate\",\"postneonatal_rate\",\"top_cause\",\"cause_rate\",\"us_rank\"],\"sorting_or_selection\":\"infant_rate descending\",\"rate_fields\":\"infant_rate, neonatal_rate, and postneonatal_rate are per 1,000 live births; cause_rate is per 100,000 live births, but all four are emitted as plain numbers without unit text\",\"top_cause\":\"emit the short cause label used in the oracle, not an expanded prose description\",\"us_rank\":\"emit the integer rank of that same cause in the overall infant leading-cause list\"}}","all_involved_urls":"null"} diff --git a/data_en/constraint/arxiv_001.json b/data_en/constraint/arxiv_001.json new file mode 100644 index 0000000000000000000000000000000000000000..79e53c5889d0872d3af4e56b29b94b361d51a800 --- /dev/null +++ b/data_en/constraint/arxiv_001.json @@ -0,0 +1,94 @@ +{ + "task_id": "arxiv_001", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "I am organizing the research trajectory of dataset distillation and dataset condensation on arXiv from 2019 to 2021, aiming to identify machine learning papers that discuss replacing large-scale training sets with a small number of synthetic training data points. Search arXiv records from 2019 to 2021 for both the phrases \"dataset distillation\" and \"dataset condensation\". Retain only entries whose primary category is Machine Learning; do not include records that are only cross-listed into Machine Learning by other primary-category papers. From these, further select papers that had a version update in the calendar year following their initial submission and whose current arXiv record still clearly indicates a subsequent publication venue. Finally, output a table sorted by v1 submitted in ascending order, with columns: arXiv ID, term family, cue location, v1 submitted, first next-year version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying items exist, output NONE.", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "Finally, output a table sorted by v1 submitted in ascending order, with columns: arXiv ID, term family, cue location, v1 submitted, first next-year version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying items exist, output NONE.", + "oracle_answer": "arXiv ID|term family|cue location|v1 submitted|first next-year version|date of that version|primary category|publication-trail source|current publication clue\n1910.02551|Distillation|Title|2019-10-06|v3|2020-05-05|cs.LG|Related DOI|10.1109/IJCNN52387.2021.9533769\n2011.00050|Distillation|Abstract-only|2020-10-30|v2|2021-03-02|cs.LG|Comments|Accepted to ICLR 2021\n2107.13034|Distillation|Title|2021-07-27|v3|2022-01-17|cs.LG|Comments|NeurIPS 2021\n2110.04181|Condensation|Title|2021-10-08|v2|2022-04-21|cs.LG|Journal reference|Proceedings of the IEEE/CVF Winter Conference on Applications of Computer Vision 2023 (WACV)", + "metadata": { + "State-Gated Retrieval": [ + "Only include arXiv records where v1 submitted falls between 2019-01-01 and 2021-12-31.", + "The title or abstract must explicitly use a phrase from the \"dataset distillation\" or \"dataset condensation\" family, and the semantics must refer to replacing large-scale training sets with a small number of synthetic training data points.", + "The current primary category must be cs.LG. Do not include records that are only cross-listed into Machine Learning by other primary-category papers.", + "The paper must have a version update in the calendar year following its initial submission, and the current record must still clearly indicate a subsequent publication venue." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Root searches yield candidate arXiv IDs", + "Each candidate abstract page yields primary category, v1 date, first next-year version, cue location, and publication-trail source", + "Answer rows are produced only after deduplication and detail-page validation" + ], + "control_dependency": [ + "Records must be filtered by original submission year, with per-record validation that a next-calendar-year version exists", + "Cross-listed-only hits must be excluded, and the current primary category must be validated on abstract pages", + "Searches must cover both Title and Abstract because valid distillation hits can appear only in the abstract", + "Topic matches without a current publication trail still fail until the Comments, Journal reference, or Related DOI field is checked on the record page" + ], + "freeze": { + "historical_window": "v1 year in {2019, 2020, 2021}" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only include arXiv records where v1 submitted falls between 2019-01-01 and 2021-12-31.", + "The title or abstract must explicitly use a phrase from the \"dataset distillation\" or \"dataset condensation\" family, and the semantics must refer to replacing large-scale training sets with a small number of synthetic training data points.", + "The current primary category must be cs.LG. Do not include records that are only cross-listed into Machine Learning by other primary-category papers.", + "The paper must have a version update in the calendar year following its initial submission, and the current record must still clearly indicate a subsequent publication venue." + ], + "exclusion_conditions": [ + "Exclude records whose current primary category is not cs.LG and are only cross-listed to cs.LG.", + "Exclude records where the title or abstract contains the words \"distillation\" or \"condensation\" but does not correspond to the dataset distillation or dataset condensation research line.", + "Exclude records that have no next-calendar-year version update, or whose current record contains no clearly visible publication clue." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "term family", + "cue location", + "v1 submitted", + "first next-year version", + "date of that version", + "primary category", + "publication-trail source", + "current publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "term_family_extraction": { + "allowed_families": [ + "Distillation", + "Condensation" + ], + "tie_break": "if both families appear, prefer the title hit; if both appear only in the abstract, keep the first abstract occurrence" + }, + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_trail_source": [ + "Comments", + "Journal reference", + "Related DOI" + ], + "current_publication_clue": "keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue", + "sorting_or_selection": { + "primary": "v1 submitted ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all four corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the abstract page, current browse context, and publication-trail fields are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_en/constraint/arxiv_002.json b/data_en/constraint/arxiv_002.json new file mode 100644 index 0000000000000000000000000000000000000000..c5dc910ed8321ecca24bb5f75168aafa6d01f473 --- /dev/null +++ b/data_en/constraint/arxiv_002.json @@ -0,0 +1,88 @@ +{ + "task_id": "arxiv_002", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 10, + "instruction": "I am compiling a reading list of 2022 research on reasoning prompts for large language models. I want to find arXiv papers whose first version was submitted in 2022 and that explicitly focus on chain-of-thought or self-consistency reasoning methods. Start with arXiv records first submitted in 2022. First, check whether the title or abstract explicitly contains clues related to chain-of-thought or self-consistency. Then, retain only papers whose primary category is Computation and Language; do not include records that are only cross-listed from other primary categories. Next, verify that these papers actually had a version update in 2023, and confirm that the current arXiv record's comments field clearly indicates subsequent publication information. Finally, output a table sorted in ascending order by the date of each paper's earliest 2023 version update, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2023 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "Finally, output a table sorted in ascending order by the date of each paper's earliest 2023 version update, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2023 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.", + "oracle_answer": "arXiv ID|cue family|cue location|v1 submitted|first 2023 version|date of that version|primary category|publication clue\n2210.01240|Chain-of-thought|Title + Abstract|2022-10-03|v2|2023-01-25|cs.CL|Published as a conference paper at ICLR 2023\n2205.11916|Chain-of-thought|Abstract-only|2022-05-24|v4|2023-01-29|cs.CL|Accepted to NeurIPS2022\n2203.11171|Self-consistency; Chain-of-thought|Title + Abstract|2022-03-21|v4|2023-03-07|cs.CL|Published at ICLR 2023; camera ready version at ICLR 2023\n2210.03629|Chain-of-thought|Abstract-only|2022-10-06|v3|2023-03-10|cs.CL|v3 is the ICLR camera ready version\n2210.03350|Chain-of-thought|Abstract-only|2022-10-07|v2|2023-05-23|cs.CL|To appear at Findings of EMNLP 2023\n2212.10001|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-01|cs.CL|ACL-23 Camera Ready\n2212.08061|Chain-of-thought|Abstract-only|2022-12-15|v2|2023-06-04|cs.CL|ACL 2023 Main Conference\n2212.10071|Chain-of-thought|Abstract-only|2022-12-20|v2|2023-06-13|cs.CL|ACL 2023 camera-ready\n2212.10509|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-23|cs.CL|ACL'23 Camera Ready\n2211.12588|Chain-of-thought; Self-consistency|Abstract-only|2022-11-22|v4|2023-10-23|cs.CL|Published at TMLR 2023", + "metadata": { + "State-Gated Retrieval": [ + "Only include arXiv papers whose v1 was submitted in 2022.", + "The title or abstract must explicitly contain clues related to chain-of-thought or self-consistency.", + "The current primary category must be cs.CL; do not include records that are only cross-listed from other primary categories.", + "Must have had a version update in 2023, and the current comments field must clearly indicate subsequent publication information." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "root searches yield candidate arXiv IDs", + "each candidate abstract page yields primary category, v1 date, first 2023 version, comments/publication clue", + "answer rows are produced only after deduplication and detail-page validation" + ], + "control_dependency": [ + "searches must cover both Title and Abstract fields because valid rows can appear only in the abstract", + "cross-listed hits whose primary category is not cs.CL must be excluded, and the primary category must be validated on the abstract page", + "topic-matched hits must be validated against a current Comments publication clue before they can be accepted", + "2023 candidates must be identified by original submission year and full version-history checks, rather than by latest-date proxies" + ], + "freeze": { + "historical_window": "v1 submitted in 2022; version-history event in 2023" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only include arXiv papers whose v1 was submitted in 2022.", + "The title or abstract must explicitly contain clues related to chain-of-thought or self-consistency.", + "The current primary category must be cs.CL; do not include records that are only cross-listed from other primary categories.", + "Must have had a version update in 2023, and the current comments field must clearly indicate subsequent publication information." + ], + "exclusion_conditions": [ + "Exclude records whose current primary category is not cs.CL, even if they appear in relevant search results.", + "Exclude records that contain only vague abbreviations or weakly related hints, but whose title and abstract lack explicit CoT/self-consistency semantics.", + "Exclude records that have no 2023 version update, or whose current record lacks a direct publication clue." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "cue family", + "cue location", + "v1 submitted", + "first 2023 version", + "date of that version", + "primary category", + "publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "cue_family": [ + "Chain-of-thought", + "Self-consistency" + ], + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_clue": { + "source": "Comments field only", + "extraction": "keep the shortest phrase that still preserves the current publication-status clue" + }, + "sorting_or_selection": { + "primary": "date of the earliest 2023 version ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the current browse context, Comments field, and full Submission history are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_en/constraint/arxiv_003.json b/data_en/constraint/arxiv_003.json new file mode 100644 index 0000000000000000000000000000000000000000..b4013201436ad0416d7f637c4537161cb7a2f742 --- /dev/null +++ b/data_en/constraint/arxiv_003.json @@ -0,0 +1,89 @@ +{ + "task_id": "arxiv_003", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "I am compiling a reading list of early vision Transformer research. Identify arXiv papers whose first version was submitted in Q4 2020 and whose title or abstract explicitly uses vision- or image-domain Transformer terminology. First, filter for papers with a first-submission date in Q4 2020. Then check whether the title or abstract explicitly contains vision- or image-related Transformer expressions. Retain only papers whose primary category is Computer Vision and Pattern Recognition. Next, confirm that the paper had at least one version update in 2021, and check whether the current arXiv record clearly indicates subsequent publication information. Finally, output a table sorted in ascending order by the date of each paper's earliest 2021 version. Columns: arXiv ID, cue family, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying items exist, output NONE.", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "Output a table sorted in ascending order by the date of each paper's earliest 2021 version. Columns: arXiv ID, cue family, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying items exist, output NONE.", + "oracle_answer": "arXiv ID|cue family|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication-trail source|current publication clue\n2101.01097|Vision Transformer|Abstract-only|2020-12-30|v2|2021-01-08|cs.CV|Journal reference|IEEE Int. Conf. on Image Processing (ICIP) 2021\n2012.12556|Visual Transformer; Vision Transformer|Title + Abstract|2020-12-23|v2|2021-01-15|cs.CV|Comments; Related DOI|Accepted by TPAMI 2022; 10.1109/TPAMI.2022.3152247\n2012.00364|Image Processing Transformer|Title + Abstract|2020-12-01|v3|2021-05-28|cs.CV|Comments|CVPR 2021\n2011.08019|Vision Transformer|Title + Abstract|2020-11-16|v2|2021-06-02|cs.CV|Comments|Accepted for Publication in IJCB2021\n2010.11929|Vision Transformer|Abstract-only|2020-10-22|v2|2021-06-03|cs.CV|Comments|ICLR camera-ready version", + "metadata": { + "State-Gated Retrieval": [ + "Only include arXiv papers whose v1 submitted date falls in Q4 2020.", + "The title or abstract must explicitly contain vision- or image-domain Transformer-related expressions.", + "The current primary category must be cs.CV.", + "The paper must have had a version update in 2021, and the current record must clearly indicate a subsequent publication venue." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "root searches yield candidate arXiv IDs", + "candidate abstract pages yield v1 submitted date, first 2021 version, primary category, cue location, and publication-trail source", + "answer rows depend on deduplication plus detail-page validation" + ], + "control_dependency": [ + "searches must cover both Title and Abstract because valid positives can appear only in the abstract", + "candidate eligibility must be determined by the original-submission date window rather than by arXiv-ID or announcement intuition", + "candidate filtering must use full Submission-history validation rather than most-recent-submission filtering", + "searches must use the broader semantic cue state rather than a ViT-only entry point, because ViT-only hits can be false positives", + "publication-trail false positives still require Comments / Journal reference / Related DOI validation before final inclusion" + ], + "freeze": { + "historical_window": "v1 submitted from 2020-10-01 through 2020-12-31; version-history event in 2021" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only include arXiv papers whose v1 submitted date falls in Q4 2020.", + "The title or abstract must explicitly contain vision- or image-domain Transformer-related expressions.", + "The current primary category must be cs.CV.", + "The paper must have had a version update in 2021, and the current record must clearly indicate a subsequent publication venue." + ], + "exclusion_conditions": [ + "Exclude records whose current primary category is not cs.CV and are only cross-listed.", + "Exclude records that contain only weak cues such as Transformer or ViT, but whose title and abstract lack explicit vision- or image-domain expressions.", + "Exclude records that had no version update in 2021, or whose current record contains no direct publication clue." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "cue family", + "cue location", + "v1 submitted", + "first 2021 version", + "date of that version", + "primary category", + "publication-trail source", + "current publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "cue_family_extraction": "record every qualifying family actually present and join multiple families with `; ` in the emitted field", + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_trail_source": [ + "Comments", + "Journal reference", + "Related DOI" + ], + "current_publication_clue": "keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue", + "sorting_or_selection": { + "primary": "date of the earliest 2021 version ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the abstract page, current browse context, Comments field, Journal reference, Related DOI, and full Submission history are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_en/constraint/arxiv_004.json b/data_en/constraint/arxiv_004.json new file mode 100644 index 0000000000000000000000000000000000000000..48c3f02caebe8a2f41e59176057905d24ecc9138 --- /dev/null +++ b/data_en/constraint/arxiv_004.json @@ -0,0 +1,84 @@ +{ + "task_id": "arxiv_004", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "I am compiling a reading list of certified robustness defense research from the first half of 2020. I want to find arXiv papers whose first version was submitted between January and June 2020 and whose title or abstract explicitly focuses on smoothed classifiers, randomized smoothing and its variants, certified defenses against backdoor or poisoning attacks, or partition aggregation. Start with arXiv records whose first submission date falls between January and June 2020. Check whether the title or abstract explicitly mentions randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor/poisoning, or partition aggregation. Then retain only papers whose primary category is Machine Learning; do not include records that are only cross-listed from other primary categories. Next, confirm that these papers actually had a version update in 2021, and check whether the current arXiv record clearly indicates formal publication or acceptance information. Finally, output a table sorted by the date of each paper's earliest 2021 version in ascending order, with columns: arXiv ID, defense family, threat/topic cue, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "Finally, output a table sorted by the date of each paper's earliest 2021 version in ascending order, with columns: arXiv ID, defense family, threat/topic cue, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.", + "oracle_answer": "arXiv ID|defense family|threat/topic cue|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication clue\n2002.10733|De-randomized smoothing; Randomized smoothing|patch attacks|Title + Abstract|2020-02-25|v3|2021-01-08|cs.LG|NeurIPS 2020\n2006.04062|Smoothed classifiers; Randomized smoothing|certified L2 robustness|Title + Abstract|2020-06-07|v4|2021-01-08|cs.LG|NeurIPS 2020\n2003.08904|RAB; Randomized smoothing|backdoor attacks|Title + Abstract|2020-03-19|v4|2021-02-26|cs.LG|IEEE Symposium on Security and Privacy 2023\n2006.14768|Deep Partition Aggregation|general poisoning attacks; label-flipping poisoning attacks|Title + Abstract|2020-06-26|v2|2021-03-18|cs.LG|ICLR 2021\n2002.12398|Transformation-specific smoothing; Randomized smoothing|semantic transformations|Title + Abstract|2020-02-27|v4|2021-09-17|cs.LG|2021 ACM SIGSAC Conference on Computer and Communications Security (CCS '21)", + "metadata": { + "State-Gated Retrieval": [ + "Only include arXiv papers whose v1 submission date falls between 2020-01-01 and 2020-06-30.", + "The title or abstract must explicitly focus on randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor or poisoning attacks, or partition aggregation.", + "The current primary category must be cs.LG.", + "The paper must have had a version update in 2021, and the current record must clearly indicate formal publication or acceptance information." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "root searches yield candidate arXiv IDs", + "candidate abstract pages yield v1 date, primary category, full Submission history, cue location, and current publication clue", + "final rows depend on deduplication plus detail-page validation" + ], + "control_dependency": [ + "candidate filtering must use the original-submission window together with full 2021 version-history validation, because valid rows can have later newest versions", + "cross-listed hits whose primary category is not the target category must be excluded, with category validation on detail pages", + "searches must cover the broader certified-defense family, including partition-aggregation and backdoor/poisoning variants, rather than smoothing-only entries", + "topic+venue hits must be confirmed by detail-history validation that a 2021 version actually exists" + ], + "freeze": { + "historical_window": "v1 submitted from 2020-01-01 through 2020-06-30; version-history event in 2021" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only include arXiv papers whose v1 submission date falls between 2020-01-01 and 2020-06-30.", + "The title or abstract must explicitly focus on randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor or poisoning attacks, or partition aggregation.", + "The current primary category must be cs.LG.", + "The paper must have had a version update in 2021, and the current record must clearly indicate formal publication or acceptance information." + ], + "exclusion_conditions": [ + "Exclude records whose current primary category is not cs.LG, even if semantically related.", + "Exclude records that are only broadly related to robustness, defense, or backdoor/poisoning but do not meet the required certified-defense semantics.", + "Exclude records that have no version update in 2021 or no current publication clue." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "defense family", + "threat/topic cue", + "cue location", + "v1 submitted", + "first 2021 version", + "date of that version", + "primary category", + "publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "defense_family_extraction": "record every qualifying defense family actually present and join multiple families with `; ` in the emitted field", + "threat_topic_cue": "keep the shortest qualifying threat or topic cue that justifies inclusion", + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_clue": "keep the shortest phrase that still preserves venue or publication-status information", + "sorting_or_selection": { + "primary": "date of the earliest 2021 version ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the abstract page, current browse context, Comments field, and full Submission history are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_en/constraint/census_001.json b/data_en/constraint/census_001.json new file mode 100644 index 0000000000000000000000000000000000000000..c744faddb584a48562ae5be9d18db2b800f6fb20 --- /dev/null +++ b/data_en/constraint/census_001.json @@ -0,0 +1,68 @@ +{ + "task_id": "census_001", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 20, + "instruction": "Using the 2014–2018 American Community Survey 5-year estimates, identify counties with limited internet access, a high share of seniors living alone, weak transportation conditions, and low income. Scope the analysis to North Carolina counties from this dataset and use the North Carolina statewide values from the same release as the comparison baseline. First, select counties with at least 4,000 households lacking internet access. Then, retain only counties that simultaneously meet all of the following conditions: share of households without internet access higher than the statewide share; share of households with a householder aged 65 or older living alone higher than the statewide share; share of households without a vehicle higher than the statewide share; and median household income lower than the statewide median. Finally, output all qualifying counties as a single line, sorted alphabetically by county name. Each county should be formatted as County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome, with counties separated by commas. Percentage fields should be given to three decimal places without a percent sign.", + "start_url": "https://www.census.gov/data.html", + "output_format": "Output all qualifying counties as a single line, sorted alphabetically by county name. Each county should be formatted as County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome, with counties separated by commas. Percentage fields should be given to three decimal places without a percent sign.", + "oracle_answer": "Beaufort County|5988|30.986|16.083|7.664|43688,Bladen County|4194|30.026|13.681|10.417|32378,Cleveland County|11599|31.449|12.469|7.825|40393,Columbus County|7371|33.045|15.148|7.958|36398,Duplin County|7574|34.773|14.370|7.424|38850,Edgecombe County|7454|34.879|13.720|11.225|35516,Halifax County|7575|35.873|14.657|11.565|34251,Lenoir County|4923|21.292|15.614|11.699|38387,Nash County|8617|23.467|13.597|7.917|48362,Richmond County|5193|28.001|13.706|9.269|36091,Robeson County|19814|43.103|11.312|9.854|33679,Rockingham County|9938|26.714|14.166|7.164|42490,Rutherford County|7583|28.783|16.033|6.335|40347,Sampson County|8216|34.907|14.088|7.686|39068,Scotland County|4971|37.909|13.910|11.470|35617,Surry County|7595|26.203|13.762|6.779|41068,Vance County|5131|30.444|12.347|11.600|37282,Wayne County|9709|20.163|11.742|8.456|42192,Wilkes County|7046|24.849|14.773|5.992|40829,Wilson County|7652|23.817|13.322|9.540|42850", + "metadata": { + "State-Gated Retrieval": [ + "Use only North Carolina county data from the 2014-2018 American Community Survey 5-year estimates, and use the North Carolina statewide values from the same release as the comparison baseline.", + "Retain only counties with at least 4,000 households lacking internet access, and where the share of households without internet access, the share of households with a householder aged 65+ living alone, and the share of households without a vehicle are all higher than the statewide shares, and the median household income is lower than the statewide median.", + "Output the final results sorted alphabetically by county name, retaining the six required fields." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2014-2018 ACS 5-year product and North Carolina county geography yield the full county candidate set plus the statewide baseline row", + "the relevant ACS tables yield no-internet households, senior-living-alone share, no-vehicle share, and median household income for each county and the state baseline", + "final rows are produced only after the 5-year product/geography setup is fixed consistently and the full county filtering chain is executed from B28002 through the downstream filters" + ], + "control_dependency": [ + "the 2018 ACS 5-year Detailed Tables product must be used instead of the 2018 ACS 1-year product", + "county coverage must be established under one consistent product-and-geography setup rather than by piecemeal fixes within the current table", + "all downstream county comparisons must use the same 5-year statewide baseline and the same all-counties geography" + ], + "freeze": { + "historical_window": "2014-2018 American Community Survey 5-year estimates for North Carolina counties, using the North Carolina statewide row from the same release as the comparison baseline" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Use only North Carolina county data from the 2014-2018 American Community Survey 5-year estimates, and use the North Carolina statewide values from the same release as the comparison baseline.", + "Retain only counties with at least 4,000 households lacking internet access, and where the share of households without internet access, the share of households with a householder aged 65+ living alone, and the share of households without a vehicle are all higher than the statewide shares, and the median household income is lower than the statewide median.", + "Output the final results sorted alphabetically by county name, retaining the six required fields." + ], + "exclusion_conditions": [ + "Exclude results that incorrectly use the 2018 ACS 1-Year Estimates Detailed Tables or any other non-2014-2018 5-year release.", + "Exclude results that do not use the North Carolina statewide row from the same release as the comparison baseline.", + "Exclude any county that does not meet any one of the thresholds or statewide comparison conditions." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "NoInternetHH", + "NoInternetRatePct", + "SeniorLivingAloneSharePct", + "NoVehicleRatePct", + "MedianIncome" + ], + "county": "use the county display name including the word `County` and excluding a trailing state suffix", + "dedup_key": "county FIPS / GEOID", + "percentage_fields": "all percentage fields are plain numbers with exactly three decimal places and no percent sign", + "numeric_fields": "household counts and median income are emitted as plain integers without commas", + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "the North Carolina statewide threshold is fixed once from the designated table", + "all 100 North Carolina counties are covered under the same table/product settings", + "every surviving county is validated against all four required tables before emission" + ] + } + } +} diff --git a/data_en/constraint/census_002.json b/data_en/constraint/census_002.json new file mode 100644 index 0000000000000000000000000000000000000000..a5ae2bc7c3c1090b5a7ccb349b8972bd1cf17b90 --- /dev/null +++ b/data_en/constraint/census_002.json @@ -0,0 +1,80 @@ +{ + "task_id": "census_002", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "Using the 2015–2019 American Community Survey 5-year estimates, identify New Mexico counties that simultaneously have a large renter population, significant language barriers, limited internet access, transportation difficulties, low income, and rental stress. Use the New Mexico county-level data from this release and the New Mexico statewide values from the same release as the comparison baseline. First, retain counties with at least 2,500 renter households and at least 500 limited-English-proficient households. Then, keep only counties that meet all of the following conditions: the share of limited-English-proficient households is higher than the statewide share; the share of households with no internet access is higher than the statewide share; the share of households with no vehicle is higher than the statewide share; and the median household income is lower than the statewide median. Next, evaluate the rental housing stress indicators for renter households. Retain only counties that meet at least one of the following: the share of renter households with a rent-to-income ratio of 35% or more is higher than the statewide share, or the share of renter households with more than one occupant per room is higher than the statewide share. If both conditions are met, indicate both. Finally, output all qualifying counties as a single line, sorted alphabetically by county name. Each county should be formatted as County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath, with counties separated by commas. StressPath must be RENT, CROWD, or BOTH. Percentage fields should have three decimal places and no percent sign.", + "start_url": "https://data.census.gov/advanced", + "output_format": "Output all qualifying counties as a single line, sorted alphabetically by county name. Each county should be formatted as County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath, with counties separated by commas. StressPath must be RENT, CROWD, or BOTH. Percentage fields should have three decimal places and no percent sign.", + "oracle_answer": "Doña Ana County|28729|7883|10.127|22.612|6.079|44.172|6.391|40973|BOTH,Luna County|3482|1109|12.455|34.030|8.165|42.700|1.407|29360|RENT,McKinley County|6090|1610|7.688|50.587|10.978|27.568|16.256|33834|CROWD,San Miguel County|3443|1200|10.337|38.470|7.684|47.376|2.440|30946|RENT,Taos County|2854|652|5.387|28.844|5.726|48.823|4.555|38329|RENT", + "metadata": { + "State-Gated Retrieval": [ + "Use only the 2015-2019 American Community Survey 5-year estimates for New Mexico counties, and use the New Mexico statewide values from the same release as the comparison baseline.", + "Candidate counties must have at least 2,500 renter households and at least 500 limited-English-proficient households. Additionally, the LEP share, no-internet share, and no-vehicle share must all be higher than the statewide shares, and the median household income must be lower than the statewide median.", + "LEPHH must be computed by summing all four limited-English language groups from C16002. Finally, retain only counties where at least one of Severe Rent Burden or Crowded Renter is higher than the statewide value, and write StressPath according to the rule." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2015-2019 ACS 5-year county geography yields New Mexico county candidates and the statewide baseline row", + "C16002 and the downstream housing/income tables yield LEPHH, LEP share, no-internet share, no-vehicle share, severe rent burden, crowded-renter share, and median income for counties and the state baseline", + "final rows are produced only after the LEPHH numerator is computed from all four limited-English language groups and the downstream stress-path filters are applied" + ], + "control_dependency": [ + "the LEPHH numerator must be computed from all four limited-English language groups in C16002 rather than from Spanish-only counts", + "county eligibility and StressPath labels must be determined from the LEPHH measure and statewide LEP baseline defined under that full four-group calculation", + "the RENT / CROWD / BOTH classification must be determined by evaluating the same county set against both downstream housing-stress branches" + ], + "freeze": { + "historical_window": "2015-2019 American Community Survey 5-year estimates for New Mexico counties, using the New Mexico statewide row from the same release as the comparison baseline" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Use only the 2015-2019 American Community Survey 5-year estimates for New Mexico counties, and use the New Mexico statewide values from the same release as the comparison baseline.", + "Candidate counties must have at least 2,500 renter households and at least 500 limited-English-proficient households. Additionally, the LEP share, no-internet share, and no-vehicle share must all be higher than the statewide shares, and the median household income must be lower than the statewide median.", + "LEPHH must be computed by summing all four limited-English language groups from C16002. Finally, retain only counties where at least one of Severe Rent Burden or Crowded Renter is higher than the statewide value, and write StressPath according to the rule." + ], + "exclusion_conditions": [ + "Exclude results that treat Spanish-only limited-English households as the entire LEPHH count.", + "Exclude results that do not use the statewide baseline from the same release or that do not recalculate LEPHH/LEPSharePct/LEPShare_state.", + "Exclude counties that do not meet the final stress-path condition of RENT, CROWD, or BOTH." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "RenterHH", + "LEPHH", + "LEPSharePct", + "NoInternetPct", + "NoVehiclePct", + "SevereRentBurdenPct", + "CrowdedRenterPct", + "MedianIncome", + "StressPath" + ], + "county": "use the county display name including the word `County` and excluding a trailing state suffix", + "dedup_key": "county FIPS / GEOID", + "LEPHH": "sum the four designated limited-English-proficient renter-household cells before emitting the integer total", + "percentage_fields": "all percentage fields are plain numbers with exactly three decimal places and no percent sign", + "numeric_fields": "household counts and median income are emitted as plain integers without commas", + "StressPath": { + "allowed_values": [ + "RENT", + "CROWD", + "BOTH" + ], + "rule": "emit BOTH only when both the severe-rent-burden and crowded-renter signals survive; otherwise emit the single surviving label" + }, + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "all candidate counties are validated under the same geography and product settings", + "the renter scope and LEP aggregation are checked before the final line is emitted" + ] + } + } +} diff --git a/data_en/constraint/census_003.json b/data_en/constraint/census_003.json new file mode 100644 index 0000000000000000000000000000000000000000..10f09f4db5f061b0e9fced0e2fe00901184cfe36 --- /dev/null +++ b/data_en/constraint/census_003.json @@ -0,0 +1,73 @@ +{ + "task_id": "census_003", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "I am compiling a pre-pandemic county screening list for the California Department of Education to identify counties where, during annual school meal applications and parent data updates, schools cannot rely solely on English online portals and must still provide paper materials and in-person assistance. Use California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline. First, select counties with a population aged 5–17 of at least 75,000. Then, retain counties with at least 2,000 individuals aged 5–17 who speak English \"not well\" or \"not at all\" and whose share of the 5–17 population exceeds the statewide share. Next, check these counties' digital access and income conditions: the share of households with no internet access must exceed the statewide share, and the median household income must be below the statewide median. Finally, among three offline support signals, retain counties where at least two exceed the statewide share: the share of households with no vehicle, the share of minors in households that received SSI, cash public assistance, Food Stamps, or SNAP in the past 12 months, and the share of renter-occupied housing units with more than one occupant per room. Output all qualifying counties in a single line, sorted alphabetically by county name. Each county should be formatted as County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath, with counties separated by commas. SupportPath uses only the three labels BENEFITS, CROWD, and MOBILITY: the public assistance signal corresponds to BENEFITS, the crowded housing signal corresponds to CROWD, and the no-vehicle signal corresponds to MOBILITY. If multiple labels apply, join them with + in the fixed order BENEFITS+CROWD+MOBILITY.", + "start_url": "https://data.census.gov/advanced", + "output_format": "Output all qualifying counties in a single line, sorted alphabetically by county name. Each county should be formatted as County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath, with counties separated by commas. SupportPath uses only the three labels BENEFITS, CROWD, and MOBILITY: the public assistance signal corresponds to BENEFITS, the crowded housing signal corresponds to CROWD, and the no-vehicle signal corresponds to MOBILITY. If multiple labels apply, join them with + in the fixed order BENEFITS+CROWD+MOBILITY.", + "oracle_answer": "Fresno County|200205|5127|2.561|20.588|8.686|46.388|13.967|48730|BENEFITS+CROWD+MOBILITY,Kern County|185802|4130|2.223|21.739|7.058|37.285|14.394|50826|BENEFITS+CROWD,Los Angeles County|1641669|37540|2.287|16.338|9.204|27.238|16.741|61015|BENEFITS+CROWD+MOBILITY,Tulare County|104542|2703|2.586|25.738|6.274|49.347|14.535|44871|BENEFITS+CROWD", + "metadata": { + "State-Gated Retrieval": [ + "Use only California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline.", + "Retain only counties with a population aged 5–17 of at least 75,000, a SchoolAgeLEP of at least 2,000 with a share exceeding the statewide share, a no-internet share exceeding the statewide share, and a median household income below the statewide median.", + "SchoolAgeLEP must be the sum of the eight \"not well\" and \"not at all\" cells across the four major language groups in B16004. The final county must also have at least two of the three offline support signals (Mobility, Benefits, Crowd) exceeding the statewide share." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "The 2013–2017 ACS 5-year county geography yields California county candidates and the statewide baseline row.", + "B16004 and the downstream access/income/support tables yield SchoolAgeLEP, no-internet share, no-vehicle share, child-benefit share, crowded-renter share, and median income for counties and the statewide baseline.", + "Final rows are produced only after the SchoolAgeLEP numerator is computed from all eight 1980-target language cells and the downstream support-path branches are applied." + ], + "control_dependency": [ + "The SchoolAgeLEP numerator must be computed from the full eight-cell language set in B16004 rather than from only two Spanish LEP cells.", + "County eligibility and SupportPath labels must be determined from the LEP numerator and candidate set defined under that full eight-cell calculation.", + "The BENEFITS / CROWD / MOBILITY path labels must be determined by applying all three downstream support branches to the same county set." + ], + "freeze": { + "historical_window": "2013–2017 American Community Survey 5-year estimates for California counties, using the California statewide row from the same release as the comparison baseline." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Use only California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline.", + "Retain only counties with a population aged 5–17 of at least 75,000, a SchoolAgeLEP of at least 2,000 with a share exceeding the statewide share, a no-internet share exceeding the statewide share, and a median household income below the statewide median.", + "SchoolAgeLEP must be the sum of the eight \"not well\" and \"not at all\" cells across the four major language groups in B16004. The final county must also have at least two of the three offline support signals (Mobility, Benefits, Crowd) exceeding the statewide share." + ], + "exclusion_conditions": [ + "Exclude results that only take the two Spanish LEP rows and do not combine all eight target cells.", + "Exclude results that do not re-run the B28011, B19013, B08201, B09010, and B25014 branches.", + "Exclude counties whose final SupportPath does not have at least two signals exceeding the statewide share." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "SchoolAgePop", + "SchoolAgeLEP", + "LEPSharePct", + "NoInternetPct", + "NoVehiclePct", + "ChildBenefitSharePct", + "CrowdedRenterPct", + "MedianIncome", + "SupportPath" + ], + "county": "Use the county display name including the word `County` and excluding a trailing state suffix.", + "dedup_key": "county FIPS / GEOID", + "SchoolAgeLEP": "Sum the eight designated school-age LEP cells before emitting the integer total.", + "percentage_fields": "All percentage fields are plain numbers with exactly three decimal places and no percent sign.", + "numeric_fields": "Population counts and median income are emitted as plain integers without commas.", + "SupportPath": "Use only BENEFITS, CROWD, and MOBILITY, and when multiple labels apply join them with `+` in the fixed order BENEFITS+CROWD+MOBILITY.", + "sorting_or_selection": "County name alphabetical ascending.", + "stop_condition": [ + "All candidate counties are validated under the same geography and product settings.", + "The school-age LEP aggregation and all three support-signal gates are checked before the final line is emitted." + ] + } + } +} diff --git a/data_en/constraint/census_004.json b/data_en/constraint/census_004.json new file mode 100644 index 0000000000000000000000000000000000000000..cf0ea70904789f2ac3fcfd7f64097ad029c7495e --- /dev/null +++ b/data_en/constraint/census_004.json @@ -0,0 +1,72 @@ +{ + "task_id": "census_004", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 7, + "instruction": "Using 2012–2016 American Community Survey 5-year estimates, identify Pennsylvania counties with high senior evacuation support needs that warrant proactive in-person outreach before winter storms. Use Pennsylvania county-level data from the 2012–2016 American Community Survey 5-year estimates, with Pennsylvania statewide values from the same release as the comparison baseline. First, retain counties with a population aged 65 and over of at least 15,000. Then, among those, keep counties with at least 4,000 people aged 65 and over who have ambulatory difficulty, and whose share exceeds the statewide share. Additionally, the county median household income must be below the statewide median. Next, evaluate four evacuation support barriers: share of households with a householder aged 65+ living alone, share of households with no vehicle, share of renter households with no vehicle, and share of mobile homes among all housing units. Retain only counties where at least two of these barriers exceed the statewide values. Finally, output all qualifying counties in a single line, sorted alphabetically by county name. Each county should be formatted as County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath, with counties separated by commas. For BarrierPath, use only the labels ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE. If multiple labels apply, join them with + in the fixed order ALONE+MOBILE_HOME+NO_VEHICLE+RENTER_NO_VEHICLE.", + "start_url": "https://www.census.gov/data.html", + "output_format": "Output all qualifying counties in a single line, sorted alphabetically by county name. Each county should be formatted as County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath, with counties separated by commas. For BarrierPath, use only the labels ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE. If multiple labels apply, join them with + in the fixed order ALONE+MOBILE_HOME+NO_VEHICLE+RENTER_NO_VEHICLE.", + "oracle_answer": "Blair County|23013|5576|24.230|14.917|9.440|24.316|6.388|44033|ALONE+MOBILE_HOME, Cambria County|27058|6308|23.313|15.243|10.309|26.627|4.070|42917|ALONE+MOBILE_HOME+RENTER_NO_VEHICLE, Fayette County|25186|5886|23.370|14.961|9.302|22.290|10.489|40511|ALONE+MOBILE_HOME, Lycoming County|19486|4311|22.124|12.164|9.257|23.312|6.726|48731|ALONE+MOBILE_HOME, Mercer County|21537|4799|22.283|14.090|9.572|24.413|7.912|45831|ALONE+MOBILE_HOME, Philadelphia County|188185|56935|30.255|11.553|30.954|44.924|0.250|39770|NO_VEHICLE+RENTER_NO_VEHICLE, Schuylkill County|26613|6465|24.293|14.357|9.676|23.652|4.080|46573|ALONE+MOBILE_HOME", + "metadata": { + "State-Gated Retrieval": [ + "Use only Pennsylvania county-level data from the 2012-2016 American Community Survey 5-year estimates, and use Pennsylvania statewide values from the same release as the comparison baseline.", + "Retain only counties with a population aged 65 and over of at least 15,000, at least 4,000 people aged 65 and over with ambulatory difficulty and a share higher than the statewide share, and a median household income below the statewide median.", + "The 65+ ambulatory difficulty numerator must combine the four target cells from B18105 for ages 65-74 and 75+, male and female. The final county must also have at least two of the four barriers—Alone, No Vehicle, Renter No Vehicle, Mobile Home—higher than the statewide values." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "ACS tables B01001 and B18105 yield county senior-population totals and the full 65+ ambulatory-difficulty numerator.", + "Statewide comparison tables yield Pennsylvania baselines plus county barrier metrics for living alone, no vehicle, renter no vehicle, mobile home, and median income.", + "Final rows are produced only after the county candidate set is defined from the full ambulatory-difficulty numerator and the downstream six-table filters are applied." + ], + "control_dependency": [ + "The ambulatory-difficulty numerator must include the full 65+ population across 65-74 and 75+ and male and female cells, rather than only the 75+ cells.", + "Downstream county eligibility and barrier labels must be determined from the county candidate set defined under that full ambulatory numerator.", + "The at-least-two-barriers test must compare every county metric against the same Pennsylvania statewide baselines from the same ACS release." + ], + "freeze": { + "historical_window": "2012-2016 American Community Survey 5-year estimates for Pennsylvania counties, with Pennsylvania statewide baselines taken from the same release." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Use only Pennsylvania county-level data from the 2012-2016 American Community Survey 5-year estimates, and use Pennsylvania statewide values from the same release as the comparison baseline.", + "Retain only counties with a population aged 65 and over of at least 15,000, at least 4,000 people aged 65 and over with ambulatory difficulty and a share higher than the statewide share, and a median household income below the statewide median.", + "The 65+ ambulatory difficulty numerator must combine the four target cells from B18105 for ages 65-74 and 75+, male and female. The final county must also have at least two of the four barriers—Alone, No Vehicle, Renter No Vehicle, Mobile Home—higher than the statewide values." + ], + "exclusion_conditions": [ + "Exclude results that take only the 75 years and over ambulatory difficulty cells and mistakenly treat them as the full 65+ value.", + "Exclude results that do not use the Pennsylvania statewide baselines from the same release.", + "Exclude counties whose final BarrierPath does not satisfy the condition of at least two barriers higher than the statewide values." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "SeniorPop", + "AmbulatoryDifficulty65Plus", + "AmbDiffPct", + "SeniorLivingAloneSharePct", + "NoVehiclePct", + "RenterNoVehiclePct", + "MobileHomePct", + "MedianIncome", + "BarrierPath" + ], + "county": "Use the county display name including the word `County` and excluding a trailing state suffix.", + "dedup_key": "county FIPS / GEOID", + "percentage_fields": "All percentage fields are plain numbers with exactly three decimal places and no percent sign.", + "numeric_fields": "Population counts and median income are emitted as plain integers without commas.", + "BarrierPath": "Use only ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE. When multiple labels apply, join them with `+` in the fixed order ALONE+MOBILE_HOME+NO_VEHICLE+RENTER_NO_VEHICLE.", + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "All candidate counties are validated under the same geography and product settings.", + "The senior ambulatory-difficulty gate and all barrier-signal gates are checked before the final line is emitted." + ] + } + } +} diff --git a/data_en/constraint/climategov_001.json b/data_en/constraint/climategov_001.json new file mode 100644 index 0000000000000000000000000000000000000000..193ad4be76826f1348b13330d0cca7d4d595c482 --- /dev/null +++ b/data_en/constraint/climategov_001.json @@ -0,0 +1,66 @@ +{ + "task_id": "climategov_001", + "domain": "NOAA_NCEI_CLIMATE_AT_A_GLANCE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "Screen the four South Texas climate divisions (South Central, Upper Coast, South, and Lower Valley) to identify divisions that remained near-normal to wet over two longer periods yet still had low heating demand in March 1966. Restrict the search strictly to these four divisions; use the official Texas climate-division page for their exact names and numbers.\n\nRetain only divisions that meet all three of the following criteria:\n- The 10-month Palmer Z-Index anomaly ending February 1966 must be at least -0.05.\n- The 24-month Palmer Z-Index anomaly ending December 1966 must be at least -0.10.\n- The March 1966 single-month Heating Degree Days actual value must be below 200°Df.\n\nAfter identifying qualifying divisions, sort them as follows:\n- Primary: sum of the February 1966 10-month Z anomaly and the December 1966 24-month Z anomaly, in descending order.\n- Secondary: March 1966 Heating Degree Days actual value, in ascending order.\n- Tertiary: Texas division number, in ascending order.\n\nOutput a single-line string with qualifying entries separated by commas. Each entry must follow this exact format:\n|||||\n\nThe moisture score is the sum of the February 1966 10-month Z anomaly and the December 1966 24-month Z anomaly, formatted to two decimal places. If no division qualifies, output NONE.", + "start_url": "https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national", + "output_format": "Output a single-line string with qualifying entries separated by commas. Each entry must follow this exact format:\n|||||\nThe moisture score is the sum of the February 1966 10-month Z anomaly and the December 1966 24-month Z anomaly, formatted to two decimal places. If no division qualifies, output NONE.", + "oracle_answer": "7|South Central|0.72|0.35|194°Df|1.07,10|Lower Valley|0.28|0.67|106°Df|0.95,9|South|0.03|0.37|148°Df|0.40", + "metadata": { + "State-Gated Retrieval": [ + "Screen only within the four South Texas divisions defined on the Texas divisional page: South Central, Upper Coast, South, Lower Valley.", + "Retain divisions that simultaneously satisfy: 1966-02 10-month Palmer Z-Index anomaly >= -0.05; 1966-12 24-month anomaly >= -0.10; 1966-03 1-month Heating Degree Days Value < 200°Df.", + "Sort by sum of the two Z anomalies descending, then by 1966-03 HDD Value ascending, then by division number ascending." + ], + "dependency_type": "Data", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "The official Texas climate-division reference fixes the four South Texas division IDs and names that must be tracked across all later pages.", + "The 1966-02 10-month Palmer Z-Index anomaly page and the 1966-12 24-month Palmer Z-Index anomaly page jointly identify the four target South Texas divisions.", + "The 1966-03 1-month Heating Degree Days Value page supplies the last filter; final rows are produced only after intersecting the three divisional screens and then sorting by summed Z-anomaly score, HDD value, and division number." + ], + "freeze": { + "historical_window": "Texas climate divisions South Central, Upper Coast, South, and Lower Valley; metrics are fixed to the 1966-02 10-month Palmer Z-Index anomaly, 1966-12 24-month anomaly, and 1966-03 1-month Heating Degree Days Value pages." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Screen only within the four South Texas divisions defined on the Texas divisional page: South Central, Upper Coast, South, Lower Valley.", + "Retain divisions that simultaneously satisfy: 1966-02 10-month Palmer Z-Index anomaly >= -0.05; 1966-12 24-month anomaly >= -0.10; 1966-03 1-month Heating Degree Days Value < 200°Df.", + "Sort by sum of the two Z anomalies descending, then by 1966-03 HDD Value ascending, then by division number ascending." + ], + "exclusion_conditions": [ + "Exclude any Texas divisional results outside the four specified South Texas divisions.", + "Exclude results that misread the 1966-03 HDD page filter field as Anomaly instead of Value.", + "Exclude any division that fails any time window or threshold condition." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "texas_division_no", + "division_name", + "feb_1966_10mo_z_text", + "dec_1966_24mo_z_text", + "mar_1966_hdd_text", + "moisture_score" + ], + "texas_division_no": "Canonical output uses the short Texas climate-division number; the scorer may accept an equivalent four-digit form, but the emitted oracle uses the short number.", + "raw_text_fields": "The two Z-index anomaly fields and the March 1966 HDD field preserve the raw displayed text; comparison may ignore optional trailing HDD unit text such as `°Df`.", + "moisture_score": "Compute as February 1966 10-month Z-index anomaly plus December 1966 24-month Z-index anomaly, formatted with exactly two decimal places.", + "sorting_or_selection": { + "primary": "moisture_score descending", + "secondary": "March 1966 HDD actual value ascending after numeric normalization", + "tertiary": "Texas division number ascending" + }, + "eligibility_rule": "Each Texas division is counted once per requested window; if any required window value is missing, exclude the division.", + "stop_condition": [ + "All candidate Texas divisions are checked under the same base period and anomaly windows.", + "The unique ordered output string is resolved before emission." + ] + } + } +} diff --git a/data_en/constraint/climategov_002.json b/data_en/constraint/climategov_002.json new file mode 100644 index 0000000000000000000000000000000000000000..5afb228b50d5c291c020a1bbff86b6444e9ab80d --- /dev/null +++ b/data_en/constraint/climategov_002.json @@ -0,0 +1,73 @@ +{ + "task_id": "climategov_002", + "domain": "NOAA_NCEI_CLIMATE_AT_A_GLANCE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am researching historical climate patterns in Texas and want to find similar historical years to reference for shoulder-season operational planning. I am particularly interested in regions that recovered from a dry state to near-normal or wet conditions in the early 20th century and had light heating loads during both shoulder-season windows.\n\nIdentify the divisions in NOAA's Climate at a Glance database that meet these criteria. A division is retained only if it satisfies all four hard constraints: the 10-month Palmer Z-Index anomaly ending April 1907 is no higher than -0.30; the 10-month Z-Index anomaly ending April 1923 is no lower than -0.20; the 2-month Heating Degree Days (HDD) actual value ending May 1915 is below 50°Df; and the 5-month HDD actual value ending October 1922 is below 20°Df.\n\nAfter identifying the qualifying divisions, sort them. First compute each division's \"rebound score\" as the April 1923 10-month Z-Index anomaly minus the April 1907 10-month Z-Index anomaly. Sort primarily by rebound score in descending order. If scores are tied, place the division with the smaller October 1922 5-month HDD actual value first. If still tied, give priority to the smaller Texas official division number.\n\nFinally, output the results as a single-line string with divisions joined by commas. Each entry must strictly follow this format: \"|<4-digit division ID>||<1907-04 10-month Z-Index anomaly raw text>|<1923-04 10-month Z-Index anomaly raw text>|<1915-05 2-month HDD actual value raw text>|<1922-10 5-month HDD actual value raw text>|\". If no division meets all conditions, output NONE in uppercase.", + "start_url": "https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national", + "output_format": "Output the results as a single-line string with divisions joined by commas. Each entry must strictly follow this format: \"|<4-digit division ID>||<1907-04 10-month Z-Index anomaly raw text>|<1923-04 10-month Z-Index anomaly raw text>|<1915-05 2-month HDD actual value raw text>|<1922-10 5-month HDD actual value raw text>|\". If no division meets all conditions, output NONE in uppercase.", + "oracle_answer": "10|4110|Lower Valley|-0.36|1.46|10°Df|7°Df|1.82,9|4109|South|-0.33|0.53|23°Df|16°Df|0.86\n10|4110|Lower Valley|-0.36|1.46|10|7|1.82,9|4109|South|-0.33|0.53|23|16|0.86", + "metadata": { + "State-Gated Retrieval": [ + "Retain only Texas divisions that satisfy all four historical conditions: the 10-month Palmer Z-Index anomaly ending April 1907 is no higher than -0.30; the 10-month anomaly ending April 1923 is no lower than -0.20; the 2-month HDD Value ending May 1915 is less than 50°Df; the 5-month HDD Value ending October 1922 is less than 20°Df.", + "Rebound score is defined as the April 1923 10-month anomaly minus the April 1907 10-month anomaly.", + "Sort by rebound score descending, then by October 1922 5-month HDD Value ascending, then by Texas division number ascending." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Texas divisional pages yield the 1907-04 and 1923-04 10-month Palmer Z-Index anomalies plus the 1915-05 2-month and 1922-10 5-month HDD values for each division.", + "The rebound score and the two shoulder-season HDD values are computed only after the same set of candidate divisions survives all four historical filters.", + "The final output is produced after sorting the surviving divisions by rebound score, then 1922-10 HDD value, then division number." + ], + "control_dependency": [ + "The workflow must cover the 1907, 1923, and 1915 pages as well as the 1922-10 5-month HDD page.", + "Both HDD pages must be read from Value rather than Anomaly.", + "The final rebound ranking must be determined after the 1922-10 5-month HDD page excludes 7 South Central and 8 Upper Coast, using ReboundScore as the ordering basis." + ], + "freeze": { + "historical_window": "Texas climate divisions evaluated on the 1907-04 and 1923-04 10-month Palmer Z-Index anomaly pages, the 1915-05 2-month HDD Value page, and the 1922-10 5-month HDD Value page." + }, + "answer_type": "mixed multi-line output" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only Texas divisions that satisfy all four historical conditions: the 10-month Palmer Z-Index anomaly ending April 1907 is no higher than -0.30; the 10-month anomaly ending April 1923 is no lower than -0.20; the 2-month HDD Value ending May 1915 is less than 50°Df; the 5-month HDD Value ending October 1922 is less than 20°Df.", + "Rebound score is defined as the April 1923 10-month anomaly minus the April 1907 10-month anomaly.", + "Sort by rebound score descending, then by October 1922 5-month HDD Value ascending, then by Texas division number ascending." + ], + "exclusion_conditions": [ + "Exclude results that stop after filtering only the 1907, 1923, and 1915 pages without also reading the 1922-10 5-month HDD page.", + "Exclude results that incorrectly read the 1915 or 1922 HDD page as Anomaly instead of Value.", + "Exclude any division that does not satisfy all historical window conditions." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "texas_division_no", + "division_id_4digit", + "division_name", + "apr_1907_10mo_z_text", + "apr_1923_10mo_z_text", + "may_1915_2mo_hdd_text", + "oct_1922_5mo_hdd_text", + "rebound_score" + ], + "texas_division_no": "Emit the short Texas climate-division number in field 1 and the four-digit division ID in field 2.", + "raw_text_fields": "The two Z-index anomaly fields preserve the raw displayed text; the two HDD fields preserve the raw displayed text, but comparison may ignore an optional trailing `°Df` suffix.", + "rebound_score": "Compute as the April 1923 10-month Z-index anomaly minus the April 1907 10-month Z-index anomaly, formatted with exactly two decimal places.", + "sorting_or_selection": { + "primary": "rebound_score descending", + "secondary": "October 1922 HDD actual value ascending after numeric normalization", + "tertiary": "Texas division number ascending" + }, + "answer_set_note": "The current oracle stores two equivalent answer sets: one preserves the HDD unit suffixes and one strips them; treat the two HDD columns as equivalent after optional `°Df` removal.", + "stop_condition": [ + "All candidate Texas divisions are checked under the same anomaly and HDD windows.", + "The unique ordered output string is resolved before emission." + ] + } + } +} diff --git a/data_en/constraint/comptox_001.json b/data_en/constraint/comptox_001.json new file mode 100644 index 0000000000000000000000000000000000000000..22fdc312127eab31fe4828bfd9c94d7e674be06e --- /dev/null +++ b/data_en/constraint/comptox_001.json @@ -0,0 +1,76 @@ +{ + "task_id": "comptox_001", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "Among the following five substances found in records related to European painted products—aniline, cobalt, chromium, 3,3’-dichlorobenzidine, and dibenz[a,h]anthracene—retain only those whose pages explicitly contain the record “Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe.” For each qualifying substance, produce a consolidated list that integrates historical keyword status and the deepest-level use categories. First, check whether each of the following five dated keywords appears (presence only, ignoring any leading numbers): Substances in Products - Canada (4/2014), Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children’s Safe Product Act (4/2020), OEHHA Proposition 65 (1/2023). Record the earliest and latest year-month among the hits. Then, separately from the painted-products record mentioned above, select two use-category routes: one from a daily-consumer perspective with priority order Formulation → Article → Occupation, and one from a production-material perspective with priority order Occupation → Article → Formulation. After selecting each category, drill down along the child category with the highest product count until no further subdivision is possible; if there is a tie at the same level, choose the one with the smaller PUC ID.", + "start_url": "https://comptox.epa.gov/chemexpo/", + "output_format": "Finally, sort results by hit count descending; for ties, sort by the consumer-side terminal node’s product count descending. Output format: |||||||||||||. Separate results with commas; if no qualifying items exist, output NONE.", + "oracle_answer": "DTXSID8020090|5|2014-04|2023-01|Formulation|272|295|type|4|Occupation|301|356|family|27,DTXSID1031040|3|2018-10|2023-01|Formulation|77|94|type|7|Occupation|301|400|family|308,DTXSID9020409|2|2019-03|2023-01|Occupation|321|321|general|11|Occupation|321|321|general|11,DTXSID6020432|2|2019-03|2023-01|Article|313|313|general|1|Occupation|301|356|family|27,DTXSID3031022|1|2023-01|2023-01|Formulation|77|95|type|4|Occupation|301|356|family|185", + "metadata": { + "State-Gated Retrieval": [ + "Screen only the five substances specified in the task, and each target substance page must explicitly contain the record “Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe.”", + "Check whether each of the five specified dated keywords appears, and record the earliest and latest year-month among the hits.", + "Then independently select one daily-consumer route and one production-material route, the former following Formulation → Article → Occupation and the latter following Occupation → Article → Formulation, and refine each route separately to its deepest level." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "each chemical page yields the five dated historical keywords, the Europe body-paint/tattoo-ink qualifying record, and the earliest/latest dated-hit months", + "PUC category paths yield one consumer-side route chosen by Formulation -> Article -> Occupation and one source-side route chosen independently by Occupation -> Article -> Formulation", + "final rows are produced only after the consumer-side and source-side routes are selected and refined separately for each chemical" + ], + "control_dependency": [ + "the source-side route must be selected independently from the consumer-side route", + "for each chemical, the second route refinement must follow the production-material priority order rather than the daily-consumer route", + "family/type/general outputs must be determined only after both route selections are made independently" + ], + "freeze": { + "historical_window": "current ChemExpo chemical pages and PUC category paths for the five named substances, using the dated keyword states through 2023-01 and the current Europe body-paint/tattoo-ink record" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Screen only the five substances specified in the task, and each target substance page must explicitly contain the record “Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe.”", + "Check whether each of the five specified dated keywords appears, and record the earliest and latest year-month among the hits.", + "Then independently select one daily-consumer route and one production-material route, the former following Formulation → Article → Occupation and the latter following Occupation → Article → Formulation, and refine each route separately to its deepest level." + ], + "exclusion_conditions": [ + "Exclude substances that do not contain the specified Europe body-paint/tattoo-ink record.", + "Exclude results that directly reuse the same daily-consumer route for the production-material side.", + "Exclude results that do not independently select and refine both routes according to the specified priority orders." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DTXSID", + "hit_count", + "earliest", + "latest", + "consumer_kind", + "consumer_general_puc_id", + "consumer_terminal_puc_id", + "consumer_level", + "consumer_products", + "material_kind", + "material_general_puc_id", + "material_terminal_puc_id", + "material_level", + "material_products" + ], + "dated_hits": "count only the exact dated keyword strings defined in the source rubric", + "date_format": "YYYY-MM", + "kind": "the kind fields use the canonical labels Article, Formulation, or Occupation", + "level": "the level fields use the canonical labels general, family, or type", + "products_source": "the Products counts come from the local chemical-detail node for the selected branch, not from an overall aggregate shown elsewhere on the site", + "sorting_or_selection": { + "primary": "hit_count descending", + "secondary": "consumer_products descending", + "tertiary": "DTXSID ascending" + } + } + } +} diff --git a/data_en/constraint/comptox_002.json b/data_en/constraint/comptox_002.json new file mode 100644 index 0000000000000000000000000000000000000000..4333c89fa6e7557f21ac938fd1130f1c91443cfb --- /dev/null +++ b/data_en/constraint/comptox_002.json @@ -0,0 +1,78 @@ +{ + "task_id": "comptox_002", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 6, + "instruction": "In ChemExpo, I want to check whether each of these six substances currently appears more often in material-contact-related uses or in manufacturing-source-related uses, and then select the most representative use category from the corresponding direction. Follow the steps below. First, restrict the scope to these six substances: Di(2-Ethylhexyl) Phthalate, Melamine, Tris(2-Ethylhexyl) Phosphate, 4,5-Dihydro-2-Mercaptoimidazole, Phthalic Acid, Triphenyl Phosphates Tert-Butylated. Then, for each substance, first check whether any of the five material-contact-related label categories appear; score 1 point for each category that appears: Indirect additives food contact (10/2018); Europe, Food contact items; Food contact items, Japan; any keyword containing \"Toys and children's products\"; any keyword containing \"artificial_saliva\" or \"artificial_sweat\". Next, check whether any of the two manufacturing-source-related label categories appear; score 1 point for each category that appears: drinking_water, Europe, manufacturing, plastic_additive; Europe, plastic_additive. Additionally, separately count how many of the following four dated keywords appear: Indirect additives food contact (10/2018); OEHHA Proposition 65 (3/2019); WA Children's Safe Product Act (4/2020); OEHHA Proposition 65 (1/2023). Record the number of hits and the earliest and latest year-month among the hits. Then determine the direction based on which side has a higher score: if the material-contact score is strictly greater than the manufacturing-source score, search for the most representative category for this substance in the order Article → Formulation → Occupation; otherwise, search in the order Occupation → Article → Formulation. After determining the category, from this level onward, at each level only follow the subcategory with the highest product count, continuing until no further subdivision is possible; if there is a tie at the same level, choose the one with the smaller PUC ID.", + "start_url": "https://comptox.epa.gov/chemexpo/", + "output_format": "Finally, sort all substances by dated hit count descending; for ties, sort by product count of the selected node descending. Output format: |||||||||||||. Separate results with commas. If datedHits is 0, write NA for both earliest and latest.", + "oracle_answer": "DTXSID5020607|5|2|4|2018-10|2023-01|contact|Article|309|493|family|1|23|58,DTXSID5020601|4|1|3|2018-10|2023-01|contact|Article|309|309|general|1|5836|1827,DTXSID6020802|4|2|1|2018-10|2018-10|contact|Article|313|313|general|15|1104|675,DTXSID8021484|3|1|1|2018-10|2018-10|contact|Occupation|321|321|general|8|28313|4200,DTXSID0021414|5|0|1|2018-10|2018-10|contact|Article|309|309|general|3|5836|1827,DTXSID20872645|0|1|0|NA|NA|source|Occupation|318|381|family|5|274|107", + "metadata": { + "State-Gated Retrieval": [ + "Only consider the six specified substances, and first compute contactHits, sourceHits, and datedHits on the chemical page.", + "prioritySide must first be determined by these historical signals, and then a most representative current use category is selected along the corresponding direction.", + "The current route selection must follow the given kind priority and the same-level smaller PUC ID tie-break rule for further drill-down." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "each chemical page yields contactHits, sourceHits, datedHits, and the earliest/latest dated-hit months from the historical keyword set", + "after the priority side is chosen, the corresponding current PUC category path yields the representative kind, PUC path, product counts, and curated-chemical counts", + "final rows are produced only after the historical hit scores determine the side first and the current route is then chosen with the side-specific priority and tie-break rules" + ], + "control_dependency": [ + "historical contact/source signal scores must take priority over current maximum-Products paths", + "the priority side must be determined from contactHits, sourceHits, and datedHits rather than from current visibility alone", + "PUC path tie-breaks are valid only after the correct side has been fixed and the route has been traced under that side's rules" + ], + "freeze": { + "historical_window": "current ChemExpo chemical pages and PUC category paths for the six named substances, using the stated historical keyword families and dated hits through 2023-01" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only consider the six specified substances, and first compute contactHits, sourceHits, and datedHits on the chemical page.", + "prioritySide must first be determined by these historical signals, and then a most representative current use category is selected along the corresponding direction.", + "The current route selection must follow the given kind priority and the same-level smaller PUC ID tie-break rule for further drill-down." + ], + "exclusion_conditions": [ + "Exclude results that ignore historical signals and directly select the path with the maximum current visible Products on the chemical page.", + "Exclude results that start PUC route selection without first determining the contact/source direction.", + "Exclude results that do not apply the smaller PUC ID tie-break rule for same-level ties." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DTXSID", + "contactHits", + "sourceHits", + "datedHits", + "earliest", + "latest", + "prioritySide", + "PUCkind", + "generalPUCID", + "terminalPUCID", + "level", + "Products", + "PUCDocuments", + "PUCCuratedChemicals" + ], + "dated_hits": "count only the exact dated keyword strings defined in the source rubric", + "date_format": "YYYY-MM; if datedHits is 0, earliest and latest are both `NA`", + "prioritySide": "emit `contact` when contactHits > sourceHits; otherwise emit `source`", + "kind": "the PUCkind field uses the canonical labels Article, Formulation, or Occupation", + "level": "the level field uses the canonical labels general, family, or type", + "products_source": "Products comes from the selected terminal chemical-detail node", + "terminal_statistics": "PUCDocuments and PUCCuratedChemicals come from the selected terminal PUC detail page Additional Statistics block", + "sorting_or_selection": { + "primary": "datedHits descending", + "secondary": "Products descending", + "tertiary": "DTXSID ascending" + } + } + } +} diff --git a/data_en/constraint/comptox_003.json b/data_en/constraint/comptox_003.json new file mode 100644 index 0000000000000000000000000000000000000000..17848e2e23f5558480f4e79e5400eab53dabf65b --- /dev/null +++ b/data_en/constraint/comptox_003.json @@ -0,0 +1,67 @@ +{ + "task_id": "comptox_003", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "In ChemExpo, first select Formulation categories with a total product count of 15,000 or more. Then, within each category, following the website's default display order, identify the first product family that meets these criteria: the family itself has no assumed attributes and its total product count is at least 3,000; additionally, the family must have at least two distinct specific product types, one with allowed attributes including aerosol and the other including child, and both types must have empty assumed attributes. Next, within each of these two specific product types, compute the product share (type product count divided by family cumulative product count). If shares are equal, compare their Curated Chemicals counts and select the higher one; if still equal, select the type with the smaller PUC ID. After completing the selection on both sides, retain only the better of the two candidate types: first prioritize the type with the higher product share; if shares are equal, compare Product Count (higher wins); if still equal, compare Curated Chemicals (higher wins); if still equal, select the type with the smaller PUC ID.", + "start_url": "https://comptox.epa.gov/chemexpo/visualizations/", + "output_format": "Output results sorted by final share in descending order, formatted as: |||||. Join records with commas and no spaces. If no qualifying items exist, output NONE.", + "oracle_answer": "48|42|62|child|2160/3531|583,137|197|210|child|6934/16904|1135", + "metadata": { + "State-Gated Retrieval": [ + "First, retain only Formulation categories with a total product count of 15,000 or more.", + "Within each candidate family, both an aerosol-side type and a child-side type must be found: the family itself must have no assumed attributes and a total product count of at least 3,000; both types must also have empty assumed attributes.", + "All final selections within a family and between the two sides must follow the specified tie-break rules: share, Product Count, Curated Chemicals, and PUC ID." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "The Formulation summary yields the high-product candidate families whose total product count is at least 15,000", + "Within each family, lower-level type pages yield the aerosol and child candidates, their assumed/allowed attributes, product counts, shares, and curated-chemical counts", + "Final rows are produced only after a family survives both aerosol and child branches and the winning type is selected by the layered share/product/chemical/PUC tie-break rules" + ], + "control_dependency": [ + "Both the aerosol and child branches within the same family must be fully checked before that family can be retained", + "If one side is missing, the workflow must reject the family and continue to the next sibling family rather than stop at the first partial hit", + "The final winner can be selected only after both sides have been independently optimized within the family and then compared against each other" + ], + "freeze": { + "historical_window": "Current ChemExpo Formulation families with total product count >= 15,000, evaluated on family/type attributes and current product/chemical counts" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "First, retain only Formulation categories with a total product count of 15,000 or more.", + "Within each candidate family, both an aerosol-side type and a child-side type must be found: the family itself must have no assumed attributes and a total product count of at least 3,000; both types must also have empty assumed attributes.", + "All final selections within a family and between the two sides must follow the specified tie-break rules: share, Product Count, Curated Chemicals, and PUC ID." + ], + "exclusion_conditions": [ + "Exclude results that stop as soon as a usable type is found on either side without requiring the same family to cover both aerosol and child sides.", + "Exclude results that stop as soon as one side is missing instead of continuing to check sibling families at the same level.", + "Exclude results that do not follow the specified layered tie-break rules to select the winning type within a family and overall." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "generalPUCID", + "familyPUCID", + "typePUCID", + "side", + "share", + "CuratedChemicals" + ], + "dedup_key": "(generalPUCID, familyPUCID, typePUCID, side)", + "side": "Emit the lower-case branch label exactly as determined in the source workflow", + "share": "Canonical output uses the raw fraction `type Products / family Cumulative Products` rather than a decimal", + "CuratedChemicals": "Emit the integer count from the selected type-level node", + "sorting_or_selection": { + "primary": "Share descending by numeric fraction value", + "secondary": "Type-level Products descending", + "tertiary": "CuratedChemicals descending, then PUC IDs ascending as tie-breaks" + } + } + } +} diff --git a/data_en/constraint/comptox_004.json b/data_en/constraint/comptox_004.json new file mode 100644 index 0000000000000000000000000000000000000000..e3c95b16cc904bd81646ed1bff7533452ce871cc --- /dev/null +++ b/data_en/constraint/comptox_004.json @@ -0,0 +1,84 @@ +{ + "task_id": "comptox_004", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "In ChemExpo, for the five substances Di(2-Ethylhexyl) Phthalate, Melamine, Phthalic Acid, Tris(2-Ethylhexyl) Phosphate, and Triphenyl Phosphates Tert-Butylated, check whether their historical labels align with their current uses. Follow the steps below. First, restrict the scope to these five substances. For each substance, collect three sets of baseline assessment data. The first set is the \"material contact\" score: check for the presence of the following five label categories, scoring 1 point for each category hit: Indirect additives food contact (10/2018); Europe, Food contact items; Food contact items, Japan; any keyword containing \"Toys and children's products\"; and any keyword containing \"artificial_saliva\" or \"artificial_sweat\". The second set is the \"production source\" score: check for the presence of the following two label categories, scoring 1 point for each category hit: \"drinking_water, Europe, manufacturing, plastic_additive\" and \"Europe, plastic_additive\". The third set is the regulatory profile for specific dates: separately count the total hits for the four exact keywords Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children's Safe Product Act (4/2020), and OEHHA Proposition 65 (1/2023), and record the earliest and latest year-month among all hits. After obtaining these three sets of data, determine the historical side by comparing scores: if the material contact score is strictly greater than the production source score, select a historically recommended kind in the order Article → Formulation → Occupation; otherwise, select in the order Occupation → Article → Formulation. After determining the kind, drill down along the subcategory with the most products at each level until no further subdivision is possible; if there is a tie at the same level, choose the one with the smaller PUC ID. Separately, independently identify the current dominant category for the same substance, ignoring historical clues: directly find the path with the most products among all use categories, drilling down to the terminal level using the same tie-breaking rule (smaller PUC ID). Finally, compare the two results: if the current dominant kind is Article or Formulation and the historical side is material, mark ALIGNED; if the current dominant kind is Occupation and the historical side is source, also mark ALIGNED; otherwise, mark MISALIGNED.", + "start_url": "https://comptox.epa.gov/chemexpo/", + "output_format": "Output MISALIGNED records first; within the same group, sort by datedHits descending; if datedHits are equal, sort by currentProducts descending. Format: |||||||||||||||||. Separate records with commas. If datedHits is 0, write NA for both earliest and latest.", + "oracle_answer": "DTXSID6020802|4|2|1|2018-10|2018-10|material|Article|Furniture and furnishings|Furniture and furnishings|general|15|Occupation|Raw materials|fireproof coatings|type|24|MISALIGNED,DTXSID8021484|3|1|1|2018-10|2018-10|material|Occupation|Laboratory supplies|Laboratory supplies|general|8|Occupation|Laboratory supplies|Laboratory supplies|general|8|MISALIGNED,DTXSID5020607|5|2|4|2018-10|2023-01|material|Article|Construction and building materials|flooring|family|1|Formulation|Home maintenance|paint|type|112|ALIGNED,DTXSID0021414|5|0|1|2018-10|2018-10|material|Article|Construction and building materials|Construction and building materials|general|3|Article|Construction and building materials|Construction and building materials|general|3|ALIGNED,DTXSID20872645|0|1|0|NA|NA|source|Occupation|Industrial products|hydraulic fluid|family|5|Occupation|Industrial products|hydraulic fluid|family|5|ALIGNED", + "metadata": { + "State-Gated Retrieval": [ + "Operate only on the five specified substances, and first compute materialHits, sourceHits, and datedHits from the keyword-set block.", + "The historically recommended category must be derived independently from these historical signals; the current dominant category must be derived separately from the current use path.", + "Finally, compare only whether the historically recommended category and the current dominant category align at the coarse side level, and mark ALIGNED or MISALIGNED accordingly." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "each chemical page yields materialHits, sourceHits, datedHits, and the historical recommendation side implied by the keyword set", + "an independent current PUC category path yields the current dominant category, path labels, and classification counts for the same chemical", + "final rows are produced only after the historical recommendation and current dominant category are computed independently and then compared at the coarse side level" + ], + "control_dependency": [ + "the historical recommendation must be determined from the keyword-set evidence rather than from the current largest category", + "historical recommendation must be computed from the keyword-set evidence before alignment is judged", + "ALIGNED / MISALIGNED status is valid only after the historical and current category directions have been derived independently and then compared" + ], + "freeze": { + "historical_window": "current ChemExpo chemical pages and PUC category paths for the five named substances, using the specified historical keyword-set evidence through 2023-01" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Operate only on the five specified substances, and first compute materialHits, sourceHits, and datedHits from the keyword-set block.", + "The historically recommended category must be derived independently from these historical signals; the current dominant category must be derived separately from the current use path.", + "Finally, compare only whether the historically recommended category and the current dominant category align at the coarse side level, and mark ALIGNED or MISALIGNED accordingly." + ], + "exclusion_conditions": [ + "Exclude results that simply take the current largest category and treat it as the historically recommended category.", + "Exclude results that default to ALIGNED without independently deriving the historically recommended category.", + "Exclude results that fail to compute the historical and current paths separately, instead mixing signals in a single path." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DTXSID", + "materialHits", + "sourceHits", + "datedHits", + "earliest", + "latest", + "historySide", + "recommendedKind", + "recommendedGeneral", + "recommendedTerminal", + "recommendedLevel", + "recommendedProducts", + "currentKind", + "currentGeneral", + "currentTerminal", + "currentLevel", + "currentProducts", + "status" + ], + "dated_hits": "count only the exact dated keyword strings defined in the source rubric", + "date_format": "YYYY-MM; if datedHits is 0, earliest and latest are both `NA`", + "historySide": "emit the lower-case historical winner `material` or `source`", + "recommended_fields": "these fields describe the historically suggested path", + "current_fields": "these fields describe the current dominant path", + "kind": "the kind fields use the canonical labels Article, Formulation, or Occupation", + "level": "the level fields use the canonical labels general, family, or type", + "status": "emit `ALIGNED` or `MISALIGNED` exactly", + "sorting_or_selection": { + "primary": "status with MISALIGNED before ALIGNED", + "secondary": "datedHits descending", + "tertiary": "currentProducts descending", + "quaternary": "DTXSID ascending" + } + } + } +} diff --git a/data_en/constraint/consumerfinance_001.json b/data_en/constraint/consumerfinance_001.json new file mode 100644 index 0000000000000000000000000000000000000000..66785ea4ee6e1a88cf3d3d1fffb78b12086b7bf7 --- /dev/null +++ b/data_en/constraint/consumerfinance_001.json @@ -0,0 +1,67 @@ +{ + "task_id": "consumerfinance_001", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "On the CFPB enforcement actions page, for the period 2022 to 2024, find one qualifying administrative enforcement action for each of the three product categories: Deposits, Furnishing, and Prepaid. Then, in the corresponding Consent Order for that action, locate the first occurrence of the consumer redress amount and the civil money penalty amount, along with their page numbers.\n\nSpecifically, first restrict the search to actions on the CFPB enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.\n\nThen, search separately for each of the three product categories: Deposits, Furnishing, and Prepaid. For each category, follow the current default case order on the CFPB website from top to bottom, and select the first action that simultaneously meets all of the following conditions:\n1. The action page provides both a Consent Order and a press release.\n2. The product category label corresponds one-to-one with the target category.\n3. The page explicitly states consumer redress, and the redress amount exceeds $5,000,000.\n4. In addition to consumer redress, the page also explicitly states a civil money penalty.\n\nAfter finding such an action for each product category, open its corresponding Consent Order and locate the two types of monetary information:\n- The specific amount of consumer redress when it first appears in the text, and the page number where it appears.\n- The specific amount of civil money penalty when it first appears in the text, and the page number where it appears.\n\nPage numbers should be based on the physical page numbering of the Consent Order PDF, i.e., the first page is p1, the second page is p2, and so on.", + "start_url": "https://www.consumerfinance.gov/enforcement/actions/", + "output_format": "Finally, output the results for the three product categories sorted alphabetically by product name. Output one segment per category in the following format:\n|||||p||p\nIf no qualifying case is found for a category, output:\n|NONE\nJoin the three results with commas, with no spaces.", + "oracle_answer": "Deposits|Bank of America, N.A.|2023-CFPB-0006|2023-07-11|$80,400,000|p11|$60,000,000|p14,Furnishing|Hyundai Capital America|2022-CFPB-0005|2022-07-26|$13,200,000|p31|$6,000,000|p35,Prepaid|U.S. Bank National Association|2023-CFPB-0019|2023-12-19|$5,700,000|p22|$15,000,000|p26", + "metadata": { + "State-Gated Retrieval": [ + "Only consider administrative enforcement actions on the CFPB Enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.", + "For each of the three product categories (Deposits, Furnishing, Prepaid), search in the current default order from top to bottom for the first action that simultaneously satisfies: the page provides a Consent Order and a Press release; the Products label corresponds one-to-one with the target category; the action detail page explicitly states consumer redress > $5,000,000 and also states a civil money penalty.", + "Finally, extract the first-occurrence amounts and page numbers of consumer redress and civil money penalty from the correct Consent Order." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Enforcement-action list pages yield product-branch candidate actions in current default order.", + "Each action detail page and linked consent-order PDF yield product singularity, document-stack presence, redress/civil-money-penalty amounts, and first-occurrence pages.", + "Final rows are emitted only after identifying, for each product, the first action that survives detail-page and PDF validation." + ], + "control_dependency": [ + "List-level \"has Consent Order + Press release\" hits must be validated on the detail page for product singularity and money thresholds.", + "Prepaid candidates force document-level disambiguation among Consent Order, Stipulation, and terminating-order PDFs.", + "Per-product first-match selection must explicitly skip rejected candidates and validate downstream PDFs before it is finalized." + ], + "freeze": { + "historical_window": "Administrative enforcement actions with Initial filing date from 2022-01-01 through 2024-12-31; current default case ordering and currently linked action documents." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only consider administrative enforcement actions on the CFPB Enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.", + "For each of the three product categories (Deposits, Furnishing, Prepaid), search in the current default order from top to bottom for the first action that simultaneously satisfies: the page provides a Consent Order and a Press release; the Products label corresponds one-to-one with the target category; the action detail page explicitly states consumer redress > $5,000,000 and also states a civil money penalty.", + "Finally, extract the first-occurrence amounts and page numbers of consumer redress and civil money penalty from the correct Consent Order." + ], + "exclusion_conditions": [ + "Exclude actions where the Products label is not a single target category, or where the action appears relevant only at the list level but the detail page does not confirm it.", + "Exclude actions that do not clearly satisfy the redress > $5M and independent civil money penalty conditions.", + "Exclude cases where a Stipulation or Order Terminating the Consent Order is mistakenly used in place of the required Consent Order." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Product", + "Respondent", + "Docket", + "FilingDate", + "RedressUSD", + "RedressPage", + "PenaltyUSD", + "PenaltyPage" + ], + "product_order": "Alphabetical by Product name", + "fallback_row": "If a product has no qualifying case, emit `|NONE`", + "date_format": "FilingDate uses YYYY-MM-DD", + "money_fields": "Canonical output preserves the dollar sign and commas from the oracle, but equivalent comparison may ignore `$` and commas and compare the numeric USD amount.", + "page_fields": "Page fields use the canonical `pN` form.", + "document_scope": "Extract both money amounts from the Consent Order PDF only; do not substitute a stipulation, termination order, or other companion document.", + "selection_rule": "For each product, keep the first action in the default filtered order that fully satisfies every gate in the source rubric." + } + } +} diff --git a/data_en/constraint/consumerfinance_002.json b/data_en/constraint/consumerfinance_002.json new file mode 100644 index 0000000000000000000000000000000000000000..6ed7fef8cf5feda2079091c821ee9993730dcfce --- /dev/null +++ b/data_en/constraint/consumerfinance_002.json @@ -0,0 +1,66 @@ +{ + "task_id": "consumerfinance_002", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I want to organize the annual household financial stability survey report series in CFPB Reports, whose latest version page still links directly to the 2023 and 2022 editions. Some topics that appeared in the 2022 edition were later dropped from subsequent annual reports, and I want to see which other reports on the site are associated with these dropped topics. First, locate this series within the CFPB Reports section and confirm that the latest version links directly to the two previous editions (2023 and 2022). Then, using the 2022 edition as the baseline, identify topics that appear in the 2022 edition but are no longer retained in subsequent annual reports. Note: exclude the topic specifically used to mark \"belongs to the same survey series.\" Next, for each identified topic, confirm the following one by one: first, the year in which this topic first disappeared from subsequent annual reports; second, when searching for this topic within the CFPB Reports section, among results from 2022 and earlier, which report that does not belong to this series appears first; third, open that report, count how many related resources are listed on the page, how many of those explicitly link to the same survey series, and among those reports that link to the same survey series, how many have appendices labeled alphabetically with at least three sections (e.g., Appendix A, B, C or more); fourth, for the report that survives this multi-level screening, provide its title, publication date, and the alphabetical range of its appendices.", + "start_url": "https://www.consumerfinance.gov/data-research/research-reports/", + "output_format": "Finally, output a single-line string sorted alphabetically by topic name: |||||||||", + "oracle_answer": "Saving|2023|Consumer Savings App Strategies and Savings Outcomes|2022-12-07|4|2|1|Emergency Savings and Financial Security: Insights from the Making Ends Meet Survey and Consumer Credit Panel|2022-03-23|A-D,Student loans|2023|Report of the CFPB Education Loan Ombudsman|2022-10-20|0|0|0|NONE|NONE|NONE", + "metadata": { + "State-Gated Retrieval": [ + "First, locate the CFPB household financial well-being annual report series whose latest version links directly to 2023 and 2022.", + "Using the 2022 edition as the baseline, retain only topics that appear in 2022 but are no longer retained in subsequent annual reports, and exclude the topic specifically marked as \"belongs to the same survey series.\"", + "For each topic, find the earliest non-series pivot report from 2022 or earlier, then count its directly listed related resources, how many link back to the same survey series, how many qualify under the appendix rule, and the appendix span of the final qualifying report." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current CFPB Reports pages yield the 2024 -> 2023 -> 2022 annual-survey chain and the 2022 topic baseline", + "report detail pages and report-search results yield first-disappearance year, pivot report title/date, related-resource counts, and links back to the annual-survey series", + "final rows are produced only after separating the first jump target from later return-to-series counting" + ], + "control_dependency": [ + "requiring the pivot report itself to link back to the same survey series incorrectly rules out valid topic rows", + "title extraction must use the pivot detail page rather than search-result snippets", + "related-resource expansion must continue even when the pivot report itself does not link back to the same survey series" + ], + "freeze": { + "historical_window": "currently linked 2024, 2023, and 2022 CFPB household financial well-being annual reports; topic disappearance is judged over that three-year chain, and pivot-report search is restricted to 2022-and-earlier reports" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "First, locate the CFPB household financial well-being annual report series whose latest version links directly to 2023 and 2022.", + "Using the 2022 edition as the baseline, retain only topics that appear in 2022 but are no longer retained in subsequent annual reports, and exclude the topic specifically marked as \"belongs to the same survey series.\"", + "For each topic, find the earliest non-series pivot report from 2022 or earlier, then count its directly listed related resources, how many link back to the same survey series, how many qualify under the appendix rule, and the appendix span of the final qualifying report." + ], + "exclusion_conditions": [ + "Exclude topics that are still retained in subsequent annual reports.", + "Exclude results that incorrectly treat \"the pivot report itself must link back to the same survey series\" as a hard condition for column 3.", + "Exclude search results that directly belong to the same survey series or reports from after 2022." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "topic", + "first-missing-year", + "pivot-report-or-NONE", + "pivot-date-or-NONE", + "direct-related-count", + "same-series-count", + "qualified-count", + "representative-report-or-NONE", + "publication-date-or-NONE", + "appendix-span-or-NONE" + ], + "topic_order": "alphabetical by topic name", + "date_format": "pivot-date and publication-date use YYYY-MM-DD when present", + "appendix_span": "canonical span uses compact labels such as `A-D`", + "none_rule": "if qualified-count is 0, representative-report, publication-date, and appendix-span are all `NONE`" + } + } +} diff --git a/data_en/constraint/consumerfinance_003.json b/data_en/constraint/consumerfinance_003.json new file mode 100644 index 0000000000000000000000000000000000000000..c4762e7415c48addd794b76d89183cb8e2a9f7a3 --- /dev/null +++ b/data_en/constraint/consumerfinance_003.json @@ -0,0 +1,69 @@ +{ + "task_id": "consumerfinance_003", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I want to clearly sort out the CFPB's 2020 Debt Collection Rules, including proposal sources, delayed effective date arrangements, final effective dates, and the accompanying quick-reference PDF information on the implementation page. Follow the steps below. First, confirm when each of the two 2020 Debt Collection Rule final rules was issued. Then separately confirm the following for each wave: 1. The issue date of this final rule; 2. Which proposal(s) it developed from, and the public comment deadline for each proposal; 3. Whether the 2021 proposed rule on delaying the effective date covers this wave, and the comment deadline for that proposal; 4. The actual final effective date; 5. Which quick-reference PDF corresponds to this wave on the implementation page; 6. The first heading in the PDF body after skipping the introductory paragraph.", + "start_url": "https://www.consumerfinance.gov/rules-policy/final-rules/", + "output_format": "Output a single-line string with results sorted by final-rule issue date in ascending order. Identify each wave by its final rule issue month (YYYY-MM). Use the following format: ||||||||", + "oracle_answer": "2020-10|2020-10-30|2019-05-07 main|2019-09-18|YES|2021-05-19|2021-11-30|Executive summary of the October 2020 final rule|Coverage and Definitions,2020-12|2020-12-18|2019-05-07 main+2020-02-21 supplemental|2019-09-18+2020-08-04|YES|2021-05-19|2021-11-30|Executive summary of the December 2020 final rule|Validation Information Requirements and Disclosures", + "metadata": { + "State-Gated Retrieval": [ + "Must process the two 2020 Debt Collection Practices (Regulation F) final rules separately, not merge them into one.", + "For each wave, separately confirm: issue date, corresponding proposal chain and public comment deadlines, whether the 2021 delayed-effective-date proposed rule covers it and its deadline, final effective date, corresponding implementation quick-reference PDF, and the first heading after the introduction in that PDF.", + "The detail page, proposal chain, and summary PDF for the October wave and the December wave must each be independently verified." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "final-rules index pages and rule-development pages yield the two 2020 Regulation F final-rule waves and their proposal branches", + "each final-rule detail page, delayed-effective-date proposal page, and implementation quick-reference PDF yields the wave-specific dates, linked proposals, comment deadlines, and first summary heading", + "final rows are produced only after the October and December waves are traced separately end to end" + ], + "control_dependency": [ + "two same-title final rules force correction from name-based collapsing to issue-date branching", + "proposal-chain validation must be done per wave; otherwise the later December chain contaminates the October row", + "implementation PDFs must be matched back to the correct wave rather than accepting the latest quick-reference page" + ], + "freeze": { + "historical_window": "the 2020-10 and 2020-12 Debt Collection Rule final-rule waves, their linked 2020 proposal pages, the 2021 delayed-effective-date proposal, and the current implementation-page quick-reference PDFs" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Must process the two 2020 Debt Collection Practices (Regulation F) final rules separately, not merge them into one.", + "For each wave, separately confirm: issue date, corresponding proposal chain and public comment deadlines, whether the 2021 delayed-effective-date proposed rule covers it and its deadline, final effective date, corresponding implementation quick-reference PDF, and the first heading after the introduction in that PDF.", + "The detail page, proposal chain, and summary PDF for the October wave and the December wave must each be independently verified." + ], + "exclusion_conditions": [ + "Exclude results that merge the two identically named 2020 final rules into one.", + "Exclude results that project the December wave's proposal chain or executive-summary heading onto the October wave.", + "Exclude results that do not independently verify each final-rule detail page and its corresponding PDF." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "wave", + "final-rule-date", + "proposal-chain", + "proposal-comment-closes", + "delay-proposal-applied", + "delay-proposal-comments-close", + "controlling-effective-date", + "quick-reference-pdf", + "summary-heading" + ], + "wave": "wave is the final-rule issue month in YYYY-MM", + "date_format": "all standalone date fields use YYYY-MM-DD", + "proposal_chain": "canonical chain joins proposal milestones with `+`, using pieces such as `2019-05-07 main` or `2020-02-21 supplemental` in chronological order", + "proposal_comment_closes": "join multiple comment-close dates with `+` in the same order as proposal_chain", + "delay_proposal_applied": "emit `YES` when a delay proposal is part of the chain; otherwise emit `NO`", + "quick_reference_pdf": "use the displayed quick-reference PDF title, not the filename", + "summary_heading": "use the first substantive heading from the final-rule PDF", + "sorting_or_selection": "final-rule-date ascending" + } + } +} diff --git a/data_en/constraint/consumerfinance_004.json b/data_en/constraint/consumerfinance_004.json new file mode 100644 index 0000000000000000000000000000000000000000..0ce4c965a79328fdd2b1119f6c06a194425ed051 --- /dev/null +++ b/data_en/constraint/consumerfinance_004.json @@ -0,0 +1,68 @@ +{ + "task_id": "consumerfinance_004", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "On the CFPB Enforcement Actions page, identify administrative enforcement actions filed in 2024 and subsequently closed, separately for the product categories Credit Cards and Deposits. Then extract the corresponding clause information linking the terminating order to the original Consent Order. Specifically, first restrict the search to administrative enforcement actions on the CFPB Enforcement Actions page whose initial filing date falls between 2024-01-01 and 2024-12-31. Then filter separately for the two product categories: Credit Cards and Deposits. For each category, retain only cases that simultaneously meet the following conditions: the case page shows the case has been closed, with a status of Expired, Terminated, or Vacated; the case page provides all four of these document types: Consent Order, Stipulation, Order Terminating the Consent Order, and Press Release; the page lists exactly one product category, and that single category is the one you are currently targeting. That is, if you are searching for Credit Cards, the page must list only that item and no other categories; the same requirement applies when searching for Deposits. After filtering, each product category may still have more than one case. For each category, retain only the case with the latest initial filing date; if multiple cases share the same filing date, select the one with the smaller docket number. Next, open the Order Terminating the Consent Order for the selected case and record the following three pieces of information: the termination date on this document; the passage in the document that states the legal authority for terminating the consent order, i.e., the termination authority, recording only the original text of its first occurrence; the PDF physical page number where this termination authority first appears. Also, within the text of this terminating order, find the first explicit reference to a paragraph number from the original Consent Order; if it reads \"Paragraphs X and Y,\" take only X. Then, return to the original Consent Order document for this case, locate the referenced paragraph, and record the section heading under which it falls.", + "start_url": "https://www.consumerfinance.gov/enforcement/actions/", + "output_format": "Finally, output a single-line string in alphabetical order by product name: ||||||p||. If a product has no qualifying case, output: |NONE", + "oracle_answer": "Credit Cards|Apple Inc.|2024-CFPB-0012|2024-10-23|2025-09-22|12 U.S.C. § 5563(b)(3)|p1|83|ADMINISTRATIVE PROVISIONS,Deposits|Navy Federal Credit Union|2024-CFPB-0014|2024-11-07|2025-07-01|12 U.S.C. § 5563(b)(3)|p1|106|ADMINISTRATIVE PROVISIONS", + "metadata": { + "State-Gated Retrieval": [ + "Consider only administrative enforcement actions with an Initial filing date in 2024, and search separately in the Credit Cards and Deposits categories.", + "Cases must have a status of Expired, Terminated, or Vacated, and the page must simultaneously provide a Consent Order, Stipulation, Order Terminating the Consent Order, and Press Release, and the Products field must correspond one-to-one with the target category.", + "Finally, for each category retain only the most recent qualifying case determined by Initial filing date, and compile the corresponding clause information linking the terminating order to the original Consent Order." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "enforcement-action list pages yield 2024 candidate actions by product branch", + "each action detail page and linked Consent Order / Stipulation / Order Terminating the Consent Order / Press Release documents yield status, initial filing date, single-product validity, and clause references", + "final rows are selected only after per-product comparison on Initial filing date and document-stack validation" + ], + "control_dependency": [ + "\"latest\" must be determined by Initial filing date rather than termination date", + "product filters on the list page are insufficient until the action detail page confirms a single matching product", + "clause extraction in the terminating order must stay aligned with the original Consent Order rather than a superficially similar section" + ], + "freeze": { + "historical_window": "administrative enforcement actions with Initial filing date from 2024-01-01 through 2024-12-31; current action status and currently linked Consent Order / Stipulation / terminating-order / Press Release documents" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Consider only administrative enforcement actions with an Initial filing date in 2024, and search separately in the Credit Cards and Deposits categories.", + "Cases must have a status of Expired, Terminated, or Vacated, and the page must simultaneously provide a Consent Order, Stipulation, Order Terminating the Consent Order, and Press Release, and the Products field must correspond one-to-one with the target category.", + "Finally, for each category retain only the most recent qualifying case determined by Initial filing date, and compile the corresponding clause information linking the terminating order to the original Consent Order." + ], + "exclusion_conditions": [ + "Exclude results that use termination date instead of Initial filing date to determine \"latest.\"", + "Exclude cases with an incomplete document stack or where Products is not a single target category.", + "Exclude cases where the required clause correspondence between the terminating order and the original Consent Order cannot be established." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Product", + "Respondent", + "Docket", + "InitialFilingDate", + "TerminationDate", + "TerminationAuthority", + "TermAuthorityPage", + "ReferencedParagraph", + "ConsentSectionHeading" + ], + "product_order": "alphabetical by Product name", + "fallback_row": "if a product has no qualifying case, emit `|NONE`", + "date_format": "InitialFilingDate and TerminationDate use YYYY-MM-DD", + "termination_authority": "use the canonical statute string extracted from the termination order", + "page_fields": "TermAuthorityPage uses the canonical `pN` form", + "ReferencedParagraph": "emit the paragraph number as a plain numeric string", + "ConsentSectionHeading": "emit the uppercase heading of the consent-order section containing the referenced paragraph" + } + } +} diff --git a/data_en/constraint/consumerfinance_005.json b/data_en/constraint/consumerfinance_005.json new file mode 100644 index 0000000000000000000000000000000000000000..b1d61189295690bc6c3f1b8a2c96db09e67ccec6 --- /dev/null +++ b/data_en/constraint/consumerfinance_005.json @@ -0,0 +1,75 @@ +{ + "task_id": "consumerfinance_005", + "domain": "CFPB_COMPLAINT_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am preparing an internal outreach memo on historical complaint clusters and need to track a specific set of complaints: from the CFPB Complaint Database, within the current product bucket covering credit reporting and other personal consumer reports, between 2018-01-01 and 2021-12-31, tagged as Servicemember, with a public narrative, and where the text explicitly mentions medical bills or doctors. Please provide two representative complaint clusters: the first is the peak month of this cohort; the second is the latest month in this cohort whose complaint count is still at least half of the peak. For each cluster, report the total complaints for that month, the state with the highest complaint count and its count, the company with the highest complaint count within that state and month and its count, and the earliest complaint received by that company in that state and month, including its ID, date, Issue, and Sub-issue. Output a single line with Peak first, then LatestHalfPeak, using the format: ||||||||||.", + "start_url": "https://www.consumerfinance.gov/data-research/consumer-complaints/", + "output_format": "Output a single line with Peak first, then LatestHalfPeak, using the format: ||||||||||. Join the Peak and LatestHalfPeak clusters with a comma. For ties: months are ordered chronologically; states are ordered alphabetically by state abbreviation; companies are ordered alphabetically by company name; for the earliest complaint, use the earliest date, then the smallest Complaint ID if dates are identical.", + "oracle_answer": "Peak|2018-02|46|CA|28|TRANSUNION INTERMEDIATE HOLDINGS, INC.|9|2806154|2018-02-07|Improper use of your report|Reporting company used your report improperly,LatestHalfPeak|2021-11|23|CA|12|EQUIFAX, INC.|3|4928768|2021-11-19|Problem with a credit reporting company's investigation into an existing problem|Their investigation did not fix an error on your report", + "metadata": { + "State-Gated Retrieval": [ + "Only consider complaints within the current product bucket covering credit reporting and other personal consumer reports, from 2018-01-01 to 2021-12-31, tagged as Servicemember, with a public narrative, and where the text explicitly mentions medical bills or doctors.", + "The first cluster must be the peak month of the cohort; the second cluster must be the latest month in the cohort whose complaint count is still at least half of the peak.", + "For each cluster, recompute the top company within the corresponding month + state subset, then locate the earliest complaint received by that company in that state and month." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current complaint-form taxonomy yields the product bucket that contains credit reporting / other personal consumer reports", + "filtered complaint records yield month counts, month-state subsets, top companies, and earliest complaint details inside each chosen subset", + "final rows are produced only after peak month and latest-half-peak month are determined, and each downstream aggregate is computed inside its narrower month-state cohort" + ], + "control_dependency": [ + "the latest month must be defined as the latest month whose count is at least ceil(PeakCount / 2)", + "overall top-company counts cannot be projected into a month-state subset without recomputation", + "earliest complaint selection is only valid after the month, state, and company filters are all frozen" + ], + "freeze": { + "historical_window": "Complaint Database records received from 2018-01-01 through 2021-12-31 under the current product-bucket mapping for the credit-reporting / other personal consumer reports family; Servicemember + public narrative + medical bills/doctors text cohort" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only consider complaints within the current product bucket covering credit reporting and other personal consumer reports, from 2018-01-01 to 2021-12-31, tagged as Servicemember, with a public narrative, and where the text explicitly mentions medical bills or doctors.", + "The first cluster must be the peak month of the cohort; the second cluster must be the latest month in the cohort whose complaint count is still at least half of the peak.", + "For each cluster, recompute the top company within the corresponding month + state subset, then locate the earliest complaint received by that company in that state and month." + ], + "exclusion_conditions": [ + "Exclude results that directly use the latest month with any complaints as the second cluster.", + "Exclude results that first find the overall top company across the full cohort and then project it onto the month-state subset.", + "Exclude results that do not first derive the half-peak threshold from PeakCount." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Cluster", + "Month", + "MonthComplaints", + "TopState", + "StateComplaints", + "TopCompany", + "CompanyComplaints", + "EarliestComplaintID", + "EarliestDate", + "Issue", + "SubIssue" + ], + "cluster_order": [ + "Peak", + "LatestHalfPeak" + ], + "date_format": { + "Month": "YYYY-MM", + "EarliestDate": "YYYY-MM-DD" + }, + "TopState": "use the uppercase two-letter state abbreviation", + "TopCompany": "use the company display name as shown in the source data", + "tie_breaks": "for tied months use chronological order; for tied states use state-code alphabetical order; for tied companies use company-name alphabetical order; for the earliest complaint use EarliestDate ascending then Complaint ID ascending", + "SubIssue": "emit `NONE` when the complaint row has no sub-issue value" + } + } +} diff --git a/data_en/constraint/consumerfinance_006.json b/data_en/constraint/consumerfinance_006.json new file mode 100644 index 0000000000000000000000000000000000000000..b48b45f2ec4a35ac61e696be18e32fe497a7e163 --- /dev/null +++ b/data_en/constraint/consumerfinance_006.json @@ -0,0 +1,78 @@ +{ + "task_id": "consumerfinance_006", + "domain": "CFPB_COMPLAINT_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am writing a crypto-complaint concentration memo. To verify whether complaint peaks within a fixed three-year window are driven only by a few top platforms, I need you to step through the CFPB complaint database and extract relevant data.\n\nFirst, define the underlying data scope. Using the current CFPB complaint form product taxonomy, determine which product bucket Virtual currency currently falls under. Once the bucket is confirmed, strictly limit the time range to 2019-08-26 through 2022-08-26 and retain only complaint records classified under the Virtual currency subcategory within that product bucket. This forms the initial cohort.\n\nSecond, identify two characteristic peak months within this cohort. Step 1: Aggregate complaints by month across the full cohort (with no companies removed) and identify the original peak month (AllCompanies). Step 2: Identify the top two companies by complaint count in that original peak month. Remove all complaint records of these two companies from the entire three-year cohort (not just from the single peak month). Then re-aggregate complaints by month on the remaining data to find the residual peak month (ResidualAfterTop2).\n\nThird, for each of these two peak months, extract detailed data. For each cluster, obtain the total complaint count for that month, the names of the two excluded top companies, and their combined complaint count in the original peak month. Also identify the state with the highest complaint count in that feature month and its complaint count, the most complained-about company within that state and its complaint count, and the full details of the earliest complaint received by that company in that state during that feature month (including Complaint ID, date, Issue, and Sub-issue).\n\nFinally, after completing all the above steps, format the two sets of core parameters into a single string with no spaces. The two rows must be ordered AllCompanies first, ResidualAfterTop2 second. The field order for each row is fixed as: ||||||||||||. To ensure a unique answer: output the two records in AllCompanies then ResidualAfterTop2 order; list ExcludedTop2Companies in descending order of their complaint count in the original peak month, breaking ties alphabetically; for any tie in sorting indicators, sort by field value in ascending alphabetical order; if the earliest complaint date is tied, select the one with the smallest Complaint ID.", + "start_url": "https://www.consumerfinance.gov/data-research/consumer-complaints/", + "output_format": "Output the two rows in AllCompanies first, ResidualAfterTop2 second order, joined into a formatted string with no spaces. The field order for each row is fixed as: ||||||||||||.", + "oracle_answer": "AllCompanies|2021-05|336|Coinbase, Inc.+BAM Management US Holdings Inc.|226|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,ResidualAfterTop2|2020-06|180|Coinbase, Inc.+BAM Management US Holdings Inc.|226|OH|28|PNC Bank N.A.|22|3687376|2020-06-07|Other transaction problem|NONE", + "metadata": { + "State-Gated Retrieval": [ + "Only consider Complaint Database records under the current product bucket for Virtual currency subcategory, with a received date between 2019-08-26 and 2022-08-26.", + "First determine the AllCompanies original peak month, then identify the top two companies by complaint count in that peak month.", + "These two companies must be removed entirely from the full three-year cohort, then recompute the residual peak month and all downstream fields based on the remaining cohort." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current complaint-form taxonomy yields the product bucket for Virtual currency", + "complaint records within the fixed three-year cohort yield the all-company peak month, per-month top companies, and residual-cohort recomputations after company removal", + "final rows are produced only after the top-2 companies from the original peak month are removed from the full cohort and downstream aggregates are computed on the resulting cohort" + ], + "control_dependency": [ + "peak-month top companies must be removed from the entire cohort, not only from the original peak month", + "residual peak detection must be computed from the rewritten cohort rather than by local patching of the original month", + "downstream state / company / earliest-complaint fields are valid only after the global company-removal step is locked" + ], + "freeze": { + "historical_window": "Complaint Database records received from 2019-08-26 through 2022-08-26 under the current product-bucket mapping for Virtual currency" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only consider Complaint Database records under the current product bucket for Virtual currency subcategory, with a received date between 2019-08-26 and 2022-08-26.", + "First determine the AllCompanies original peak month, then identify the top two companies by complaint count in that peak month.", + "These two companies must be removed entirely from the full three-year cohort, then recompute the residual peak month and all downstream fields based on the remaining cohort." + ], + "exclusion_conditions": [ + "Exclude results that only locally delete top-2 company records from the original peak month.", + "Exclude results that do not write the top-2 company set back into the full cohort before recomputing the residual peak.", + "Exclude results that use downstream state, company, or earliest complaint fields computed from a cohort that has not been recomputed after removal." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Cluster", + "Month", + "MonthComplaints", + "ExcludedTop2Companies", + "ExcludedTop2PeakMonthComplaints", + "TopState", + "StateComplaints", + "TopCompany", + "CompanyComplaints", + "EarliestComplaintID", + "EarliestDate", + "Issue", + "SubIssue" + ], + "cluster_order": [ + "AllCompanies", + "ResidualAfterTop2" + ], + "date_format": { + "Month": "YYYY-MM", + "EarliestDate": "YYYY-MM-DD" + }, + "ExcludedTop2Companies": "join the two excluded company names with `+` in source-peak complaint-count descending order, breaking ties alphabetically", + "TopState": "use the uppercase two-letter state abbreviation", + "TopCompany": "use the company display name as shown in the source data", + "tie_breaks": "for the earliest complaint use EarliestDate ascending then Complaint ID ascending", + "SubIssue": "emit `NONE` when the complaint row has no sub-issue value" + } + } +} diff --git a/data_en/constraint/consumerfinance_007.json b/data_en/constraint/consumerfinance_007.json new file mode 100644 index 0000000000000000000000000000000000000000..d026a67c5754c278493444e9f1ea891c75794128 --- /dev/null +++ b/data_en/constraint/consumerfinance_007.json @@ -0,0 +1,82 @@ +{ + "task_id": "consumerfinance_007", + "domain": "CFPB_COMPLAINT_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "I am drafting a layered analysis report on the core factors behind a batch of cryptocurrency complaints. I need your help to verify the true causes of this complaint surge step by step using the CFPB complaint database.\n\nFirst, define the base scope of the analysis. Using the current CFPB product and issue taxonomy documentation, confirm the product bucket that \"Virtual currency\" falls under. Once the bucket is determined, strictly restrict the time range to between 2020-01-01 and 2022-08-26, and only for the \"Virtual currency\" subcategory under that product bucket, extract the original peak month (BaselinePeak) and its total complaint count for this initial complaint cohort.\n\nSecond, determine the shift in peaks by progressively removing core influencing factors. Round 1: In the original peak month identified above, identify the most frequent \"Company public response\" value, then completely remove all complaints with that value from the entire initial cohort to obtain the recalculated second peak month (AfterDominantPublicResponse). Round 2: In the second peak month, identify the most frequent \"Issue\" type, remove it from the residual data of the previous round to lock in the third emerging peak month (AfterDominantPublicResponseAndIssue). Round 3: In the third peak month, identify the single most complained-about company (Company), remove that company, and perform the final round of statistics to obtain the final residual peak month (AfterDominantPublicResponseIssueAndCompany).\n\nThird, for each of the identified characteristic months, extract detailed data. For these four complaint clusters, besides obtaining the total complaint count for that month, also determine the newly added removal dimension and its specific excluded value, and the count of that excluded value in the month that served as its reference source. Additionally, identify the state with the highest complaint count in that month and its complaint count, the most complained-about company within that state and its complaint volume, and the complete information of the earliest complaint received by the highest-complaint company in that state during that characteristic month, including complaint ID, date, Issue, and Sub-issue.\n\nFinally, after completing the investigation and information collation for all the above dimensions, concatenate all extracted parameters for these four complaint clusters strictly in the order of BaselinePeak, AfterDominantPublicResponse, AfterDominantPublicResponseAndIssue, and AfterDominantPublicResponseIssueAndCompany into four strings with no spaces. Each line's field order is strictly fixed as: |||||||||||||. In case of ties, always select by lexicographic ascending order; for the earliest complaint with the same date, select by ascending Complaint ID numeric value. Normalize all empty values to NONE before sorting.", + "start_url": "https://www.consumerfinance.gov/data-research/consumer-complaints/", + "output_format": "Concatenate into four strings with no spaces, strictly in the order of BaselinePeak, AfterDominantPublicResponse, AfterDominantPublicResponseAndIssue, AfterDominantPublicResponseIssueAndCompany; each line's field order is strictly fixed as: |||||||||||||. In case of ties, always select by lexicographic ascending order; for the earliest complaint with the same date, select by ascending Complaint ID numeric value. Normalize all empty values to NONE before sorting.", + "oracle_answer": "BaselinePeak|2021-05|336|NONE|NONE|0|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,AfterDominantPublicResponse|2022-07|31|Company public response|NONE|321|CA|6|BANK OF AMERICA, NATIONAL ASSOCIATION|4|5735227|2022-07-05|Other transaction problem|NONE,AfterDominantPublicResponseAndIssue|2021-10|13|Issue|Fraud or scam|26|TX|2|BANK OF AMERICA, NATIONAL ASSOCIATION|1|4821611|2021-10-18|Other transaction problem|NONE,AfterDominantPublicResponseIssueAndCompany|2021-06|8|Company|Foris DAX, Inc.|5|NC|3|TRUIST FINANCIAL CORPORATION|2|4462160|2021-06-15|Money was not available when promised|NONE", + "metadata": { + "State-Gated Retrieval": [ + "Only consider Complaint Database records under the current product bucket's Virtual currency subcategory with a received date between 2020-01-01 and 2022-08-26.", + "Determine the peak months for the four stages BaselinePeak, AfterDominantPublicResponse, AfterDominantIssue, and AfterDominantCompany sequentially as required.", + "Each round's identified dominant Company public response, dominant Issue, and dominant Company must be written back and globally deleted from the corresponding upstream residual cohort before running the next round of statistics." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current complaint-form taxonomy yields the product bucket for Virtual currency", + "complaint records yield the baseline peak plus the dominant Company public response, dominant Issue, and dominant Company at successive residual-peak states", + "final rows are produced only after each dominant value is applied to the full upstream residual cohort and then used to determine the next peak" + ], + "control_dependency": [ + "dominant values found in a peak month cannot be deleted only inside that month; each must be propagated to the full upstream cohort", + "each new residual peak depends on the prior round's global rewrite, so local month-by-month deletion gives the wrong chain", + "downstream counts and exemplar complaints are valid only after the full three-stage waterfall is executed" + ], + "freeze": { + "historical_window": "Complaint Database records received from 2020-01-01 through 2022-08-26 under the current product-bucket mapping for Virtual currency" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only consider Complaint Database records under the current product bucket's Virtual currency subcategory with a received date between 2020-01-01 and 2022-08-26.", + "Determine the peak months for the four stages BaselinePeak, AfterDominantPublicResponse, AfterDominantIssue, and AfterDominantCompany sequentially as required.", + "Each round's identified dominant Company public response, dominant Issue, and dominant Company must be written back and globally deleted from the corresponding upstream residual cohort before running the next round of statistics." + ], + "exclusion_conditions": [ + "Exclude results that only delete records locally within the current peak month without writing back to the entire upstream cohort.", + "Exclude results that do not re-find the next peak month on each round's residual cohort.", + "Exclude intermediate or final fields based on downstream statistics that were not fully re-run." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Cluster", + "Month", + "MonthComplaints", + "NewExclusionType", + "NewExclusionValue", + "NewExclusionCountInSourcePeak", + "TopState", + "StateComplaints", + "TopCompany", + "CompanyComplaints", + "EarliestComplaintID", + "EarliestDate", + "Issue", + "SubIssue" + ], + "cluster_order": [ + "BaselinePeak", + "AfterDominantPublicResponse", + "AfterDominantPublicResponseAndIssue", + "AfterDominantPublicResponseIssueAndCompany" + ], + "date_format": { + "Month": "YYYY-MM", + "EarliestDate": "YYYY-MM-DD" + }, + "NewExclusionType": "emit the canonical exclusion-type label from the source workflow; when no new exclusion is applied, emit NONE", + "NewExclusionValue": "emit the canonical excluded value; when no value exists, emit NONE", + "TopState": "use the uppercase two-letter state abbreviation", + "TopCompany": "use the company display name as shown in the source data", + "tie_breaks": "normalize empty values to NONE before sorting; for other ties use lexicographic order ascending, and for the earliest complaint use EarliestDate ascending then Complaint ID ascending", + "SubIssue": "emit NONE when the complaint row has no sub-issue value" + } + } +} diff --git a/data_en/constraint/europemc_001.json b/data_en/constraint/europemc_001.json new file mode 100644 index 0000000000000000000000000000000000000000..e3227106f435065b8b00969e4c9b46961d334081 --- /dev/null +++ b/data_en/constraint/europemc_001.json @@ -0,0 +1,67 @@ +{ + "task_id": "europemc_001", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 21, + "instruction": "I want to consolidate the admission variables actually used by several prediction schemes in this 2020 COVID-19 mortality risk prediction paper into a single line, to make it easy to see which variables overlap and which appear only in the comparison schemes.\nPlease follow the steps below. First, locate the target paper — a 2020 open-access review whose title contains all of \"prognosis model\", \"mortality risk\", and \"COVID-19\", and whose main text discusses hospitalized patients in Wuhan.\nThen, retain only two types of variables:\n- Type 1: admission variables that appear in both the Random Forest and XGBoost variable importance rankings.\n- Type 2: additional admission variables that do not appear in both rankings but are present in the CURB-65 or NEWS schemes used by the authors for comparison.\nNext, for each retained variable, record it in the following format:\nvariable~RF_rank_or_0~XGB_rank_or_0~F~C~N~X\nWhere:\n- RF_rank_or_0: the rank of this variable in the Random Forest ranking; write 0 if it is not included.\n- XGB_rank_or_0: the rank of this variable in the XGBoost ranking used in the paper; write 0 if it is not included.\n- F: whether this variable entered the authors' final logistic regression model.\n- C: whether this variable belongs to CURB-65.\n- N: whether this variable belongs to NEWS.\n- X: whether this variable belongs to the XGBoost model used as a comparison in the paper.\nFinally, sort all variables alphabetically by variable name, join them with | into a single line; if the paper cannot be found, output NONE.", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "Next, for each retained variable, record it in the following format:\nvariable~RF_rank_or_0~XGB_rank_or_0~F~C~N~X\nWhere:\n- RF_rank_or_0: the rank of this variable in the Random Forest ranking; write 0 if it is not included.\n- XGB_rank_or_0: the rank of this variable in the XGBoost ranking used in the paper; write 0 if it is not included.\n- F: whether this variable entered the authors' final logistic regression model.\n- C: whether this variable belongs to CURB-65.\n- N: whether this variable belongs to NEWS.\n- X: whether this variable belongs to the XGBoost model used as a comparison in the paper.\nFinally, sort all variables alphabetically by variable name, join them with | into a single line; if the paper cannot be found, output NONE.", + "oracle_answer": "Age~4~2~1~1~0~0|Alanine aminotransferase~17~11~0~0~0~0|Aspartate transaminase~6~4~0~0~0~0|Blood urea nitrogen~5~7~0~1~0~0|Confusion~0~0~0~1~1~0|CRP~2~6~1~0~0~1|Creatinine~9~13~0~0~0~0|Diastolic pressure~16~17~0~1~0~0|Heart rate~15~14~0~0~1~0|LDH~1~1~1~0~0~1|Lymphocyte count~3~5~0~0~0~1|Monocytes~12~16~0~0~0~0|Neutrophil~7~3~0~0~0~0|Normal platelet~10~9~0~0~0~0|Oxygen inhalation~0~0~0~0~1~0|Respiratory rate~11~10~0~1~1~0|SPO2~0~0~0~0~1~0|Systolic pressure~13~12~0~1~1~0|Temperature~18~18~0~0~1~0|Total bilirubin~14~15~0~0~0~0|White blood cell~8~8~0~0~0~0", + "metadata": { + "State-Gated Retrieval": [ + "First, locate the target paper: a 2020 open-access review whose title contains all of \"prognosis model\", \"mortality risk\", and \"COVID-19\", and whose main text discusses hospitalized patients in Wuhan.", + "Retain only two types of variables: admission variables that appear in both the Random Forest and XGBoost rankings; or variables that do not appear in both rankings but are additional items belonging to CURB-65 or NEWS.", + "For each variable, annotate it as required with RF rank, XGB rank, and whether it belongs to the final logistic regression, CURB-65, NEWS, and the comparison XGBoost model, then output in alphabetical order by variable name." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Europe PMC search results and the target open-access article yield the candidate Wuhan COVID mortality-risk review", + "article tables and discussion sections yield RF/XGBoost rankings, final logistic-regression inclusion, and comparator-variable memberships for CURB-65 / NEWS / external XGBoost", + "final rows are produced only after overlapping variables and comparator-only variables are merged into one normalized variable table" + ], + "control_dependency": [ + "comparator-only variables must be captured from the discussion definitions rather than from Table 2 + Table 3 alone", + "comparator membership must be read from the article's explicit scheme definitions rather than inferred from common clinical usage", + "variable normalization must wait until RF/XGBoost overlap and comparator-only additions are both complete" + ], + "freeze": { + "historical_window": "the 2020 open-access COVID-19 mortality-risk review about Wuhan inpatients; variable inclusion and comparator definitions are taken from the article's current full-text tables and discussion" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "First, locate the target paper: a 2020 open-access review whose title contains all of \"prognosis model\", \"mortality risk\", and \"COVID-19\", and whose main text discusses hospitalized patients in Wuhan.", + "Retain only two types of variables: admission variables that appear in both the Random Forest and XGBoost rankings; or variables that do not appear in both rankings but are additional items belonging to CURB-65 or NEWS.", + "For each variable, annotate it as required with RF rank, XGB rank, and whether it belongs to the final logistic regression, CURB-65, NEWS, and the comparison XGBoost model, then output in alphabetical order by variable name." + ], + "exclusion_conditions": [ + "Exclude admission variables that do not appear in both RF and XGB rankings and also do not belong to CURB-65 / NEWS additional variables.", + "Exclude results that stop at Table 2 + Table 3 and do not proceed to the discussion to read the comparator definitions.", + "Exclude results that infer comparator variables by common sense rather than verifying against the paper's explicit definitions." + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "variable", + "RF_rank_or_0", + "XGB_rank_or_0", + "F", + "C", + "N", + "X" + ], + "variable": "use the variable wording normalized in the article tables; keep `Systolic pressure` and `Diastolic pressure` as separate variables", + "rank_fields": "RF_rank_or_0 and XGB_rank_or_0 are positive integer ranks when present, otherwise 0", + "boolean_fields": "F, C, N, and X are emitted as 1 or 0 only", + "sorting_or_selection": "variable name alphabetical ascending", + "stop_condition": [ + "the shared variable set from Table 2 and Table 3 is fully resolved", + "the comparator definitions for CURB-65, NEWS, and the comparison XGBoost model are fixed before the final line is emitted" + ] + } + } +} diff --git a/data_en/constraint/europemc_002.json b/data_en/constraint/europemc_002.json new file mode 100644 index 0000000000000000000000000000000000000000..0c24027f072408dbe7a64622a178d7d55bc34a3f --- /dev/null +++ b/data_en/constraint/europemc_002.json @@ -0,0 +1,62 @@ +{ + "task_id": "europemc_002", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 6, + "instruction": "Track studies that were Phase 1 in the 2021 Alzheimer's disease drug development pipeline review by their ClinicalTrials.gov identifier, and check whether they continue to appear in the 2022 and 2023 pipeline reviews.\nFollow these steps. First, locate the three articles: the 2021 review titled \"Alzheimer's disease drug development pipeline\", and the 2022 and 2023 open-access reviews in the same series.\nIn the 2021 review, retain only the studies that were listed as Phase 1 at that time.\nThen, in the 2022 and 2023 reviews, check each of these studies one by one, but match them by the same ClinicalTrials.gov identifier rather than by drug name alone, because drug names can change across years.\nFinally, keep only those studies that can still be found under the same ClinicalTrials.gov identifier in both 2022 and 2023. Format the result as a single line: NCT~2021_agent~2022_phase~2022_agent~2023_phase~2023_agent. Sort by NCT in ascending order and join records with |. If the set of three articles cannot be found, output NONE.", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "Finally, keep only those studies that can still be found under the same ClinicalTrials.gov identifier in both 2022 and 2023. Format the result as a single line: NCT~2021_agent~2022_phase~2022_agent~2023_phase~2023_agent. Sort by NCT in ascending order and join records with |. If the set of three articles cannot be found, output NONE.", + "oracle_answer": "NCT03277573~Salsalate~P1~Salsalate~P1~Salsalate|NCT03634007~AAVrh.10hAPOE2~P1~LX1001~P2~LX1001|NCT03748303~Allopregnanolone (Allo)~P1~Allopregnanolone~P1~Allopregnanolone|NCT04149860~Lu AF87908~P1~Lu AF87908~P1~Lu AF87908|NCT04451408~LY3372993~P1~LY3372993~P1~LY3372993|NCT04500847~Emtricitabine~P1~Emtricitabine~P1~Emtricitabine", + "metadata": { + "State-Gated Retrieval": [ + "Use only the Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline article as the baseline.", + "Retention in 2022 and 2023 must be determined by exact match on the ClinicalTrials.gov NCT identifier, not by drug name alone.", + "Keep only studies that are found under the same NCT in both 2022 and 2023, and output them sorted by NCT in ascending order." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2021, 2022, and 2023 pipeline reviews yield the 2021 Phase 1 baseline cohort and the later-year lookup tables", + "article tables yield exact ClinicalTrials.gov NCT IDs, yearly phase labels, and yearly drug names for the same study", + "final rows are produced only after 2021 baseline studies are re-identified in both later reviews by exact NCT matching" + ], + "control_dependency": [ + "continuation must be matched by exact NCT rather than by drug name, because drug names drift across years", + "2022 and 2023 lookups must use the fixed 2021 Phase 1 NCT set as the starting cohort rather than later-year table membership alone", + "yearly phase/name fields are only valid after the same NCT is confirmed across all three reviews" + ], + "freeze": { + "historical_window": "the 2021, 2022, and 2023 open-access Alzheimer's disease drug development pipeline reviews; the baseline is the 2021 Phase 1 cohort and continuation is matched by exact ClinicalTrials.gov NCT" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Use only the Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline article as the baseline.", + "Retention in 2022 and 2023 must be determined by exact match on the ClinicalTrials.gov NCT identifier, not by drug name alone.", + "Keep only studies that are found under the same NCT in both 2022 and 2023, and output them sorted by NCT in ascending order." + ], + "exclusion_conditions": [ + "Exclude results that are continued by drug name alone without an exact match on the same ClinicalTrials.gov identifier.", + "Exclude studies found only in 2022 or only in 2023, not continuously retained in both years.", + "Exclude studies not in the 2021 baseline Phase 1 set." + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "NCT", + "agent_2021", + "phase_2022", + "agent_2022", + "phase_2023", + "agent_2023" + ], + "NCT": "use the exact ClinicalTrials.gov identifier as the cross-year identity key", + "phase_fields": "normalize phases to P1, P2, or P3; if the same NCT appears multiple times in a year, keep the highest phase for that year", + "agent_fields": "keep the agent text as shown in each year-specific table", + "sorting_or_selection": "NCT ascending" + } + } +} diff --git a/data_en/constraint/europemc_003.json b/data_en/constraint/europemc_003.json new file mode 100644 index 0000000000000000000000000000000000000000..162ba5d05a975e984eea358cc4657ecbdc3bc3ca --- /dev/null +++ b/data_en/constraint/europemc_003.json @@ -0,0 +1,63 @@ +{ + "task_id": "europemc_003", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "I want to see which candidate molecules predicted in the 2023 \"Antibodies to Watch\" article as expected to submit their first marketing applications in 2022–2023 have actually been approved or entered first regulatory review in the 2024 installment of the same series.\nFollow the steps below. First, find the open-access full texts of both the 2023 and 2024 \"Antibodies to Watch\" articles in Europe PMC.\nThen, in the 2023 article, identify all candidate molecules listed as **\"expected to submit first marketing applications in 2022–2023\"**.\nNext, check each of these molecules against the 2024 article and retain only those that have been approved or have entered first regulatory review.\nFinally, format each qualifying molecule as follows:\nINN~2023 category~2023 prediction label~2024 status~2024 indication~2024 region\nwhere:\n\t•\t2023 category uses NC/CA for non-cancer/cancer;\n\t•\t2024 status uses A/R for first approval/first regulatory review.\nSort by INN alphabetically and output as a single line joined by |; if neither article is found, output NONE.", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "Finally, format each qualifying molecule as follows:\nINN~2023 category~2023 prediction label~2024 status~2024 indication~2024 region\nwhere:\n\t•\t2023 category uses NC/CA for non-cancer/cancer;\n\t•\t2024 status uses A/R for first approval/first regulatory review.\nSort by INN alphabetically and output as a single line joined by |; if neither article is found, output NONE.", + "oracle_answer": "Cosibelimab~CA~MAA,Q2 2023~R~Squamous cell carcinoma~US|Elranatamab~CA~2023~A~Multiple myeloma~US,EU,Switzerland,Brazil|Garadacimab~NC~BLA,2023~R~Hereditary angioedema~EU|Odronextamab~CA~BLA,H2 2022~R~Diffuse large B-cell lymphoma~US,EU|Pozelimab~NC~BLA,H2 2022~A~CHAPLE disease~US|Suciraslimab~NC~NDA,2023~R~Rheumatoid arthritis~China|Talquetamab~CA~2023–25~A~Multiple myeloma~US,EU,UK,Switzerland|Zolbetuximab~CA~BLA,2023~R~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China", + "metadata": { + "State-Gated Retrieval": [ + "First, identify all candidate molecules in the 2023 Antibodies to Watch article that are predicted to submit first marketing applications in 2022-2023.", + "Then, check each of these molecules against the 2024 article and retain only those that have been first approved or have entered first regulatory review.", + "The 2024 status must distinguish A=first approval from R=first regulatory review, and include the 2024 indication and region." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2023 Antibodies to Watch article yields the forecast baseline of candidates expected to file in 2022-2023", + "the 2024 article tables yield first-approval outcomes, first-regulatory-review outcomes, indications, and regions for the same INNs", + "final rows are produced only after Table 1 approvals and Table 2 first-review candidates are merged back onto the 2023 forecast cohort" + ], + "control_dependency": [ + "both 2024 Table 1 and Table 2 must be read so that first-review-but-not-yet-approved candidates are retained", + "2024 status coding must distinguish approval from first regulatory review instead of collapsing both into a single positive match", + "region and indication fields are valid only after the 2023 forecast cohort is reconciled against both 2024 tables" + ], + "freeze": { + "historical_window": "the 2023 and 2024 open-access Antibodies to Watch articles; baseline candidates come from the 2023 forecast set and 2024 outcomes come from current Table 1 plus Table 2" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "First, identify all candidate molecules in the 2023 Antibodies to Watch article that are predicted to submit first marketing applications in 2022-2023.", + "Then, check each of these molecules against the 2024 article and retain only those that have been first approved or have entered first regulatory review.", + "The 2024 status must distinguish A=first approval from R=first regulatory review, and include the 2024 indication and region." + ], + "exclusion_conditions": [ + "Exclude results that only check approvals in 2024 Table 1 without also consulting Table 2 for first regulatory review candidates.", + "Exclude molecules not in the 2023 forecast baseline.", + "Exclude candidates that were neither first approved nor entered first regulatory review in 2024." + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "INN", + "category_2023", + "prediction_label_2023", + "status_2024", + "indication_2024", + "region_2024" + ], + "category_2023": "emit `NC` or `CA` exactly", + "prediction_label_2023": "keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H2 2022`", + "status_2024": "emit `A` for first approval and `R` for first regulatory review", + "region_2024": "preserve the raw region string but remove spaces after commas, for example `US,EU`", + "sorting_or_selection": "INN alphabetical ascending" + } + } +} diff --git a/data_en/constraint/europemc_004.json b/data_en/constraint/europemc_004.json new file mode 100644 index 0000000000000000000000000000000000000000..a3b86b381362447b41668891aaa97dbdcb89b54e --- /dev/null +++ b/data_en/constraint/europemc_004.json @@ -0,0 +1,67 @@ +{ + "task_id": "europemc_004", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 9, + "instruction": "I am evaluating the accuracy of annual antibody drug watchlist predictions and want to trace whether the 2022 cohort of candidates from the Antibodies to Watch series simply experienced delays in development progress. I need you to use the Europe PMC database to systematically map the year-over-year status changes for these candidates.\n\nFirst, establish the literature baseline and initial candidate set. Precisely locate the three open-access full-text Antibodies to Watch articles published in 2022, 2023, and 2024 in Europe PMC. Once all three articles are found, identify a set of antibodies (INN) with a specific delay pattern: those that were explicitly listed in the 2022 article under a category such as \"expected to file soon\" (identified by INN, drug code, project name, or other recognizable name) but, due to slower progress, still remained as watchlist candidates in the 2023 article.\n\nSecond, determine the latest status of these consecutively delayed candidates. For the identified antibody group, ascertain their final status in the 2024 article: whether they finally received first approval, are in first regulatory review, remain on the 2024 watchlist, or have completely disappeared from the 2024 main article list.\n\nFinally, after completing the cross-year literature review and status confirmation, aggregate the extracted parameters into a specific formatted single-line record. If all three target articles cannot be found, output NONE. If all three are successfully located, concatenate the internal parameters for each qualifying antibody in the fixed order \"INN~2022 category~2022 phase~2023 prediction label~2024 status~2024 phase or NA~2024 indication or NA~2024 region or NA\". Then join all identified candidates in strict alphabetical order by INN using the \"|\" symbol into a single string with no spaces.", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "If all three target articles cannot be found, output NONE. If all three are successfully located, concatenate the internal parameters for each qualifying antibody in the fixed order \"INN~2022 category~2022 phase~2023 prediction label~2024 status~2024 phase or NA~2024 indication or NA~2024 region or NA\". Then, join all identified candidates in strict alphabetical order by INN using the \"|\" symbol into a single string with no spaces.", + "oracle_answer": "Apamistamab-I-131~CA~P3~BLA,H1 2023~F~P3~Ablation of bone marrow prior to transplantation in AML patients~NA|Bentracimab~NC~P3~BLA,Q4 2022~F~P3~Reversal of the antiplatelet effects of ticagrelor~NA|Cosibelimab~CA~P3~MAA,Q2 2023~R~NA~Squamous cell carcinoma~US|Erfonrilimab~CA~P3~NDA~F~P3~Pancreatic ductal adenocarcinoma~NA|Odronextamab~CA~P2~BLA,H2 2022~R~NA~Diffuse large B-cell lymphoma~US,EU|Talquetamab~CA~P2~2023-25~A~NA~Multiple myeloma~US,EU,UK,Switzerland|Tiragolumab~CA~P3~2023~F~P3~NSCLC~NA|Zanidatamab~CA~P2~2023~D~NA~NA~NA|Zolbetuximab~CA~P3~BLA,2023~R~NA~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China", + "metadata": { + "State-Gated Retrieval": [ + "Start with the 2022 Antibodies to Watch candidates listed as \"expected to file soon\", but retain only those molecules that still remain as watchlist candidates in the 2023 article of the same series.", + "For these consecutively delayed candidates, determine their final status in the 2024 article: first approved, in first regulatory review, or completely absent from Tables 1-4.", + "Name matching must handle the Apamistamab naming drift; complete absence in 2024 must be explicitly encoded as D." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2022, 2023, and 2024 Antibodies to Watch articles yield the 2022 soon-to-file baseline, 2023 carry-over membership, and 2024 status tables", + "article tables and full-text naming context yield name normalizations, 2024 table presence/absence, and final status labels for each carried-over INN", + "final rows are produced only after 2022 candidates are filtered by 2023 carry-over status and then resolved against 2024 Tables 1-4 plus explicit absence" + ], + "control_dependency": [ + "2022 candidates must first be filtered by 2023 carry-over status before they are matched against the 2024 tables", + "Apamistamab naming drift forces explicit normalization before 2024 lookup", + "complete 2024 absence must be emitted as D rather than treated as a lookup failure" + ], + "freeze": { + "historical_window": "the 2022, 2023, and 2024 open-access Antibodies to Watch articles; the 2022 baseline is filtered by 2023 carry-over status and then checked against 2024 Tables 1-4, with explicit absence retained as a status" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Start with the 2022 Antibodies to Watch candidates listed as \"expected to file soon\", but retain only those molecules that still remain as watchlist candidates in the 2023 article of the same series.", + "For these consecutively delayed candidates, determine their final status in the 2024 article: first approved, in first regulatory review, or completely absent from Tables 1-4.", + "Name matching must handle the Apamistamab naming drift; complete absence in 2024 must be explicitly encoded as D." + ], + "exclusion_conditions": [ + "Exclude results that directly match the 2022 baseline against 2024 without applying the 2023 carry-over filter.", + "Exclude matching results that do not handle the Apamistamab naming drift.", + "Exclude cases where complete 2024 absence is treated as a lookup failure rather than a status that must be output." + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "INN", + "category_2022", + "phase_2022", + "prediction_label_2023", + "status_2024", + "phase_or_NA_2024", + "indication_or_NA_2024", + "region_or_NA_2024" + ], + "category_2022": "emit `NC` or `CA` exactly", + "phase_2022": "normalize stage labels such as `Phase 3` to `P3` and `Pivotal Phase 2` to `P2`", + "prediction_label_2023": "keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H1 2023`", + "status_2024": "emit one of `A`, `R`, `F`, or `D` exactly", + "conditional_fields_2024": "if status is A or R, phase_or_NA_2024 must be `NA` and region_or_NA_2024 must carry the raw region string; if status is F, region_or_NA_2024 is `NA` and phase_or_NA_2024 carries the normalized phase; if status is D, all three trailing 2024 fields are `NA`", + "naming_exception": "preserve the fixed source exception around the Apamistamab-I-131 naming variant instead of over-normalizing the INN", + "sorting_or_selection": "INN alphabetical ascending" + } + } +} diff --git a/data_en/constraint/europemc_005.json b/data_en/constraint/europemc_005.json new file mode 100644 index 0000000000000000000000000000000000000000..59cb625209f71a1f49575dfb6a275ae7728317a4 --- /dev/null +++ b/data_en/constraint/europemc_005.json @@ -0,0 +1,69 @@ +{ + "task_id": "europemc_005", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 20, + "instruction": "I am compiling a cross-platform correspondence checklist for core predictors of COVID-19 hospitalization prognosis. Using the Europe PMC database, I need to work through the process of identifying the variables each specific model actually used, together with their matching attributes.\n\nFirst, establish the literature baseline. In Europe PMC, precisely locate the 2024 WHO global individual patient data validation paper and identify the four prognostic models that were successfully externally validated in low- and middle-income country data. Then trace back to the three original model papers corresponding to these four models.\n\nAfter locating these four target papers, the core task is to extract and verify the specific characteristics of the predictors. Determine which distinct admission variables each of the four models actually used in the evaluation. For each identified variable, clarify its acquisition pathway in the WHO platform baseline table: either a direct match under the same or a substantively equivalent name (marked as E), or a fixed mapped conversion (marked as M). Also trace the model-source attributes of these variables: whether they belong to the model with the strongest external validation performance (TopAUC), the model with calibration closest to the ideal (BestCal), or an original model that explicitly used dynamic data (Dyn).\n\nTo ensure consistent judgment criteria, model attribution, performance attribution, and variable conflicts must all be based on the verifiable model descriptions, performance summaries, and field definitions in the target papers. When the same concept has multiple naming or mapping methods, prioritize conservative mappings that maintain cross-model interpretability consistency, and flag mapping differences that may affect interpretability consistency.\n\nAfter completing the above literature tracing and variable characteristic extraction, finally extract these parameters to generate a formatted single-line summary record. For status flags, uniformly use 1 for yes and 0 for no for all boolean types. If the search fails to locate the one validation paper and the three original model papers, output NONE. If all are successfully located, after arranging all distinct variables strictly in alphabetical order by variable name, concatenate the parameters within each variable in the fixed order \"variable~category~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict\", then join all variables with \"|\" into a single string with no spaces.", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "If the search fails to locate the one validation paper and the three original model papers, output NONE. If all are successfully located, after arranging all distinct variables strictly in alphabetical order by variable name, concatenate the parameters within each variable in the fixed order \"variable~category~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict\", then join all variables with \"|\" into a single string with no spaces. For all boolean types, uniformly use 1 for yes and 0 for no.", + "oracle_answer": "Age~DEM~1~1~1~1~Age~E~1~1~1~0|Cancer~COM~0~0~1~0~Cancer~E~1~0~0~0|Chronic kidney disease~COM~0~0~0~1~CKD~M~0~0~0~1|Chronic lung disease~COM~0~0~1~0~Pulmonary disease~M~1~0~0~0|Chronic renal disease~COM~0~0~1~0~CKD~M~1~0~0~1|Coronary heart disease~COM~0~1~0~0~CHD~M~0~0~0~1|Cough~SYM~0~0~1~0~Cough~E~1~0~0~0|Diabetes mellitus~COM~0~0~1~0~Diabetes~M~1~0~0~0|Diarrhea~SYM~0~0~1~0~Diarrhea~E~1~0~0~0|Dyspnea~SYM~0~0~1~0~Dyspnea~E~1~0~0~0|Fever~VIT~0~0~0~1~Body temperature~M~0~0~0~0|Heart disease~COM~0~0~1~0~CHD~M~1~0~0~1|Hypertension~COM~0~1~1~0~Hypertension~E~1~0~0~0|Immunocompromised status~COM~0~0~1~0~Immunosuppression~M~1~0~0~0|O2 saturation~VIT~1~0~0~0~Oxygen saturation~M~0~1~1~0|Respiratory rate~VIT~1~0~0~1~Respiratory rate~E~0~1~1~0|Sex~DEM~0~0~1~0~Men~M~1~0~0~0|Smoking~DEM~1~0~0~0~Smoking~E~0~1~1~1|Smoking status~DEM~0~0~0~1~Smoking~M~0~0~0~1|Systolic blood pressure~VIT~0~0~0~1~Systolic blood pressure~E~0~0~0~0", + "metadata": { + "State-Gated Retrieval": [ + "First, in the 2024 WHO global individual patient data validation paper, identify the four prognostic models that were successfully externally validated in LMIC data, and trace back to the three corresponding original model papers.", + "For each predictor, retain the original wording from WHO Table 1, annotate its matching method (E/M) in the WHO baseline table, and indicate whether it comes from the TopAUC, BestCal, or Dyn model.", + "When encountering a predictor that was conceptually merged on the WHO side, trace back to the original Wang/Zhou papers to split it apart and then recalculate the relevant fields." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2024 WHO global validation paper yields the four externally validated models and the WHO-side predictor wording/mapping baseline", + "the three original model papers yield model-specific predictor wordings, dynamic-data flags, and conflicts hidden by WHO-side conceptual merging", + "final rows are produced only after WHO predictors are kept separate, traced back to the original papers, and then re-annotated for mapping and model provenance" + ], + "control_dependency": [ + "conceptually merged WHO predictors must be split back out when the original Wang/Zhou papers expose distinct variables", + "Table 2 mapping decisions are not valid until Table 1 wording and original-paper predictor sets are reconciled", + "TopAUC / BestCal / Dyn flags must be determined after the predictor split is applied correctly" + ], + "freeze": { + "historical_window": "the 2024 WHO global IPD validation paper and the three linked original COVID prognosis-model papers, using their current open-access full texts and tables" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "First, in the 2024 WHO global individual patient data validation paper, identify the four prognostic models that were successfully externally validated in LMIC data, and trace back to the three corresponding original model papers.", + "For each predictor, retain the original wording from WHO Table 1, annotate its matching method (E/M) in the WHO baseline table, and indicate whether it comes from the TopAUC, BestCal, or Dyn model.", + "When encountering a predictor that was conceptually merged on the WHO side, trace back to the original Wang/Zhou papers to split it apart and then recalculate the relevant fields." + ], + "exclusion_conditions": [ + "Exclude results that directly merged conceptually similar predictors after WHO Table 1 without tracing back to the original papers for splitting.", + "Exclude results that relied solely on loose mapping from WHO Table 2 without incorporating the original paper wording.", + "Exclude results that fixed TopAUC/BestCal/Dyn annotations before applying the predictor split correction." + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "variable", + "category", + "B", + "W", + "Zh", + "Zo", + "WHOfield", + "WHOx", + "TopAUC", + "BestCal", + "Dyn", + "Conflict" + ], + "variable_set": "the candidate variable set comes only from the WHO validation Table 1 and remains at the original 20 predictors", + "conflict_groups": "do not pre-merge the three source conflict groups `Smoking`/`Smoking status`, `Chronic renal disease`/`Chronic kidney disease`, and `Coronary heart disease`/`Heart disease` before applying the conflict flag", + "boolean_fields": "B, W, Zh, Zo, TopAUC, BestCal, Dyn, and Conflict are emitted as 1 or 0 only", + "WHOx": "emit `E` for exact WHO matches or direct matches under a substantively equivalent name, `M` for the fixed mapped match, and `NA` when no WHO field matches", + "sorting_or_selection": "variable name alphabetical ascending" + } + } +} diff --git a/data_en/constraint/genome_001.json b/data_en/constraint/genome_001.json new file mode 100644 index 0000000000000000000000000000000000000000..eaeed5a56897c15c7004ded30c681446db2ff1e4 --- /dev/null +++ b/data_en/constraint/genome_001.json @@ -0,0 +1,64 @@ +{ + "task_id": "genome_001", + "domain": "KEGG_BRITE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "I am compiling a reference list of medications for ulcerative colitis for in-hospital use. From the immunosuppressants cataloged in KEGG, I want to select those drug entries that have been approved in Japan by the end of June 2025 and that carry explicit CYP-related metabolism information or CYP inhibition indications. Please proceed in the following order: first, within the scope of KEGG immunosuppressants for ulcerative colitis, screen for drug entries approved in Japan by the end of June 2025; then check whether each entry has explicit CYP-related metabolism information or CYP inhibition indications, retaining only qualifying entries. Next, record each entry's Japanese therapeutic classification code, ATC code, corresponding target branch, and Japan first approval date. Finally, output a single-line string sorted by Japan first approval date from earliest to latest, in the format ||||; separate entries with commas; if no qualifying entries exist, output NONE.", + "start_url": "https://www.genome.jp/kegg/brite.html", + "output_format": "Output a single-line string sorted by Japan first approval date from earliest to latest, in the format ||||; separate entries with commas; if no qualifying entries exist, output NONE.", + "oracle_answer": "D09783|3999|L04AF01|JAK1/JAK2/JAK3/TYK2|2013/3/25,D11048|3999|L04AF03|JAK1|2020/1/23,D10931|2399|L04AE05|S1PR1/S1PR4/S1PR5|2025/6/24", + "metadata": { + "State-Gated Retrieval": [ + "Within the scope of KEGG immunosuppressants for ulcerative colitis, retain only entries approved in Japan by 2025-06-30 and that carry explicit CYP-related metabolism information or CYP inhibition indications.", + "Candidate drugs must be re-verified against the corrected UC drug list for Japanese therapeutic classification, ATC, target branch, CYP evidence, and Japan first approval date.", + "Finally, output sorted by Japan first approval date from earliest to latest." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "KEGG disease H01466 and linked drug entries yield the ulcerative-colitis immunosuppressant candidate set", + "each candidate drug entry yields Japanese class, ATC, target branch, CYP metabolism/inhibition evidence, and Japan approval date", + "final rows are produced only after the full UC candidate set is determined and every candidate is checked against CYP evidence and PMDA timing" + ], + "control_dependency": [ + "the candidate set must include Japanese class 3999 UC drugs when the disease page exposes them rather than being limited to 2399 alone", + "target / CYP / PMDA validation must be applied across the full candidate set rather than only the old 2399 subset", + "entries without explicit CYP evidence may be dropped only after the full candidate set has been established" + ], + "freeze": { + "historical_window": "KEGG ulcerative-colitis drug candidates with Japan approvals on or before 2025-06-30; current drug-entry annotations provide target, CYP, and Japan-class metadata" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Within the scope of KEGG immunosuppressants for ulcerative colitis, retain only entries approved in Japan by 2025-06-30 and that carry explicit CYP-related metabolism information or CYP inhibition indications.", + "Candidate drugs must be re-verified against the corrected UC drug list for Japanese therapeutic classification, ATC, target branch, CYP evidence, and Japan first approval date.", + "Finally, output sorted by Japan first approval date from earliest to latest." + ], + "exclusion_conditions": [ + "Exclude results that incorrectly lock the upstream scope to the 2399 digestive branch without falling back to the full UC drug list.", + "Exclude entries without explicit CYP-related metabolism information or CYP inhibition indications.", + "Exclude entries with a Japan approval date after 2025-06-30 or that are not within the KEGG UC immunosuppressant scope." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DRUG_ID", + "JP_class", + "ATC", + "Target_branch", + "JP_date" + ], + "dedup_key": "DRUG_ID", + "JP_date": "use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value", + "Target_branch": "emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`", + "sorting_or_selection": { + "primary": "JP_date ascending", + "secondary": "DRUG_ID ascending" + } + } + } +} diff --git a/data_en/constraint/genome_002.json b/data_en/constraint/genome_002.json new file mode 100644 index 0000000000000000000000000000000000000000..537ddaa4a4a9a8b184ff335139e5f28d2fd89308 --- /dev/null +++ b/data_en/constraint/genome_002.json @@ -0,0 +1,65 @@ +{ + "task_id": "genome_002", + "domain": "KEGG_GENOME", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am preparing a lecture page on classic animal endosymbiosis cases and want to find, among KEGG's host-symbiont examples, the case that meets the following conditions: it was already recorded by the end of 2005, its bacterial symbiont genome contains named extra replicons, and the names of those replicons directly correspond to amino acid synthesis modules on the host-symbiont joint pathway map. Process in the following order: first, among KEGG's host-symbiont examples, select those combinations whose bacterial symbiont KEGG GENOME entry has a Created year on or before 2005; then retain cases where the bacterial symbiont genome carries named extra replicons; next, verify that the replicon names directly correspond to amino acid synthesis modules on the host-symbiont joint pathway map; finally, within the joint pathway map for that host-symbiont combination, list all qualifying pathway-module pairs for that case and output a single-line string: ||||| (sorted by pathway ID in ascending order, separated by commas; output NONE if no qualifying items exist).", + "start_url": "https://www.genome.jp/kegg/genome/", + "output_format": "Output a single-line string: ||||| (sorted by pathway ID in ascending order, separated by commas; output NONE if no qualifying items exist).", + "oracle_answer": "api+buc|buc|00290|M00432|pLeu|2000,api+buc|buc|00400|M00023|pTrp|2000", + "metadata": { + "State-Gated Retrieval": [ + "Retain only those host-symbiont examples where the bacterial symbiont KEGG GENOME Created year is on or before 2005 and the genome carries named extra replicons.", + "The replicon names must directly correspond to amino acid synthesis modules on the host-symbiont joint pathway page.", + "Finally, output all qualifying pathway-module-replicon records from the surviving case, sorted by pathway ID in ascending order." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "KEGG host-symbiont examples and symbiont genome pages yield the pre-2006 candidate pairs and named extra replicons", + "Joint pathway maps, module pages, and genome annotations yield the pathway-module-replicon links attributable to the symbiont side", + "Final rows are produced only after the surviving host-symbiont pair is validated against both replicon existence and module support on the joint pathway page" + ], + "control_dependency": [ + "Only branches satisfying the named-plasmid requirement may be retained, so the bmy+wbm branch must be excluded when the wbm genome page fails that requirement", + "Module retrieval must use the api+buc pathway state and the 00400 view, because that view is the one that actually exposes M00023", + "Module support is valid only after symbiont-side evidence for both M00023 and M00432 is validated in the selected pathway state" + ], + "freeze": { + "historical_window": "KEGG host-symbiont examples whose symbiont GENOME Created year is on or before 2005; current joint pathway, module, and genome replicon annotations" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only those host-symbiont examples where the bacterial symbiont KEGG GENOME Created year is on or before 2005 and the genome carries named extra replicons.", + "The replicon names must directly correspond to amino acid synthesis modules on the host-symbiont joint pathway page.", + "Finally, output all qualifying pathway-module-replicon records from the surviving case, sorted by pathway ID in ascending order." + ], + "exclusion_conditions": [ + "Exclude cases like bmy+wbm where the symbiont genome page does not satisfy the named-plasmid requirement.", + "Exclude results that only follow pathway names along pages such as 00380 without returning to the joint pathway page to verify module evidence.", + "Exclude records where the relationship between replicon name and module cannot be directly established on the joint pathway map." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "group", + "symbiont", + "pathway", + "module", + "replicon", + "created_year" + ], + "group": "Use the canonical host-symbiont group label from the source workflow, such as `api+buc`", + "symbiont": "Use the bare lowercase KEGG organism code", + "pathway": "Emit the numeric KEGG pathway ID without a `map` prefix", + "module": "Normalize the KEGG module identifier to the `Mxxxxx` form", + "replicon": "Preserve the named extra replicon exactly as displayed in the source, such as `pLeu` or `pTrp`", + "created_year": "Emit the four-digit created year", + "sorting_or_selection": "Pathway numeric ascending" + } + } +} diff --git a/data_en/constraint/genome_003.json b/data_en/constraint/genome_003.json new file mode 100644 index 0000000000000000000000000000000000000000..2762c14f63aeacf2f9f2de3b6bbcc1c57f8756d4 --- /dev/null +++ b/data_en/constraint/genome_003.json @@ -0,0 +1,64 @@ +{ + "task_id": "genome_003", + "domain": "KEGG_BRITE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "I am compiling a table of the approval order of systemic drugs for plaque psoriasis in Japan. Process as follows: first, within the scope of systemic drugs for plaque psoriasis approved in Japan by the end of 2024, identify the active ingredients that act on the IL-17/IL-23 signaling axis; then exclude all topical drugs and systemic drugs acting on other axes. Next, sort these active ingredients by their first approval date in Japan from earliest to latest; if approved on the same day, sort by DRUG_ID in ascending order. Finally, output a multi-row table with each row formatted as ||||.", + "start_url": "https://www.kegg.jp/brite/br08301", + "output_format": "Output a multi-row table with each row formatted as ||||.", + "oracle_answer": "D09967|Secukinumab|L04AC10|IL17A|2014/12/26\nD10061|Brodalumab|L04AC12|IL17RA|2016/7/4\nD10071|Ixekizumab|L04AC13|IL17A|2016/7/4\nD10438|Guselkumab|L04AC16|IL23A|2018/3/23\nD11052|Risankizumab|L04AC18|IL23A|2019/3/26\nD10400|Tildrakizumab|L04AC17|IL23A|2020/6/29\nD11550|Bimekizumab|L04AC21|IL17A/IL17F|2022/1/20\nD11817|Deucravacitinib|L04AF07|TYK2|2022/9/26", + "metadata": { + "State-Gated Retrieval": [ + "Retain only the active ingredients that truly act on the IL-17/IL-23 signaling axis among systemic drugs for plaque psoriasis approved in Japan by 2024-12-31.", + "The candidate set must cover the ligand side, receptor side, and TYK2 kinase side, not just the interleukin ligand side.", + "Sort final entries by Japan first approval date in ascending order; if on the same day, sort by DRUG_ID in ascending order." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "KEGG disease/drug entry points yield the Japan-approved systemic plaque-psoriasis drug cohort through 2024-12-31", + "each drug entry yields target branch, ATC, systemic-use validity, and Japan approval date for IL-17/IL-23-axis candidates", + "final rows are produced only after ligand-side, receptor-side, and kinase-side candidates are jointly reconciled and re-sorted by Japan approval date" + ], + "control_dependency": [ + "entry-point coverage must include receptor-side IL17RA and kinase-side TYK2 mechanisms when downstream drug pages expose them, rather than staying ligand-only", + "Ustekinumab must be removed only when target interpretation shows IL12 + IL23A rather than the IL-17/IL-23-axis criterion required here", + "systemic-use, Japanese 3999, and PMDA-date filtering must be applied after each expansion of the candidate set rather than attached to the earlier ligand-only state" + ], + "freeze": { + "historical_window": "Japanese plaque-psoriasis systemic drugs approved on or before 2024-12-31; current KEGG drug-entry annotations supply target branches and Japan approval dates" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only the active ingredients that truly act on the IL-17/IL-23 signaling axis among systemic drugs for plaque psoriasis approved in Japan by 2024-12-31.", + "The candidate set must cover the ligand side, receptor side, and TYK2 kinase side, not just the interleukin ligand side.", + "Sort final entries by Japan first approval date in ascending order; if on the same day, sort by DRUG_ID in ascending order." + ], + "exclusion_conditions": [ + "Exclude topical drugs, non-systemic drugs, or entries outside the specified historical freeze window.", + "Exclude entries such as Ustekinumab whose actual target is IL12 + IL23A and which do not meet the IL-17/IL-23 axis criterion required here.", + "Exclude results that miss Brodalumab or Deucravacitinib due to looking only at the ligand side." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "DRUG_ID", + "Name", + "ATC", + "Target_branch", + "PMDA_date" + ], + "PMDA_date": "use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value", + "Target_branch": "emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`", + "sorting_or_selection": { + "primary": "PMDA_date ascending", + "secondary": "DRUG_ID ascending" + } + } + } +} diff --git a/data_en/constraint/genome_004.json b/data_en/constraint/genome_004.json new file mode 100644 index 0000000000000000000000000000000000000000..dfad79167638b7cce4b9f109db80e552a97baec7 --- /dev/null +++ b/data_en/constraint/genome_004.json @@ -0,0 +1,78 @@ +{ + "task_id": "genome_004", + "domain": "KEGG_GENOME", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am preparing a handout for a primate evolution course and want to summarize, in a two-row comparison table, the anomalous pattern behind why this lineage must obtain vitamin C from the diet. Among primate genome entries established by the end of 2022, identify the anomalous lower-level clade in which the upstream glucuronate module M00014 is still retained but the animal-type vitamin C biosynthesis module M00129 has been lost. Then verify the corresponding sister branch and confirm that it still retains M00129. Finally, output a two-row comparison table with columns rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year. The first row should be EXCEPTION_CLADE and the second row RETAINED_SISTER_CLADE. In all rows, vitamin_c_synthesis_module is fixed as M00129; vitamin_c_module_status should be LOST for the first row and RETAINED for the second. Use KEGG organism codes for the example species.", + "start_url": "https://www.genome.jp/kegg/kegg2.html", + "output_format": "Output a two-row comparison table with columns rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year.", + "oracle_answer": "1|EXCEPTION_CLADE|Primates|Haplorrhini|map00053|map00040|M00014|M00129|LOST|csyr|2022\n2|RETAINED_SISTER_CLADE|Primates|Strepsirrhini|map00053|map00040|M00014|M00129|RETAINED|oga|2022", + "metadata": { + "State-Gated Retrieval": [ + "Search only among primate genome entries established by the end of 2022, and isolate the anomalous lower-level clade that retains the upstream glucuronate module M00014 but lacks the animal-type vitamin C biosynthesis module M00129.", + "That anomalous clade must be paired with a sister branch under the same higher-level split, and the sister branch must still retain M00129.", + "The final output must place the anomalous branch and the retained sister branch into a two-row comparison table, including the required pathway, module, and example-species fields." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the KEGG primate clade pages and genome entries yield candidate subclades and example species established through the cutoff year", + "the pathway and module views yield M00014 and M00129 presence/absence evidence for the exception clade and its sister branch", + "final rows are produced only after the exception clade and retained sister branch are jointly validated under the same parent split and paired with example organisms" + ], + "control_dependency": [ + "the exception clade remains provisional until both the sister-branch contrast and the example-species checks succeed", + "the comparison view must make retained M00014 and missing M00129 visible together", + "the two output rows are emitted together only after the exception clade and retained sister branch are fixed under the same parent split" + ], + "freeze": { + "historical_window": "primate genome entries established on or before 2022, with current KEGG clade, pathway, and module pages used as relatively stable reference information for comparing retained M00014 against lost M00129" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Search only among primate genome entries established by the end of 2022, and isolate the anomalous lower-level clade that retains the upstream glucuronate module M00014 but lacks the animal-type vitamin C biosynthesis module M00129.", + "That anomalous clade must have a contrastable sister branch, and that sister branch must still retain M00129.", + "The final output must place the anomalous branch and the retained sister branch into a two-row comparison table, including the required pathway, module, and example-species fields." + ], + "exclusion_conditions": [ + "Exclude results that stop at Simiiformes without checking the broader boundary and therefore miss Haplorrhini.", + "Exclude pathway views that do not make the M00014 versus M00129 contrast visible together.", + "Exclude candidate clades that have not been validated against a retained sister branch." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "clade_role", + "parent_clade", + "clade", + "anomaly_pathway", + "contrast_pathway", + "retained_upstream_module", + "vitamin_c_synthesis_module", + "vitamin_c_module_status", + "example_org", + "cutoff_year" + ], + "rank": "emit 1 for EXCEPTION_CLADE and 2 for RETAINED_SISTER_CLADE", + "clade_role": [ + "EXCEPTION_CLADE", + "RETAINED_SISTER_CLADE" + ], + "pathway_normalization": "emit KEGG pathway ids with the map prefix", + "module_normalization": "emit KEGG module ids with the leading M", + "vitamin_c_module_status": [ + "LOST", + "RETAINED" + ], + "organism_code": "use bare KEGG organism codes in lowercase, not species names", + "cutoff_year": "use a four-digit year; this task is frozen at 2022", + "sorting_or_selection": "emit rows in the fixed order EXCEPTION_CLADE then RETAINED_SISTER_CLADE" + } + } +} diff --git a/data_en/constraint/nvd_001.json b/data_en/constraint/nvd_001.json new file mode 100644 index 0000000000000000000000000000000000000000..f15a714ef5f5d5106c2d93b8bcbb25e842f281aa --- /dev/null +++ b/data_en/constraint/nvd_001.json @@ -0,0 +1,66 @@ +{ + "task_id": "nvd_001", + "domain": "NVD", + "autonomy_type": "ordered table", + "instruction": "We are cleaning up a batch of old SBOM matching rules for the Duplicator product line. Some rules still rely on legacy vendor lineage and outdated product labeling, so we need to identify Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator but can still be traced back to snapcreek:duplicator in the deprecated vendor chain. Search NVD records for Duplicator-related CVEs published from 2018-01-01 through 2024-12-31. Retain only CVEs that satisfy all of the following conditions in Change History: the Initial Analysis is not yet lite or lite+pro; the first change to lite or lite+pro occurs in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurs on 2026-02-02. Exclude CVEs whose Initial Analysis already contained lite/lite+pro, as well as records that lack the required vendor-remap event or do not belong to the Duplicator product line. Finally, output a single-line ordered table with columns: CVE | lite_upper_version | lite_vs_lite+pro | analysis_event@date | snapcreek_to_awesomemotive@date.", + "start_url": "https://nvd.nist.gov/vuln/search#/nvd/home?resultType=records", + "output_format": "Output a single-line ordered table with columns: CVE | lite_upper_version | lite_vs_lite+pro | analysis_event@date | snapcreek_to_awesomemotive@date. Join rows with commas and sort by NVD published date ascending, then by CVE ascending.", + "oracle_output_cardinality": 3, + "oracle_answer": "CVE:2018-7543|1.2.32|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2018-17207|1.2.42|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2020-11738|1.3.28|lite+pro|ModifiedAnalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02", + "metadata": { + "State-Gated Retrieval": [ + "Retain only Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator and that can be traced back to snapcreek:duplicator in the deprecated old vendor chain.", + "Each candidate CVE must simultaneously satisfy the following in its Change History: the Initial Analysis is not yet lite/lite+pro; the first change to lite or lite+pro occurs in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurs on 2026-02-02.", + "The final output retains only CVE rows that satisfy all three conditions above." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "NVD product/CPE search pages yield the current awesomemotive:duplicator family and the deprecated snapcreek:duplicator lineage", + "each target CVE detail page and Change History yield the Initial Analysis state, the first lite/lite+pro analysis event, and the 2026-02-02 vendor-remap event", + "final rows are produced only after candidate CVEs are intersected on both snapcreek -> awesomemotive migration and later introduction of lite/lite+pro in NIST analysis history" + ], + "control_dependency": [ + "the search must include the deprecated snapcreek lineage rather than only the current product state", + "vendor migration alone is insufficient until detail-level history confirms that lite/lite+pro was introduced after Initial Analysis", + "candidate CVEs must be filtered against the full change-history chronology, excluding any whose Initial Analysis already contained lite" + ], + "freeze": { + "historical_window": "Duplicator CVEs published from 2018-01-01 through 2024-12-31, evaluated against NVD analysis history up to the 2026-02-02 snapcreek -> awesomemotive vendor-remap events" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator and that can be traced back to snapcreek:duplicator in the deprecated old vendor chain.", + "Each candidate CVE must simultaneously satisfy the following in its Change History: the Initial Analysis is not yet lite/lite+pro; the first change to lite or lite+pro occurs in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurs on 2026-02-02.", + "The final output retains only CVE rows that satisfy all three conditions above." + ], + "exclusion_conditions": [ + "Exclude results that only look at the current description or current product state without falling back to the deprecated snapcreek chain and Change History.", + "Exclude CVEs whose Initial Analysis was already lite/lite+pro.", + "Exclude records without a 2026-02-02 vendor remap, or that do not belong to the Duplicator product line." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema_note": "the checked oracle rowset uses the Duplicator CVE schema below, and normalization follows that verified schema throughout this task", + "schema": [ + "CVE", + "lite_upper_version", + "lite_vs_lite+pro", + "analysis_event@date", + "snapcreek_to_awesomemotive@date" + ], + "CVE": "emit the identifier in the canonical `CVE:YYYY-NNNN` form used by the oracle", + "lite_vs_lite+pro": "emit `lite` or `lite+pro` exactly", + "analysis_event@date": "emit `Reanalysis@YYYY-MM-DD` or `ModifiedAnalysis@YYYY-MM-DD` exactly as supported by the source record", + "snapcreek_to_awesomemotive@date": "emit the ownership-transfer event as `snapcreek->awesomemotive@YYYY-MM-DD`", + "sorting_or_selection": { + "primary": "NVD published date ascending", + "secondary": "CVE ascending" + } + } + } +} diff --git a/data_en/constraint/nvd_002.json b/data_en/constraint/nvd_002.json new file mode 100644 index 0000000000000000000000000000000000000000..5d687e2c85cac80018d0ddeba91fb0f85b5035f1 --- /dev/null +++ b/data_en/constraint/nvd_002.json @@ -0,0 +1,62 @@ +{ + "task_id": "nvd_002", + "instruction": "Identify which CPE 2.3 product identifiers using the legacy vendor name mysql:mysql within the MySQL 5.1 branch were explicitly migrated by NIST to the corresponding oracle:mysql CPE 2.3 product identifiers in the NVD (National Vulnerability Database) records for the four InnoDB denial-of-service vulnerabilities CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680. Migration here refers only to the vendor field in the CPE changing from the old vendor mysql to the new vendor oracle; it does not include cases where the identifier remains under the old vendor name and only version aliases are normalized. Retain only entries from the MySQL 5.1 branch that meet this criterion. Exclude entries from the MySQL 5.0 branch, as well as all entries that did not undergo a vendor migration and only had internal version-alias normalization under the old vendor. Output a multi-row ordered table with columns version_update | legacy_cpe | current_cpe | remap_time_nvd, sorted by numeric version in ascending order; within the same version, entries without an update suffix come before entries with an update suffix.", + "domain": "NVD", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 44, + "start_url": "https://nvd.nist.gov/products/cpe/search", + "output_format": "Output a multi-row ordered table with columns version_update | legacy_cpe | current_cpe | remap_time_nvd, sorted by numeric version in ascending order; within the same version, entries without an update suffix come before entries with an update suffix.", + "oracle_answer": "version_update|legacy_cpe|current_cpe|remap_time_nvd\n5.1.1|cpe:2.3:a:mysql:mysql:5.1.1:::::::*|cpe:2.3:a:oracle:mysql:5.1.1:::::::*|2019-12-17 15:04:33\n5.1.2|cpe:2.3:a:mysql:mysql:5.1.2:::::::*|cpe:2.3:a:oracle:mysql:5.1.2:::::::*|2019-12-17 15:04:39\n5.1.3|cpe:2.3:a:mysql:mysql:5.1.3:::::::*|cpe:2.3:a:oracle:mysql:5.1.3:::::::*|2019-12-17 15:04:46\n5.1.4|cpe:2.3:a:mysql:mysql:5.1.4:::::::*|cpe:2.3:a:oracle:mysql:5.1.4:::::::*|2019-12-17 15:04:53\n5.1.10|cpe:2.3:a:mysql:mysql:5.1.10:::::::*|cpe:2.3:a:oracle:mysql:5.1.10:::::::*|2019-12-17 15:05:30\n5.1.11|cpe:2.3:a:mysql:mysql:5.1.11:::::::*|cpe:2.3:a:oracle:mysql:5.1.11:::::::*|2019-12-17 15:05:37\n5.1.12|cpe:2.3:a:mysql:mysql:5.1.12:::::::*|cpe:2.3:a:oracle:mysql:5.1.12:::::::*|2019-12-17 15:05:45\n5.1.13|cpe:2.3:a:mysql:mysql:5.1.13:::::::*|cpe:2.3:a:oracle:mysql:5.1.13:::::::*|2019-12-17 15:05:52\n5.1.14|cpe:2.3:a:mysql:mysql:5.1.14:::::::*|cpe:2.3:a:oracle:mysql:5.1.14:::::::*|2019-12-17 15:05:59\n5.1.15|cpe:2.3:a:mysql:mysql:5.1.15:::::::*|cpe:2.3:a:oracle:mysql:5.1.15:::::::*|2019-12-17 15:06:07\n5.1.16|cpe:2.3:a:mysql:mysql:5.1.16:::::::*|cpe:2.3:a:oracle:mysql:5.1.16:::::::*|2019-12-17 15:06:14\n5.1.17|cpe:2.3:a:mysql:mysql:5.1.17:::::::*|cpe:2.3:a:oracle:mysql:5.1.17:::::::*|2019-12-17 15:06:21\n5.1.18|cpe:2.3:a:mysql:mysql:5.1.18:::::::*|cpe:2.3:a:oracle:mysql:5.1.18:::::::*|2019-12-17 15:06:27\n5.1.19|cpe:2.3:a:mysql:mysql:5.1.19:::::::*|cpe:2.3:a:oracle:mysql:5.1.19:::::::*|2019-12-17 15:06:34\n5.1.20|cpe:2.3:a:mysql:mysql:5.1.20:::::::*|cpe:2.3:a:oracle:mysql:5.1.20:::::::*|2019-12-17 15:06:42\n5.1.21|cpe:2.3:a:mysql:mysql:5.1.21:::::::*|cpe:2.3:a:oracle:mysql:5.1.21:::::::*|2019-12-17 15:06:50\n5.1.22|cpe:2.3:a:mysql:mysql:5.1.22:::::::*|cpe:2.3:a:oracle:mysql:5.1.22:::::::*|2019-12-17 15:06:56\n5.1.23:a|cpe:2.3:a:mysql:mysql:5.1.23:a::::::|cpe:2.3:a:oracle:mysql:5.1.23:a::::::|2019-12-17 15:23:28\n5.1.24|cpe:2.3:a:mysql:mysql:5.1.24:::::::*|cpe:2.3:a:oracle:mysql:5.1.24:::::::*|2019-12-17 15:07:03\n5.1.25|cpe:2.3:a:mysql:mysql:5.1.25:::::::*|cpe:2.3:a:oracle:mysql:5.1.25:::::::*|2019-12-17 15:07:10\n5.1.26|cpe:2.3:a:mysql:mysql:5.1.26:::::::*|cpe:2.3:a:oracle:mysql:5.1.26:::::::*|2019-12-17 15:07:17\n5.1.27|cpe:2.3:a:mysql:mysql:5.1.27:::::::*|cpe:2.3:a:oracle:mysql:5.1.27:::::::*|2019-12-17 15:07:24\n5.1.28|cpe:2.3:a:mysql:mysql:5.1.28:::::::*|cpe:2.3:a:oracle:mysql:5.1.28:::::::*|2019-12-17 15:07:31\n5.1.29|cpe:2.3:a:mysql:mysql:5.1.29:::::::*|cpe:2.3:a:oracle:mysql:5.1.29:::::::*|2019-12-17 15:07:38\n5.1.30|cpe:2.3:a:mysql:mysql:5.1.30:::::::*|cpe:2.3:a:oracle:mysql:5.1.30:::::::*|2019-12-17 15:07:46\n5.1.31:sp1|cpe:2.3:a:mysql:mysql:5.1.31:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.31:sp1::::::|2019-12-17 15:23:35\n5.1.33|cpe:2.3:a:mysql:mysql:5.1.33:::::::*|cpe:2.3:a:oracle:mysql:5.1.33:::::::*|2019-12-17 15:07:55\n5.1.34:sp1|cpe:2.3:a:mysql:mysql:5.1.34:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.34:sp1::::::|2019-12-17 15:23:42\n5.1.35|cpe:2.3:a:mysql:mysql:5.1.35:::::::*|cpe:2.3:a:oracle:mysql:5.1.35:::::::*|2019-12-17 15:08:03\n5.1.36|cpe:2.3:a:mysql:mysql:5.1.36:::::::*|cpe:2.3:a:oracle:mysql:5.1.36:::::::*|2019-12-17 15:08:10\n5.1.37:sp1|cpe:2.3:a:mysql:mysql:5.1.37:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.37:sp1::::::|2019-12-17 15:23:49\n5.1.38|cpe:2.3:a:mysql:mysql:5.1.38:::::::*|cpe:2.3:a:oracle:mysql:5.1.38:::::::*|2019-12-17 15:08:17\n5.1.39|cpe:2.3:a:mysql:mysql:5.1.39:::::::*|cpe:2.3:a:oracle:mysql:5.1.39:::::::*|2019-12-17 10:22:31\n5.1.40|cpe:2.3:a:mysql:mysql:5.1.40:::::::*|cpe:2.3:a:oracle:mysql:5.1.40:::::::*|2019-12-17 10:22:46\n5.1.40:sp1|cpe:2.3:a:mysql:mysql:5.1.40:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.40:sp1::::::|2019-12-17 10:22:39\n5.1.41|cpe:2.3:a:mysql:mysql:5.1.41:::::::*|cpe:2.3:a:oracle:mysql:5.1.41:::::::*|2019-12-17 10:22:52\n5.1.42|cpe:2.3:a:mysql:mysql:5.1.42:::::::*|cpe:2.3:a:oracle:mysql:5.1.42:::::::*|2019-12-17 10:22:59\n5.1.43|cpe:2.3:a:mysql:mysql:5.1.43:::::::*|cpe:2.3:a:oracle:mysql:5.1.43:::::::*|2019-12-17 10:23:06\n5.1.43:sp1|cpe:2.3:a:mysql:mysql:5.1.43:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.43:sp1::::::|2019-12-17 10:23:11\n5.1.44|cpe:2.3:a:mysql:mysql:5.1.44:::::::*|cpe:2.3:a:oracle:mysql:5.1.44:::::::*|2019-12-17 10:23:17\n5.1.45|cpe:2.3:a:mysql:mysql:5.1.45:::::::*|cpe:2.3:a:oracle:mysql:5.1.45:::::::*|2019-12-17 10:23:24\n5.1.46|cpe:2.3:a:mysql:mysql:5.1.46:::::::*|cpe:2.3:a:oracle:mysql:5.1.46:::::::*|2019-12-17 10:23:38\n5.1.46:sp1|cpe:2.3:a:mysql:mysql:5.1.46:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.46:sp1::::::|2019-12-17 10:23:31\n5.1.47|cpe:2.3:a:mysql:mysql:5.1.47:::::::*|cpe:2.3:a:oracle:mysql:5.1.47:::::::*|2019-12-17 10:23:45", + "metadata": { + "State-Gated Retrieval": [ + "Retain only CPE 2.3 entries from the MySQL 5.1 branch for which the NVD Change History of all four vulnerabilities CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680 clearly shows a mysql:mysql -> oracle:mysql vendor migration.", + "Every result must provide version_update, legacy_cpe, current_cpe, and remap_time_nvd.", + "Within the same version, entries without an update suffix come before entries with an update suffix, and output is sorted by numeric version in ascending order." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Current and deprecated MySQL 5.1 CPE search results yield candidate legacy/current CPE strings.", + "The four target CVE pages and their Change History entries yield vendor-migration evidence, exact version_update strings, and remap timestamps.", + "Final rows are produced only after taking the common mysql:mysql 5.1 -> oracle:mysql 5.1 migrations across all four CVEs and removing alias-only or 5.0 entries." + ], + "control_dependency": [ + "Legacy vendor mapping must be determined from Analysis Description plus Change History rather than from the current description/current CPE view.", + "Include-deprecated results cannot be accepted wholesale because alias-only remaps must be filtered out.", + "5.1-branch membership and sort order must be determined after the vendor-migration filter removes 5.0 and non-migration rows." + ], + "freeze": { + "historical_window": "The MySQL 5.1 branches visible in CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680, restricted to explicit mysql:mysql -> oracle:mysql vendor-migration events." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only CPE 2.3 entries from the MySQL 5.1 branch for which the NVD Change History of all four vulnerabilities CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680 clearly shows a mysql:mysql -> oracle:mysql vendor migration.", + "Every result must provide version_update, legacy_cpe, current_cpe, and remap_time_nvd.", + "Within the same version, entries without an update suffix come before entries with an update suffix, and output is sorted by numeric version in ascending order." + ], + "exclusion_conditions": [ + "Exclude entries from the MySQL 5.0 branch.", + "Exclude entries that remain under the old vendor mysql:mysql, only have internal version-alias normalization, and did not undergo a vendor migration.", + "Exclude results that are read only from the current Oracle MySQL 5.1 CPE state without using legacy mapping and Change History." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row `version_update|legacy_cpe|current_cpe|remap_time_nvd`", + "schema": [ + "version_update", + "legacy_cpe", + "current_cpe", + "remap_time_nvd" + ], + "version_update": "sort by numeric MySQL version ascending; within the same base version, the empty update comes before any non-empty update suffix", + "legacy_cpe": "preserve the exact legacy CPE 2.3 string", + "current_cpe": "preserve the exact current CPE 2.3 string", + "remap_time_nvd": "emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form", + "dedup_key": "(legacy_cpe, current_cpe)" + } + } +} diff --git a/data_en/constraint/nvd_003.json b/data_en/constraint/nvd_003.json new file mode 100644 index 0000000000000000000000000000000000000000..e35a01f57543b050e55fffaf56d9527d82c201bb --- /dev/null +++ b/data_en/constraint/nvd_003.json @@ -0,0 +1,114 @@ +{ + "task_id": "nvd_003", + "domain": "NVD", + "autonomy_type": "ordered table", + "instruction": "We are cleaning up a batch of old SBOM matching rules that still represent Apache Tomcat 9.0.0 pre-release milestone versions using the legacy CPE form 9.0.0.Mx. We need to identify which milestone versions satisfy both of the following conditions: (1) they appear in the current NVD affected-product version ranges for the four historical vulnerabilities CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797; and (2) the NVD change history shows that the CPE for these versions was remapped from the old short form (e.g., m1, m2) to the full form (e.g., milestone1, milestone2). Start from the Apache Tomcat 9.0.0 milestone versions, check each against the current NVD affected-product version ranges for these four CVEs, then examine the corresponding change history records. Retain only those milestone versions that satisfy both conditions. Exclude milestones that are included only because of other Tomcat 9.0.0 pre-release vulnerabilities, and do not include Tomcat 6, 7, 8, 8.5, or any non-Tomcat products. Finally, output an ordered multi-row table sorted by milestone number in ascending order, with columns: milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd.", + "start_url": "https://nvd.nist.gov/products/cpe/search", + "output_format": "Output as a Markdown multi-row table with fixed column names: milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd. Sort by milestone number in ascending order (M1, M2, ..., M9).", + "oracle_output_cardinality": 9, + "oracle_answer": "milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd\nM1|cpe:2.3:a:apache:tomcat:9.0.0:m1:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone1:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM2|cpe:2.3:a:apache:tomcat:9.0.0:m2:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone2:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM3|cpe:2.3:a:apache:tomcat:9.0.0:m3:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone3:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM4|cpe:2.3:a:apache:tomcat:9.0.0:m4:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone4:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM5|cpe:2.3:a:apache:tomcat:9.0.0:m5:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone5:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM6|cpe:2.3:a:apache:tomcat:9.0.0:m6:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone6:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM7|cpe:2.3:a:apache:tomcat:9.0.0:m7:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone7:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM8|cpe:2.3:a:apache:tomcat:9.0.0:m8:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone8:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM9|cpe:2.3:a:apache:tomcat:9.0.0:m9:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone9:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18", + "metadata": { + "State-Gated Retrieval": [ + "Retain only Apache Tomcat 9.0.0 milestone versions that appear in the current affected-product ranges for all four target CVEs: CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797.", + "These versions must also have a CPE Deprecation Remap from mN to milestoneN visible in the NVD Change History.", + "Finally, output sorted by milestone number in ascending order, and the required_cves field must list these four specific CVEs." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the current milestoneN CPE search and detail pages yield the Tomcat milestone family and the legacy mN mapping anchors", + "the four target CVE pages and Change History entries yield the exact mN -> milestoneN deprecation remaps and the required-CVE intersection", + "final rows are produced only after taking the remaps common to all four target CVEs and sorting by numeric milestone" + ], + "control_dependency": [ + "the candidate milestone set must be determined from the four-target-CVE intersection rather than from all prerelease Tomcat CVEs", + "later remapped milestones such as M10+ must be excluded by applying the specified four-CVE boundary", + "only explicit NVD CPE Deprecation Remap events from mN to milestoneN count, so generic Tomcat prerelease visibility cannot be accepted as evidence" + ], + "freeze": { + "historical_window": "the Tomcat 9.0.0 prerelease milestones jointly covered by CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797, with remap evidence fixed to the 2023-12-08 11:41:18 NVD deprecation events" + }, + "answer_type": "multi-row ordered table" + }, + "all_involved_urls": { + "fixed_entry_and_docs": [ + "https://nvd.nist.gov/products/cpe/search", + "https://nvd.nist.gov/vuln/vulnerability-detail-pages" + ], + "cpe_search_result_pages": [ + "https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL", + "https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED", + "https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20m&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED", + "https://nvd.nist.gov/products/cpe/search/results?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED" + ], + "representative_cpe_detail_pages": [ + "https://nvd.nist.gov/products/cpe/detail/615922?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED", + "https://nvd.nist.gov/products/cpe/detail/615947?keyword=cpe%3A2.3%3Aa%3Aapache&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED" + ], + "row_level_cpe_api_urls_m1_to_m9": [ + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone2%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone3%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone4%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone5%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone6%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone7%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone8%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone9%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A" + ], + "target_cve_detail_pages": [ + "https://nvd.nist.gov/vuln/detail/CVE-2016-5018", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6794", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6796", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6797" + ], + "negative_control_cve_detail_pages": [ + "https://nvd.nist.gov/vuln/detail/CVE-2016-6816", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6817", + "https://nvd.nist.gov/vuln/detail/CVE-2019-0221" + ], + "cve_change_history_api": [ + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-5018&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6794&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6796&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6797&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6816&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6817&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2019-0221&eventName=CPE%20Deprecation%20Remap" + ], + "representative_change_record_pages": [ + "https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=04%2F18%2F2022T13%3A57%3A03.500-0400", + "https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=08%2F24%2F2017T09%3A11%3A40.690-0400" + ] + }, + "rubric": { + "inclusion_conditions": [ + "Retain only Apache Tomcat 9.0.0 milestone versions that appear in the current affected-product ranges for all four target CVEs: CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797.", + "These versions must also have a CPE Deprecation Remap from mN to milestoneN visible in the NVD Change History.", + "Finally, output sorted by milestone number in ascending order, and the required_cves field must list these four specific CVEs." + ], + "exclusion_conditions": [ + "Exclude milestones that are included only because of other Tomcat 9.0.0 pre-release vulnerabilities, such as M10/M11 and later milestones.", + "Exclude Tomcat 6, 7, 8, 8.5, or any non-Tomcat products.", + "Exclude records that lack explicit NVD remap evidence and are only visible on the current milestone page." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row `milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd`", + "schema": [ + "milestone", + "legacy_cpe", + "current_cpe", + "required_cves", + "remap_time_nvd" + ], + "milestone": "emit the canonical milestone label `M1` through `M9` and sort by the numeric suffix ascending", + "legacy_cpe": "preserve the exact legacy CPE 2.3 string containing the short milestone token such as `m1`", + "current_cpe": "preserve the exact current CPE 2.3 string containing the full milestone token such as `milestone1`", + "required_cves": "emit the fixed literal `CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797`", + "remap_time_nvd": "emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form" + } + } +} diff --git a/data_en/constraint/reptile_001.json b/data_en/constraint/reptile_001.json new file mode 100644 index 0000000000000000000000000000000000000000..424416cf472eba8cbd33c656975cde8b1870b6a4 --- /dev/null +++ b/data_en/constraint/reptile_001.json @@ -0,0 +1,61 @@ +{ + "task_id": "reptile_001", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "I am compiling a name concordance for early museum specimens of Indian snakes recorded in George A. Boulenger's 1890 work *The Fauna of British India, Including Ceylon and Burma*. Proceed as follows: first, using this specimen set as the scope, look up each corresponding current species page in the Reptile Database and retain only entries that simultaneously satisfy the following conditions: the species has since been reassigned to a different genus; the page still retains BMNH type specimen information; and the type locality still corresponds to India. For each qualifying entry, identify from the names listed on that page the oldest binomial that is closest to the present but has not yet been updated to the current genus name. Then, search again using this full old name and determine whether the search result points to only this single record. Finally, output the results as a single line sorted alphabetically by current accepted name, in the format |||; separate entries with semicolons. If no qualifying entries exist, output NONE.", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "Output the results as a single line sorted alphabetically by current accepted name, in the format |||; separate entries with semicolons. If no qualifying entries exist, output NONE.", + "oracle_answer": "Argyrophis oatesii|Typhlops oatesii|UNIQUE|SYNTYPES;Dendrelaphis grandoculis|Ahaetulla grandoculis|UNIQUE|LECTOTYPE;Fowlea sanctijohannis|Xenochrophis sanctijohannis|UNIQUE|HOLOTYPE;Gerrhopilus beddomii|Typhlops beddomii|UNIQUE|SYNTYPES;Hebius khasiensis|Amphiesma khasiense|UNIQUE|LECTOTYPE;Hebius parallelus|Amphiesma parallelum|AMBIG|LECTOTYPE;Indotyphlops jerdoni|Typhlops jerdoni|UNIQUE|SYNTYPES;Myriopholis blanfordii|Leptotyphlops blanfordi|AMBIG|SYNTYPES", + "metadata": { + "State-Gated Retrieval": [ + "Candidates must come from the historical museum entries of Indian snakes in Boulenger 1890 *Fauna of British India*.", + "The current Reptile Database species page must simultaneously satisfy: the species has been reassigned to a different genus; the page still retains BMNH type specimen information; the type locality still corresponds to India.", + "On each qualifying page, select the oldest binomial that is closest to the present but has not yet been updated to the current genus name, then perform an exact back-search using this old name and label it UNIQUE or AMBIG." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Boulenger 1890 historical sample and current accepted-species pages yield candidates that changed genus while retaining BMNH type data and India-compatible type locality", + "each accepted page yields the nearest pre-current-genus old label, the BMNH type status, and the historical/type-locality evidence anchoring the entity", + "final rows are produced only after the old-label exact back-search is evaluated for uniqueness without losing the original entity anchor" + ], + "control_dependency": [ + "when an exact old-label back-search now hits multiple species, the original anchored entity must be kept and the uniqueness label must be set to AMBIG", + "once a candidate has passed the historical-cluster, genus-shift, BMNH, and India-locality gates, later old-label ambiguity can only rewrite the uniqueness field, not the entity itself", + "candidate anchoring must be preserved across the two-stage workflow so that old-label search noise does not redirect the accepted-species row" + ], + "freeze": { + "historical_window": "the George A. Boulenger 1890 British India sample, evaluated against current Reptile Database accepted pages, synonym labels, BMNH type data, and present type-locality text" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Candidates must come from the historical museum entries of Indian snakes in Boulenger 1890 *Fauna of British India*.", + "The current Reptile Database species page must simultaneously satisfy: the species has been reassigned to a different genus; the page still retains BMNH type specimen information; the type locality still corresponds to India.", + "On each qualifying page, select the oldest binomial that is closest to the present but has not yet been updated to the current genus name, then perform an exact back-search using this old name and label it UNIQUE or AMBIG." + ], + "exclusion_conditions": [ + "Exclude entries where the current accepted name has not undergone a genus change, or where the page no longer retains BMNH type specimen information.", + "Exclude entries whose type locality does not correspond to India.", + "Do not discard candidates whose exact old-name back-search is non-unique; such candidates should be retained and labeled AMBIG." + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "accepted name", + "old label", + "UNIQUE/AMBIG", + "BMNH status" + ], + "accepted_name": "emit the current accepted binomial exactly as shown in the reconciled source", + "old_label": "preserve the historical label exactly as used on the legacy branch", + "UNIQUE/AMBIG": "emit `UNIQUE` or `AMBIG` in uppercase", + "BMNH_status": "normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or SYNTYPES", + "sorting_or_selection": "accepted name alphabetical ascending" + } + } +} diff --git a/data_en/constraint/reptile_002.json b/data_en/constraint/reptile_002.json new file mode 100644 index 0000000000000000000000000000000000000000..f84ebe32aee683c1431c1cc24667f74622174c45 --- /dev/null +++ b/data_en/constraint/reptile_002.json @@ -0,0 +1,63 @@ +{ + "task_id": "reptile_002", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "I am compiling current name correspondences for early museum specimens of Southeast Asian Lygosoma. The old labels correspond to Riopa combinations attributed to Smith (1935/1937) in the Synonym section of each species page, but some of these old names now map to multiple current species under the current classification. Process as follows: first, within the current Lygosoma checklist, examine each current species page and locate these Smith (1935/1937) Riopa combinations in the Synonym section; then compare these old names, identify those that point to multiple current species, and list all involved current species. Next, for each qualifying current species, record the first-listed type specimen number, type category, and the region ultimately corresponding to the type locality on that page. Finally, output the results as a single line with entries sorted alphabetically by current accepted name, in the format ||||; separate entries with semicolons; if no qualifying entries exist, output NONE.", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "Output the results as a single line with entries sorted alphabetically by current accepted name, in the format ||||; separate entries with semicolons; if no qualifying entries exist, output NONE.", + "oracle_answer": "Lygosoma bampfyldei|Riopa bampfyldei|BMNH 1946.8.10.84|SYNTYPES|East Malaysia;Lygosoma peninsulare|Riopa bampfyldei|LSUHC 13857|HOLOTYPE|Peninsular Malaysia;Lygosoma schneideri|Riopa bampfyldei|NMBA 4743|HOLOTYPE|Indonesia", + "metadata": { + "State-Gated Retrieval": [ + "Retain only those accepted species that can be traced from the Smith 1937 old-name chain to a current Lygosoma record and for which the type accession, type status, and locality can be read on the current page.", + "For each accepted record, output the accepted name, the corresponding old label, the type accession, the type status, and the locality.", + "If the same exact old name is attached to multiple accepted species, retain them as separate chains." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Smith 1937 old-name chain yields the three current Lygosoma accepted pages connected to Riopa bampfyldei / Lygosoma bampfyldei", + "each accepted page yields its own type accession, type status, and type locality needed to separate the homonymous old-name paths", + "final rows are produced only after the one-to-many old-name split is rebuilt and the three paths are re-anchored to their own type evidence" + ], + "control_dependency": [ + "same-specific-epithet matching cannot establish a one-to-one mapping when the same Smith 1937 old name appears on multiple accepted pages", + "once literal old-name reuse is exposed, the workflow must keep the original parallel three-chain state rather than collapsing to a one-to-one mapping", + "type accession and locality evidence must be read separately for each chain rather than patched onto the first stopping page" + ], + "freeze": { + "historical_window": "the current Reptile Database accepted pages linked to the Smith 1937 old-name cluster around Riopa bampfyldei, using current type accessions, statuses, and localities" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only those accepted species that can be traced from the Smith 1937 old-name chain to a current Lygosoma record and for which the type accession, type status, and locality can be read on the current page.", + "For each accepted record, output the accepted name, the corresponding old label, the type accession, the type status, and the locality.", + "If the same exact old name is attached to multiple accepted species, retain them as separate chains." + ], + "exclusion_conditions": [ + "Exclude results that assume the same species based solely on the old name and current specific epithet being identical.", + "Exclude results that retain only the first chain after discovering the same exact old name on multiple accepted pages.", + "Exclude results that do not return to each accepted page to re-verify the type accession and locality." + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "accepted", + "Smith-era Riopa label", + "first type code", + "type status", + "region" + ], + "accepted": "emit the current accepted binomial exactly as shown in the reconciled source", + "Smith-era_Riopa_label": "preserve the Smith-era Riopa label exactly as used on the legacy branch", + "first_type_code": "emit the first accession code that follows the selected type-status statement", + "type_status": "normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES", + "region": "emit the modern geographic region label from the source reconciliation, such as East Malaysia or Peninsular Malaysia", + "sorting_or_selection": "accepted name alphabetical ascending" + } + } +} diff --git a/data_en/constraint/reptile_003.json b/data_en/constraint/reptile_003.json new file mode 100644 index 0000000000000000000000000000000000000000..12327e47d3268ef82e781c8ee46d125358afb3e2 --- /dev/null +++ b/data_en/constraint/reptile_003.json @@ -0,0 +1,66 @@ +{ + "task_id": "reptile_003", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 10, + "instruction": "I am organizing current-name cross-references for a batch of early museum catalog cards that were still filed under Mabuya or Mabuia around 1980, and need to map them into the current Eutropis checklist. Process as follows: first, examine each species page in the current Eutropis checklist one by one, and on each page identify the first synonym label that is both in Mabuya or Mabuia form and tagged with the 1980 citation year. Then, perform an exact name search using that 1980 old label, and retain only those species for which the back-search result points to more than one current Eutropis entry. For each qualifying entry, record its current accepted name, the 1980 old label, the qualifier annotation for that old label on the page, and the first type category and code listed on the current page. Finally, output a single line per entry in the format |<1980 label>|||, sorted alphabetically by old label and, within the same old label, by accepted name. Join entries with semicolons. If no qualifying entries exist, output NONE.", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "Output a single line per entry in the format |<1980 label>|||, sorted alphabetically by old label and, within the same old label, by accepted name. Join entries with semicolons. If no qualifying entries exist, output NONE.", + "oracle_answer": "Eutropis indeprensa|Mabuya indeprensa|NONE|HOLOTYPE|CAS 85664;Eutropis sahulinghangganan|Mabuya indeprensa|PART-MISID|HOLOTYPE|PNM 9867;Eutropis multifasciata|Mabuya multifasciata|NONE|NEOTYPE|MZB 11912;Eutropis multicarinata|Mabuya multicarinata|NONE|HOLOTYPE|BMNH 1946.8.15.13-15;Eutropis borealis|Mabuya multicarinata borealis|NONE|HOLOTYPE|CAS 15447;Eutropis islamaliit|Mabuya multicarinata borealis|PART-MISID|HOLOTYPE|PNM 9847;Eutropis caraga|Mabuya multicarinata multicarinata|PART-MISID|HOLOTYPE|PNM 9845;Eutropis palauensis|Mabuya multicarinata multicarinata|PART-BYIMPL|HOLOTYPE|CAS 248251;Eutropis dattaroyi|Mabuya rudis|PART|HOLOTYPE|ZSI 25118;Eutropis rudis|Mabuya rudis|NONE|LECTOTYPE|BMNH 1946.8.15.26", + "metadata": { + "State-Gated Retrieval": [ + "Retain only those current Eutropis accepted species for which the synonym block contains, scanning top-down, a first synonym label that begins with Mabuya or Mabuia and has the year 1980.", + "Then, perform an exact name search using that 1980 old label, and output the accepted name, old label, back-search qualifier, type status, and type specimen.", + "If the subsequent back-search reveals additional matching entries, revisit the earlier results and include them in the final output." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current Eutropis detail pages yield the first 1980-tagged Mabuya/Mabuia synonym label for each accepted species", + "exact back-search on that 1980 old label yields the present accepted page, type status, and type specimen needed for the output row", + "final rows are produced only after the 1980-specific old-label anchor is rebuilt and the accepted-species set is expanded when back-search evidence reveals omitted entries" + ], + "control_dependency": [ + "the workflow must identify the first Mabuya/Mabuia label carrying the 1980 year rather than stopping at the first old label on the page", + "when old-label back-search reveals missing entries such as Eutropis dattaroyi, the accepted-species set must be expanded to include them rather than patched in place", + "accepted-page synonym parsing and back-search interpretation must stay coupled so that 1980 labels are not replaced by older but irrelevant names" + ], + "freeze": { + "historical_window": "current Reptile Database Eutropis pages, restricted to the first synonym label that is both Mabuya/Mabuia-form and tagged with the 1980 citation year" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only those current Eutropis accepted species for which the synonym block contains, scanning top-down, a first synonym label that begins with Mabuya or Mabuia and has the year 1980.", + "Then, perform an exact name search using that 1980 old label, and output the accepted name, old label, back-search qualifier, type status, and type specimen.", + "If the subsequent back-search reveals additional matching entries, revisit the earlier results and include them in the final output." + ], + "exclusion_conditions": [ + "Exclude results that mistakenly treat the first old name on the page as the first 1980 old label.", + "Exclude results whose exact back-search on the 1980 old label points to only a single current Eutropis entry.", + "Exclude results that, when subsequent evidence reveals omitted entries, do not revisit the earlier results and rebuild the accepted-species set." + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "accepted", + "1980 label", + "qualifier", + "type status", + "first type code" + ], + "accepted": "emit the current accepted binomial exactly as shown in the reconciled source", + "1980_label": "preserve the 1980-era label exactly as used on the legacy branch", + "qualifier": "normalize to one of `NONE`, `PART`, `PART-MISID`, or `PART-BYIMPL`", + "type_status": "normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES", + "first_type_code": "emit the first accession code that follows the selected type-status statement", + "sorting_or_selection": { + "primary": "1980 label alphabetical ascending", + "secondary": "accepted name alphabetical ascending" + } + } + } +} diff --git a/data_en/constraint/reptile_004.json b/data_en/constraint/reptile_004.json new file mode 100644 index 0000000000000000000000000000000000000000..93dd97d79ebe8e9ca1fd5d9b0946344299731809 --- /dev/null +++ b/data_en/constraint/reptile_004.json @@ -0,0 +1,65 @@ +{ + "task_id": "reptile_004", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 6, + "instruction": "I am organizing a batch of early museum catalog cards for half-toed geckos that still use the old labels listed in the comments section of the Hemidactylus brookii species page. Process as follows: first examine the old labels listed in the comments section of the current Hemidactylus brookii species page, and select those that are no longer placed in Hemidactylus brookii and for which the database has clearly provided their current assignment. Then, for each qualifying label, determine the current species it should ultimately be assigned to; if merging from that label to the current species must pass through an intermediate old name, write that intermediate name, otherwise write DIRECT. At the same time, record the type status, type code, and the country of the type locality for that label itself. Finally, output a single line with entries sorted alphabetically by legacy label: |||||; separate entries with semicolons; if no qualifying entries exist, output NONE.", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "Output a single line with entries sorted alphabetically by legacy label: |||||; separate entries with semicolons; if no qualifying entries exist, output NONE.", + "oracle_answer": "Hemidactylus brooki leightoni|Hemidactylus angulatus|DIRECT|HOLOTYPE|BMNH 1946.8.25.65|Colombia;Hemidactylus brookii haitianus|Hemidactylus angulatus|DIRECT|LECTOTYPE|ZMH R22378|Haiti;Hemidactylus brookii parvimaculatus|Hemidactylus parvimaculatus|DIRECT|HOLOTYPE|NMSL No. RG. 15|Sri Lanka;Hemidactylus brookii subtriedroides|Hemidactylus murrayi|Hemidactylus tenkatei|LECTOTYPE|BMNH [subtriedroides] [tenkatei]|Myanmar;Hemidactylus gleadowi|Hemidactylus gleadowi|DIRECT|NEOTYPE|BMNH 1884.7.25.8|Pakistan;Hemidactylus tenkatei|Hemidactylus murrayi|DIRECT|LECTOTYPE|RMNH 4353|Indonesia", + "metadata": { + "State-Gated Retrieval": [ + "Each result must start from the old-label chain specified in the task and ultimately determine the accepted name, bridge status, type status, type accession, and locality from the current accepted page.", + "For the subtriedroides branch, continue along tenkatei to murrayi, output the final accepted name as Hemidactylus murrayi, and retain bridge=Hemidactylus tenkatei.", + "For branches such as haitianus and leightoni, read their own locality/type lines rather than borrowing header information from the wrong page." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "The old-label chains from Hemidactylus angulatus and related names yield accepted pages, bridge names, and the type/locality lines for each path.", + "Comment, Types, and type-comment blocks yield the later evidence that tenkatei is further sunk into H. murrayi.", + "Final rows are produced only after each old-label path is re-anchored to its own locality/type line and the subtriedroides -> tenkatei -> murrayi bridge chain is completed." + ], + "control_dependency": [ + "Type data must be taken from the locality/type line belonging to the actual old-label branch rather than from the header block of the wrong accepted page.", + "Stopping at the intermediate tenkatei bridge is insufficient; the workflow must continue to the later murrayi evidence and rewrite both tenkatei and subtriedroides final accepted names.", + "Bridge labels remain useful, but final accepted names and type lines must be determined from the deeper synonym chain." + ], + "freeze": { + "historical_window": "Current Reptile Database pages for the Hemidactylus angulatus / brookii / murrayi complex, using present locality, type, comment, and type-comment blocks." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Each result must start from the old-label chain specified in the task and ultimately determine the accepted name, bridge status, type status, type accession, and locality from the current accepted page.", + "For the subtriedroides branch, continue along tenkatei to murrayi, output the final accepted name as Hemidactylus murrayi, and retain bridge=Hemidactylus tenkatei.", + "For branches such as haitianus and leightoni, read their own locality/type lines rather than borrowing header information from the wrong page." + ], + "exclusion_conditions": [ + "Exclude results that follow the wrong page hierarchy and apply the Holotype/locality from the H. angulatus page header to other branches.", + "Exclude results that stop early on the subtriedroides -> tenkatei chain without continuing to read the murrayi evidence.", + "Exclude results that fail to align the locality/type line with each specific old-label branch." + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "legacy label", + "accepted", + "bridge", + "type status", + "type code", + "country" + ], + "legacy_label": "Preserve the legacy label exactly as used on the source branch.", + "accepted": "Emit the current accepted binomial exactly as shown in the reconciled source.", + "bridge": "Emit `DIRECT` when no intermediate legacy bridge name is needed; otherwise emit the intermediate legacy name that links the branches.", + "type_status": "Normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or NEOTYPE.", + "type_code": "Take the type accession from the legacy-label branch rather than from a generic type line elsewhere on the page.", + "country": "Emit the modern English country name from the reconciled source branch.", + "sorting_or_selection": "Legacy label alphabetical ascending." + } + } +} diff --git a/data_en/constraint/reptile_005.json b/data_en/constraint/reptile_005.json new file mode 100644 index 0000000000000000000000000000000000000000..a949b9c271eeb4ec9b6a732baa6d2c65ac3edc17 --- /dev/null +++ b/data_en/constraint/reptile_005.json @@ -0,0 +1,68 @@ +{ + "task_id": "reptile_005", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am checking a synonymization record in the current Naja species list that involves an early Sri Lankan museum name, and I want to organize the key information from the accepted side and the contested-name side into a two-row comparison table. First, in the current Naja list, locate the contested-name record associated with Sri Lanka. Then verify its recent-use evidence, the database's final treatment, the correction concerning lectotype assignment, the restricted type locality, and the holotype information for the contested name itself. Finally, output a two-row comparison table with columns rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note. Row 1 should be ACCEPTED_NAME and give the accepted name, final status, valid lectotype, and restricted type locality. Row 2 should be CONTESTED_NAME and give the contested name, recent-use evidence, holotype, and the corrected invalid lectotype claim.", + "start_url": "https://reptile-database.reptarium.cz/advanced_search?genus=Naja&submit=Search", + "output_format": "Output a two-row comparison table with columns rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note.", + "oracle_answer": "1|ACCEPTED_NAME|Naja naja|SUBJECTIVE_JUNIOR_SYNONYM_OF_NAJA_NAJA|VALID_LECTOTYPE|ZMB 2796|restricted type locality: Sri Lanka\n2|CONTESTED_NAME|Naja polyocellata|SHI et al. 2022+SILVA et al. 2023|HOLOTYPE|BMNH 1946.1.18.50|invalid lectotype claim: NRM (= NHR) Lin-90", + "metadata": { + "State-Gated Retrieval": [ + "Within the current Naja list, identify the Sri Lanka contested-name branch: the name was recently reused as a distinct valid name, but the database now explicitly merges it back into the accepted name.", + "On the current Naja naja page, read the recent-use evidence, final synonym status, lectotype correction, restricted type locality, and the holotype information for the contested name itself.", + "The final output must organize the ACCEPTED_NAME side and the CONTESTED_NAME side into a two-row comparison table." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the current Naja species list and the Naja naja page yield the Sri Lanka contested-name branch, recent-use citations, and the accepted-name context", + "comment, Types, and type-comment blocks yield the final synonym treatment plus the valid and invalid lectotype assignments and the contested-name holotype", + "final rows are produced only after the accepted-name side and the contested-name side are reconciled on the current Naja naja page" + ], + "control_dependency": [ + "recent-use evidence for Naja polyocellata must be interpreted together with the current final synonym treatment shown on that page", + "lectotype status must be fixed from the combined Types and type-comment evidence rather than from a single provisional assignment", + "the accepted-name and contested-name rows are emitted together only after final status, type locality, and specimen roles are fixed" + ], + "freeze": { + "historical_window": "the objectively existing taxa in the Sri Lanka Naja branch, using current Reptile Database comment, Types, and type-comment blocks as nearly objective and highly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Within the current Naja list, identify the Sri Lanka contested-name record: the name was recently reused in the literature as a distinct valid name, but the database now explicitly states that it should still be merged into the accepted name.", + "On the current Naja naja page, the result must jointly recover the recent-use evidence, final synonym status, lectotype correction, restricted type locality, and the holotype information for the contested name itself.", + "The final output must organize the ACCEPTED_NAME side and the CONTESTED_NAME side into a two-row comparison table." + ], + "exclusion_conditions": [ + "Exclude results that treat the recently revived contested name as the current accepted name.", + "Exclude results that stop at the Wallach 2014 lectotype designation and do not continue to the later comment and type-comment correction.", + "Exclude results that fail to output both the restricted type locality and the contested-name holotype." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "name_role", + "name", + "status_or_evidence", + "specimen_role", + "specimen_code", + "supporting_note" + ], + "rank": "emit 1 for ACCEPTED_NAME and 2 for CONTESTED_NAME", + "name_role": [ + "ACCEPTED_NAME", + "CONTESTED_NAME" + ], + "name_fields": "use the current binomial spellings exactly", + "specimen_code_normalization": "preserve museum abbreviations, spaces, parentheses, and specimen punctuation exactly as the page shows", + "sorting_or_selection": "emit rows in the fixed order ACCEPTED_NAME then CONTESTED_NAME" + } + } +} diff --git a/data_en/constraint/wateroffice_001.json b/data_en/constraint/wateroffice_001.json new file mode 100644 index 0000000000000000000000000000000000000000..a6b0592f997090a0ff80aa4024123550f3625146 --- /dev/null +++ b/data_en/constraint/wateroffice_001.json @@ -0,0 +1,67 @@ +{ + "task_id": "wateroffice_001", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am compiling historical daily flow comparison data for the Saint John River spring freshet period and want to determine, along the mainstem, which station in the current monitoring network is the last one that still allows daily flow comparisons for March–April 1973 and March–April 2018, and which mainstem station downstream of it is the first one that no longer satisfies that condition. First, use the current monitoring network shown on the Wateroffice real-time page as of April 16, 2026, and retain only stations on the Saint John River mainstem. Then, for each station, check the historical availability page, distinguish Flow Data Availability from Daily Water Level Data Availability, and determine whether March–April 1973 and March–April 2018 both have complete daily flow records. If the target windows satisfy the complete daily flow condition, set target_window_status to PASS and final_verdict to KEEP. If the target years have only water level records and no daily flow records, set target_window_status to LEVEL_ONLY and final_verdict to REJECT. If daily flow records exist but any target month in March–April 1973 or March–April 2018 is missing or incomplete, set target_window_status to FLOW_GAP and final_verdict to REJECT. Finally, output a two-row breakpoint table with columns rank|station_number|breakpoint_role|target_window_status|final_verdict. In the first row, give the last usable station and set breakpoint_role to LAST_USABLE. In the second row, give the first failing station encountered downstream and set breakpoint_role to FIRST_DOWNSTREAM_FAIL.", + "start_url": "https://wateroffice.ec.gc.ca/search/real_time_e.html", + "output_format": "Output a two-row breakpoint table with columns rank|station_number|breakpoint_role|target_window_status|final_verdict.", + "oracle_answer": "1|01AF002|LAST_USABLE|PASS|KEEP\n2|01AK003|FIRST_DOWNSTREAM_FAIL|LEVEL_ONLY|REJECT", + "metadata": { + "State-Gated Retrieval": [ + "Determine the last station still usable for the target historical-window comparison only within the Saint John River mainstem stations in the current monitoring network.", + "On the historical availability page, Flow Data Availability must be distinguished from Daily Water Level Data Availability, and completeness for March–April 1973 and March–April 2018 must be checked.", + "The final output must provide both breakpoint rows, LAST_USABLE and FIRST_DOWNSTREAM_FAIL, under the same validation rule." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the current Saint John River mainstem station sequence provides the downstream order in which the breakpoints must be checked", + "per-station historical availability pages yield Flow Data Availability, Daily Water Level Data Availability, and target-month completeness for 1973 and 2018", + "the final breakpoint rows are produced only after the availability-page checks identify the last usable station and the first downstream failure under the same rule" + ], + "control_dependency": [ + "the breakpoint pair must be determined from historical availability that distinguishes flow from level-only evidence", + "target-year/month completeness must be checked on the availability page rather than inferred from the station list", + "the second row is emitted only after the first downstream failing mainstem station is fixed under the same validation rule" + ], + "freeze": { + "historical_window": "mainstem candidate stations evaluated by historical daily availability, with the target completeness rule applied to the specified 1973 and 2018 March/April windows" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Search for the final station only within the mainstem station set specified in the task, and continue downstream along the mainstem to identify the first station after it that no longer meets the condition.", + "The historical daily availability page must distinguish Flow Data Availability from Daily Water Level Data Availability, and must verify the completeness of the required March–April windows for 1973 and 2018.", + "The final output must provide both breakpoint rows, LAST_USABLE and FIRST_DOWNSTREAM_FAIL, under the same validation rule." + ], + "exclusion_conditions": [ + "Exclude results that rely only on the current Saint John River mainstem station sequence and directly take the most downstream station by reference index.", + "Exclude results that mistakenly treat level-only evidence as satisfying the flow condition.", + "Exclude results that do not check each station's availability page to verify target-month completeness." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "breakpoint_role", + "target_window_status", + "final_verdict" + ], + "rank": "emit `1` for LAST_USABLE and `2` for FIRST_DOWNSTREAM_FAIL", + "station_number": "preserve the station number exactly", + "breakpoint_role": "emit `LAST_USABLE` and `FIRST_DOWNSTREAM_FAIL` exactly", + "target_window_status": "emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly", + "final_verdict": "emit `KEEP` for the usable breakpoint row and `REJECT` for the downstream failing breakpoint row", + "stop_condition": [ + "the last usable mainstem station is fixed under the availability-page validation rule", + "the first downstream failing mainstem station is fixed under the same validation rule before the two-row output is emitted" + ] + } + } +} diff --git a/data_en/constraint/wateroffice_002.json b/data_en/constraint/wateroffice_002.json new file mode 100644 index 0000000000000000000000000000000000000000..c448376aac91f2d3edf6c7ec16b53bdc4ef17d28 --- /dev/null +++ b/data_en/constraint/wateroffice_002.json @@ -0,0 +1,66 @@ +{ + "task_id": "wateroffice_002", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "I am compiling historical daily flow records for the Bulkley River reach from Houston to Hazelton and want to verify, station by station, whether candidate mainstem stations on the Bulkley River truly have complete daily flow records for April–July 1948 and April–July 1950. First, from the Historical Results list, select candidate stations that lie on the Bulkley River mainstem, fall within the Houston-to-Hazelton reach, appear to cover both 1948 and 1950, and carry a Flow label. Then open each station's availability page and check whether the target years fall within the Flow section and whether April-July is marked C throughout. If the target windows satisfy the complete daily flow condition, set target_window_status to PASS and final_verdict to KEEP. If the target years have only water level records and no daily flow records, set target_window_status to LEVEL_ONLY and final_verdict to REJECT. If daily flow records exist but any month from April to July is not complete, set target_window_status to FLOW_GAP and final_verdict to REJECT. Finally, output a table in downstream-to-upstream order with columns rank|station_number|target_window_status|final_verdict.", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "Output a table in downstream-to-upstream order with columns rank|station_number|target_window_status|final_verdict.", + "oracle_answer": "1|08EE004|PASS|KEEP\n2|08EE001|LEVEL_ONLY|REJECT\n3|08EE005|FLOW_GAP|REJECT\n4|08EE003|FLOW_GAP|REJECT", + "metadata": { + "State-Gated Retrieval": [ + "First identify mainstem candidate stations on the Historical Results list that appear to cover 1948/1950 and carry a Flow label.", + "A station qualifies only if its availability page shows the target years in the Flow section and all of April-July marked C.", + "The final output must report target_window_status and final_verdict for each station in the same station set, ordered from downstream to upstream." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Historical Results list yields four downstream-to-upstream mainstem candidates whose result rows span the target years and include Flow labels", + "each candidate's availability page yields whether the target years are in the Flow table and whether April-July is complete", + "the final ordered rows are produced only after all four stations are classified under the full Flow-table-and-Apr-Jul-C rule" + ], + "control_dependency": [ + "list-level year spans and coarse Flow tags must be confirmed by explicit target-month checks on the availability page", + "Hazelton, Smithers, and Houston candidate statuses must be fixed before the downstream-most KEEP row can be confirmed", + "row order and KEEP/REJECT labels must be emitted only after the full availability-page rule is applied to all four stations" + ], + "freeze": { + "historical_window": "the target mainstem stations tested against 1948 and 1950 daily Flow availability, with April-July requiring complete C coverage" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "First, from the Historical Results list, identify mainstem candidate stations that superficially appear to cover 1948/1950 and have a Flow label.", + "A truly qualified station must satisfy, on its availability page, that the target years are in the Flow section and that April–July are all marked C.", + "Finally, report target_window_status and final_verdict for each station in the same station set, ordered from downstream to upstream." + ], + "exclusion_conditions": [ + "Exclude stations deemed usable based solely on list-level year span and coarse Flow label.", + "Exclude retaining LEVEL_ONLY or FLOW_GAP stations in the final answer.", + "Exclude results that do not apply the full availability-page rule to all initially screened stations." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "target_window_status", + "final_verdict" + ], + "rank": "emit 1 through 4 in downstream-to-upstream order within the validated station set", + "station_number": "preserve the station number exactly", + "target_window_status": "emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly", + "final_verdict": "emit `KEEP` or `REJECT` exactly", + "sorting_or_selection": "downstream to upstream within the validated Bulkley River mainstem station set", + "stop_condition": [ + "all four initially screened stations are classified under the full availability-page rule", + "the ordered table is emitted only after the downstream-to-upstream sequence is fixed" + ] + } + } +} diff --git a/data_en/constraint/wateroffice_003.json b/data_en/constraint/wateroffice_003.json new file mode 100644 index 0000000000000000000000000000000000000000..01e7b6e2e5be772f4f988666bb2419cc5647b9c8 --- /dev/null +++ b/data_en/constraint/wateroffice_003.json @@ -0,0 +1,62 @@ +{ + "task_id": "wateroffice_003", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "I am compiling historical snowmelt daily flow data for the Thompson River from Chase to Spences Bridge. I need to verify, station by station, whether the mainstem stations along this reach actually have daily flow records for May–July of 1958 and 1971. First, in downstream order from Chase to Spences Bridge, select stations from the list that show coverage for 1958 and 1971 and have flow records for the Thompson River mainstem. Then, for each selected station, check whether it provides complete daily flow records for May–July of both 1958 and 1971. If a station has only water level records (no daily flow) for a target year, mark it LEVEL_ONLY. If daily flow records exist but the May–July window is missing or any target month is incomplete, mark it FLOW_GAP. Only when both years' May–July daily flow records are complete should the final_verdict be KEEP; otherwise, REJECT. Finally, output a table with columns rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict, ordered downstream from Chase to Spences Bridge.", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "Output a table with columns rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict, ordered downstream from Chase to Spences Bridge.", + "oracle_answer": "1|08LE031|SOUTH THOMPSON RIVER AT CHASE|PASS|PASS|KEEP\n2|08LE069|SOUTH THOMPSON RIVER AT MONTE CREEK|FLOW_GAP|LEVEL_ONLY|REJECT\n3|08LF023|THOMPSON RIVER AT KAMLOOPS|LEVEL_ONLY|LEVEL_ONLY|REJECT\n4|08LF033|THOMPSON RIVER NEAR SAVONA|FLOW_GAP|FLOW_GAP|REJECT\n5|08LF051|THOMPSON RIVER NEAR SPENCES BRIDGE|PASS|PASS|KEEP", + "metadata": { + "State-Gated Retrieval": [ + "All five candidate stations must be verified on the availability page to confirm that the target years are present in the Flow table and that May–July is entirely marked C.", + "Each station must output a PASS / LEVEL_ONLY / FLOW_GAP judgment for both target years, and then be marked KEEP or REJECT accordingly.", + "The result order must follow the river-path ordering specified in the task." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the river-path ordering yields five South Thompson / Thompson mainstem candidates", + "each station's availability page yields whether 1958 and 1971 are present in the Flow table and whether May-July is complete", + "final rows are produced only after every candidate is classified under the stricter target-year and target-month Flow rule" + ], + "control_dependency": [ + "overall year coverage on the results list must be confirmed by the availability page inside the Flow table", + "Monte Creek, Savona, and Kamloops must be rejected by LEVEL_ONLY / FLOW_GAP evidence before the KEEP rows are final", + "the river-order sequence remains fixed, but station statuses must be assigned only after the availability-page rule is applied to all five stations" + ], + "freeze": { + "historical_window": "the ordered South Thompson / Thompson mainstem candidates tested against 1958 and 1971 Flow availability, with May-July requiring complete C coverage" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "All five candidate stations must be verified on the availability page to confirm that the target years are present in the Flow table and that May–July is entirely marked C.", + "Each station must output a PASS / LEVEL_ONLY / FLOW_GAP judgment for both target years, and then be marked KEEP or REJECT accordingly.", + "The result order must follow the river-path ordering specified in the task." + ], + "exclusion_conditions": [ + "Exclude results that treat overall year coverage on the list as sufficient evidence.", + "Exclude results that fail to distinguish between Flow table target-year and month completeness versus Level-only evidence.", + "Exclude results that do not apply the same availability-page rule uniformly to all five stations." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "station_name", + "1958_MayJul", + "1971_MayJul", + "final_verdict" + ], + "rank": "use the fixed Chase-to-Spences-Bridge mainstem order from the reference index, not the transient search-result order", + "year_window_fields": "the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP", + "final_verdict": "emit `KEEP` or `REJECT` exactly" + } + } +} diff --git a/data_en/constraint/wateroffice_004.json b/data_en/constraint/wateroffice_004.json new file mode 100644 index 0000000000000000000000000000000000000000..a7e6e192273aa9e8b4cbb0de80f94520fc807ba8 --- /dev/null +++ b/data_en/constraint/wateroffice_004.json @@ -0,0 +1,62 @@ +{ + "task_id": "wateroffice_004", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 13, + "instruction": "I am compiling historical daily flow records for the mainstem Columbia River from Fairmont Hot Springs to the International Boundary. I want to check, station by station in Wateroffice, which stations have complete daily flow records for May–October of 1955 and 1956. First, locate stations on the Columbia River mainstem between Fairmont Hot Springs and the International Boundary whose records span both 1955 and 1956. Then, proceeding from upstream to downstream, check the availability of daily flow for May–October of 1955 and 1956 at each station. If a station has only water-level records and no daily flow records for a given target year, mark that year as LEVEL_ONLY. If daily flow for May–October of that year is complete, mark it as PASS. Otherwise, if the year has no usable daily flow records or any month within May–October is incomplete, mark it as FLOW_GAP. Only when both years satisfy the PASS condition should the final_verdict be KEEP; otherwise write REJECT. Finally, output a table in upstream-to-downstream order with columns: rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict.", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "Output a table in upstream-to-downstream order with columns: rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict.", + "oracle_answer": "1|08NA045|COLUMBIA RIVER NEAR FAIRMONT HOT SPRINGS|PASS|PASS|KEEP\n2|08NA004|COLUMBIA RIVER AT ATHALMER|LEVEL_ONLY|LEVEL_ONLY|REJECT\n3|08NA052|COLUMBIA RIVER NEAR EDGEWATER|PASS|FLOW_GAP|REJECT\n4|08NA002|COLUMBIA RIVER AT NICHOLSON|PASS|PASS|KEEP\n5|08NB005|COLUMBIA RIVER AT DONALD|PASS|PASS|KEEP\n6|08NB006|COLUMBIA RIVER AT SURPRISE RAPIDS|PASS|PASS|KEEP\n7|08ND007|COLUMBIA RIVER ABOVE NAGLE CREEK|PASS|PASS|KEEP\n8|08ND011|COLUMBIA RIVER ABOVE STEAMBOAT RAPIDS|FLOW_GAP|PASS|REJECT\n9|08ND006|COLUMBIA RIVER AT TWELVE MILE FERRY|PASS|PASS|KEEP\n10|08NE002|COLUMBIA RIVER AT CASTLEGAR|LEVEL_ONLY|LEVEL_ONLY|REJECT\n11|08NE049|COLUMBIA RIVER AT BIRCHBANK|PASS|PASS|KEEP\n12|08NE003|COLUMBIA RIVER AT TRAIL|LEVEL_ONLY|LEVEL_ONLY|REJECT\n13|08NE058|COLUMBIA RIVER AT INTERNATIONAL BOUNDARY|PASS|PASS|KEEP", + "metadata": { + "State-Gated Retrieval": [ + "Every candidate Columbia River station must be checked on its availability page to confirm that the target years appear in the Flow table and that May–October is fully marked C.", + "For each station, provide the KEEP/REJECT basis for both 1955 and 1956, distinguishing LEVEL_ONLY and FLOW_GAP cases from stations that only appear eligible from their overall year span.", + "The final table must preserve the order and fields specified in the task." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Columbia River candidate ordering yields fourteen stations spanning the target years", + "each availability page yields whether 1955 and 1956 are present in the Flow table and whether May-October is complete", + "final rows are produced only after every station is classified under the stricter Flow-table-and-May-Oct-C rule" + ], + "control_dependency": [ + "list-level year spans must be confirmed by the availability page inside the Flow table", + "LEVEL_ONLY and FLOW_GAP evidence must be applied to each station before the KEEP/REJECT table is finalized", + "station-by-station verdicts and rejection reasons must be determined only after the full availability-page rule replaces the initial year-span screen" + ], + "freeze": { + "historical_window": "the ordered Columbia River candidates tested against 1955 and 1956 Flow availability, with May-October requiring complete C coverage" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Every candidate Columbia River station must be checked on its availability page to confirm that the target years appear in the Flow table and that May–October is fully marked C.", + "For each station, provide the KEEP/REJECT basis for both 1955 and 1956, distinguishing LEVEL_ONLY and FLOW_GAP cases from stations that only appear eligible from their overall year span.", + "The final table must preserve the order and fields specified in the task." + ], + "exclusion_conditions": [ + "Exclude results that retain a station solely because its overall record spans 1955/1956.", + "Exclude results that fail to distinguish, station by station, between Flow availability, Level-only, and incomplete months.", + "Exclude results that do not apply the full availability-page rule uniformly to all 14 stations." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "station_name", + "1955_MayOct", + "1956_MayOct", + "final_verdict" + ], + "rank": "use the fixed upstream-to-downstream Columbia mainstem order from the reference index, not the transient search-result order", + "year_window_fields": "the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP", + "final_verdict": "emit `KEEP` or `REJECT` exactly" + } + } +} diff --git a/data_en/constraint/wateroffice_005.json b/data_en/constraint/wateroffice_005.json new file mode 100644 index 0000000000000000000000000000000000000000..6d913599ae8f97d8f01770161d9793135687ccc7 --- /dev/null +++ b/data_en/constraint/wateroffice_005.json @@ -0,0 +1,74 @@ +{ + "task_id": "wateroffice_005", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "I am organizing historical daily-flow records for the Peace River reach from Dunvegan Bridge to Fifth Meridian and want to verify three things at once: the true furthest-downstream reusable station on the mainstem, the first failing station encountered after it, and the provisional terminal station that a station-level screen based only on year coverage and record type would mistakenly treat as the downstream winner. Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian. First, from the station list, identify provisional candidates that appear to cover both 1966 and 1967 and show a daily-flow record type. Then open each availability page and verify whether May through September in both 1966 and 1967 appears in the Flow table and is complete for every month. If both target years satisfy the complete daily-flow condition, write PASS in target_window_status. If a target year has only level records and no daily-flow records, write LEVEL_ONLY. If daily-flow records exist but any target month from May through September is incomplete, write FLOW_GAP. If the target year has neither daily-flow nor level records, write NO_TARGET_RECORD. Finally, output a three-row diagnostic table with columns rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count. The rows must be FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION in that order, and the last two columns must repeat the global provisional_count and final_count in every row.", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "Output a three-row diagnostic table with columns rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count.", + "oracle_answer": "1|07HA001|FINAL_STATION|PASS|5|2\n2|07HD001|FIRST_BREAK_AFTER_FINAL|FLOW_GAP|5|2\n3|07KA002|PROVISIONAL_STATION|FLOW_GAP|5|2", + "metadata": { + "State-Gated Retrieval": [ + "Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian.", + "A genuinely reusable station must satisfy the availability-page rule that both 1966 and 1967 appear in the Flow table and that every month from May through September is complete.", + "The final output must jointly report FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION, while repeating provisional_count and final_count in every row." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Peace River mainstem chain between Dunvegan Bridge and Fifth Meridian yields the initial station list and the downstream breakpoint positions that need revalidation", + "each availability page yields whether 1966 and 1967 are present in the Flow or Level tables and whether May-September is complete", + "final rows are produced only after the final station, the first downstream failure, and the provisional downstream winner are all fixed under the same availability-page validation rule" + ], + "control_dependency": [ + "station-level target-year Flow evidence must be validated by explicit May-September completeness checks on the availability page", + "the final downstream reusable station and the first downstream failure must be determined under the same validation rule rather than from the initial station screen", + "the provisional downstream winner is kept in the output only for reference after its FLOW_GAP status is confirmed on the availability page" + ], + "freeze": { + "historical_window": "Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian, evaluated within the fixed historical 1966 and 1967 Flow-availability windows, with May-September complete-C coverage used as nearly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian.", + "A genuinely reusable station must satisfy the availability-page rule that both 1966 and 1967 appear in the Flow table and that every month from May through September is complete.", + "The final output must jointly report FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION, while repeating provisional_count and final_count in every row." + ], + "exclusion_conditions": [ + "Exclude results that treat a station as usable simply because the target years have Flow records.", + "Exclude results that do not verify completeness month by month from May through September.", + "Exclude results that mark a station such as 07KA002 as FINAL_STATION when availability-page evidence shows FLOW_GAP." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "diagnosis_role", + "target_window_status", + "provisional_count", + "final_count" + ], + "rank": "emit the fixed order 1, 2, 3 for FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION", + "station_number": "use uppercase WSC station codes exactly as the Reference Index and availability pages show", + "diagnosis_role": [ + "FINAL_STATION", + "FIRST_BREAK_AFTER_FINAL", + "PROVISIONAL_STATION" + ], + "target_window_status": [ + "PASS", + "LEVEL_ONLY", + "FLOW_GAP", + "NO_TARGET_RECORD" + ], + "count_fields": "repeat the global provisional_count and final_count in every row as plain integers", + "sorting_or_selection": "emit rows in the fixed diagnostic order FINAL_STATION, FIRST_BREAK_AFTER_FINAL, PROVISIONAL_STATION" + } + } +} diff --git a/data_en/constraint/waterquality_001.json b/data_en/constraint/waterquality_001.json new file mode 100644 index 0000000000000000000000000000000000000000..99f0885b04237ee0776f99cfa14f2b41747c3c0e --- /dev/null +++ b/data_en/constraint/waterquality_001.json @@ -0,0 +1,67 @@ +{ + "task_id": "waterquality_001", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am reviewing historical monitoring records for a reach of the middle Rio Grande and need to select two monitoring stations suitable for observing wastewater impacts on the main channel. Starting from RIO GRANDE AT EMBUDO, NM and proceeding downstream, retain only stations that are confirmed to lie on the Rio Grande mainstem. Then, find the first mainstem monitoring station downstream of the Town of Bernalillo wastewater treatment plant outfall that meets the following conditions; continuing further downstream, find the first mainstem monitoring station that has passed both the Town of Bernalillo WWTP outfall and the Rio Rancho No. 2 WWTP outfall and meets the same conditions. Both stations must satisfy: the station itself is not an outfall, facility, well, canal, or drainage ditch; the type on the station detail page is labeled as River/Stream; records for the four characteristic groups Microbiological, Nutrient, Organics, Other, and Physical fully cover 2015–2020; and the start years for both Microbiological and Physical records are earlier than 2010. Finally, output a single-line string in upstream-to-downstream order: ||, with the two segments separated by a comma.", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "Output a single-line string in upstream-to-downstream order: ||, with the two segments separated by a comma.", + "oracle_answer": "SANDIAWQ_WQX-RG003|2004|2004,SANDIAWQ_WQX-RG008|2004|2004", + "metadata": { + "State-Gated Retrieval": [ + "Select two target stations only from Rio Grande mainstem monitoring stations downstream of RIO GRANDE AT EMBUDO, NM, and both must have passed the specified outfall locations.", + "The station detail page must explicitly show River/Stream, and records for the four characteristic groups Microbiological, Nutrient, Organics, Other, and Physical must fully cover 2015–2020, while the start years for both Microbiological and Physical must be earlier than 2010.", + "Output the two final stations in upstream-to-downstream order." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "provider/list views yield the Rio Grande mainstem candidates downstream of the Bernalillo and Rio Rancho No. 2 discharge points", + "detail pages yield flow position, location type, characteristic-group period-of-record coverage for 2015-2020, and the Microbiological/Physical baseline years", + "final rows are produced only after the corrected downstream sentry stations are fixed and ordered from upstream to downstream" + ], + "control_dependency": [ + "provider-list stream tags are only provisional and must be confirmed on the detail page by both mainstem placement and location type", + "target-window presence is insufficient until full 2015-2020 coverage is confirmed on the detail page for all four groups", + "once RG002/RG007 fail the full detail-page checks, the workflow must continue downstream from the discharge-point starting position to RG003/RG008" + ], + "freeze": { + "historical_window": "Rio Grande mainstem stations downstream of the Town of Bernalillo and Rio Rancho No. 2 WWTP outfalls, validated against 2015-2020 coverage for Microbiological, Nutrient, Organics, Other, and Physical" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Select two target stations only from Rio Grande mainstem monitoring stations downstream of RIO GRANDE AT EMBUDO, NM, and both must have passed the specified outfall locations.", + "The station detail page must explicitly show River/Stream, and records for the four characteristic groups Microbiological, Nutrient, Organics, Other, and Physical must fully cover 2015–2020, while the start years for both Microbiological and Physical must be earlier than 2010.", + "Output the two final stations in upstream-to-downstream order." + ], + "exclusion_conditions": [ + "Exclude stations that have only a superficial (Stream) tag on the provider list or have records near the target window, but whose detail page does not satisfy the flow position, location type, or complete period-of-record conditions.", + "Exclude locations that are outfalls, facilities, wells, canals, or drainage ditches.", + "Exclude candidates such as RG002 and RG007 that are not the qualifying sentry stations downstream of the corresponding outfalls." + ], + "normalization": { + "record_separator": ",", + "field_separator": "|", + "schema_per_record": [ + "MonitoringLocationIdentifier", + "Microbiological_start_year", + "Physical_start_year" + ], + "ordering": "emit exactly two records from upstream to downstream", + "station_id": "use uppercase MonitoringLocationIdentifier", + "year_fields": "emit four-digit years as plain integers", + "selection": { + "record_1": "the first qualifying mainstem station below the Bernalillo outfall", + "record_2": "the first qualifying mainstem station below both the Bernalillo and Rio Rancho No. 2 outfalls" + }, + "stop_condition": [ + "the Bernalillo branch stops only after its first qualifying mainstem station is fixed", + "the Rio Rancho No. 2 branch stops only after its first qualifying mainstem station is fixed", + "the two segments are emitted as one comma-joined line in upstream-to-downstream order" + ] + } + } +} diff --git a/data_en/constraint/waterquality_002.json b/data_en/constraint/waterquality_002.json new file mode 100644 index 0000000000000000000000000000000000000000..530a466744c0b1d2ca44578c3e2d6f32f2ac3cb3 --- /dev/null +++ b/data_en/constraint/waterquality_002.json @@ -0,0 +1,67 @@ +{ + "task_id": "waterquality_002", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am analyzing trends in the lower Rio Grande from 2001 to 2010. From monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002, select one representative station for Hidalgo County and one for Cameron County. First, screen candidate stations for each county within the specified area. Retain only stations whose detail page lists the type as River/Stream and that have records covering 2001–2010 for all four characteristic groups: Microbiological, Nutrient, Organics, Other, and Physical. If multiple stations in the same county qualify, select the station with the earliest year in which all four groups are simultaneously present. Then record the MonitoringLocationIdentifier of the selected station, the earliest year all four groups are simultaneously present, and the start year for each of Microbiological, Nutrient, Organics, Other, and Physical. Finally, output a single-line string in the order Hidalgo then Cameron: :|||||, with the two segments separated by a comma.", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "Output a single-line string in the order Hidalgo then Cameron: :|||||, with the two segments separated by a comma.", + "oracle_answer": "Hidalgo:TCEQMAIN-15808|1998|1998|1998|1998|1998,Cameron:TCEQMAIN-13177|1995|1981|1981|1995|1981", + "metadata": { + "State-Gated Retrieval": [ + "Select one representative station for Hidalgo County and one for Cameron County from monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002.", + "Candidate detail pages must list the type as River/Stream, and records for all four characteristic groups (Microbiological, Nutrient, Organics, Other, Physical) must cover 2001–2010.", + "If multiple stations in the same county qualify, select the station with the earliest year in which all four groups are simultaneously present." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the fixed downstream starting point and county split yield Hidalgo and Cameron candidate mainstem stations within HUC 13090002", + "detail pages yield River/Stream validity, the four characteristic-group start years, and the earliest year when all four groups are simultaneously present for 2001-2010 coverage", + "final rows are produced only after the county-specific searches are rerun from the fixed downstream starting point and then ranked by common-start year" + ], + "control_dependency": [ + "the Hidalgo search must preserve the \"below TCEQMAIN-13664\" downstream starting point rather than returning to the anchor station itself", + "a station is only provisional until all four characteristic groups are confirmed for the same MonitoringLocationIdentifier and tidal/intake conflicts are excluded on the detail page", + "county winners are valid only after late-start and non-river candidates are removed and the common-start-year tie-break is recomputed" + ], + "freeze": { + "historical_window": "stations below RIO GRANDE BELOW ANZALDUAS within HUC 13090002, split by Hidalgo and Cameron County, with Microbiological, Nutrient, Organics, Other, and Physical coverage over 2001-2010" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Select one representative station for Hidalgo County and one for Cameron County from monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002.", + "Candidate detail pages must list the type as River/Stream, and records for all four characteristic groups (Microbiological, Nutrient, Organics, Other, Physical) must cover 2001–2010.", + "If multiple stations in the same county qualify, select the station with the earliest year in which all four groups are simultaneously present." + ], + "exclusion_conditions": [ + "Exclude results where the Hidalgo search loses the downstream starting point and brings the starting station itself back into the candidate set.", + "Exclude results that treat a single multi-select of the four characteristic groups as sufficient without verifying that all four belong to the same station ID.", + "Exclude stations with tidal, intake, late-start, or other conflicts clearly indicated on the detail page." + ], + "normalization": { + "record_separator": ",", + "field_separator": "|", + "schema_per_record": [ + "County:MonitoringLocationIdentifier", + "common_start_year", + "Microbiological_start_year", + "Nutrient_start_year", + "Organics_Other_start_year", + "Physical_start_year" + ], + "ordering": "emit exactly two records, with Hidalgo first and Cameron second", + "county_prefix": "use the county label in title case, followed by : and the uppercase MonitoringLocationIdentifier", + "year_fields": "emit four-digit years as plain integers", + "common_start_year": "the earliest year in which all four required groups are simultaneously present for the chosen county station", + "stop_condition": [ + "each county branch is rerun until one River/Stream station survives all four group checks", + "the county winner is fixed only after late-start and non-river candidates are excluded after checking the detail page", + "the two county segments are emitted on one line in the fixed Hidalgo-then-Cameron order" + ] + } + } +} diff --git a/data_en/constraint/waterquality_003.json b/data_en/constraint/waterquality_003.json new file mode 100644 index 0000000000000000000000000000000000000000..08171a8f0fa507da712fa0bac67294f7a8adf673 --- /dev/null +++ b/data_en/constraint/waterquality_003.json @@ -0,0 +1,66 @@ +{ + "task_id": "waterquality_003", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "I am compiling 2012–2018 water quality reference data for the Brazos River mainstem downstream of Brazos Rv at Waco, TX. I want to select one TCEQ monitoring station suitable as a long-term reference point in each of the three HUCs (12060202, 12070101, 12070104) that the mainstem passes through. Process as follows: first, within the Brazos River mainstem reach downstream of Brazos Rv at Waco, TX, screen candidate stations in HUCs 12060202, 12070101, and 12070104 respectively; retain only monitoring locations whose detail page labels them as River/Stream and whose station name still corresponds to the Brazos River mainstem rather than another named waterbody. Next, check the record categories for these stations, retaining only those that cover 2012–2018 for all five categories: Inorganics, Major, Non-metals; Microbiological; Nutrient; Organics, Other; and Physical. Specifically, the station start year must be no later than 2012 and the end year no earlier than 2018. Finally, list the 3 results in order from upstream to downstream, each row formatted as: |||||||.", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "List the 3 results in order from upstream to downstream, each row formatted as: |||||||.", + "oracle_answer": "12060202|TCEQMAIN-12037|2000|1991|2000|1991|1999|1991\n12070101|TCEQMAIN-12030|2006|1972|1972|1972|2006|1972\n12070104|TCEQMAIN-11848|1975|1974|1975|1974|1975|1974", + "metadata": { + "State-Gated Retrieval": [ + "The search must stay anchored downstream of Waco and look for Brazos mainstem monitoring stations within the three HUCs specified in the task.", + "Each candidate station must be checked separately across the five characteristic groups and then matched back to the same station ID, after which the detail page must verify full 2012–2018 coverage and mainstem semantics.", + "For each HUC, retain only the qualifying station with the earliest common start year, and output the start-year fields required by the task." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the fixed downstream starting point below Waco and the three target HUC searches yield the Brazos mainstem candidate stations", + "detail pages yield true downstream position, mainstem-vs-tributary semantics, and five-group period-of-record coverage across 2012-2018", + "final rows are produced only after the three HUC-specific searches are carried out, matched by station ID, and ranked by the earliest year when all five groups are jointly available" + ], + "control_dependency": [ + "the workflow must stay anchored downstream of Waco rather than reintroducing upstream stations such as TCEQMAIN-12044", + "name-based waterbody matches must be validated on the detail page by excluding tributaries such as LITTLE BRAZOS RIVER and confirming full-window coverage", + "station ranking must be determined after false positives from partial-window records are removed" + ], + "freeze": { + "historical_window": "Brazos River mainstem stations downstream of the Waco anchor, split across HUC 12060202, 12070101, and 12070104, with five characteristic groups covering 2012-2018" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "The search must stay anchored downstream of Waco and look for Brazos mainstem monitoring stations within the three HUCs specified in the task.", + "Each candidate station must be checked separately across the five characteristic groups and then matched back to the same station ID, after which the detail page must verify full 2012–2018 coverage and mainstem semantics.", + "For each HUC, retain only the qualifying station with the earliest common start year, and output the start-year fields required by the task." + ], + "exclusion_conditions": [ + "Exclude results that lose the downstream starting point below Waco and bring upstream stations back into the candidate set.", + "Exclude results that mistake tributaries such as LITTLE BRAZOS RIVER for the Brazos mainstem.", + "Exclude stations that have data near the query window but do not cover the entire 2012–2018 window." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "HUC", + "MonitoringLocationIdentifier", + "common_start_year", + "Inorganics_start", + "Microbiological_start", + "Nutrient_start", + "Organics_Other_start", + "Physical_start" + ], + "HUC": "preserve the HUC exactly as emitted in the source result", + "MonitoringLocationIdentifier": "preserve the monitoring-location identifier exactly, for example `TCEQMAIN-12037`", + "common_start_year": "emit the maximum of the five per-group start years", + "selection_rule": "only keep mainstem river/stream sites whose five required groups all cover the target 2012-2018 window", + "sorting_or_selection": "upstream to downstream along the mainstem" + } + } +} diff --git a/data_en/constraint/waterquality_004.json b/data_en/constraint/waterquality_004.json new file mode 100644 index 0000000000000000000000000000000000000000..18640c8b14b486ae5c84726ea31210335f6fc523 --- /dev/null +++ b/data_en/constraint/waterquality_004.json @@ -0,0 +1,67 @@ +{ + "task_id": "waterquality_004", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "I am reviewing toxic-pollutant-related water quality monitoring data for 1993–2001 along the Trinity River mainstem, bounded upstream by the reach near FM 85 and downstream by the reach near Interstate 10. I need to select one TCEQ long-term reference station for each of the upper, middle, and lower segments.\n\nStarting from the Trinity River mainstem between the reach near FM 85 and the reach near Interstate 10, screen candidate monitoring locations in the upper, middle, and lower segments. Retain only stations whose record is tagged as River/Stream and whose name still refers to the Trinity River mainstem, not to other named water bodies or distributaries. Then check the record categories for these stations; keep only those that have all six record categories covering 1993–2001 (i.e., the start year is no later than 1993 and the end year is no earlier than 2001). Output the results from upstream to downstream.\n\nFinally, list three rows from upstream to downstream along the river, each in the format: ||||||||.", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "List three rows from upstream to downstream along the river, each in the format: ||||||||.", + "oracle_answer": "12030105|TCEQMAIN-10924|1983|1982|1983|1982|1983|1983|1982\n12030202|TCEQMAIN-10897|1993|1969|1972|1972|1993|1974|1969\n12030203|TCEQMAIN-10892|1976|1969|1971|1972|1974|1976|1969", + "metadata": { + "State-Gated Retrieval": [ + "Screen only among candidate stations where Trinity River mainstem semantics hold, and require all six characteristic groups to cover 1993–2001.", + "The six groups must be searched separately and then matched back to the same station ID, after which the detail page must verify full-window coverage and legacy toxics group completeness.", + "For each target segment, retain only the station that meets all group requirements and has the best common start year." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Trinity River mainstem candidate stations are generated from the target HUC searches and the six characteristic-group searches", + "detail pages yield River/Stream validity, 1993–2001 full-window coverage, and the group-specific start years needed for ranking", + "final rows are produced only after all six groups have been matched by station ID and detail-page validation removes partial-group and non-mainstem false positives" + ], + "control_dependency": [ + "each of the six characteristic groups must be evaluated separately and confirmed against the same station ID before a multi-select result can be retained", + "station names and River/Stream tags are insufficient until the detail page confirms Trinity mainstem semantics and 1993–2001 full-window coverage", + "candidate rejection and final ranking must be determined after applying the PCBs / Organics, Other gap checks" + ], + "freeze": { + "historical_window": "Trinity River mainstem stations validated against six characteristic groups over 1993–2001, with ranking based on the earliest joint availability and group start years" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Screen only among candidate stations where Trinity River mainstem semantics hold, and require all six characteristic groups to cover 1993–2001.", + "The six groups must be searched separately and then matched back to the same station ID, after which the detail page must verify full-window coverage and legacy toxics group completeness.", + "For each target segment, retain only the station that meets all group requirements and has the best common start year." + ], + "exclusion_conditions": [ + "Exclude results that mistakenly treat a single multi-select of characteristic groups as sufficient to satisfy the requirement.", + "Exclude results that only check station names and River/Stream tags without verifying 1993–2001 full-window coverage.", + "Exclude stations that ignore missing PCBs or Organics, Other groups." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "HUC", + "MonitoringLocationIdentifier", + "common_start_year", + "Inorganics_start", + "Microbiological_start", + "Nutrient_start", + "Organics_Other_start", + "Organics_PCBs_start", + "Physical_start" + ], + "HUC": "preserve the HUC exactly as emitted in the source result", + "MonitoringLocationIdentifier": "preserve the monitoring-location identifier exactly, for example `TCEQMAIN-10924`", + "common_start_year": "emit the maximum of the six per-group start years", + "selection_rule": "only keep mainstem river/stream sites whose six required groups all cover the target window", + "sorting_or_selection": "upstream to downstream along the mainstem" + } + } +} diff --git a/data_en/constraint/waterquality_005.json b/data_en/constraint/waterquality_005.json new file mode 100644 index 0000000000000000000000000000000000000000..248adddb44349866355efabf9d7dc43e6e507dd5 --- /dev/null +++ b/data_en/constraint/waterquality_005.json @@ -0,0 +1,68 @@ +{ + "task_id": "waterquality_005", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 9, + "instruction": "I am organizing integrated water-quality records for the lower Neches River during 1978-1984. Starting downstream from NECHES RIVER AT CR 4915, I want to identify the nearest TCEQ long-term reference station that still represents the inland Neches River mainstem, and then tabulate the start year of nine Characteristic Groups at that station. Search downstream along the mainstem and retain only monitoring stations whose detail page labels the site type as River/Stream. Exclude stations located in lake or reservoir waters or in the Sabine-Neches outlet boundary reach. Among stations that satisfy these location conditions, identify the nearest qualifying station for which all nine record categories cover 1978-1984: Biological, Algae, Phytoplankton; Inorganics, Major, Non-metals; Inorganics, Minor, Metals; Microbiological; Nutrient; Organics, Other; Organics, PCBs; Organics, Pesticide; and Physical. Finally, output a table for that final station, one row per Characteristic Group, with columns rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year. The row order is fixed as Biological, Algae, Phytoplankton; Inorganics, Major, Non-metals; Inorganics, Minor, Metals; Microbiological; Nutrient; Organics, Other; Organics, PCBs; Organics, Pesticide; Physical.", + "start_url": "https://www.waterqualitydata.us/provider/STORET/TCEQMAIN/TCEQMAIN-10598/", + "output_format": "Output a 9-row table with columns rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year.", + "oracle_answer": "1|TCEQMAIN-10580|12020003|Hardin County|Biological, Algae, Phytoplankton|1972|1977\n2|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Major, Non-metals|1971|1977\n3|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Minor, Metals|1974|1977\n4|TCEQMAIN-10580|12020003|Hardin County|Microbiological|1972|1977\n5|TCEQMAIN-10580|12020003|Hardin County|Nutrient|1972|1977\n6|TCEQMAIN-10580|12020003|Hardin County|Organics, Other|1974|1977\n7|TCEQMAIN-10580|12020003|Hardin County|Organics, PCBs|1974|1977\n8|TCEQMAIN-10580|12020003|Hardin County|Organics, Pesticide|1977|1977\n9|TCEQMAIN-10580|12020003|Hardin County|Physical|1971|1977", + "metadata": { + "State-Gated Retrieval": [ + "Search only among TCEQ monitoring stations downstream of NECHES RIVER AT CR 4915 that still represent the inland Neches River mainstem.", + "A candidate station must cover 1978-1984 in all nine Characteristic Groups and, on the detail page, must still qualify as River/Stream, outside lake or reservoir waters, and outside the Sabine-Neches outlet boundary reach.", + "The final output must be centered on the single winning station and list group_start_year plus common_start_year row by row in the fixed nine-group order." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the fixed downstream starting point at NECHES RIVER AT CR 4915 yields candidate inland mainstem stations across successive downstream HUCs", + "detail pages yield River/Stream validity, inland-vs-boundary semantics, and nine-group period-of-record coverage across 1978-1984", + "final rows are produced only after one winning station survives the inland-mainstem checks and the requirement that all nine groups match the same station, after which its nine group start years are emitted in the required order" + ], + "control_dependency": [ + "the nearest downstream mainstem station remains provisional until all nine characteristic groups have been checked separately and matched back to the same station ID", + "the downstream search must continue to the next mainstem HUC when the first candidate fails the nine-group coverage requirement", + "location semantics remain valid only after detail-page exclusion of lake/reservoir and Sabine-Neches boundary stations" + ], + "freeze": { + "historical_window": "Neches River inland mainstem stations downstream of NECHES RIVER AT CR 4915, validated within the fixed 1978-1984 window against nine characteristic groups as largely stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Search only among TCEQ monitoring stations downstream of NECHES RIVER AT CR 4915 that still represent the inland Neches River mainstem.", + "A candidate station must cover 1978-1984 in all nine Characteristic Groups and, on the detail page, must still qualify as River/Stream, outside lake or reservoir waters, and outside the Sabine-Neches outlet boundary reach.", + "The final output must be centered on the single winning station and list group_start_year plus common_start_year row by row in the fixed nine-group order." + ], + "exclusion_conditions": [ + "Exclude results that retain TCEQMAIN-10591 merely because it appears to be the nearest downstream mainstem station.", + "Exclude results that do not check the nine Characteristic Groups separately and verify that they all belong to the same station ID.", + "Exclude stations located in lake or reservoir waters or in the Sabine-Neches outlet boundary reach." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "MonitoringLocationIdentifier", + "HUC", + "County", + "characteristic_group", + "group_start_year", + "common_start_year" + ], + "rank": "emit 1 through 9 in the fixed characteristic-group order required by the task", + "MonitoringLocationIdentifier": "use uppercase MonitoringLocationIdentifier", + "HUC": "emit the HUC as an 8-digit string with no separators", + "County": "use the county name exactly as shown on the detail page", + "characteristic_group": "preserve the group label exactly as listed in the task", + "year_fields": "emit four-digit years as plain integers", + "common_start_year": "repeat the earliest year in which all nine required groups are simultaneously present for the chosen station", + "sorting_or_selection": "emit rows in the fixed nine-group order stated in the task" + } + } +} diff --git a/data_en/constraint/wonder_001.json b/data_en/constraint/wonder_001.json new file mode 100644 index 0000000000000000000000000000000000000000..b266bb77321ef7e279d5d7d666e8823fe7ea7c32 --- /dev/null +++ b/data_en/constraint/wonder_001.json @@ -0,0 +1,64 @@ +{ + "task_id": "wonder_001", + "domain": "CDC_WONDER", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "I am preparing a public health brief on changes in U.S. home births in 2020. I need to identify months where the home-birth rate among all mothers increased by at least 25% compared to the same month in 2019, and also examine the corresponding changes for non-Hispanic Black mothers and Hispanic mothers in those months. First, compare the home-birth rates for all mothers by calendar month between 2019 and 2020, retaining only months in 2020 where the rate increased by at least 25% relative to the same month in 2019. Then, for those months, add the 2020 home-birth rates for non-Hispanic Black mothers and Hispanic mothers, along with their changes relative to the same month in 2019. Finally, output a multi-row pipe-delimited table in calendar month order with the fixed header: month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel. All numeric values should be plain numbers without percent signs.", + "start_url": "https://wonder.cdc.gov/natality-expanded-current.html", + "output_format": "Output a multi-row pipe-delimited table in calendar month order with the fixed header: month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel. All numeric values should be plain numbers without percent signs.", + "oracle_answer": "month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel\nMay|1.03|1.49|45|0.74|54|0.55|57\nJune|1.04|1.31|26|0.66|20|0.48|30\nJuly|1.03|1.30|26|0.68|42|0.48|30\nAugust|1.02|1.29|26|0.69|50|0.48|26\nSeptember|1.01|1.31|30|0.73|43|0.54|54\nOctober|1.00|1.28|28|0.75|50|0.47|27\nNovember|0.99|1.30|31|0.73|43|0.55|67\nDecember|0.92|1.28|39|0.80|63|0.53|61", + "metadata": { + "State-Gated Retrieval": [ + "First, compare the home-birth rates for all mothers by calendar month between 2019 and 2020, retaining only months in 2020 where the rate increased by at least 25% relative to the same month in 2019.", + "The home-birth numerator must use the full home category, not Home intended alone.", + "For those months, add the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, along with their changes relative to the same month in 2019." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Monthly natality queries yield the 2019 vs 2020 home-birth rates for all mothers and the candidate month set.", + "Follow-up race/ethnicity queries yield the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, plus their same-month changes versus 2019.", + "Final rows are produced only after qualifying months are determined from rate growth, and the resulting month set is reused for both subgroup backfill chains." + ], + "control_dependency": [ + "Month selection must be based on relative rate increase rather than counts alone.", + "The home-birth numerator must use Residence or an equivalent full-home measure rather than Home intended alone before downstream subgroup queries run.", + "Subgroup columns must be generated from the resulting month set rather than appended to earlier rows." + ], + "freeze": { + "historical_window": "2019 and 2020 U.S. natality monthly home-birth rates for all mothers, non-Hispanic Black mothers, and Hispanic mothers." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "First, compare the home-birth rates for all mothers by calendar month between 2019 and 2020, retaining only months in 2020 where the rate increased by at least 25% relative to the same month in 2019.", + "The home-birth numerator must use the full home category, not Home intended alone.", + "For those months, add the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, along with their changes relative to the same month in 2019." + ], + "exclusion_conditions": [ + "Exclude month-row sets that misinterpret \"rate increase of at least 25%\" as \"count increase of at least 25%.\"", + "Exclude results that use only the Home intended category instead of the full home numerator.", + "Exclude results that add subgroup columns to an incorrect month set." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "Required literal first row: month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel", + "schema": [ + "month", + "all_2019", + "all_2020", + "all_rel", + "black_2020", + "black_rel", + "hispanic_2020", + "hispanic_rel" + ], + "month": "Use the English month name and keep calendar order.", + "numeric_fields": "All numeric outputs are plain numbers without a percent sign.", + "relative_change_fields": "all_rel, black_rel, and hispanic_rel are emitted as integer percentages without the `%` character." + } + } +} diff --git a/data_en/constraint/wonder_002.json b/data_en/constraint/wonder_002.json new file mode 100644 index 0000000000000000000000000000000000000000..90c61db052521d46949f8749a419445031a2f0a7 --- /dev/null +++ b/data_en/constraint/wonder_002.json @@ -0,0 +1,64 @@ +{ + "task_id": "wonder_002", + "domain": "CDC_WONDER", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "I am preparing a one-page public health brief on 2021 U.S. infant mortality disparities. I want to identify groups that are separately listed in the report by mother's race and Hispanic origin, have an infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death. First, from the separately listed groups in the report, select those with an infant mortality rate above the U.S. overall rate and a clearly identifiable leading cause of death. Then, for each qualifying group, record the full-year infant mortality rate, the neonatal rate (under 28 days), and the postneonatal rate (28 days and older), along with the group's leading cause of death, its cause-specific rate, and the rank of that cause among all infant causes. Finally, output a multi-row pipe-delimited table sorted by full-year infant mortality rate from high to low: group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank.", + "start_url": "https://wonder.cdc.gov/lbd-current-expanded.html", + "output_format": "Finally, output a multi-row pipe-delimited table sorted by full-year infant mortality rate from high to low: group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank.", + "oracle_answer": "group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank\nnon-Hispanic Black|10.55|6.35|4.19|Short gestation and low birth weight|196.4|2\nnon-Hispanic American Indian or Alaska Native|7.46|3.83|3.67|Congenital malformations|134.0|1\nPuerto Rican|6.05|3.93|2.13|Short gestation and low birth weight|108.9|2", + "metadata": { + "State-Gated Retrieval": [ + "Retain only groups that are separately listed in the 2021 U.S. infant mortality statistics, have a full-year infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death.", + "For each qualifying group, provide the infant rate, neonatal rate, postneonatal rate, top cause, cause rate, and the rank of that cause among all infant causes.", + "The leading cause must be determined by a group-level leading-cause query and verified for availability using notes/reliability markers." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "infant-mortality queries yield group-level overall, neonatal, and postneonatal rates for reportable mother race/Hispanic-origin groups", + "leading-cause queries and reliability notes yield each eligible group's top cause, cause-specific rate, and U.S. rank", + "final rows are produced only after the eligible-group set is rebuilt using both overall-rate and cause-specific-identifiability criteria" + ], + "control_dependency": [ + "groups above the U.S. overall rate cannot be accepted until cause-specific reliability checks are run, which removes NHOPI", + "leading cause must be queried at the group level rather than inherited from an all-infants cause table", + "the cause-rate multiplier must be defined as per 100,000 live births before downstream ranking/output" + ], + "freeze": { + "historical_window": "2021 U.S. infant mortality by mother race and Hispanic origin, including the group-level leading-cause tables and reliability notes" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only groups that are separately listed in the 2021 U.S. infant mortality statistics, have a full-year infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death.", + "For each qualifying group, provide the infant rate, neonatal rate, postneonatal rate, top cause, cause rate, and the rank of that cause among all infant causes.", + "The leading cause must be determined by a group-level leading-cause query and verified for availability using notes/reliability markers." + ], + "exclusion_conditions": [ + "Exclude groups that, despite having a full-year mortality rate above the U.S. overall rate, cannot provide a clearly identifiable leading cause due to cause-specific reliability issues.", + "Exclude results that only inherit the top cause from the all-infants cause table without performing a group-level leading-cause query.", + "Exclude results where the cause_rate uses an incorrect rate multiplier and is not read at the per-100,000-live-births denominator." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row `group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank`", + "schema": [ + "group", + "infant_rate", + "neonatal_rate", + "postneonatal_rate", + "top_cause", + "cause_rate", + "us_rank" + ], + "sorting_or_selection": "infant_rate descending", + "rate_fields": "infant_rate, neonatal_rate, and postneonatal_rate are per 1,000 live births; cause_rate is per 100,000 live births, but all four are emitted as plain numbers without unit text", + "top_cause": "emit the short cause label used in the oracle, not an expanded prose description", + "us_rank": "emit the integer rank of that same cause in the overall infant leading-cause list" + } + } +} diff --git a/data_en/goal/arxiv_001-g.json b/data_en/goal/arxiv_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..bd948410eddee2d0f52ad722d5bd743e7ebe647b --- /dev/null +++ b/data_en/goal/arxiv_001-g.json @@ -0,0 +1,94 @@ +{ + "task_id": "arxiv_001-g", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "I am organizing the research trajectory of dataset distillation and dataset condensation on arXiv from 2019 to 2021, aiming to identify machine learning papers that discuss using a small set of synthetic training data to replace large-scale training sets. From the 2019–2021 arXiv records, retain only entries whose primary category is Machine Learning; if a paper is only cross-listed into Machine Learning by another primary category, do not include it. Additionally, these papers must have a revision within the next calendar year after the initial submission, and the current record must still clearly indicate a subsequent publication venue. Output a table sorted by v1 submitted in ascending order, with columns: arXiv ID, term family, cue location, v1 submitted, first next-year version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying entries exist, output NONE.", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "Output a table sorted by v1 submitted in ascending order, with columns: arXiv ID, term family, cue location, v1 submitted, first next-year version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying entries exist, output NONE.", + "oracle_answer": "arXiv ID|term family|cue location|v1 submitted|first next-year version|date of that version|primary category|publication-trail source|current publication clue\n1910.02551|Distillation|Title|2019-10-06|v3|2020-05-05|cs.LG|Related DOI|10.1109/IJCNN52387.2021.9533769\n2011.00050|Distillation|Abstract-only|2020-10-30|v2|2021-03-02|cs.LG|Comments|Accepted to ICLR 2021\n2107.13034|Distillation|Title|2021-07-27|v3|2022-01-17|cs.LG|Comments|NeurIPS 2021\n2110.04181|Condensation|Title|2021-10-08|v2|2022-04-21|cs.LG|Journal reference|Proceedings of the IEEE/CVF Winter Conference on Applications of Computer Vision 2023 (WACV)", + "metadata": { + "State-Gated Retrieval": [ + "Only include arXiv records where v1 submitted falls between 2019-01-01 and 2021-12-31.", + "The title or abstract must explicitly use terms from the dataset distillation or dataset condensation family, and the semantics must refer to replacing large-scale training sets with a small set of synthetic training data.", + "The current primary category must be cs.LG; if a paper is only cross-listed into Machine Learning by another primary category, do not include it.", + "The paper must have a revision within the next calendar year after the initial submission, and the current record must still clearly indicate a subsequent publication venue." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Root searches yield candidate arXiv IDs", + "Each candidate abstract page yields primary category, v1 date, first next-year version, cue location, and publication-trail source", + "Answer rows are produced only after deduplication and detail-page validation" + ], + "control_dependency": [ + "Records must be filtered by original submission year, with per-record validation that a version in the next calendar year exists", + "Cross-listed-only hits must be excluded, and the current primary category must be validated on abstract pages", + "Searches must cover both Title and Abstract because valid distillation hits can appear only in the abstract", + "Topic matches without a current publication trail still fail until the Comments, Journal reference, or Related DOI field is checked on the abstract page" + ], + "freeze": { + "historical_window": "v1 year in {2019, 2020, 2021}" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only include arXiv records where v1 submitted falls between 2019-01-01 and 2021-12-31.", + "The title or abstract must explicitly use terms from the dataset distillation or dataset condensation family, and the semantics must refer to replacing large-scale training sets with a small set of synthetic training data.", + "The current primary category must be cs.LG; if a paper is only cross-listed into Machine Learning by another primary category, do not include it.", + "The paper must have a revision within the next calendar year after the initial submission, and the current record must still clearly indicate a subsequent publication venue." + ], + "exclusion_conditions": [ + "Exclude records whose current primary category is not cs.LG and that are only cross-listed to cs.LG.", + "Exclude records where the title or abstract contains distillation/condensation terms but does not correspond to the dataset distillation or dataset condensation research line.", + "Exclude records that have no version revision in the next calendar year, or whose current record contains no clearly visible publication clue." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "term family", + "cue location", + "v1 submitted", + "first next-year version", + "date of that version", + "primary category", + "publication-trail source", + "current publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "term_family_extraction": { + "allowed_families": [ + "Distillation", + "Condensation" + ], + "tie_break": "if both families appear, prefer the title hit; if both appear only in the abstract, keep the first abstract occurrence" + }, + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_trail_source": [ + "Comments", + "Journal reference", + "Related DOI" + ], + "current_publication_clue": "keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue", + "sorting_or_selection": { + "primary": "v1 submitted ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all four corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the abstract page, current browse context, and publication-trail fields are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_en/goal/arxiv_002-g.json b/data_en/goal/arxiv_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..cf67f4f8574b167d05bdcfcacd3c08c028757bc6 --- /dev/null +++ b/data_en/goal/arxiv_002-g.json @@ -0,0 +1,88 @@ +{ + "task_id": "arxiv_002-g", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 10, + "instruction": "I am compiling a reading list of 2022 research on reasoning prompting for large language models. From arXiv papers whose first version (v1) was submitted in 2022, I want to select those whose title or abstract explicitly focuses on chain-of-thought or self-consistency reasoning and whose primary category is Computation and Language. Candidate papers must also have a version update in 2023, and the current arXiv record's Comments field must directly indicate a subsequent publication venue. Output a table sorted by the date of each paper's earliest 2023 version in ascending order, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2023 version, date of that version, primary category, publication clue. If no qualifying papers exist, output NONE.", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "Output a table sorted by the date of each paper's earliest 2023 version in ascending order, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2023 version, date of that version, primary category, publication clue. If no qualifying papers exist, output NONE.", + "oracle_answer": "arXiv ID|cue family|cue location|v1 submitted|first 2023 version|date of that version|primary category|publication clue\n2210.01240|Chain-of-thought|Title + Abstract|2022-10-03|v2|2023-01-25|cs.CL|Published as a conference paper at ICLR 2023\n2205.11916|Chain-of-thought|Abstract-only|2022-05-24|v4|2023-01-29|cs.CL|Accepted to NeurIPS2022\n2203.11171|Self-consistency; Chain-of-thought|Title + Abstract|2022-03-21|v4|2023-03-07|cs.CL|Published at ICLR 2023; camera ready version at ICLR 2023\n2210.03629|Chain-of-thought|Abstract-only|2022-10-06|v3|2023-03-10|cs.CL|v3 is the ICLR camera ready version\n2210.03350|Chain-of-thought|Abstract-only|2022-10-07|v2|2023-05-23|cs.CL|To appear at Findings of EMNLP 2023\n2212.10001|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-01|cs.CL|ACL-23 Camera Ready\n2212.08061|Chain-of-thought|Abstract-only|2022-12-15|v2|2023-06-04|cs.CL|ACL 2023 Main Conference\n2212.10071|Chain-of-thought|Abstract-only|2022-12-20|v2|2023-06-13|cs.CL|ACL 2023 camera-ready\n2212.10509|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-23|cs.CL|ACL'23 Camera Ready\n2211.12588|Chain-of-thought; Self-consistency|Abstract-only|2022-11-22|v4|2023-10-23|cs.CL|Published at TMLR 2023", + "metadata": { + "State-Gated Retrieval": [ + "Only retain arXiv papers whose v1 was submitted in 2022.", + "The title or abstract must explicitly contain cues related to chain-of-thought or self-consistency.", + "The current primary category must be cs.CL; do not include records that are only cross-listed from other primary categories.", + "The paper must have a version update in 2023, and the current Comments field must clearly indicate a subsequent publication venue." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "root searches yield candidate arXiv IDs", + "each candidate abstract page yields primary category, v1 date, first 2023 version, comments/publication clue", + "answer rows are produced only after deduplication and detail-page validation" + ], + "control_dependency": [ + "searches must cover both Title and Abstract fields because valid rows can appear only in the abstract", + "cross-listed hits whose primary category is not cs.CL must be excluded, and the primary category must be validated on the abstract page", + "topic-matched hits must be validated against a current Comments publication clue before they can be accepted", + "2023 candidates must be identified by original submission year and full version-history checks, rather than by latest-date proxies" + ], + "freeze": { + "historical_window": "v1 submitted in 2022; version-history event in 2023" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only retain arXiv papers whose v1 was submitted in 2022.", + "The title or abstract must explicitly contain cues related to chain-of-thought or self-consistency.", + "The current primary category must be cs.CL; do not include records that are only cross-listed from other primary categories.", + "The paper must have a version update in 2023, and the current Comments field must clearly indicate a subsequent publication venue." + ], + "exclusion_conditions": [ + "Exclude records whose current primary category is not cs.CL, even if they appear in relevant search results.", + "Exclude records that contain only vague abbreviations or weak related hints, but whose title and abstract lack clear CoT/self-consistency semantics.", + "Exclude records that have no 2023 version update, or whose current record lacks a direct publication clue." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "cue family", + "cue location", + "v1 submitted", + "first 2023 version", + "date of that version", + "primary category", + "publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "cue_family": [ + "Chain-of-thought", + "Self-consistency" + ], + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_clue": { + "source": "Comments field only", + "extraction": "keep the shortest phrase that still preserves the current publication-status clue" + }, + "sorting_or_selection": { + "primary": "date of the earliest 2023 version ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the current browse context, Comments field, and full Submission history are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_en/goal/arxiv_003-g.json b/data_en/goal/arxiv_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..a46f93283310328c74af57b338e8e92b188dc79f --- /dev/null +++ b/data_en/goal/arxiv_003-g.json @@ -0,0 +1,89 @@ +{ + "task_id": "arxiv_003-g", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "I am compiling a reading list of early vision Transformer papers. From arXiv papers whose first version (v1) was submitted in Q4 2020, I want to select those whose title or abstract explicitly uses vision- or image-related Transformer terminology and whose primary category is Computer Vision and Pattern Recognition. Additionally, eligible papers must have had at least one updated version in 2021, and their current arXiv record must still directly indicate a subsequent publication venue. Output a table sorted in ascending order by the date of each paper's earliest 2021 version, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying papers exist, output NONE.", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "Output a table sorted in ascending order by the date of each paper's earliest 2021 version, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying papers exist, output NONE.", + "oracle_answer": "arXiv ID|cue family|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication-trail source|current publication clue\n2101.01097|Vision Transformer|Abstract-only|2020-12-30|v2|2021-01-08|cs.CV|Journal reference|IEEE Int. Conf. on Image Processing (ICIP) 2021\n2012.12556|Visual Transformer; Vision Transformer|Title + Abstract|2020-12-23|v2|2021-01-15|cs.CV|Comments; Related DOI|Accepted by TPAMI 2022; 10.1109/TPAMI.2022.3152247\n2012.00364|Image Processing Transformer|Title + Abstract|2020-12-01|v3|2021-05-28|cs.CV|Comments|CVPR 2021\n2011.08019|Vision Transformer|Title + Abstract|2020-11-16|v2|2021-06-02|cs.CV|Comments|Accepted for Publication in IJCB2021\n2010.11929|Vision Transformer|Abstract-only|2020-10-22|v2|2021-06-03|cs.CV|Comments|ICLR camera-ready version", + "metadata": { + "State-Gated Retrieval": [ + "Only include arXiv papers whose v1 submission date falls in Q4 2020.", + "The title or abstract must explicitly contain vision- or image-related Transformer terminology.", + "The current primary category must be cs.CV.", + "The paper must have had an updated version in 2021, and the current record must still directly indicate a subsequent publication venue." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "root searches yield candidate arXiv IDs", + "candidate abstract pages yield v1 submitted date, first 2021 version, primary category, cue location, and publication-trail source", + "answer rows depend on deduplication plus detail-page validation" + ], + "control_dependency": [ + "searches must cover both Title and Abstract because valid positives can appear only in the abstract", + "candidate eligibility must be determined by the original-submission date window rather than by arXiv-ID or announcement intuition", + "candidate filtering must use full Submission-history validation rather than most-recent-submission filtering", + "searches must use the broader semantic cue state rather than a ViT-only entry point, because ViT-only hits can be false positives", + "publication-trail false positives still require Comments / Journal reference / Related DOI validation before final inclusion" + ], + "freeze": { + "historical_window": "v1 submitted from 2020-10-01 through 2020-12-31; version-history event in 2021" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only include arXiv papers whose v1 submission date falls in Q4 2020.", + "The title or abstract must explicitly contain vision- or image-related Transformer terminology.", + "The current primary category must be cs.CV.", + "The paper must have had an updated version in 2021, and the current record must still directly indicate a subsequent publication venue." + ], + "exclusion_conditions": [ + "Exclude records whose current primary category is not cs.CV and are only cross-listed.", + "Exclude records that contain only weak cues such as Transformer/ViT but lack explicit vision- or image-related terminology in the title and abstract.", + "Exclude records that had no version update in 2021 or whose current record contains no direct publication clue." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "cue family", + "cue location", + "v1 submitted", + "first 2021 version", + "date of that version", + "primary category", + "publication-trail source", + "current publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "cue_family_extraction": "record every qualifying family actually present and join multiple families with `; ` in the emitted field", + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_trail_source": [ + "Comments", + "Journal reference", + "Related DOI" + ], + "current_publication_clue": "keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue", + "sorting_or_selection": { + "primary": "date of the earliest 2021 version ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the abstract page, current browse context, Comments field, Journal reference, Related DOI, and full Submission history are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_en/goal/arxiv_004-g.json b/data_en/goal/arxiv_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..7bce4895e882404550771716cdf4e2b4c0842d43 --- /dev/null +++ b/data_en/goal/arxiv_004-g.json @@ -0,0 +1,84 @@ +{ + "task_id": "arxiv_004-g", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "From arXiv papers whose first version was submitted in the first half of 2020, select those whose primary category is Machine Learning and whose title or abstract clearly focuses on certified robustness defenses. The research subject of each candidate paper must explicitly involve at least one of the following cues: randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor/poisoning, or partition aggregation. Additionally, these papers must have a version update in 2021, and the current arXiv record must still show a formal publication or acceptance destination. Output a table sorted in ascending order by the date of each paper's earliest 2021 version, with columns: arXiv ID, defense family, threat/topic cue, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "Output a table sorted in ascending order by the date of each paper's earliest 2021 version, with columns: arXiv ID, defense family, threat/topic cue, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.", + "oracle_answer": "arXiv ID|defense family|threat/topic cue|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication clue\n2002.10733|De-randomized smoothing; Randomized smoothing|patch attacks|Title + Abstract|2020-02-25|v3|2021-01-08|cs.LG|NeurIPS 2020\n2006.04062|Smoothed classifiers; Randomized smoothing|certified L2 robustness|Title + Abstract|2020-06-07|v4|2021-01-08|cs.LG|NeurIPS 2020\n2003.08904|RAB; Randomized smoothing|backdoor attacks|Title + Abstract|2020-03-19|v4|2021-02-26|cs.LG|IEEE Symposium on Security and Privacy 2023\n2006.14768|Deep Partition Aggregation|general poisoning attacks; label-flipping poisoning attacks|Title + Abstract|2020-06-26|v2|2021-03-18|cs.LG|ICLR 2021\n2002.12398|Transformation-specific smoothing; Randomized smoothing|semantic transformations|Title + Abstract|2020-02-27|v4|2021-09-17|cs.LG|2021 ACM SIGSAC Conference on Computer and Communications Security (CCS '21)", + "metadata": { + "State-Gated Retrieval": [ + "Only include arXiv papers with v1 submitted between 2020-01-01 and 2020-06-30.", + "The title or abstract must clearly focus on randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor or poisoning attacks, or partition aggregation.", + "The current primary category must be cs.LG.", + "Must have a version update in 2021, and the current record must show a formal publication or acceptance destination." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "root searches yield candidate arXiv IDs", + "candidate abstract pages yield v1 date, primary category, full Submission history, cue location, and current publication clue", + "final rows depend on deduplication plus detail-page validation" + ], + "control_dependency": [ + "candidate filtering must use the original-submission window together with full 2021 version-history validation, because valid rows can have later newest versions", + "cross-listed hits whose primary category is not the target category must be excluded, with category validation on detail pages", + "searches must cover the broader certified-defense family, including partition-aggregation and backdoor/poisoning variants, rather than smoothing-only entries", + "topic+venue hits must be confirmed by detail-history validation that a 2021 version actually exists" + ], + "freeze": { + "historical_window": "v1 submitted from 2020-01-01 through 2020-06-30; version-history event in 2021" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only include arXiv papers with v1 submitted between 2020-01-01 and 2020-06-30.", + "The title or abstract must clearly focus on randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor or poisoning attacks, or partition aggregation.", + "The current primary category must be cs.LG.", + "Must have a version update in 2021, and the current record must show a formal publication or acceptance destination." + ], + "exclusion_conditions": [ + "Exclude records whose current primary category is not cs.LG, even if semantically related.", + "Exclude records that are only broadly related to robustness, defense, or backdoor/poisoning but do not meet the required certified-defense semantics.", + "Exclude records without a 2021 version update or without a current publication clue." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "defense family", + "threat/topic cue", + "cue location", + "v1 submitted", + "first 2021 version", + "date of that version", + "primary category", + "publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "defense_family_extraction": "record every qualifying defense family actually present and join multiple families with `; ` in the emitted field", + "threat_topic_cue": "keep the shortest qualifying threat or topic cue that justifies inclusion", + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_clue": "keep the shortest phrase that still preserves venue or publication-status information", + "sorting_or_selection": { + "primary": "date of the earliest 2021 version ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the abstract page, current browse context, Comments field, and full Submission history are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_en/goal/census_001-g.json b/data_en/goal/census_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..d4f85f2a0a8285cab702367d667a879550d3b61c --- /dev/null +++ b/data_en/goal/census_001-g.json @@ -0,0 +1,68 @@ +{ + "task_id": "census_001-g", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 20, + "instruction": "Using the 2014–2018 American Community Survey 5-year estimates, identify North Carolina counties that simultaneously exhibit insufficient internet access, a high share of seniors living alone, limited transportation options, and low income. Candidate counties must meet all of the following conditions: at least 4,000 households with no internet access; a share of households with no internet access higher than the statewide share; a share of households with a householder aged 65 or older living alone higher than the statewide share; a share of households with no vehicle higher than the statewide share; and a median household income lower than the statewide median. All statewide comparisons must use the North Carolina statewide estimate from the same data release. List all qualifying counties in a single line ordered alphabetically by county name. Each county should be formatted as County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome, with counties separated by commas. Percentage fields should retain three decimal places without a percent sign.", + "start_url": "https://www.census.gov/data.html", + "output_format": "List all qualifying counties in a single line ordered alphabetically by county name. Each county should be formatted as County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome, with counties separated by commas. Percentage fields should retain three decimal places without a percent sign.", + "oracle_answer": "Beaufort County|5988|30.986|16.083|7.664|43688,Bladen County|4194|30.026|13.681|10.417|32378,Cleveland County|11599|31.449|12.469|7.825|40393,Columbus County|7371|33.045|15.148|7.958|36398,Duplin County|7574|34.773|14.370|7.424|38850,Edgecombe County|7454|34.879|13.720|11.225|35516,Halifax County|7575|35.873|14.657|11.565|34251,Lenoir County|4923|21.292|15.614|11.699|38387,Nash County|8617|23.467|13.597|7.917|48362,Richmond County|5193|28.001|13.706|9.269|36091,Robeson County|19814|43.103|11.312|9.854|33679,Rockingham County|9938|26.714|14.166|7.164|42490,Rutherford County|7583|28.783|16.033|6.335|40347,Sampson County|8216|34.907|14.088|7.686|39068,Scotland County|4971|37.909|13.910|11.470|35617,Surry County|7595|26.203|13.762|6.779|41068,Vance County|5131|30.444|12.347|11.600|37282,Wayne County|9709|20.163|11.742|8.456|42192,Wilkes County|7046|24.849|14.773|5.992|40829,Wilson County|7652|23.817|13.322|9.540|42850", + "metadata": { + "State-Gated Retrieval": [ + "Use only the 2014-2018 American Community Survey 5-year estimates for North Carolina counties, and use the North Carolina statewide value from the same release as the comparison baseline.", + "Retain only counties with at least 4,000 households with no internet access, and where the share of households with no internet access, the share of households with a householder aged 65 or older living alone, and the share of households with no vehicle are all higher than the statewide shares, while the median household income is lower than the statewide median.", + "Output the final results in alphabetical order by county name, retaining the six required fields." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2014-2018 ACS 5-year product and North Carolina county geography yield the full county candidate set plus the statewide baseline row", + "the relevant ACS tables yield no-internet households, senior-living-alone share, no-vehicle share, and median household income for each county and the state baseline", + "final rows are produced only after the 5-year product/geography setup is fixed consistently and the full county filtering chain is executed from B28002 through the downstream filters" + ], + "control_dependency": [ + "the 2018 ACS 5-year Detailed Tables product must be used instead of the 2018 ACS 1-year product", + "county coverage must be established under one consistent product-and-geography setup rather than by piecemeal fixes within the current table", + "all downstream county comparisons must use the same 5-year statewide baseline and the same all-counties geography" + ], + "freeze": { + "historical_window": "2014-2018 American Community Survey 5-year estimates for North Carolina counties, using the North Carolina statewide row from the same release as the comparison baseline" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Use only the 2014-2018 American Community Survey 5-year estimates for North Carolina counties, and use the North Carolina statewide value from the same release as the comparison baseline.", + "Retain only counties with at least 4,000 households with no internet access, and where the share of households with no internet access, the share of households with a householder aged 65 or older living alone, and the share of households with no vehicle are all higher than the statewide shares, while the median household income is lower than the statewide median.", + "Output the final results in alphabetical order by county name, retaining the six required fields." + ], + "exclusion_conditions": [ + "Exclude results that incorrectly use the 2018 ACS 1-Year Estimates Detailed Tables or any data other than the 2014-2018 5-year release.", + "Exclude results that do not use the North Carolina statewide row from the same release as the comparison baseline.", + "Exclude any county that does not satisfy every threshold or statewide comparison condition." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "NoInternetHH", + "NoInternetRatePct", + "SeniorLivingAloneSharePct", + "NoVehicleRatePct", + "MedianIncome" + ], + "county": "use the county display name including the word `County` and excluding a trailing state suffix", + "dedup_key": "county FIPS / GEOID", + "percentage_fields": "all percentage fields are plain numbers with exactly three decimal places and no percent sign", + "numeric_fields": "household counts and median income are emitted as plain integers without commas", + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "the North Carolina statewide threshold is fixed once from the designated table", + "all 100 North Carolina counties are covered under the same table/product settings", + "every surviving county is validated against all four required tables before emission" + ] + } + } +} diff --git a/data_en/goal/census_002-g.json b/data_en/goal/census_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..cf0cb366c4368f939949496d0e43a7ab3800e52d --- /dev/null +++ b/data_en/goal/census_002-g.json @@ -0,0 +1,80 @@ +{ + "task_id": "census_002-g", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "Using the 2015–2019 American Community Survey 5-year estimates, identify New Mexico counties that simultaneously exhibit large renter populations, notable language barriers, limited internet access, transportation disadvantages, low income, and rental stress. These counties are intended to assess which areas were unsuitable for replacing in-person tenant legal aid with online self-service before the pandemic. Candidate counties must meet all of the following conditions: at least 2,500 renter-occupied households; at least 500 limited-English-speaking households; a share of limited-English-speaking households higher than the statewide share; a share of households with no internet access higher than the statewide share; a share of households with no vehicle higher than the statewide share; a median household income lower than the statewide median; and rental stress higher than the statewide level. Rental stress higher than the statewide level must be demonstrated by at least one of the following: a share of renter households with a rent-to-income ratio of 35% or higher that exceeds the statewide share, or a share of renter households with more than one occupant per room that exceeds the statewide share. All comparisons of “higher than statewide” or “lower than statewide” use the New Mexico statewide value from the same data release. Output a single line with all qualifying counties sorted alphabetically by county name. Each county is written as County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath, where StressPath must be RENT, CROWD, or BOTH. Separate multiple counties with commas. Percentage fields retain three decimal places with no percent sign.", + "start_url": "https://data.census.gov/advanced", + "output_format": "Output a single line with all qualifying counties sorted alphabetically by county name. Each county is written as County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath, where StressPath must be RENT, CROWD, or BOTH. Separate multiple counties with commas. Percentage fields retain three decimal places with no percent sign.", + "oracle_answer": "Doña Ana County|28729|7883|10.127|22.612|6.079|44.172|6.391|40973|BOTH,Luna County|3482|1109|12.455|34.030|8.165|42.700|1.407|29360|RENT,McKinley County|6090|1610|7.688|50.587|10.978|27.568|16.256|33834|CROWD,San Miguel County|3443|1200|10.337|38.470|7.684|47.376|2.440|30946|RENT,Taos County|2854|652|5.387|28.844|5.726|48.823|4.555|38329|RENT", + "metadata": { + "State-Gated Retrieval": [ + "Use only New Mexico county data from the 2015–2019 American Community Survey 5-year estimates, and use the New Mexico statewide value from the same release as the comparison baseline.", + "Candidate counties must have at least 2,500 renter households, at least 500 limited-English-speaking households, and LEP share, no-internet share, and no-vehicle share all higher than the statewide values, while median household income is lower than the statewide value.", + "LEPHH must be computed by summing all four limited-English language groups in C16002. Retain only counties where at least one of Severe Rent Burden or Crowded Renter exceeds the statewide value, and write StressPath according to the rule." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2015-2019 ACS 5-year county geography yields New Mexico county candidates and the statewide baseline row", + "C16002 and the downstream housing/income tables yield LEPHH, LEP share, no-internet share, no-vehicle share, severe rent burden, crowded-renter share, and median income for counties and the state baseline", + "final rows are produced only after the LEPHH numerator is computed from all four limited-English language groups and the downstream stress-path filters are applied" + ], + "control_dependency": [ + "the LEPHH numerator must be computed from all four limited-English language groups in C16002 rather than from Spanish-only counts", + "county eligibility and StressPath labels must be determined from the LEPHH measure and statewide LEP baseline defined under that full four-group calculation", + "the RENT / CROWD / BOTH classification must be determined by evaluating the same county set against both downstream housing-stress branches" + ], + "freeze": { + "historical_window": "2015-2019 American Community Survey 5-year estimates for New Mexico counties, using the New Mexico statewide row from the same release as the comparison baseline" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Use only New Mexico county data from the 2015–2019 American Community Survey 5-year estimates, and use the New Mexico statewide value from the same release as the comparison baseline.", + "Candidate counties must have at least 2,500 renter households, at least 500 limited-English-speaking households, and LEP share, no-internet share, and no-vehicle share all higher than the statewide values, while median household income is lower than the statewide value.", + "LEPHH must be computed by summing all four limited-English language groups in C16002. Retain only counties where at least one of Severe Rent Burden or Crowded Renter exceeds the statewide value, and write StressPath according to the rule." + ], + "exclusion_conditions": [ + "Exclude results that treat Spanish-only limited-English households as the entire LEPHH count.", + "Exclude results that do not use the statewide baseline from the same release or do not recompute LEPHH/LEPSharePct/LEPShare_state.", + "Exclude counties that do not satisfy the final stress-path condition of RENT, CROWD, or BOTH." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "RenterHH", + "LEPHH", + "LEPSharePct", + "NoInternetPct", + "NoVehiclePct", + "SevereRentBurdenPct", + "CrowdedRenterPct", + "MedianIncome", + "StressPath" + ], + "county": "use the county display name including the word `County` and excluding a trailing state suffix", + "dedup_key": "county FIPS / GEOID", + "LEPHH": "sum the four designated limited-English-proficient renter-household cells before emitting the integer total", + "percentage_fields": "all percentage fields are plain numbers with exactly three decimal places and no percent sign", + "numeric_fields": "household counts and median income are emitted as plain integers without commas", + "StressPath": { + "allowed_values": [ + "RENT", + "CROWD", + "BOTH" + ], + "rule": "emit BOTH only when both the severe-rent-burden and crowded-renter signals survive; otherwise emit the single surviving label" + }, + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "all candidate counties are validated under the same geography and product settings", + "the renter scope and LEP aggregation are checked before the final line is emitted" + ] + } + } +} diff --git a/data_en/goal/census_003-g.json b/data_en/goal/census_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..6f2509cc98da5f5251aa793c27085e2c51a1c367 --- /dev/null +++ b/data_en/goal/census_003-g.json @@ -0,0 +1,73 @@ +{ + "task_id": "census_003-g", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "Using the 2013–2017 American Community Survey 5-year estimates for California counties, identify counties where, for school meal material updates and annual parent information updates, relying solely on an English-only online portal is insufficient and paper materials with offline assistance must still be retained. Candidate counties must meet all of the following conditions: population aged 5–17 at least 75,000; among the population aged 5–17, the number of people who speak English \"not well\" or \"not at all\" is at least 2,000 and its share is higher than the statewide share; share of households without internet access higher than the statewide share; median household income lower than the statewide share; and at least two of three support-need signals higher than the statewide share. The three support-need signals are: share of households with no vehicle; share of minors living in households that received SSI, cash public assistance, or Food Stamps/SNAP in the past 12 months; and share of renter-occupied households with more than one occupant per room. All comparisons of \"higher than statewide\" or \"lower than statewide\" use the California statewide value from the same data release. Output all qualifying counties in a single line sorted alphabetically by county name. Each county is written as County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath, where SupportPath uses only the three labels BENEFITS, CROWD, and MOBILITY joined by + in that fixed order. Multiple counties are separated by commas.", + "start_url": "https://data.census.gov/advanced", + "output_format": "Output all qualifying counties in a single line sorted alphabetically by county name. Each county is written as County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath, where SupportPath uses only the three labels BENEFITS, CROWD, and MOBILITY joined by + in that fixed order. Multiple counties are separated by commas.", + "oracle_answer": "Fresno County|200205|5127|2.561|20.588|8.686|46.388|13.967|48730|BENEFITS+CROWD+MOBILITY,Kern County|185802|4130|2.223|21.739|7.058|37.285|14.394|50826|BENEFITS+CROWD,Los Angeles County|1641669|37540|2.287|16.338|9.204|27.238|16.741|61015|BENEFITS+CROWD+MOBILITY,Tulare County|104542|2703|2.586|25.738|6.274|49.347|14.535|44871|BENEFITS+CROWD", + "metadata": { + "State-Gated Retrieval": [ + "Use only California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline.", + "Retain only counties with a population aged 5–17 of at least 75,000, a SchoolAgeLEP count of at least 2,000 with its share higher than the statewide share, a no-internet share higher than the statewide share, and a median household income lower than the statewide share.", + "SchoolAgeLEP must be the sum of the eight not-well/not-at-all cells across the four major language groups in B16004. The final county must also have at least two of the three offline support signals (Mobility, Benefits, Crowd) higher than the statewide share." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2013-2017 ACS 5-year county geography yields California county candidates and the statewide baseline row", + "B16004 and the downstream access/income/support tables yield SchoolAgeLEP, no-internet share, no-vehicle share, child-benefit share, crowded-renter share, and median income for counties and the statewide baseline", + "final rows are produced only after the SchoolAgeLEP numerator is computed from all eight 1980-target language cells and the downstream support-path branches are applied" + ], + "control_dependency": [ + "the SchoolAgeLEP numerator must be computed from the full eight-cell language set in B16004 rather than from only two Spanish LEP cells", + "county eligibility and SupportPath labels must be determined from the LEP numerator and candidate set defined under that full eight-cell calculation", + "the BENEFITS / CROWD / MOBILITY path labels must be determined by applying all three downstream support branches to the same county set" + ], + "freeze": { + "historical_window": "2013-2017 American Community Survey 5-year estimates for California counties, using the California statewide row from the same release as the comparison baseline" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Use only California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline.", + "Retain only counties with a population aged 5–17 of at least 75,000, a SchoolAgeLEP count of at least 2,000 with its share higher than the statewide share, a no-internet share higher than the statewide share, and a median household income lower than the statewide share.", + "SchoolAgeLEP must be the sum of the eight not-well/not-at-all cells across the four major language groups in B16004. The final county must also have at least two of the three offline support signals (Mobility, Benefits, Crowd) higher than the statewide share." + ], + "exclusion_conditions": [ + "Exclude results that use only the two Spanish LEP rows without merging all eight target cells.", + "Exclude results that do not rerun the B28011, B19013, B08201, B09010, and B25014 branches.", + "Exclude counties whose final SupportPath does not have at least two signals higher than the statewide share." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "SchoolAgePop", + "SchoolAgeLEP", + "LEPSharePct", + "NoInternetPct", + "NoVehiclePct", + "ChildBenefitSharePct", + "CrowdedRenterPct", + "MedianIncome", + "SupportPath" + ], + "county": "use the county display name including the word `County` and excluding a trailing state suffix", + "dedup_key": "county FIPS / GEOID", + "SchoolAgeLEP": "sum the eight designated school-age LEP cells before emitting the integer total", + "percentage_fields": "all percentage fields are plain numbers with exactly three decimal places and no percent sign", + "numeric_fields": "population counts and median income are emitted as plain integers without commas", + "SupportPath": "use only BENEFITS, CROWD, and MOBILITY, and when multiple labels apply join them with `+` in the fixed order BENEFITS+CROWD+MOBILITY", + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "all candidate counties are validated under the same geography and product settings", + "the school-age LEP aggregation and all three support-signal gates are checked before the final line is emitted" + ] + } + } +} diff --git a/data_en/goal/census_004-g.json b/data_en/goal/census_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..0ea269c685ca92652cbc90d2fd1e31876b7e23d4 --- /dev/null +++ b/data_en/goal/census_004-g.json @@ -0,0 +1,72 @@ +{ + "task_id": "census_004-g", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 7, + "instruction": "Using the 2012–2016 American Community Survey 5-year estimates, identify Pennsylvania counties with high elderly evacuation support needs that should conduct in-person outreach before winter storms. A candidate county must meet all of the following conditions: a population aged 65 and older of at least 15,000; a population aged 65 and older with ambulatory difficulty of at least 4,000, with its share of the 65+ population higher than the statewide share; a median household income below the statewide median; and at least two of four evacuation-support barriers above the statewide level. The four barriers are: share of households with a householder aged 65+ living alone, share of households with no vehicle, share of renter-occupied households with no vehicle, and mobile homes as a share of all housing units. All comparisons to the statewide level use the Pennsylvania statewide values from the same data release. Output all qualifying counties as a single line, sorted alphabetically by county name. Each county is formatted as County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath, with counties separated by commas. For BarrierPath, use only ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE, joined by + in that fixed order.", + "start_url": "https://www.census.gov/data.html", + "output_format": "Output all qualifying counties as a single line, sorted alphabetically by county name. Each county is formatted as County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath, with counties separated by commas. For BarrierPath, use only ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE, joined by + in that fixed order.", + "oracle_answer": "Blair County|23013|5576|24.230|14.917|9.440|24.316|6.388|44033|ALONE+MOBILE_HOME, Cambria County|27058|6308|23.313|15.243|10.309|26.627|4.070|42917|ALONE+MOBILE_HOME+RENTER_NO_VEHICLE, Fayette County|25186|5886|23.370|14.961|9.302|22.290|10.489|40511|ALONE+MOBILE_HOME, Lycoming County|19486|4311|22.124|12.164|9.257|23.312|6.726|48731|ALONE+MOBILE_HOME, Mercer County|21537|4799|22.283|14.090|9.572|24.413|7.912|45831|ALONE+MOBILE_HOME, Philadelphia County|188185|56935|30.255|11.553|30.954|44.924|0.250|39770|NO_VEHICLE+RENTER_NO_VEHICLE, Schuylkill County|26613|6465|24.293|14.357|9.676|23.652|4.080|46573|ALONE+MOBILE_HOME", + "metadata": { + "State-Gated Retrieval": [ + "Use only Pennsylvania county data from the 2012–2016 American Community Survey 5-year estimates, and use the Pennsylvania statewide values from the same release as the comparison baseline.", + "Retain only counties with a 65+ population of at least 15,000, a 65+ ambulatory-difficulty population of at least 4,000 with a share above the statewide share, and a median household income below the statewide median.", + "The 65+ ambulatory-difficulty numerator must combine the four target cells from B18105 for ages 65–74 and 75+, male and female. The final county must also have at least two of the four barriers (Alone, No Vehicle, Renter No Vehicle, Mobile Home) above the statewide level." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "ACS tables B01001 and B18105 yield county senior-population totals and the full 65+ ambulatory-difficulty numerator", + "statewide comparison tables yield Pennsylvania baselines plus county barrier metrics for living alone, no vehicle, renter no vehicle, mobile home, and median income", + "final rows are produced only after the county candidate set is defined from the full ambulatory-difficulty numerator and the downstream six-table filters are applied" + ], + "control_dependency": [ + "the ambulatory-difficulty numerator must include the full 65+ population across 65–74 and 75+ and male and female cells rather than only the 75+ cells", + "downstream county eligibility and barrier labels must be determined from the county candidate set defined under that full ambulatory numerator", + "the at-least-two-barriers test must compare every county metric against the same Pennsylvania statewide baselines from the same ACS release" + ], + "freeze": { + "historical_window": "2012–2016 American Community Survey 5-year estimates for Pennsylvania counties, with Pennsylvania statewide baselines taken from the same release" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Use only Pennsylvania county data from the 2012–2016 American Community Survey 5-year estimates, and use the Pennsylvania statewide values from the same release as the comparison baseline.", + "Retain only counties with a 65+ population of at least 15,000, a 65+ ambulatory-difficulty population of at least 4,000 with a share above the statewide share, and a median household income below the statewide median.", + "The 65+ ambulatory-difficulty numerator must combine the four target cells from B18105 for ages 65–74 and 75+, male and female. The final county must also have at least two of the four barriers (Alone, No Vehicle, Renter No Vehicle, Mobile Home) above the statewide level." + ], + "exclusion_conditions": [ + "Exclude results that take only the 75-and-over ambulatory-difficulty cells and mistakenly treat them as the full 65+ count.", + "Exclude results that do not use the Pennsylvania statewide baselines from the same release.", + "Exclude counties whose final BarrierPath does not satisfy at least two barriers above the statewide level." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "SeniorPop", + "AmbulatoryDifficulty65Plus", + "AmbDiffPct", + "SeniorLivingAloneSharePct", + "NoVehiclePct", + "RenterNoVehiclePct", + "MobileHomePct", + "MedianIncome", + "BarrierPath" + ], + "county": "use the county display name including the word `County` and excluding a trailing state suffix", + "dedup_key": "county FIPS / GEOID", + "percentage_fields": "all percentage fields are plain numbers with exactly three decimal places and no percent sign", + "numeric_fields": "population counts and median income are emitted as plain integers without commas", + "BarrierPath": "use only ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE, and when multiple labels apply join them with `+` in the fixed order ALONE+MOBILE_HOME+NO_VEHICLE+RENTER_NO_VEHICLE", + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "all candidate counties are validated under the same geography and product settings", + "the senior ambulatory-difficulty gate and all barrier-signal gates are checked before the final line is emitted" + ] + } + } +} diff --git a/data_en/goal/climategov_001-g.json b/data_en/goal/climategov_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..ee6705f0fb5a1b120b96178a0b9fe75edf05c29d --- /dev/null +++ b/data_en/goal/climategov_001-g.json @@ -0,0 +1,66 @@ +{ + "task_id": "climategov_011-g", + "domain": "NOAA_NCEI_CLIMATE_AT_A_GLANCE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "Identify South Texas climate divisions that were near-normal or wetter over two longer periods and still had light heating demand in March 1966. Restrict the search strictly to the four divisions South Central, Upper Coast, South, and Lower Valley, using the exact names and numbering order from the official Texas climate-division page fragment.\n\nRetain only divisions that meet all three hard climate criteria: (1) the 10-month Palmer Z-Index anomaly ending February 1966 must be at least -0.05; (2) the 24-month Palmer Z-Index anomaly ending December 1966 must be at least -0.10; and (3) the actual March 1966 monthly Heating Degree Days value must be below 200°Df.\n\nSort qualifying divisions as follows: primary key is the sum of the February 1966 10-month Z-index anomaly and the December 1966 24-month Z-index anomaly, in descending order; secondary key is the March 1966 HDD actual value, in ascending order; tertiary key is the Texas division number, in ascending order.\n\nFinally, output all matching divisions as a single comma-separated string. Each entry must follow the format \"|||||\", where the moisture score is the sum of the two Z-index anomalies. If no division qualifies, output NONE in uppercase.", + "start_url": "https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national", + "output_format": "Output all matching divisions as a single comma-separated string. Each entry must follow the format \"|||||\", where the moisture score is the sum of the two Z-index anomalies. If no division qualifies, output NONE in uppercase.", + "oracle_answer": "7|South Central|0.72|0.35|194°Df|1.07,10|Lower Valley|0.28|0.67|106°Df|0.95,9|South|0.03|0.37|148°Df|0.40", + "metadata": { + "State-Gated Retrieval": [ + "Filter only within the four South Texas divisions defined on the Texas divisional page: South Central, Upper Coast, South, and Lower Valley.", + "Retain divisions that simultaneously satisfy: 1966-02 10-month Palmer Z-Index anomaly >= -0.05; 1966-12 24-month anomaly >= -0.10; 1966-03 1-month Heating Degree Days Value < 200°Df.", + "Sort by sum of the two Z anomalies descending, then by 1966-03 HDD Value ascending, then by division number ascending." + ], + "dependency_type": "Data", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "The official Texas climate-division reference fixes the four South Texas division IDs and names that must be tracked across all later pages.", + "The 1966-02 10-month Palmer Z-Index anomaly page and the 1966-12 24-month Palmer Z-Index anomaly page jointly identify the four target South Texas divisions.", + "The 1966-03 1-month Heating Degree Days Value page supplies the last filter; final rows are produced only after intersecting the three divisional screens and then sorting by summed Z-anomaly score, HDD value, and division number." + ], + "freeze": { + "historical_window": "Texas climate divisions South Central, Upper Coast, South, and Lower Valley; metrics are fixed to the 1966-02 10-month Palmer Z-Index anomaly, 1966-12 24-month anomaly, and 1966-03 1-month Heating Degree Days Value pages." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Filter only within the four South Texas divisions defined on the Texas divisional page: South Central, Upper Coast, South, and Lower Valley.", + "Retain divisions that simultaneously satisfy: 1966-02 10-month Palmer Z-Index anomaly >= -0.05; 1966-12 24-month anomaly >= -0.10; 1966-03 1-month Heating Degree Days Value < 200°Df.", + "Sort by sum of the two Z anomalies descending, then by 1966-03 HDD Value ascending, then by division number ascending." + ], + "exclusion_conditions": [ + "Exclude any Texas divisional results outside the four specified South Texas divisions.", + "Exclude results that misread the 1966-03 HDD page filter field as Anomaly instead of Value.", + "Exclude any division that fails any time window or threshold condition." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "texas_division_no", + "division_name", + "feb_1966_10mo_z_text", + "dec_1966_24mo_z_text", + "mar_1966_hdd_text", + "moisture_score" + ], + "texas_division_no": "Canonical output uses the short Texas climate-division number; the scorer may accept an equivalent four-digit form, but the emitted oracle uses the short number.", + "raw_text_fields": "The two Z-index anomaly fields and the March 1966 HDD field preserve the raw displayed text; comparison may ignore optional trailing HDD unit text such as `°Df`.", + "moisture_score": "Compute as February 1966 10-month Z-index anomaly plus December 1966 24-month Z-index anomaly, formatted with exactly two decimal places.", + "sorting_or_selection": { + "primary": "moisture_score descending", + "secondary": "March 1966 HDD actual value ascending after numeric normalization", + "tertiary": "Texas division number ascending" + }, + "eligibility_rule": "Each Texas division is counted once per requested window; if any required window value is missing, exclude the division.", + "stop_condition": [ + "All candidate Texas divisions are checked under the same base period and anomaly windows.", + "The unique ordered output string is resolved before emission." + ] + } + } +} diff --git a/data_en/goal/climategov_002-g.json b/data_en/goal/climategov_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..82c57cb8789e8679f642268720fb67b8dd7b3d00 --- /dev/null +++ b/data_en/goal/climategov_002-g.json @@ -0,0 +1,73 @@ +{ + "task_id": "climategov_012-g", + "domain": "NOAA_NCEI_CLIMATE_AT_A_GLANCE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am researching historical climate patterns in Texas and want to find similar historical years as references for shoulder-season operational planning. To do this, I need to identify specific Texas climate divisions in NOAA's Climate at a Glance database. The divisions I am looking for must have experienced a shift from a dry long-term moisture background back toward near-normal or wetter conditions in the early 20th century, and must have had light heating loads in two different shoulder-season windows.\n\nSpecifically, the selected divisions must satisfy all four of the following hard climate criteria: first, the 10-month Palmer Z-Index anomaly ending April 1907 must be no higher than -0.30; second, the 10-month Z-Index anomaly ending April 1923 must be no lower than -0.20; third, the 2-month Heating Degree Days (HDD) actual value ending May 1915 must be below 50°Df; and fourth, the 5-month HDD actual value ending October 1922 must be below 20°Df.\n\nAfter identifying the qualifying divisions, sort them according to the following rules. The primary sort key is the \"rebound score\", defined as the April 1923 10-month Z-Index anomaly minus the April 1907 10-month Z-Index anomaly, sorted in descending order. In case of a tie, place the division with the smaller October 1922 5-month HDD actual value first. If still tied, place the division with the smaller Texas division number first.\n\nFinally, output all matching divisions as a single comma-separated string. Each matching item must be formatted exactly as: \"|<4-digit division ID>||||||\". If after checking all divisions none meet the combined criteria, output NONE in uppercase.", + "start_url": "https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national", + "output_format": "Output all matching divisions as a single comma-separated string. Each matching item must be formatted exactly as: \"|<4-digit division ID>||||||\". If after checking all divisions none meet the combined criteria, output NONE in uppercase.", + "oracle_answer": "10|4110|Lower Valley|-0.36|1.46|10°Df|7°Df|1.82,9|4109|South|-0.33|0.53|23°Df|16°Df|0.86\n10|4110|Lower Valley|-0.36|1.46|10|7|1.82,9|4109|South|-0.33|0.53|23|16|0.86", + "metadata": { + "State-Gated Retrieval": [ + "Retain only Texas divisions that satisfy all four historical conditions: the 10-month Palmer Z-Index anomaly for April 1907 must be no higher than -0.30; the 10-month anomaly for April 1923 must be no lower than -0.20; the 2-month HDD Value for May 1915 must be less than 50°Df; and the 5-month HDD Value for October 1922 must be less than 20°Df.", + "The rebound score is defined as the April 1923 10-month anomaly minus the April 1907 10-month anomaly.", + "Sort first by rebound score descending, then by the October 1922 5-month HDD Value ascending, then by Texas division number ascending." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Texas divisional pages yield the 1907-04 and 1923-04 10-month Palmer Z-Index anomalies plus the 1915-05 2-month and 1922-10 5-month HDD values for each division.", + "The rebound score and the two shoulder-season HDD values are computed only after the same set of candidate divisions survives all four historical filters.", + "The final output is produced after sorting the surviving divisions by rebound score, then 1922-10 HDD value, then division number." + ], + "control_dependency": [ + "The workflow must cover the 1907, 1923, and 1915 pages as well as the 1922-10 5-month HDD page.", + "Both HDD pages must be read from Value rather than Anomaly.", + "The final rebound ranking must be determined after the 1922-10 5-month HDD page excludes 7 South Central and 8 Upper Coast, using ReboundScore as the ordering basis." + ], + "freeze": { + "historical_window": "Texas climate divisions evaluated on the 1907-04 and 1923-04 10-month Palmer Z-Index anomaly pages, the 1915-05 2-month HDD Value page, and the 1922-10 5-month HDD Value page." + }, + "answer_type": "mixed multi-line output" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only Texas divisions that satisfy all four historical conditions: the 10-month Palmer Z-Index anomaly for April 1907 must be no higher than -0.30; the 10-month anomaly for April 1923 must be no lower than -0.20; the 2-month HDD Value for May 1915 must be less than 50°Df; and the 5-month HDD Value for October 1922 must be less than 20°Df.", + "The rebound score is defined as the April 1923 10-month anomaly minus the April 1907 10-month anomaly.", + "Sort first by rebound score descending, then by the October 1922 5-month HDD Value ascending, then by Texas division number ascending." + ], + "exclusion_conditions": [ + "Exclude results that stop after filtering only the 1907, 1923, and 1915 pages without also reading the 1922-10 5-month HDD page.", + "Exclude results that mistakenly read the 1915 or 1922 HDD page as Anomaly instead of Value.", + "Exclude any division that does not satisfy any one of the historical window conditions." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "texas_division_no", + "division_id_4digit", + "division_name", + "apr_1907_10mo_z_text", + "apr_1923_10mo_z_text", + "may_1915_2mo_hdd_text", + "oct_1922_5mo_hdd_text", + "rebound_score" + ], + "texas_division_no": "Emit the short Texas climate-division number in field 1 and the four-digit division ID in field 2.", + "raw_text_fields": "The two Z-index anomaly fields preserve the raw displayed text; the two HDD fields preserve the raw displayed text, but comparison may ignore an optional trailing °Df suffix.", + "rebound_score": "Compute as the April 1923 10-month Z-index anomaly minus the April 1907 10-month Z-index anomaly, formatted with exactly two decimal places.", + "sorting_or_selection": { + "primary": "rebound_score descending", + "secondary": "October 1922 HDD actual value ascending after numeric normalization", + "tertiary": "Texas division number ascending" + }, + "answer_set_note": "The current oracle stores two equivalent answer sets: one preserves the HDD unit suffixes and one strips them; treat the two HDD columns as equivalent after optional °Df removal.", + "stop_condition": [ + "All candidate Texas divisions are checked under the same anomaly and HDD windows.", + "The unique ordered output string is resolved before emission." + ] + } + } +} diff --git a/data_en/goal/comptox_001-g.json b/data_en/goal/comptox_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..c7e402addadff477a36f8c0f0f6e14f0d819dafd --- /dev/null +++ b/data_en/goal/comptox_001-g.json @@ -0,0 +1,76 @@ +{ + "task_id": "comptox_010-g", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "Among the following five substances found in records related to painted products in Europe—aniline, cobalt, chromium, 3,3'-dichlorobenzidine, and dibenz[a,h]anthracene—select those whose pages explicitly contain the record 'Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe'. For each qualifying substance, produce a consolidated list that integrates historical keyword status and the deepest-level use categories. First, for each substance, count how many of the following five dated historical keywords are present (presence only, ignoring any leading numbers): Substances in Products - Canada (4/2014), Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children's Safe Product Act (4/2020), OEHHA Proposition 65 (1/2023). Also record the earliest and latest year-month among the hits. Second, for each substance, retain one category that best reflects its current use. After excluding the use category to which the above-mentioned painted-products record belongs, establish for each substance a terminal-use profile along two dimensions: 'daily consumer goods' (with the broad-category selection priority Formulation → Article → Occupation) and 'production materials' (with the broad-category selection priority Occupation → Article → Formulation). Finally, sort all substances by historical keyword hit count in descending order; for ties, sort by the number of products at the selected consumer-side node in descending order.", + "start_url": "https://comptox.epa.gov/chemexpo/", + "output_format": "Output format: |||||||||||||. Results separated by commas; if no qualifying items exist, output NONE.", + "oracle_answer": "DTXSID8020090|5|2014-04|2023-01|Formulation|272|295|type|4|Occupation|301|356|family|27,DTXSID1031040|3|2018-10|2023-01|Formulation|77|94|type|7|Occupation|301|400|family|308,DTXSID9020409|2|2019-03|2023-01|Occupation|321|321|general|11|Occupation|321|321|general|11,DTXSID6020432|2|2019-03|2023-01|Article|313|313|general|1|Occupation|301|356|family|27,DTXSID3031022|1|2023-01|2023-01|Formulation|77|95|type|4|Occupation|301|356|family|185", + "metadata": { + "State-Gated Retrieval": [ + "Screen only the five specified substances, and the target substance page must explicitly contain the record 'Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe'.", + "Count whether each of the five specified dated keywords appears, and record the earliest and latest year-month among the hits.", + "Then independently select one consumer-side route and one production-material-side route, the former following Formulation → Article → Occupation and the latter following Occupation → Article → Formulation, and refine each route separately to its deepest level." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "each chemical page yields the five dated historical keywords, the Europe body-paint/tattoo-ink qualifying record, and the earliest/latest dated-hit months", + "PUC category paths yield one consumer-side route chosen by Formulation -> Article -> Occupation and one source-side route chosen independently by Occupation -> Article -> Formulation", + "final rows are produced only after the consumer-side and source-side routes are selected and refined separately for each chemical" + ], + "control_dependency": [ + "the source-side route must be selected independently from the consumer-side route", + "for each chemical, the second route refinement must follow the production-material priority order rather than the daily-consumer route", + "family/type/general outputs must be determined only after both route selections are made independently" + ], + "freeze": { + "historical_window": "the five named substances as objectively existing chemicals, using their ChemExpo chemical pages, PUC category paths, keyword-state evidence, and Europe body-paint/tattoo-ink presence as relatively stable classification signals" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Screen only the five specified substances, and the target substance page must explicitly contain the record 'Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe'.", + "Count whether each of the five specified dated keywords appears, and record the earliest and latest year-month among the hits.", + "Then independently select one consumer-side route and one production-material-side route, the former following Formulation → Article → Occupation and the latter following Occupation → Article → Formulation, and refine each route separately to its deepest level." + ], + "exclusion_conditions": [ + "Exclude substances that do not contain the specified Europe painted-products/tattoo-ink record.", + "Exclude results that directly reuse the same consumer-side route for the production-material side.", + "Exclude results that do not independently select and refine both routes according to the specified priority orders." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DTXSID", + "hit_count", + "earliest", + "latest", + "consumer_kind", + "consumer_general_puc_id", + "consumer_terminal_puc_id", + "consumer_level", + "consumer_products", + "material_kind", + "material_general_puc_id", + "material_terminal_puc_id", + "material_level", + "material_products" + ], + "dated_hits": "count only the exact dated keyword strings defined in the source rubric", + "date_format": "YYYY-MM", + "kind": "the kind fields use the canonical labels Article, Formulation, or Occupation", + "level": "the level fields use the canonical labels general, family, or type", + "products_source": "the Products counts come from the local chemical-detail node for the selected branch, not from an overall aggregate shown elsewhere on the site", + "sorting_or_selection": { + "primary": "hit_count descending", + "secondary": "consumer_products descending", + "tertiary": "DTXSID ascending" + } + } + } +} diff --git a/data_en/goal/comptox_002-g.json b/data_en/goal/comptox_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..5bbef2d021a42994d2ef0c15029a6a7942bc2d1b --- /dev/null +++ b/data_en/goal/comptox_002-g.json @@ -0,0 +1,78 @@ +{ + "task_id": "comptox_011-g", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 6, + "instruction": "In ChemExpo, for each of the six substances, determine whether it appears more often in material-contact uses or manufacturing-source uses, then select the most representative use category from the corresponding direction. Specifically, the scope is limited to these six substances: Di(2-Ethylhexyl) Phthalate, Melamine, Tris(2-Ethylhexyl) Phosphate, 4,5-Dihydro-2-Mercaptoimidazole, Phthalic Acid, and Triphenyl Phosphates Tert-Butylated. For each substance, three sets of data must be checked: first, a 'material-contact score' obtained by summing the occurrences of five specific labels (Indirect additives food contact (10/2018), Europe, Food contact items, Food contact items, Japan, entries containing 'Toys and children's products', and entries containing 'artificial_saliva' or 'artificial_sweat'); second, a 'manufacturing-source score' obtained by summing the occurrences of two specific labels (drinking_water, Europe, manufacturing, plastic_additive and Europe, plastic_additive); third, a regulatory profile generated by counting the total hits of four date-keyword labels (Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children's Safe Product Act (4/2020), OEHHA Proposition 65 (1/2023)) and extracting the earliest and latest month-year range spanned. Based on this, if the material-contact score is strictly greater than the manufacturing-source score, the substance is considered to favor material contact, and the most representative category is selected in the order Article → Formulation → Occupation; otherwise, it is considered to favor manufacturing source, and the selection order is Occupation → Article → Formulation. After determining the category, at each level, follow only the subcategory with the highest product count, continuing until no further subdivision is possible; if there is a tie at the same level, select the one with the smaller PUC ID.", + "start_url": "https://comptox.epa.gov/chemexpo/", + "output_format": "Finally, sort the substances by datedHits in descending order; for ties, sort by Products of the selected node in descending order. Output format: ||||||||||||. Results are separated by commas; if datedHits is 0, write NA for both earliest and latest.", + "oracle_answer": "DTXSID5020607|5|2|4|2018-10|2023-01|contact|Article|309|493|family|1|23|58,DTXSID5020601|4|1|3|2018-10|2023-01|contact|Article|309|309|general|1|5836|1827,DTXSID6020802|4|2|1|2018-10|2018-10|contact|Article|313|313|general|15|1104|675,DTXSID8021484|3|1|1|2018-10|2018-10|contact|Occupation|321|321|general|8|28313|4200,DTXSID0021414|5|0|1|2018-10|2018-10|contact|Article|309|309|general|3|5836|1827,DTXSID20872645|0|1|0|NA|NA|source|Occupation|318|381|family|5|274|107", + "metadata": { + "State-Gated Retrieval": [ + "Only consider the six specified substances, and first compute contactHits, sourceHits, and datedHits on the chemical page.", + "prioritySide must be determined by these historical signals first, then select the most representative current use category along the corresponding direction.", + "The current route selection must continue drilling down according to the given kind priority and the same-level smaller PUC ID rule." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "each chemical page yields contactHits, sourceHits, datedHits, and the earliest/latest dated-hit months from the historical keyword set", + "after the priority side is chosen, the corresponding current PUC category path yields the representative kind, PUC path, product counts, and curated-chemical counts", + "final rows are produced only after the historical hit scores determine the side first and the current route is then chosen with the side-specific priority and tie-break rules" + ], + "control_dependency": [ + "historical contact/source signal scores must take priority over current maximum-Products paths", + "the priority side must be determined from contactHits, sourceHits, and datedHits rather than from current visibility alone", + "PUC path tie-breaks are valid only after the correct side has been fixed and the route has been traced under that side's rules" + ], + "freeze": { + "historical_window": "the six named substances as objectively existing chemicals, using their ChemExpo chemical pages, PUC category paths, historical keyword families, and keyword-hit evidence as relatively stable classification signals" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only consider the six specified substances, and first compute contactHits, sourceHits, and datedHits on the chemical page.", + "prioritySide must be determined by these historical signals first, then select the most representative current use category along the corresponding direction.", + "The current route selection must continue drilling down according to the given kind priority and the same-level smaller PUC ID rule." + ], + "exclusion_conditions": [ + "Exclude results that ignore historical signals and directly select the path with the maximum currently visible Products on the chemical page.", + "Exclude results that start PUC route selection without first determining the contact/source direction.", + "Exclude results where same-level tie-breaks do not follow the smaller PUC ID rule." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DTXSID", + "contactHits", + "sourceHits", + "datedHits", + "earliest", + "latest", + "prioritySide", + "PUCkind", + "generalPUCID", + "terminalPUCID", + "level", + "Products", + "PUCDocuments", + "PUCCuratedChemicals" + ], + "dated_hits": "count only the exact dated keyword strings defined in the source rubric", + "date_format": "YYYY-MM; if datedHits is 0, earliest and latest are both `NA`", + "prioritySide": "emit `contact` when contactHits > sourceHits; otherwise emit `source`", + "kind": "the PUCkind field uses the canonical labels Article, Formulation, or Occupation", + "level": "the level field uses the canonical labels general, family, or type", + "products_source": "Products comes from the selected terminal chemical-detail node", + "terminal_statistics": "PUCDocuments and PUCCuratedChemicals come from the selected terminal PUC detail page Additional Statistics block", + "sorting_or_selection": { + "primary": "datedHits descending", + "secondary": "Products descending", + "tertiary": "DTXSID ascending" + } + } + } +} diff --git a/data_en/goal/comptox_003-g.json b/data_en/goal/comptox_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..33b763b5686044e0d54bc6cb6a018c3be0684c9b --- /dev/null +++ b/data_en/goal/comptox_003-g.json @@ -0,0 +1,67 @@ +{ + "task_id": "comptox_012-g", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I want to first screen for Formulation categories with many products in ChemExpo, and then from each category pick one specific product type that carries a child or aerosol label and is most worth prioritizing. Specifically, I am looking for a set of results: for each Formulation category with a total product count of at least 15,000, find one optimal specific product type. This target type must belong to the first family under that category's default display order that meets the following conditions: the family has a total product count of at least 3,000 and no assumed attributes, and it must have product types whose allowed attributes include 'aerosol' and 'child', with those types themselves having no assumed attributes. Then, among all qualifying 'aerosol' and 'child' types under that family, select the one with the highest product share (type product count divided by family cumulative product count). In case of a tie in share, prioritize in order: higher Product Count, more Curated Chemicals, or smaller PUC ID, until a single winner is determined. Finally, retain one final result: prefer the specific product type with the higher product share; if shares are equal, compare Product Count, Curated Chemicals, and PUC ID in that order, retaining the type with the higher count, more chemicals, or smaller ID, until a single final type is obtained.", + "start_url": "https://comptox.epa.gov/chemexpo/visualizations/", + "output_format": "Finally, output results sorted by final share descending, in the format: |||||. Join results with commas and no spaces. If no qualifying results exist, output NONE.", + "oracle_answer": "48|42|62|child|2160/3531|583,137|197|210|child|6934/16904|1135", + "metadata": { + "State-Gated Retrieval": [ + "First, retain only Formulation categories with a total product count of at least 15,000.", + "In each candidate family, both an aerosol-side type and a child-side type must be found: the family itself must have no assumed attributes and a total product count of at least 3,000; both types must also have no assumed attributes.", + "All selections within a family and between the two sides must follow the specified tie-break rules: share, Product Count, Curated Chemicals, PUC ID." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "The Formulation summary yields the high-product candidate families whose total product count is at least 15,000.", + "Within each family, lower-level type pages yield the aerosol and child candidates, their assumed/allowed attributes, product counts, shares, and curated-chemical counts.", + "Final rows are produced only after a family survives both aerosol and child branches and the winning type is selected by the layered share/product/chemical/PUC tie-break rules." + ], + "control_dependency": [ + "Both the aerosol and child branches within the same family must be fully checked before that family can be retained.", + "If one side is missing, the workflow must reject the family and continue to the next sibling family rather than stop at the first partial hit.", + "The final winner can be selected only after both sides have been independently optimized within the family and then compared against each other." + ], + "freeze": { + "historical_window": "ChemExpo Formulation families as objectively existing catalog families, especially large families with total product count >= 15,000, evaluated by family/type identity and product/chemical counts as relatively stable catalog descriptors." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "First, retain only Formulation categories with a total product count of at least 15,000.", + "In each candidate family, both an aerosol-side type and a child-side type must be found: the family itself must have no assumed attributes and a total product count of at least 3,000; both types must also have no assumed attributes.", + "All selections within a family and between the two sides must follow the specified tie-break rules: share, Product Count, Curated Chemicals, PUC ID." + ], + "exclusion_conditions": [ + "Exclude results that stop as soon as a usable type is found on either side, without requiring the same family to cover both aerosol and child sides.", + "Exclude results that stop as soon as one side is missing instead of continuing to check sibling families at the same level.", + "Exclude results that do not follow the specified layered tie-break rules to select the winning type within the family and as the final winner." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "generalPUCID", + "familyPUCID", + "typePUCID", + "side", + "share", + "CuratedChemicals" + ], + "dedup_key": "(generalPUCID, familyPUCID, typePUCID, side)", + "side": "emit the lower-case branch label exactly as determined in the source workflow", + "share": "canonical output uses the raw fraction `type Products / family Cumulative Products` rather than a decimal", + "CuratedChemicals": "emit the integer count from the selected type-level node", + "sorting_or_selection": { + "primary": "share descending by numeric fraction value", + "secondary": "type-level Products descending", + "tertiary": "CuratedChemicals descending, then PUC IDs ascending as tie-breaks" + } + } + } +} diff --git a/data_en/goal/comptox_004-g.json b/data_en/goal/comptox_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..365f63567fb380e3b667e2410e68fe9c6883d8a5 --- /dev/null +++ b/data_en/goal/comptox_004-g.json @@ -0,0 +1,84 @@ +{ + "task_id": "comptox_013-g", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "In ChemExpo, for the five substances Di(2-Ethylhexyl) Phthalate, Melamine, Phthalic Acid, Tris(2-Ethylhexyl) Phosphate, and Triphenyl Phosphates Tert-Butylated, check whether their historical labels are consistent with their current uses. The scope is limited to these five substances. For each substance, examine three groups of data. First, the material-contact score: check whether each of the following five label types appears, scoring 1 point per type: Indirect additives food contact (10/2018), Europe, Food contact items, Food contact items, Japan, any keyword containing Toys and children's products, and any keyword containing artificial_saliva or artificial_sweat. Second, the production-source score: check whether each of the following two label types appears, scoring 1 point per type: drinking_water, Europe, manufacturing, plastic_additive and Europe, plastic_additive. Third, dated-keyword hits: check only whether each of the following four keywords appears: Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children's Safe Product Act (4/2020), OEHHA Proposition 65 (1/2023); record the number of hits and the earliest and latest year-month among the hits. Then, if the material-contact score is strictly greater than the production-source score, treat it as leaning toward material contact and select a historically recommended category following the order Article → Formulation → Occupation; otherwise treat it as leaning toward production source and select following the order Occupation → Article → Formulation. After determining the category, follow the subcategory with the most products downward until no further subdivision is possible; if there is a tie at the same level, take the one with the smaller PUC ID. Separately, also find the current dominant category for this substance, ignoring historical clues, directly finding the path with the most products among all use categories, again following downward until no further subdivision is possible, breaking ties by smaller PUC ID. Finally, compare the two results: if the current dominant category is Article or Formulation and the historical clue also points to material contact, record ALIGNED; if the current dominant category is Occupation and the historical clue also points to production source, record ALIGNED; otherwise record MISALIGNED.", + "start_url": "https://comptox.epa.gov/chemexpo/", + "output_format": "Output MISALIGNED records first; within the same group, sort by dated hits descending; if hits are equal, sort by current dominant category product count descending. Format: |||||||||||||||||. Separate records with commas. If dated hits is 0, write NA for both earliest and latest.", + "oracle_answer": "DTXSID6020802|4|2|1|2018-10|2018-10|material|Article|Furniture and furnishings|Furniture and furnishings|general|15|Occupation|Raw materials|fireproof coatings|type|24|MISALIGNED,DTXSID8021484|3|1|1|2018-10|2018-10|material|Occupation|Laboratory supplies|Laboratory supplies|general|8|Occupation|Laboratory supplies|Laboratory supplies|general|8|MISALIGNED,DTXSID5020607|5|2|4|2018-10|2023-01|material|Article|Construction and building materials|flooring|family|1|Formulation|Home maintenance|paint|type|112|ALIGNED,DTXSID0021414|5|0|1|2018-10|2018-10|material|Article|Construction and building materials|Construction and building materials|general|3|Article|Construction and building materials|Construction and building materials|general|3|ALIGNED,DTXSID20872645|0|1|0|NA|NA|source|Occupation|Industrial products|hydraulic fluid|family|5|Occupation|Industrial products|hydraulic fluid|family|5|ALIGNED", + "metadata": { + "State-Gated Retrieval": [ + "Work only on the five specified substances, and first compute materialHits, sourceHits, and datedHits from the keyword-set blocks.", + "The historically recommended category must be derived independently from these historical signals; the current dominant category must be derived separately from the current use path.", + "Finally, compare only whether the broad direction of the historically recommended category and the current dominant category match, and mark ALIGNED or MISALIGNED accordingly." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "each chemical page yields materialHits, sourceHits, datedHits, and the historical recommendation side implied by the keyword set", + "an independent current PUC category path yields the current dominant category, path labels, and classification counts for the same chemical", + "final rows are produced only after the historical recommendation and current dominant category are computed independently and then compared at the coarse side level" + ], + "control_dependency": [ + "the historical recommendation must be determined from the keyword-set evidence rather than from the current largest category", + "historical recommendation must be computed from the keyword-set evidence before alignment is judged", + "ALIGNED / MISALIGNED status is valid only after the historical and current category directions have been derived independently and then compared" + ], + "freeze": { + "historical_window": "the five named substances as objectively existing chemicals, using their ChemExpo chemical pages, PUC category paths, and specified keyword-set evidence as relatively stable recommendation signals" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Work only on the five specified substances, and first compute materialHits, sourceHits, and datedHits from the keyword-set blocks.", + "The historically recommended category must be derived independently from these historical signals; the current dominant category must be derived separately from the current use path.", + "Finally, compare only whether the broad direction of the historically recommended category and the current dominant category match, and mark ALIGNED or MISALIGNED accordingly." + ], + "exclusion_conditions": [ + "Exclude results that only look at the current largest category and directly treat it as the historically recommended category.", + "Exclude results that default to ALIGNED for all cases without independently deriving the historically recommended category.", + "Exclude results that do not compute the historical and current paths separately but mix signals in the same route." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DTXSID", + "materialHits", + "sourceHits", + "datedHits", + "earliest", + "latest", + "historySide", + "recommendedKind", + "recommendedGeneral", + "recommendedTerminal", + "recommendedLevel", + "recommendedProducts", + "currentKind", + "currentGeneral", + "currentTerminal", + "currentLevel", + "currentProducts", + "status" + ], + "dated_hits": "count only the exact dated keyword strings defined in the source rubric", + "date_format": "YYYY-MM; if datedHits is 0, earliest and latest are both `NA`", + "historySide": "emit the lower-case historical winner `material` or `source`", + "recommended_fields": "these fields describe the historically suggested path", + "current_fields": "these fields describe the current dominant path", + "kind": "the kind fields use the canonical labels Article, Formulation, or Occupation", + "level": "the level fields use the canonical labels general, family, or type", + "status": "emit `ALIGNED` or `MISALIGNED` exactly", + "sorting_or_selection": { + "primary": "status with MISALIGNED before ALIGNED", + "secondary": "datedHits descending", + "tertiary": "currentProducts descending", + "quaternary": "DTXSID ascending" + } + } + } +} diff --git a/data_en/goal/consumerfinance_001-g.json b/data_en/goal/consumerfinance_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..1b16a153ca6970eb695227aebc6110913d486b26 --- /dev/null +++ b/data_en/goal/consumerfinance_001-g.json @@ -0,0 +1,67 @@ +{ + "task_id": "consumerfinance_008-g", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "For CFPB administrative enforcement actions filed between 2022-01-01 and 2024-12-31, produce a core-amount extraction report covering three product categories: Deposits, Furnishing, and Prepaid. For each category, identify the first action in the website’s default display order that satisfies all of the following: the action detail page provides both a Consent Order and a press release; the Products label corresponds exclusively and exactly to the target category; and the page explicitly states a consumer redress amount exceeding $5,000,000 along with a separate civil money penalty. After locating these three target actions, extract from each action’s Consent Order PDF the first occurrence of the consumer redress amount and the civil money penalty amount in the body text, along with their physical page numbers (PDF page 1 is p1).", + "start_url": "https://www.consumerfinance.gov/enforcement/actions/", + "output_format": "Output the results strictly in alphabetical order of the product category’s English name, using the format |||||p||p. Join entries with commas and no spaces. If no qualifying case is found for a category, output |NONE.", + "oracle_answer": "Deposits|Bank of America, N.A.|2023-CFPB-0006|2023-07-11|$80,400,000|p11|$60,000,000|p14,Furnishing|Hyundai Capital America|2022-CFPB-0005|2022-07-26|$13,200,000|p31|$6,000,000|p35,Prepaid|U.S. Bank National Association|2023-CFPB-0019|2023-12-19|$5,700,000|p22|$15,000,000|p26", + "metadata": { + "State-Gated Retrieval": [ + "Consider only administrative enforcement actions on the CFPB Enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.", + "For each of the three product categories (Deposits, Furnishing, Prepaid), search top-down in the current default order for the first action that simultaneously satisfies: the page provides a Consent Order and a Press release; the Products label corresponds one-to-one with the target category; and the action detail page explicitly states consumer redress > $5,000,000 and also includes a civil money penalty.", + "Finally, extract from the correct Consent Order the first-occurrence amounts and page numbers for consumer redress and civil money penalty." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Enforcement-action list pages yield product-branch candidate actions in current default order.", + "Each action detail page and linked consent-order PDF yield product singularity, document-stack presence, redress and civil-money-penalty amounts, and first-occurrence pages.", + "Final rows are emitted only after identifying, for each product, the first action that survives detail-page and PDF validation." + ], + "control_dependency": [ + "List-level “has Consent Order + Press release” hits must be validated on the detail page for product singularity and money thresholds.", + "Prepaid candidates force document-level disambiguation among Consent Order, Stipulation, and terminating-order PDFs.", + "Per-product first-match selection must explicitly skip rejected candidates and validate downstream PDFs before it is finalized." + ], + "freeze": { + "historical_window": "Administrative enforcement actions with Initial filing date from 2022-01-01 through 2024-12-31; current default case ordering and currently linked action documents." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Consider only administrative enforcement actions on the CFPB Enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.", + "For each of the three product categories (Deposits, Furnishing, Prepaid), search top-down in the current default order for the first action that simultaneously satisfies: the page provides a Consent Order and a Press release; the Products label corresponds one-to-one with the target category; and the action detail page explicitly states consumer redress > $5,000,000 and also includes a civil money penalty.", + "Finally, extract from the correct Consent Order the first-occurrence amounts and page numbers for consumer redress and civil money penalty." + ], + "exclusion_conditions": [ + "Exclude cases where Products is not a single target category, or where the case appears relevant only at the list level but fails validation on the detail page.", + "Exclude cases that do not clearly satisfy redress > $5M and a separate civil money penalty.", + "Exclude cases that mistakenly use a Stipulation or Order Terminating the Consent Order in place of the required Consent Order." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Product", + "Respondent", + "Docket", + "FilingDate", + "RedressUSD", + "RedressPage", + "PenaltyUSD", + "PenaltyPage" + ], + "product_order": "alphabetical by Product name", + "fallback_row": "if a product has no qualifying case, emit `|NONE`", + "date_format": "FilingDate uses YYYY-MM-DD", + "money_fields": "canonical output preserves the dollar sign and commas from the oracle, but equivalent comparison may ignore `$` and commas and compare the numeric USD amount", + "page_fields": "page fields use the canonical `pN` form", + "document_scope": "extract both money amounts from the Consent Order PDF only; do not substitute a stipulation, termination order, or other companion document", + "selection_rule": "for each product, keep the first action in the default filtered order that fully satisfies every gate in the source rubric" + } + } +} diff --git a/data_en/goal/consumerfinance_002-g.json b/data_en/goal/consumerfinance_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..b0efc555f3764811a683f08d664aa9a0a8021629 --- /dev/null +++ b/data_en/goal/consumerfinance_002-g.json @@ -0,0 +1,66 @@ +{ + "task_id": "consumerfinance_009-g", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I want to organize the annual household financial stability survey reports in CFPB Reports, whose latest version page links directly to the 2023 and 2022 editions. I am interested in topics that appeared in the 2022 edition but no longer appear in subsequent annual reports, excluding the topic specifically used to mark \"belongs to the same survey series.\" For each such topic, I need the following information: the earliest subsequent year in which it disappeared; the first report not belonging to this series among the results related to these topics from 2022 and earlier; the total number of related resources listed in that report, how many of them link back to the same survey series, how many of those linked reports have appendices with letter labels and at least three sections; and the title, publication date, and appendix letter range of the final selected report.", + "start_url": "https://www.consumerfinance.gov/data-research/research-reports/", + "output_format": "Output a single line per topic, sorted alphabetically by topic name: |||||||||", + "oracle_answer": "Saving|2023|Consumer Savings App Strategies and Savings Outcomes|2022-12-07|4|2|1|Emergency Savings and Financial Security: Insights from the Making Ends Meet Survey and Consumer Credit Panel|2022-03-23|A-D,Student loans|2023|Report of the CFPB Education Loan Ombudsman|2022-10-20|0|0|0|NONE|NONE|NONE", + "metadata": { + "State-Gated Retrieval": [ + "First, identify the CFPB household financial well-being annual report series whose latest version links directly to the 2023 and 2022 editions.", + "Using the 2022 edition as the baseline, retain only topics that appear in 2022 but are no longer retained in subsequent annual reports, and exclude the topic specifically marked as \"belongs to the same survey series.\"", + "For each topic, find the earliest non-series pivot report from 2022 or earlier, then count its directly listed related resources, how many link back to the same survey series, how many qualify under the appendix rule, and the appendix span of the final qualifying report." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current CFPB Reports pages yield the 2024 -> 2023 -> 2022 annual-survey chain and the 2022 topic baseline", + "report detail pages and report-search results yield first-disappearance year, pivot report title/date, related-resource counts, and links back to the annual-survey series", + "final rows are produced only after separating the first jump target from later return-to-series counting" + ], + "control_dependency": [ + "requiring the pivot report itself to link back to the same survey series incorrectly rules out valid topic rows", + "title extraction must use the pivot detail page rather than search-result snippets", + "related-resource expansion must continue even when the pivot report itself does not link back to the same survey series" + ], + "freeze": { + "historical_window": "currently linked 2024, 2023, and 2022 CFPB household financial well-being annual reports; topic disappearance is judged over that three-year chain, and pivot-report search is restricted to 2022-and-earlier reports" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "First, identify the CFPB household financial well-being annual report series whose latest version links directly to the 2023 and 2022 editions.", + "Using the 2022 edition as the baseline, retain only topics that appear in 2022 but are no longer retained in subsequent annual reports, and exclude the topic specifically marked as \"belongs to the same survey series.\"", + "For each topic, find the earliest non-series pivot report from 2022 or earlier, then count its directly listed related resources, how many link back to the same survey series, how many qualify under the appendix rule, and the appendix span of the final qualifying report." + ], + "exclusion_conditions": [ + "Exclude topics that are still retained in subsequent annual reports.", + "Exclude results that incorrectly treat \"the pivot report itself must link back to the same survey series\" as a hard condition for column 3.", + "Exclude search results that directly belong to the same survey series or reports after 2022." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "topic", + "first-missing-year", + "pivot-report-or-NONE", + "pivot-date-or-NONE", + "direct-related-count", + "same-series-count", + "qualified-count", + "representative-report-or-NONE", + "publication-date-or-NONE", + "appendix-span-or-NONE" + ], + "topic_order": "alphabetical by topic name", + "date_format": "pivot-date and publication-date use YYYY-MM-DD when present", + "appendix_span": "canonical span uses compact labels such as `A-D`", + "none_rule": "if qualified-count is 0, representative-report, publication-date, and appendix-span are all `NONE`" + } + } +} diff --git a/data_en/goal/consumerfinance_003-g.json b/data_en/goal/consumerfinance_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..2a8af682220282ad31f0ade3b8fd807fbc649e7b --- /dev/null +++ b/data_en/goal/consumerfinance_003-g.json @@ -0,0 +1,69 @@ +{ + "task_id": "consumerfinance_010-g", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I want to clearly organize the two waves of the Debt Collection Rule issued by the CFPB in 2020, including their respective proposal sources, delayed-effective-date arrangements, final effective dates, and the accompanying quick-reference PDF information on the implementation page. Specifically, I need the following: the exact issue date of each Final Rule; the originating proposed rule source and name, and the public comment deadline; whether the 2021 delayed-effective-date proposed rule applies to this batch of final rules, its public comment deadline, and the actual effective date that ultimately took effect; the quick-reference PDF file name on the official implementation page, and the first subheading in the body (excluding introductory or background paragraphs).", + "start_url": "https://www.consumerfinance.gov/rules-policy/final-rules/", + "output_format": "Output the two waves as a single-line string sorted by final-rule issue date from earliest to latest, identifying each wave by its final rule issue month (YYYY-MM):\n||||||||", + "oracle_answer": "2020-10|2020-10-30|2019-05-07 main|2019-09-18|YES|2021-05-19|2021-11-30|Executive summary of the October 2020 final rule|Coverage and Definitions,2020-12|2020-12-18|2019-05-07 main+2020-02-21 supplemental|2019-09-18+2020-08-04|YES|2021-05-19|2021-11-30|Executive summary of the December 2020 final rule|Validation Information Requirements and Disclosures", + "metadata": { + "State-Gated Retrieval": [ + "The two 2020 Debt Collection Practices (Regulation F) final rules that share the same name must be processed separately, not merged into one.", + "For each wave, independently confirm: the issue date, the corresponding proposal chain and public comment deadlines, whether the 2021 delayed-effective-date proposed rule covers it and its comment deadline, the final effective date, the corresponding implementation quick-reference PDF, and the first subheading in that PDF after skipping the introduction.", + "The detail page, proposal chain, and summary PDF for the October wave and the December wave must each be verified independently." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "final-rules index pages and rule-development pages yield the two 2020 Regulation F final-rule waves and their proposal branches", + "each final-rule detail page, delayed-effective-date proposal page, and implementation quick-reference PDF yields the wave-specific dates, linked proposals, comment deadlines, and first summary heading", + "final rows are produced only after the October and December waves are traced separately end to end" + ], + "control_dependency": [ + "two same-title final rules force correction from name-based collapsing to issue-date branching", + "proposal-chain validation must be done per wave; otherwise the later December chain contaminates the October row", + "implementation PDFs must be matched back to the correct wave rather than accepting the latest quick-reference page" + ], + "freeze": { + "historical_window": "the 2020-10 and 2020-12 Debt Collection Rule final-rule waves, their linked 2020 proposal pages, the 2021 delayed-effective-date proposal, and the current implementation-page quick-reference PDFs" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "The two 2020 Debt Collection Practices (Regulation F) final rules that share the same name must be processed separately, not merged into one.", + "For each wave, independently confirm: the issue date, the corresponding proposal chain and public comment deadlines, whether the 2021 delayed-effective-date proposed rule covers it and its comment deadline, the final effective date, the corresponding implementation quick-reference PDF, and the first subheading in that PDF after skipping the introduction.", + "The detail page, proposal chain, and summary PDF for the October wave and the December wave must each be verified independently." + ], + "exclusion_conditions": [ + "Exclude results that merge the two identically named 2020 final rules into one.", + "Exclude results that project the December wave's proposal chain or executive-summary heading onto the October wave.", + "Exclude results that are not independently verified against each wave's own final-rule detail page and corresponding PDF." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "wave", + "final-rule-date", + "proposal-chain", + "proposal-comment-closes", + "delay-proposal-applied", + "delay-proposal-comments-close", + "controlling-effective-date", + "quick-reference-pdf", + "summary-heading" + ], + "wave": "wave is the final-rule issue month in YYYY-MM", + "date_format": "all standalone date fields use YYYY-MM-DD", + "proposal_chain": "canonical chain joins proposal milestones with `+`, using pieces such as `2019-05-07 main` or `2020-02-21 supplemental` in chronological order", + "proposal_comment_closes": "join multiple comment-close dates with `+` in the same order as proposal_chain", + "delay_proposal_applied": "emit `YES` when a delay proposal is part of the chain; otherwise emit `NO`", + "quick_reference_pdf": "use the displayed quick-reference PDF title, not the filename", + "summary_heading": "use the first substantive heading from the final-rule PDF", + "sorting_or_selection": "final-rule-date ascending" + } + } +} diff --git a/data_en/goal/consumerfinance_004-g.json b/data_en/goal/consumerfinance_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..497d5ff995e5bb9fe7fe6ddbfa594ac8fac6224e --- /dev/null +++ b/data_en/goal/consumerfinance_004-g.json @@ -0,0 +1,68 @@ +{ + "task_id": "consumerfinance_011-g", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "On the CFPB enforcement actions page, find the most recent 2024 administrative enforcement action that has since been terminated, separately for Credit Cards and Deposits, and align the termination order with the corresponding clause information in the original Consent Order. Specifically, identify one action for each of the two Products labels: Credit Cards and Deposits. The candidate pool is limited to administrative enforcement actions under Enforcement actions with an Initial filing date between 2024-01-01 and 2024-12-31. For each product label, select the action with the latest Initial filing date among those meeting all of the following conditions (if tied, pick the one with the smaller docket number): Initial filing date between 2024-01-01 and 2024-12-31; case status changed to Expired, Terminated, or Dismissed; the document set includes a Consent Order, a Stipulation, an Order Terminating the Consent Order, and a press release; and the Products label currently maps uniquely to the target product. For each selected action, extract the following from its Order Terminating the Consent Order: TerminationDate (the termination date); TerminationAuthority (the exact text of the termination authority at its first occurrence); TermAuthorityPage (the PDF physical page number where this text first appears). Additionally, find the first explicit reference to a paragraph number of the original Consent Order within the termination order text; if it reads \"Paragraphs X and Y\", take only X. Then go back to the original Consent Order and find the section heading that contains that paragraph.", + "start_url": "https://www.consumerfinance.gov/enforcement/actions/", + "output_format": "Finally, output a single-line string in alphabetical order by product name: ||||||p||. If a product has no qualifying case, output: |NONE", + "oracle_answer": "Credit Cards|Apple Inc.|2024-CFPB-0012|2024-10-23|2025-09-22|12 U.S.C. § 5563(b)(3)|p1|83|ADMINISTRATIVE PROVISIONS,Deposits|Navy Federal Credit Union|2024-CFPB-0014|2024-11-07|2025-07-01|12 U.S.C. § 5563(b)(3)|p1|106|ADMINISTRATIVE PROVISIONS", + "metadata": { + "State-Gated Retrieval": [ + "Consider only administrative enforcement actions with an Initial filing date in 2024, and search for cases separately under Credit Cards and Deposits.", + "The case must have a status of Expired, Terminated, or Dismissed, and the page must simultaneously provide a Consent Order, Stipulation, Order Terminating the Consent Order, and Press release, with the Products label mapping one-to-one to the target category.", + "For each category, retain only the most recent qualifying case determined by Initial filing date, and compile the corresponding clause information from the termination order and the original Consent Order." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Enforcement-action list pages yield 2024 candidate actions by product branch.", + "Each action detail page and linked Consent Order, Stipulation, Order Terminating the Consent Order, and Press release documents yield status, initial filing date, single-product validity, and clause references.", + "Final rows are selected only after per-product comparison on Initial filing date and document-stack validation." + ], + "control_dependency": [ + "\"Latest\" must be determined by Initial filing date rather than termination date.", + "Product filters on the list page are insufficient until the action detail page confirms a single matching product.", + "Clause extraction in the terminating order must stay aligned with the original Consent Order rather than a superficially similar section." + ], + "freeze": { + "historical_window": "Administrative enforcement actions with Initial filing date from 2024-01-01 through 2024-12-31; current action status and currently linked Consent Order, Stipulation, terminating-order, and Press release documents." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Consider only administrative enforcement actions with an Initial filing date in 2024, and search for cases separately under Credit Cards and Deposits.", + "The case must have a status of Expired, Terminated, or Dismissed, and the page must simultaneously provide a Consent Order, Stipulation, Order Terminating the Consent Order, and Press release, with the Products label mapping one-to-one to the target category.", + "For each category, retain only the most recent qualifying case determined by Initial filing date, and compile the corresponding clause information from the termination order and the original Consent Order." + ], + "exclusion_conditions": [ + "Exclude results that use termination date instead of Initial filing date to determine \"latest\".", + "Exclude cases with an incomplete document stack or where Products does not map to a single target category.", + "Exclude cases where the required clause correspondence between the terminating order and the original Consent Order cannot be established." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Product", + "Respondent", + "Docket", + "InitialFilingDate", + "TerminationDate", + "TerminationAuthority", + "TermAuthorityPage", + "ReferencedParagraph", + "ConsentSectionHeading" + ], + "product_order": "Alphabetical by Product name", + "fallback_row": "If a product has no qualifying case, emit `|NONE`", + "date_format": "InitialFilingDate and TerminationDate use YYYY-MM-DD", + "termination_authority": "Use the canonical statute string extracted from the termination order", + "page_fields": "TermAuthorityPage uses the canonical `pN` form", + "ReferencedParagraph": "Emit the paragraph number as a plain numeric string", + "ConsentSectionHeading": "Emit the uppercase heading of the consent-order section containing the referenced paragraph" + } + } +} diff --git a/data_en/goal/consumerfinance_005-g.json b/data_en/goal/consumerfinance_005-g.json new file mode 100644 index 0000000000000000000000000000000000000000..9e6762e5d7ea656449520f7b35de124d537396a3 --- /dev/null +++ b/data_en/goal/consumerfinance_005-g.json @@ -0,0 +1,75 @@ +{ + "task_id": "consumerfinance_012-g", + "domain": "CFPB_COMPLAINT_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am preparing an internal outreach memo on historical complaint clusters and want to track a specific set of complaints: in the CFPB Complaint Database, identify complaints under the current product bucket covering credit reporting and other personal consumer reports, received between 2018-01-01 and 2021-12-31, tagged as Servicemember, with a public narrative, and whose text explicitly mentions medical bills or doctors. Please provide two representative complaint clusters: the first is the peak month of this cohort; the second is the latest month in this cohort whose complaint count is still at least half of the peak count. For each cluster, report the total complaint count for that month, the state with the highest complaint count in that month and its count, the company with the highest complaint count in that state and month and its count, and the earliest complaint received by that company in that state and month, including its ID, date, Issue, and Sub-issue. Output a single line with Peak first and LatestHalfPeak second, using the format: ||||||||||.", + "start_url": "https://www.consumerfinance.gov/data-research/consumer-complaints/", + "output_format": "Output a single line with Peak first and LatestHalfPeak second, using the format: ||||||||||. Join the Peak and LatestHalfPeak clusters with a comma. For ties: months are ordered chronologically; states are ordered by state abbreviation alphabetically ascending, taking the first; companies are ordered by company name alphabetically ascending, taking the first; for the earliest complaint, if multiple complaints share the same date, take the one with the smallest Complaint ID.", + "oracle_answer": "Peak|2018-02|46|CA|28|TRANSUNION INTERMEDIATE HOLDINGS, INC.|9|2806154|2018-02-07|Improper use of your report|Reporting company used your report improperly,LatestHalfPeak|2021-11|23|CA|12|EQUIFAX, INC.|3|4928768|2021-11-19|Problem with a credit reporting company's investigation into an existing problem|Their investigation did not fix an error on your report", + "metadata": { + "State-Gated Retrieval": [ + "Only consider complaints under the current product bucket for credit reporting / other personal consumer reports, received from 2018-01-01 to 2021-12-31, tagged as Servicemember, with a public narrative, and whose text explicitly mentions medical bills or doctors.", + "The first cluster must be the peak month of this cohort; the second cluster must be the latest month in this cohort whose complaint count is at least half of the peak count.", + "For each cluster, recompute the top company within the corresponding month-state subset, then locate the earliest complaint received by that company in that state and month." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current complaint-form taxonomy yields the product bucket that contains credit reporting / other personal consumer reports", + "filtered complaint records yield month counts, month-state subsets, top companies, and earliest complaint details inside each chosen subset", + "final rows are produced only after peak month and latest-half-peak month are determined, and each downstream aggregate is computed inside its narrower month-state cohort" + ], + "control_dependency": [ + "the latest month must be defined as the latest month whose count is at least ceil(PeakCount / 2)", + "overall top-company counts cannot be projected into a month-state subset without recomputation", + "earliest complaint selection is only valid after the month, state, and company filters are all frozen" + ], + "freeze": { + "historical_window": "Complaint Database records received from 2018-01-01 through 2021-12-31 under the current product-bucket mapping for the credit-reporting / other personal consumer reports family; Servicemember + public narrative + medical bills/doctors text cohort" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only consider complaints under the current product bucket for credit reporting / other personal consumer reports, received from 2018-01-01 to 2021-12-31, tagged as Servicemember, with a public narrative, and whose text explicitly mentions medical bills or doctors.", + "The first cluster must be the peak month of this cohort; the second cluster must be the latest month in this cohort whose complaint count is at least half of the peak count.", + "For each cluster, recompute the top company within the corresponding month-state subset, then locate the earliest complaint received by that company in that state and month." + ], + "exclusion_conditions": [ + "Exclude results that directly treat the latest month with any complaints as the second cluster.", + "Exclude results that first find an overall top company in the full cohort and then project it onto a month-state subset.", + "Exclude results that do not first derive the half-peak threshold from PeakCount." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Cluster", + "Month", + "MonthComplaints", + "TopState", + "StateComplaints", + "TopCompany", + "CompanyComplaints", + "EarliestComplaintID", + "EarliestDate", + "Issue", + "SubIssue" + ], + "cluster_order": [ + "Peak", + "LatestHalfPeak" + ], + "date_format": { + "Month": "YYYY-MM", + "EarliestDate": "YYYY-MM-DD" + }, + "TopState": "use the uppercase two-letter state abbreviation", + "TopCompany": "use the company display name as shown in the source data", + "tie_breaks": "for tied months use chronological order; for tied states use state-code alphabetical order; for tied companies use company-name alphabetical order; for the earliest complaint use EarliestDate ascending then Complaint ID ascending", + "SubIssue": "emit `NONE` when the complaint row has no sub-issue value" + } + } +} diff --git a/data_en/goal/consumerfinance_006-g.json b/data_en/goal/consumerfinance_006-g.json new file mode 100644 index 0000000000000000000000000000000000000000..293864558803bf572ca3190b4056dd3d3eaddac5 --- /dev/null +++ b/data_en/goal/consumerfinance_006-g.json @@ -0,0 +1,78 @@ +{ + "task_id": "consumerfinance_013-g", + "domain": "CFPB_COMPLAINT_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am collecting data for an internal crypto-complaint concentration memo and need to identify two representative complaint-month clusters from the CFPB complaint database and extract their core data records.\nThe data must come from a specific cohort: the product category must correspond to the current form’s bucket for Virtual currency, with the sub-product explicitly set to Virtual currency; the time window is strictly 2019-08-26 through 2022-08-26.\nWithin this cohort, the two characteristic months to identify are:\n• Original peak month (AllCompanies): the month with the absolute highest complaint volume in the cohort without removing any company.\n• Residual peak month (ResidualAfterTop2): after identifying the two companies with the highest complaint volume in the original peak month and completely removing all records of those two companies from the entire three-year analysis period, the month with the highest complaint volume that emerges from the remaining data.\nFor these two specific months, I need detailed attributes: total complaints for that month, the names of the two removed companies and their combined complaint contribution in the original peak month, the state with the highest complaint volume in that month and its volume, and the earliest complaint detail (including ID, date, Issue, and Sub-issue) for the most complained-about company within that state and month.\nPlease confirm the identity of these two months and output one formatted string per month with no spaces, in the order AllCompanies first, ResidualAfterTop2 second. The field sequence per row is strictly: ||||||||||||\nSpecial notes:\n• The field must be filled with AllCompanies or ResidualAfterTop2 accordingly.\n• ExcludedTop2Companies and ExcludedTop2PeakMonthComplaints in both rows refer to the two companies identified from the original peak month and their combined complaint volume at that time.\n• The four Earliest-related fields must correspond to the earliest complaint record for the top company in that state and month.\n• To ensure a unique answer: output the two records in the order AllCompanies, ResidualAfterTop2; list ExcludedTop2Companies in descending order of their complaint volume in the original peak month, breaking ties alphabetically by field value; if the earliest complaint date is tied, take the one with the smallest Complaint ID.", + "start_url": "https://www.consumerfinance.gov/data-research/consumer-complaints/", + "output_format": "Output one formatted string per row with no spaces, in the order AllCompanies first, ResidualAfterTop2 second. The field sequence per row is strictly: ||||||||||||.", + "oracle_answer": "AllCompanies|2021-05|336|Coinbase, Inc.+BAM Management US Holdings Inc.|226|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,ResidualAfterTop2|2020-06|180|Coinbase, Inc.+BAM Management US Holdings Inc.|226|OH|28|PNC Bank N.A.|22|3687376|2020-06-07|Other transaction problem|NONE", + "metadata": { + "State-Gated Retrieval": [ + "Only consider Complaint Database records under the current product bucket for Virtual currency, with sub-product Virtual currency, and received between 2019-08-26 and 2022-08-26.", + "First determine the AllCompanies original peak month, then identify the top two companies by complaint volume in that peak month.", + "These two companies must be completely removed from the entire three-year cohort, then recompute the residual peak month and all downstream fields based on the remaining cohort." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current complaint-form taxonomy yields the product bucket for Virtual currency", + "complaint records within the fixed three-year cohort yield the all-company peak month, per-month top companies, and residual-cohort recomputations after company removal", + "final rows are produced only after the top-2 companies from the original peak month are removed from the full cohort and downstream aggregates are computed on the resulting cohort" + ], + "control_dependency": [ + "peak-month top companies must be removed from the entire cohort, not only from the original peak month", + "residual peak detection must be computed from the rewritten cohort rather than by local patching of the original month", + "downstream state / company / earliest-complaint fields are valid only after the global company-removal step is locked" + ], + "freeze": { + "historical_window": "Complaint Database records received from 2019-08-26 through 2022-08-26 under the current product-bucket mapping for Virtual currency" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only consider Complaint Database records under the current product bucket for Virtual currency, with sub-product Virtual currency, and received between 2019-08-26 and 2022-08-26.", + "First determine the AllCompanies original peak month, then identify the top two companies by complaint volume in that peak month.", + "These two companies must be completely removed from the entire three-year cohort, then recompute the residual peak month and all downstream fields based on the remaining cohort." + ], + "exclusion_conditions": [ + "Exclude results that only locally delete the top-2 company records from the original peak month.", + "Exclude results that do not reapply the top-2 company set to the entire cohort before recomputing the residual peak.", + "Exclude downstream state, company, or earliest-complaint fields based on a cohort that has not been recomputed after removal." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Cluster", + "Month", + "MonthComplaints", + "ExcludedTop2Companies", + "ExcludedTop2PeakMonthComplaints", + "TopState", + "StateComplaints", + "TopCompany", + "CompanyComplaints", + "EarliestComplaintID", + "EarliestDate", + "Issue", + "SubIssue" + ], + "cluster_order": [ + "AllCompanies", + "ResidualAfterTop2" + ], + "date_format": { + "Month": "YYYY-MM", + "EarliestDate": "YYYY-MM-DD" + }, + "ExcludedTop2Companies": "join the two excluded company names with `+` in source-peak complaint-count descending order, breaking ties alphabetically", + "TopState": "use the uppercase two-letter state abbreviation", + "TopCompany": "use the company display name as shown in the source data", + "tie_breaks": "for the earliest complaint use EarliestDate ascending then Complaint ID ascending", + "SubIssue": "emit `NONE` when the complaint row has no sub-issue value" + } + } +} diff --git a/data_en/goal/consumerfinance_007-g.json b/data_en/goal/consumerfinance_007-g.json new file mode 100644 index 0000000000000000000000000000000000000000..2284abbdda099fd6750b92ee23a8e8b5e99451f9 --- /dev/null +++ b/data_en/goal/consumerfinance_007-g.json @@ -0,0 +1,82 @@ +{ + "task_id": "consumerfinance_014-g", + "domain": "CFPB_COMPLAINT_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "I am writing an internal crypto-complaint sensitivity waterfall memo and need to extract four characteristic months (Clusters) at different filtering stages from the CFPB complaint database, along with their core data.\n\nThe underlying complaint cohort has clear boundaries: time is strictly limited to between 2020-01-01 and 2022-08-26, and it includes only complaint records classified under the \"Virtual currency\" subcategory within the current product taxonomy.\n\nBased on this underlying cohort, I need to identify four characteristic peak months representing different successive exclusion stages:\n• BaselinePeak: The absolute peak month with the highest total complaint volume in the initial complaint pool.\n• AfterDominantPublicResponse: After globally removing all complaints related to the dominant Company public response from the BaselinePeak month, the new peak month in the remaining data pool.\n• AfterDominantPublicResponseAndIssue: After further globally removing all complaints related to the dominant Issue from the second-round peak month, the third-round peak month formed from the remaining data.\n• AfterDominantPublicResponseIssueAndCompany: After finally globally removing all complaints related to the most complained-about Company from the third-round peak month, the final peak month that emerges from the remaining data.\n\nFor these four characteristic months, I need their data under each respective filtering state: total complaints for that month, the new exclusion dimension triggered in this round (NewExclusionType) and its specific value (NewExclusionValue), the frequency of that excluded value in its \"source peak month\", the state with the highest complaint volume in that month and its complaint count, the most complained-about company within that state and its complaint count, and the detailed information (ID, date, Issue, and Sub-issue) of the earliest complaint received by that top company in that state and characteristic month.\n\nPlease confirm the identity and data for these four characteristic months, and output four formatted strings with no spaces, strictly in the specific order: BaselinePeak, AfterDominantPublicResponse, AfterDominantPublicResponseAndIssue, AfterDominantPublicResponseIssueAndCompany. The field sequence for each row must be fixed as:\n|||||||||||||\n\nFor ties, always select in ascending lexicographic order; for the earliest complaint with the same date, select by ascending Complaint ID numerically. Normalize all empty values to NONE before sorting.", + "start_url": "https://www.consumerfinance.gov/data-research/consumer-complaints/", + "output_format": "Output four formatted strings with no spaces, strictly in the specific order: BaselinePeak, AfterDominantPublicResponse, AfterDominantPublicResponseAndIssue, AfterDominantPublicResponseIssueAndCompany. The field sequence for each row must be fixed as: |||||||||||||. For ties, always select in ascending lexicographic order; for the earliest complaint with the same date, select by ascending Complaint ID numerically. Normalize all empty values to NONE before sorting.", + "oracle_answer": "BaselinePeak|2021-05|336|NONE|NONE|0|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,AfterDominantPublicResponse|2022-07|31|Company public response|NONE|321|CA|6|BANK OF AMERICA, NATIONAL ASSOCIATION|4|5735227|2022-07-05|Other transaction problem|NONE,AfterDominantPublicResponseAndIssue|2021-10|13|Issue|Fraud or scam|26|TX|2|BANK OF AMERICA, NATIONAL ASSOCIATION|1|4821611|2021-10-18|Other transaction problem|NONE,AfterDominantPublicResponseIssueAndCompany|2021-06|8|Company|Foris DAX, Inc.|5|NC|3|TRUIST FINANCIAL CORPORATION|2|4462160|2021-06-15|Money was not available when promised|NONE", + "metadata": { + "State-Gated Retrieval": [ + "Only consider Complaint Database records under the Virtual currency subcategory within the current product bucket, with a received date between 2020-01-01 and 2022-08-26.", + "Sequentially determine the peak months for the four stages: BaselinePeak, AfterDominantPublicResponse, AfterDominantIssue, and AfterDominantCompany, as required by the task.", + "Each identified dominant Company public response, dominant Issue, and dominant Company must be written back to the corresponding upstream residual cohort, globally removed, and then the next round of statistics must be recalculated." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current complaint-form taxonomy yields the product bucket for Virtual currency", + "complaint records yield the baseline peak plus the dominant Company public response, dominant Issue, and dominant Company at successive residual-peak states", + "final rows are produced only after each dominant value is applied to the full upstream residual cohort and then used to determine the next peak" + ], + "control_dependency": [ + "dominant values found in a peak month cannot be deleted only inside that month; each must be propagated to the full upstream cohort", + "each new residual peak depends on the prior round's global rewrite, so local month-by-month deletion gives the wrong chain", + "downstream counts and exemplar complaints are valid only after the full three-stage waterfall is executed" + ], + "freeze": { + "historical_window": "Complaint Database records received from 2020-01-01 through 2022-08-26 under the current product-bucket mapping for Virtual currency" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only consider Complaint Database records under the Virtual currency subcategory within the current product bucket, with a received date between 2020-01-01 and 2022-08-26.", + "Sequentially determine the peak months for the four stages: BaselinePeak, AfterDominantPublicResponse, AfterDominantIssue, and AfterDominantCompany, as required by the task.", + "Each identified dominant Company public response, dominant Issue, and dominant Company must be written back to the corresponding upstream residual cohort, globally removed, and then the next round of statistics must be recalculated." + ], + "exclusion_conditions": [ + "Exclude results that only delete records locally within the current peak month without writing back to the entire upstream cohort.", + "Exclude results that do not re-find the next peak month on each round's residual cohort.", + "Exclude intermediate or final fields based on downstream statistics that were not recalculated globally." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Cluster", + "Month", + "MonthComplaints", + "NewExclusionType", + "NewExclusionValue", + "NewExclusionCountInSourcePeak", + "TopState", + "StateComplaints", + "TopCompany", + "CompanyComplaints", + "EarliestComplaintID", + "EarliestDate", + "Issue", + "SubIssue" + ], + "cluster_order": [ + "BaselinePeak", + "AfterDominantPublicResponse", + "AfterDominantPublicResponseAndIssue", + "AfterDominantPublicResponseIssueAndCompany" + ], + "date_format": { + "Month": "YYYY-MM", + "EarliestDate": "YYYY-MM-DD" + }, + "NewExclusionType": "emit the canonical exclusion-type label from the source workflow; when no new exclusion is applied, emit `NONE`", + "NewExclusionValue": "emit the canonical excluded value; when no value exists, emit `NONE`", + "TopState": "use the uppercase two-letter state abbreviation", + "TopCompany": "use the company display name as shown in the source data", + "tie_breaks": "normalize empty values to `NONE` before sorting; for other ties use lexicographic order ascending, and for the earliest complaint use EarliestDate ascending then Complaint ID ascending", + "SubIssue": "emit `NONE` when the complaint row has no sub-issue value" + } + } +} diff --git a/data_en/goal/europemc_001-g.json b/data_en/goal/europemc_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..db66433b11f7f9b8ebe4648fd01b76016f812f27 --- /dev/null +++ b/data_en/goal/europemc_001-g.json @@ -0,0 +1,67 @@ +{ + "task_id": "europemc_001-g", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 21, + "instruction": "I want to consolidate into a single line the admission variables actually used by several prediction schemes in this 2020 COVID-19 mortality risk prediction paper, so that it is easy to see which variables overlap across schemes and which appear only in the comparator schemes.\nSpecifically, the target paper is a 2020 open-access review whose title contains all three terms \"prognosis model\", \"mortality risk\", and \"COVID-19\", and whose main text discusses Wuhan inpatients.\nThe variables to retain fall into two categories: (1) admission variables that appear in both the Random Forest and XGBoost variable importance rankings; (2) admission variables that do not appear in both rankings but are additional variables present in the CURB-65 or NEWS schemes used by the authors as comparators.\nFormat each variable as follows:\nvariable~RF_rank_or_0~XGB_rank_or_0~F~C~N~X\nwhere:\n\t•\tRF is the variable's rank in the Random Forest ranking, or 0 if absent;\n\t•\tXGB is the variable's rank in the XGBoost ranking used in the paper, or 0 if absent;\n\t•\tF, C, N, X indicate, respectively, whether the variable entered the authors' final logistic regression model, belongs to CURB-65, belongs to NEWS, and belongs to the XGBoost model used as a comparator in the paper.\nFinally, sort all variables alphabetically by variable name, join them with | into a single line; if the target paper cannot be found, output NONE.", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "Format each variable as follows:\nvariable~RF_rank_or_0~XGB_rank_or_0~F~C~N~X\nwhere:\n\t•\tRF is the variable's rank in the Random Forest ranking, or 0 if absent;\n\t•\tXGB is the variable's rank in the XGBoost ranking used in the paper, or 0 if absent;\n\t•\tF, C, N, X indicate, respectively, whether the variable entered the authors' final logistic regression model, belongs to CURB-65, belongs to NEWS, and belongs to the XGBoost model used as a comparator in the paper.\nFinally, sort all variables alphabetically by variable name, join them with | into a single line; if the target paper cannot be found, output NONE.", + "oracle_answer": "Age~4~2~1~1~0~0|Alanine aminotransferase~17~11~0~0~0~0|Aspartate transaminase~6~4~0~0~0~0|Blood urea nitrogen~5~7~0~1~0~0|Confusion~0~0~0~1~1~0|CRP~2~6~1~0~0~1|Creatinine~9~13~0~0~0~0|Diastolic pressure~16~17~0~1~0~0|Heart rate~15~14~0~0~1~0|LDH~1~1~1~0~0~1|Lymphocyte count~3~5~0~0~0~1|Monocytes~12~16~0~0~0~0|Neutrophil~7~3~0~0~0~0|Normal platelet~10~9~0~0~0~0|Oxygen inhalation~0~0~0~0~1~0|Respiratory rate~11~10~0~1~1~0|SPO2~0~0~0~0~1~0|Systolic pressure~13~12~0~1~1~0|Temperature~18~18~0~0~1~0|Total bilirubin~14~15~0~0~0~0|White blood cell~8~8~0~0~0~0", + "metadata": { + "State-Gated Retrieval": [ + "First locate the target paper: a 2020 open-access review whose title contains all three terms \"prognosis model\", \"mortality risk\", and \"COVID-19\", and whose main text discusses Wuhan inpatients.", + "Retain only two categories of variables: admission variables that appear in both the Random Forest and XGBoost rankings; or admission variables that, although not appearing in both rankings, belong to the CURB-65 or NEWS comparator schemes.", + "For each variable, annotate the RF rank, XGB rank, and whether it belongs to the final logistic regression, CURB-65, NEWS, and the comparator XGBoost model as required, then output sorted alphabetically by variable name." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Europe PMC search results and the target open-access article yield the candidate Wuhan COVID mortality-risk review", + "article tables and discussion sections yield RF/XGBoost rankings, final logistic-regression inclusion, and comparator-variable memberships for CURB-65 / NEWS / external XGBoost", + "final rows are produced only after overlapping variables and comparator-only variables are merged into one normalized variable table" + ], + "control_dependency": [ + "comparator-only variables must be captured from the discussion definitions rather than from Table 2 + Table 3 alone", + "comparator membership must be read from the article's explicit scheme definitions rather than inferred from common clinical usage", + "variable normalization must wait until RF/XGBoost overlap and comparator-only additions are both complete" + ], + "freeze": { + "historical_window": "the 2020 open-access COVID-19 mortality-risk review about Wuhan inpatients; variable inclusion and comparator definitions are taken from the article's current full-text tables and discussion" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "First locate the target paper: a 2020 open-access review whose title contains all three terms \"prognosis model\", \"mortality risk\", and \"COVID-19\", and whose main text discusses Wuhan inpatients.", + "Retain only two categories of variables: admission variables that appear in both the Random Forest and XGBoost rankings; or admission variables that, although not appearing in both rankings, belong to the CURB-65 or NEWS comparator schemes.", + "For each variable, annotate the RF rank, XGB rank, and whether it belongs to the final logistic regression, CURB-65, NEWS, and the comparator XGBoost model as required, then output sorted alphabetically by variable name." + ], + "exclusion_conditions": [ + "Exclude admission variables that appear in neither both RF and XGB rankings nor the CURB-65 / NEWS additional variables.", + "Exclude results that stop at Table 2 + Table 3 without proceeding to the discussion to read the comparator definitions.", + "Exclude results that infer comparator variables from common knowledge rather than verifying against the paper's explicit definitions." + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "variable", + "RF_rank_or_0", + "XGB_rank_or_0", + "F", + "C", + "N", + "X" + ], + "variable": "use the variable wording normalized in the article tables; keep `Systolic pressure` and `Diastolic pressure` as separate variables", + "rank_fields": "RF_rank_or_0 and XGB_rank_or_0 are positive integer ranks when present, otherwise 0", + "boolean_fields": "F, C, N, and X are emitted as 1 or 0 only", + "sorting_or_selection": "variable name alphabetical ascending", + "stop_condition": [ + "the shared variable set from Table 2 and Table 3 is fully resolved", + "the comparator definitions for CURB-65, NEWS, and the comparison XGBoost model are fixed before the final line is emitted" + ] + } + } +} diff --git a/data_en/goal/europemc_002-g.json b/data_en/goal/europemc_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..f00b6670b5215eb3c5ec02918d99606a4b936616 --- /dev/null +++ b/data_en/goal/europemc_002-g.json @@ -0,0 +1,62 @@ +{ + "task_id": "europemc_002-g", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 6, + "instruction": "Track Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline review by ClinicalTrials.gov identifier, and check whether they persist in the 2022 and 2023 open-access reviews of the same series. Only include studies that were Phase 1 in the 2021 review and can still be found under the same ClinicalTrials.gov identifier in both the 2022 and 2023 reviews. Do not rely on drug names alone, as they may change. Output all qualifying studies as a single line in the format: NCT~2021 drug~2022 phase~2022 drug~2023 phase~2023 drug, sorted by NCT ascending and joined by |. If the three papers cannot be found, output NONE.", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "Output all qualifying studies as a single line in the format: NCT~2021 drug~2022 phase~2022 drug~2023 phase~2023 drug, sorted by NCT ascending and joined by |. If no qualifying studies exist, output NONE.", + "oracle_answer": "NCT03277573~Salsalate~P1~Salsalate~P1~Salsalate|NCT03634007~AAVrh.10hAPOE2~P1~LX1001~P2~LX1001|NCT03748303~Allopregnanolone (Allo)~P1~Allopregnanolone~P1~Allopregnanolone|NCT04149860~Lu AF87908~P1~Lu AF87908~P1~Lu AF87908|NCT04451408~LY3372993~P1~LY3372993~P1~LY3372993|NCT04500847~Emtricitabine~P1~Emtricitabine~P1~Emtricitabine", + "metadata": { + "State-Gated Retrieval": [ + "Only use Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline article as the baseline.", + "Whether a study is retained in 2022 and 2023 must be determined by exact matching on the same ClinicalTrials.gov NCT identifier, not by drug name alone.", + "Only retain studies that can be found under the same NCT in both 2022 and 2023, and output them sorted by NCT ascending." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2021, 2022, and 2023 pipeline reviews yield the 2021 Phase 1 baseline cohort and the later-year lookup tables", + "article tables yield exact ClinicalTrials.gov NCT IDs, yearly phase labels, and yearly drug names for the same study", + "final rows are produced only after 2021 baseline studies are re-identified in both later reviews by exact NCT matching" + ], + "control_dependency": [ + "continuation must be matched by exact NCT rather than by drug name, because drug names drift across years", + "2022 and 2023 lookups must use the fixed 2021 Phase 1 NCT set as the starting cohort rather than later-year table membership alone", + "yearly phase/name fields are only valid after the same NCT is confirmed across all three reviews" + ], + "freeze": { + "historical_window": "the 2021, 2022, and 2023 open-access Alzheimer's disease drug development pipeline reviews; the baseline is the 2021 Phase 1 cohort and continuation is matched by exact ClinicalTrials.gov NCT" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only use Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline article as the baseline.", + "Whether a study is retained in 2022 and 2023 must be determined by exact matching on the same ClinicalTrials.gov NCT identifier, not by drug name alone.", + "Only retain studies that can be found under the same NCT in both 2022 and 2023, and output them sorted by NCT ascending." + ], + "exclusion_conditions": [ + "Exclude results that are continued only by drug name without exact matching on the same ClinicalTrials.gov identifier.", + "Exclude studies found only in 2022 or only in 2023, not continuously retained in both years.", + "Exclude studies not in the 2021 baseline Phase 1 set." + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "NCT", + "agent_2021", + "phase_2022", + "agent_2022", + "phase_2023", + "agent_2023" + ], + "NCT": "use the exact ClinicalTrials.gov identifier as the cross-year identity key", + "phase_fields": "normalize phases to P1, P2, or P3; if the same NCT appears multiple times in a year, keep the highest phase for that year", + "agent_fields": "keep the agent text as shown in each year-specific table", + "sorting_or_selection": "NCT ascending" + } + } +} diff --git a/data_en/goal/europemc_003-g.json b/data_en/goal/europemc_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..3515bf25ce557e23039ef48924c60c6bbeee4c1a --- /dev/null +++ b/data_en/goal/europemc_003-g.json @@ -0,0 +1,63 @@ +{ + "task_id": "europemc_003-g", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "Identify the candidate molecules predicted in the 2023 \"Antibodies to Watch\" article to file their first marketing applications in 2022–2023, and determine which of them have actually received first approval or entered first regulatory review in the 2024 installment of the same series.\nSpecifically, the scope is limited to the open-access full texts of the 2023 and 2024 \"Antibodies to Watch\" articles in Europe PMC. Retain only those molecules that were listed in the 2023 article as **\"predicted to file first marketing applications in 2022–2023\"** and that, by the 2024 article, have either been approved or have entered first regulatory review.\nFor each qualifying molecule, output a record in the format:\nINN~2023_category~2023_prediction_label~2024_status~2024_indication~2024_region\nwhere:\n\t•\t2023_category is NC (non-cancer) or CA (cancer);\n\t•\t2024_status is A (first approval) or R (first regulatory review).\nFinally, sort records alphabetically by INN, join them with | into a single line, and output that line. If neither article can be found, output NONE.", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "For each qualifying molecule, output: INN~2023_category~2023_prediction_label~2024_status~2024_indication~2024_region\nwhere:\n\t•\t2023_category is NC (non-cancer) or CA (cancer);\n\t•\t2024_status is A (first approval) or R (first regulatory review).\nSort records alphabetically by INN, join them with | into a single line, and output that line. If neither article can be found, output NONE.", + "oracle_answer": "Cosibelimab~CA~MAA,Q2 2023~R~Squamous cell carcinoma~US|Elranatamab~CA~2023~A~Multiple myeloma~US,EU,Switzerland,Brazil|Garadacimab~NC~BLA,2023~R~Hereditary angioedema~EU|Odronextamab~CA~BLA,H2 2022~R~Diffuse large B-cell lymphoma~US,EU|Pozelimab~NC~BLA,H2 2022~A~CHAPLE disease~US|Suciraslimab~NC~NDA,2023~R~Rheumatoid arthritis~China|Talquetamab~CA~2023–25~A~Multiple myeloma~US,EU,UK,Switzerland|Zolbetuximab~CA~BLA,2023~R~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China", + "metadata": { + "State-Gated Retrieval": [ + "First, in the 2023 Antibodies to Watch article, identify all candidate molecules predicted to file first marketing applications in 2022–2023.", + "Then, in the 2024 article of the same series, check each of these molecules and retain only those that have received first approval or entered first regulatory review.", + "The 2024 status must distinguish A = first approval from R = first regulatory review, and the 2024 indication and region must be included." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2023 Antibodies to Watch article yields the forecast baseline of candidates expected to file in 2022-2023", + "the 2024 article tables yield first-approval outcomes, first-regulatory-review outcomes, indications, and regions for the same INNs", + "final rows are produced only after Table 1 approvals and Table 2 first-review candidates are merged back onto the 2023 forecast cohort" + ], + "control_dependency": [ + "both 2024 Table 1 and Table 2 must be read so that first-review-but-not-yet-approved candidates are retained", + "2024 status coding must distinguish approval from first regulatory review instead of collapsing both into a single positive match", + "region and indication fields are valid only after the 2023 forecast cohort is reconciled against both 2024 tables" + ], + "freeze": { + "historical_window": "the 2023 and 2024 open-access Antibodies to Watch articles; baseline candidates come from the 2023 forecast set and 2024 outcomes come from current Table 1 plus Table 2" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "First, in the 2023 Antibodies to Watch article, identify all candidate molecules predicted to file first marketing applications in 2022–2023.", + "Then, in the 2024 article of the same series, check each of these molecules and retain only those that have received first approval or entered first regulatory review.", + "The 2024 status must distinguish A = first approval from R = first regulatory review, and the 2024 indication and region must be included." + ], + "exclusion_conditions": [ + "Exclude results that only check approvals in 2024 Table 1 without also consulting Table 2 for first-regulatory-review candidates.", + "Exclude molecules not in the 2023 forecast baseline.", + "Exclude candidates that in 2024 have neither received first approval nor entered first regulatory review." + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "INN", + "category_2023", + "prediction_label_2023", + "status_2024", + "indication_2024", + "region_2024" + ], + "category_2023": "emit `NC` or `CA` exactly", + "prediction_label_2023": "keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H2 2022`", + "status_2024": "emit `A` for first approval and `R` for first regulatory review", + "region_2024": "preserve the raw region string but remove spaces after commas, for example `US,EU`", + "sorting_or_selection": "INN alphabetical ascending" + } + } +} diff --git a/data_en/goal/europemc_004-g.json b/data_en/goal/europemc_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..96c69026a53cd24f7610295bb5db4054e6d5893a --- /dev/null +++ b/data_en/goal/europemc_004-g.json @@ -0,0 +1,67 @@ +{ + "task_id": "europemc_004-g", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 9, + "instruction": "I am evaluating the accuracy of annual antibody watchlist predictions. Based on the Europe PMC database, I need to identify a set of candidate antibodies (INNs) whose progress has clearly lagged behind, and extract their status changes over the three-year period.\nThese target antibodies are special because their dynamics are continuously recorded across three open-access full-text articles in the Antibodies to Watch series from 2022, 2023, and 2024. Specifically, they were originally listed as \"expected to be submitted for review soon\" in the 2022 article, but due to delays, they remained as candidates on the watchlist in the 2023 article. Screening should be done at the antibody-candidate level, not by exact name string matching. If the 2022 article uses a drug code, project name, or other identifiable name, and the 2023 or 2024 article explicitly provides its correspondence to a specific INN, it should be treated as the same candidate entity, and the confirmed INN should be used in the final output.\nFor these continuously delayed candidate antibodies, I need to determine their final status in the 2024 article: whether they finally received first approval, are in first regulatory review, remain on a subsequent watchlist, or have completely disappeared from the main 2024 article list.\nPlease help me identify this set of antibodies and output the extracted parameters as a single-line string joined by |, strictly sorted alphabetically by INN. If the three target articles cannot all be found in the database, output NONE. The internal field order for each antibody must be fixed as: INN~2022 category~2022 phase~2023 prediction label~2024 status~2024 phase or NA~2024 indication or NA~2024 region or NA. No extra spaces should be added around the delimiters in the output, but original spaces within fields should be preserved. Use CA/NC uniformly for 2022 category, P2/P3 for phase, and A/R/F/D for 2024 status, representing First approved, In first regulatory review, subsequent watchlist, and disappeared from the 2024 main article list, respectively.", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "Output the extracted parameters as a single-line string joined by |, strictly sorted alphabetically by INN. If the three target articles cannot all be found in the database, output NONE. The internal field order for each antibody must be fixed as: INN~2022 category~2022 phase~2023 prediction label~2024 status~2024 phase or NA~2024 indication or NA~2024 region or NA. No extra spaces should be added around the delimiters in the output, but original spaces within fields should be preserved. Use CA/NC uniformly for 2022 category, P2/P3 for phase, and A/R/F/D for 2024 status, representing First approved, In first regulatory review, subsequent watchlist, and disappeared from the 2024 main article list, respectively.", + "oracle_answer": "Apamistamab-I-131~CA~P3~BLA,H1 2023~F~P3~Ablation of bone marrow prior to transplantation in AML patients~NA|Bentracimab~NC~P3~BLA,Q4 2022~F~P3~Reversal of the antiplatelet effects of ticagrelor~NA|Cosibelimab~CA~P3~MAA,Q2 2023~R~NA~Squamous cell carcinoma~US|Erfonrilimab~CA~P3~NDA~F~P3~Pancreatic ductal adenocarcinoma~NA|Odronextamab~CA~P2~BLA,H2 2022~R~NA~Diffuse large B-cell lymphoma~US,EU|Talquetamab~CA~P2~2023-25~A~NA~Multiple myeloma~US,EU,UK,Switzerland|Tiragolumab~CA~P3~2023~F~P3~NSCLC~NA|Zanidatamab~CA~P2~2023~D~NA~NA~NA|Zolbetuximab~CA~P3~BLA,2023~R~NA~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China", + "metadata": { + "State-Gated Retrieval": [ + "Start with the 2022 Antibodies to Watch candidates listed as \"expected to be submitted for review soon\" as the baseline, but retain only those molecules that still remain as watchlist candidates in the 2023 same-series article.", + "For these continuously delayed candidates, then determine their final status in the 2024 article: first approved, in first regulatory review, or completely absent from Tables 1-4.", + "Name comparison must handle the Apamistamab naming drift; complete absence in 2024 must be explicitly encoded as D." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2022, 2023, and 2024 Antibodies to Watch articles yield the 2022 soon-to-file baseline, 2023 carry-over membership, and 2024 status tables", + "article tables and full-text naming context yield name normalizations, 2024 table presence/absence, and final status labels for each carried-over INN", + "final rows are produced only after 2022 candidates are filtered by 2023 carry-over status and then resolved against 2024 Tables 1-4 plus explicit absence" + ], + "control_dependency": [ + "2022 candidates must first be filtered by 2023 carry-over status before they are matched against the 2024 tables", + "Apamistamab naming drift forces explicit normalization before 2024 lookup", + "complete 2024 absence must be emitted as D rather than treated as a lookup failure" + ], + "freeze": { + "historical_window": "the 2022, 2023, and 2024 open-access Antibodies to Watch articles; the 2022 baseline is filtered by 2023 carry-over status and then checked against 2024 Tables 1-4, with explicit absence retained as a status" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Start with the 2022 Antibodies to Watch candidates listed as \"expected to be submitted for review soon\" as the baseline, but retain only those molecules that still remain as watchlist candidates in the 2023 same-series article.", + "For these continuously delayed candidates, then determine their final status in the 2024 article: first approved, in first regulatory review, or completely absent from Tables 1-4.", + "Name comparison must handle the Apamistamab naming drift; complete absence in 2024 must be explicitly encoded as D." + ], + "exclusion_conditions": [ + "Exclude results that directly match the 2022 baseline against 2024 by literal string matching without first applying the 2023 carry-over filter.", + "Exclude matching results that do not handle the Apamistamab naming drift.", + "Exclude cases where complete absence in 2024 is treated as a lookup failure rather than a status that must be output." + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "INN", + "category_2022", + "phase_2022", + "prediction_label_2023", + "status_2024", + "phase_or_NA_2024", + "indication_or_NA_2024", + "region_or_NA_2024" + ], + "category_2022": "emit `NC` or `CA` exactly", + "phase_2022": "normalize stage labels such as `Phase 3` to `P3` and `Pivotal Phase 2` to `P2`", + "prediction_label_2023": "keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H1 2023`", + "status_2024": "emit one of `A`, `R`, `F`, or `D` exactly", + "conditional_fields_2024": "if status is A or R, phase_or_NA_2024 must be `NA` and region_or_NA_2024 must carry the raw region string; if status is F, region_or_NA_2024 is `NA` and phase_or_NA_2024 carries the normalized phase; if status is D, all three trailing 2024 fields are `NA`", + "naming_exception": "preserve the fixed source exception around the Apamistamab-I-131 naming variant instead of over-normalizing the INN", + "sorting_or_selection": "INN alphabetical ascending" + } + } +} diff --git a/data_en/goal/europemc_005-g.json b/data_en/goal/europemc_005-g.json new file mode 100644 index 0000000000000000000000000000000000000000..205caaffcaa11164c28297c6da3b132406ef6d19 --- /dev/null +++ b/data_en/goal/europemc_005-g.json @@ -0,0 +1,69 @@ +{ + "task_id": "europemc_005-g", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 20, + "instruction": "I am compiling a cross-platform summary of predictors for COVID-19 inpatient outcome trajectories. This task centers on a 2024 WHO global individual patient data validation paper and its three linked original model papers. In this 2024 validation paper, four prognostic models ultimately completed external validation in low- and middle-income country data. We need to identify which distinct admission variables each of these four models used in their actual evaluations.\nFor each admission variable identified, we need to determine its characteristics in actual use: first, its matching difficulty in the WHO platform baseline table, i.e., whether it can be matched directly under the same or a substantively equivalent name or must go through a fixed mapping; second, its source background, i.e., whether it belongs to the model with the strongest performance in validation, the model with calibration closest to ideal, or an original model that explicitly used dynamic data.\nTo ensure consistency, model abbreviations, performance attributions, dynamic-data attributes, and variable conflicts shall be based on verifiable model descriptions, summary performance results, method explanations, and field definitions in the target literature; any variable naming or mapping differences shall be marked with a conservative correspondence that maintains cross-model interpretability.\nIf all four articles (the one validation paper and the three original model papers) can be found in the database, please organize all extracted variable information and output it as a single string with no spaces, joining records by | in strict alphabetical order of variable names (if the four articles cannot be found, output NONE).\nFormat requirement: each variable's internal information must be written in the fixed format variable~category~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict. Boolean states use 1 for yes and 0 for no; WHO baseline table matching uses E for a direct or substantively equivalent-name match and M for fixed mapping required.", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "If all four articles (the one validation paper and the three original model papers) can be found in the database, organize all extracted variable information and output it as a single string with no spaces, joining records by | in strict alphabetical order of variable names; if the four articles cannot be found, output NONE. Each variable's internal information must be written in the fixed format variable~category~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict. Boolean states use 1 for yes and 0 for no; WHO baseline table matching uses E for a direct or substantively equivalent-name match and M for fixed mapping required.", + "oracle_answer": "Age~DEM~1~1~1~1~Age~E~1~1~1~0|Cancer~COM~0~0~1~0~Cancer~E~1~0~0~0|Chronic kidney disease~COM~0~0~0~1~CKD~M~0~0~0~1|Chronic lung disease~COM~0~0~1~0~Pulmonary disease~M~1~0~0~0|Chronic renal disease~COM~0~0~1~0~CKD~M~1~0~0~1|Coronary heart disease~COM~0~1~0~0~CHD~M~0~0~0~1|Cough~SYM~0~0~1~0~Cough~E~1~0~0~0|Diabetes mellitus~COM~0~0~1~0~Diabetes~M~1~0~0~0|Diarrhea~SYM~0~0~1~0~Diarrhea~E~1~0~0~0|Dyspnea~SYM~0~0~1~0~Dyspnea~E~1~0~0~0|Fever~VIT~0~0~0~1~Body temperature~M~0~0~0~0|Heart disease~COM~0~0~1~0~CHD~M~1~0~0~1|Hypertension~COM~0~1~1~0~Hypertension~E~1~0~0~0|Immunocompromised status~COM~0~0~1~0~Immunosuppression~M~1~0~0~0|O2 saturation~VIT~1~0~0~0~Oxygen saturation~M~0~1~1~0|Respiratory rate~VIT~1~0~0~1~Respiratory rate~E~0~1~1~0|Sex~DEM~0~0~1~0~Men~M~1~0~0~0|Smoking~DEM~1~0~0~0~Smoking~E~0~1~1~1|Smoking status~DEM~0~0~0~1~Smoking~M~0~0~0~1|Systolic blood pressure~VIT~0~0~0~1~Systolic blood pressure~E~0~0~0~0", + "metadata": { + "State-Gated Retrieval": [ + "First, in the 2024 WHO global individual patient data validation paper, identify the four prognostic models that successfully completed external validation in LMIC data, and trace back to the three corresponding original model papers.", + "For each predictor, retain the original wording from WHO Table 1, and annotate its matching method in the WHO baseline table as E or M, and whether it comes from the TopAUC, BestCal, or Dyn model.", + "When encountering a predictor that is conceptually merged on the WHO side, trace back to the original Wang/Zhou papers to split it apart before recalculating the relevant fields." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2024 WHO global validation paper yields the four externally validated models and the WHO-side predictor wording/mapping baseline", + "the three original model papers yield model-specific predictor wordings, dynamic-data flags, and conflicts hidden by WHO-side conceptual merging", + "final rows are produced only after WHO predictors are kept separate, traced back to the original papers, and then re-annotated for mapping and model provenance" + ], + "control_dependency": [ + "conceptually merged WHO predictors must be split back out when the original Wang/Zhou papers expose distinct variables", + "Table 2 mapping decisions are not valid until Table 1 wording and original-paper predictor sets are reconciled", + "TopAUC / BestCal / Dyn flags must be determined after the predictor split is applied correctly" + ], + "freeze": { + "historical_window": "the 2024 WHO global IPD validation paper and the three linked original COVID prognosis-model papers, using their current open-access full texts and tables" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "First, in the 2024 WHO global individual patient data validation paper, identify the four prognostic models that successfully completed external validation in LMIC data, and trace back to the three corresponding original model papers.", + "For each predictor, retain the original wording from WHO Table 1, and annotate its matching method in the WHO baseline table as E or M, and whether it comes from the TopAUC, BestCal, or Dyn model.", + "When encountering a predictor that is conceptually merged on the WHO side, trace back to the original Wang/Zhou papers to split it apart before recalculating the relevant fields." + ], + "exclusion_conditions": [ + "Exclude results that directly merge conceptually similar predictors after WHO Table 1 without tracing back to the original papers for splitting.", + "Exclude results that rely solely on WHO Table 2 for loose mapping without incorporating the original paper wording.", + "Exclude results that fix TopAUC / BestCal / Dyn annotations before the predictor split correction is applied." + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "variable", + "category", + "B", + "W", + "Zh", + "Zo", + "WHOfield", + "WHOx", + "TopAUC", + "BestCal", + "Dyn", + "Conflict" + ], + "variable_set": "the candidate variable set comes only from the WHO validation Table 1 and remains at the original 20 predictors", + "conflict_groups": "do not pre-merge the three source conflict groups `Smoking`/`Smoking status`, `Chronic renal disease`/`Chronic kidney disease`, and `Coronary heart disease`/`Heart disease` before applying the conflict flag", + "boolean_fields": "B, W, Zh, Zo, TopAUC, BestCal, Dyn, and Conflict are emitted as 1 or 0 only", + "WHOx": "emit `E` for exact WHO matches or direct matches under a substantively equivalent name, `M` for the fixed mapped match, and `NA` when no WHO field matches", + "sorting_or_selection": "variable name alphabetical ascending" + } + } +} diff --git a/data_en/goal/genome_001-g.json b/data_en/goal/genome_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..0b189e669d8e377ebba33028e901b79b1f5bd2ad --- /dev/null +++ b/data_en/goal/genome_001-g.json @@ -0,0 +1,64 @@ +{ + "task_id": "genome_001-g", + "domain": "KEGG_BRITE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "From KEGG, identify immunosuppressants used for ulcerative colitis that have been approved in Japan by the end of June 2025 and carry clear cytochrome P450 (CYP) metabolism or inhibition evidence. For each qualifying drug, retain its Japanese therapeutic classification code, ATC code, corresponding target branch, and Japan first approval date. Output a single-line string sorted by Japan first approval date from earliest to latest, formatted as ||||; separate multiple entries with commas; if no qualifying items exist, output NONE.", + "start_url": "https://www.genome.jp/kegg/brite.html", + "output_format": "Output a single-line string sorted by Japan first approval date from earliest to latest, formatted as ||||; separate multiple entries with commas; if no qualifying items exist, output NONE.", + "oracle_answer": "D09783|3999|L04AF01|JAK1/JAK2/JAK3/TYK2|2013/3/25,D11048|3999|L04AF03|JAK1|2020/1/23,D10931|2399|L04AE05|S1PR1/S1PR4/S1PR5|2025/6/24", + "metadata": { + "State-Gated Retrieval": [ + "Within the scope of KEGG immunosuppressants for ulcerative colitis, retain only those approved in Japan by 2025-06-30 and carrying clear CYP-related metabolism information or CYP inhibition evidence.", + "Each candidate drug must be re-verified against the corrected UC drug list for Japanese therapeutic classification, ATC, target branch, CYP evidence, and Japan first approval date.", + "Finally, output sorted by Japan first approval date from earliest to latest." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "KEGG disease H01466 and linked drug entries yield the ulcerative-colitis immunosuppressant candidate set", + "each candidate drug entry yields Japanese class, ATC, target branch, CYP metabolism/inhibition evidence, and Japan approval date", + "final rows are produced only after the full UC candidate set is determined and every candidate is checked against CYP evidence and PMDA timing" + ], + "control_dependency": [ + "the candidate set must include Japanese class 3999 UC drugs when the disease page exposes them rather than being limited to 2399 alone", + "target / CYP / PMDA validation must be applied across the full candidate set rather than only the old 2399 subset", + "entries without explicit CYP evidence may be dropped only after the full candidate set has been established" + ], + "freeze": { + "historical_window": "KEGG ulcerative-colitis drug entries as objectively existing drug entities, using target, CYP, Japan-class, and related entry metadata as relatively stable annotations" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Within the scope of KEGG immunosuppressants for ulcerative colitis, retain only those approved in Japan by 2025-06-30 and carrying clear CYP-related metabolism information or CYP inhibition evidence.", + "Each candidate drug must be re-verified against the corrected UC drug list for Japanese therapeutic classification, ATC, target branch, CYP evidence, and Japan first approval date.", + "Finally, output sorted by Japan first approval date from earliest to latest." + ], + "exclusion_conditions": [ + "Exclude results that incorrectly lock the upstream scope to the 2399 digestive branch without falling back to the full UC drug list.", + "Exclude entries without clear CYP-related metabolism information or CYP inhibition evidence.", + "Exclude entries with a Japan approval date after 2025-06-30 or that are not within the KEGG UC immunosuppressant scope." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DRUG_ID", + "JP_class", + "ATC", + "Target_branch", + "JP_date" + ], + "dedup_key": "DRUG_ID", + "JP_date": "use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value", + "Target_branch": "emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`", + "sorting_or_selection": { + "primary": "JP_date ascending", + "secondary": "DRUG_ID ascending" + } + } + } +} diff --git a/data_en/goal/genome_002-g.json b/data_en/goal/genome_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..34545c8c45a406eed6bbd2c3943a88cee4e28ddc --- /dev/null +++ b/data_en/goal/genome_002-g.json @@ -0,0 +1,65 @@ +{ + "task_id": "genome_002-g", + "domain": "KEGG_GENOME", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "From the KEGG host–symbiont examples, identify animal endosymbiosis cases whose bacterial symbiont KEGG GENOME entry was already recorded by the end of 2005 and whose bacterial symbiont genome contains a clearly named extra replicon. Additionally, the names of these replicons must directly correspond to amino acid biosynthesis modules on the host–symbiont joint pathway map. For the surviving case(s), list all qualifying pathway–module–replicon combinations. Output a single-line string in the format |||||, sorted by pathway ID in ascending order, with entries separated by commas. If no qualifying items exist, output NONE. Use KEGG organism codes for species identifiers.", + "start_url": "https://www.genome.jp/kegg/genome/", + "output_format": "Output a single-line string in the format |||||, sorted by pathway ID in ascending order, with entries separated by commas. If no qualifying items exist, output NONE. Use KEGG organism codes for species identifiers.", + "oracle_answer": "api+buc|buc|00290|M00432|pLeu|2000,api+buc|buc|00400|M00023|pTrp|2000", + "metadata": { + "State-Gated Retrieval": [ + "Retain only host–symbiont examples where the bacterial symbiont KEGG GENOME Created year is no later than 2005 and the genome carries a named extra replicon.", + "The names of these replicons must directly correspond to amino acid biosynthesis modules on the host–symbiont joint pathway page.", + "Finally, output all qualifying pathway–module–replicon records from the surviving case(s), sorted by pathway ID in ascending order." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "KEGG host–symbiont examples and symbiont genome pages yield the pre-2006 candidate pairs and named extra replicons", + "Joint pathway maps, module pages, and genome annotations yield the pathway–module–replicon links attributable to the symbiont side", + "Final rows are produced only after the surviving host–symbiont pair is validated against both replicon existence and module support on the joint pathway page" + ], + "control_dependency": [ + "Only branches satisfying the named-plasmid requirement may be retained, so the bmy+wbm branch must be excluded when the wbm genome page fails that requirement", + "Module retrieval must use the api+buc pathway state and the 00400 view, because that view is the one that actually exposes M00023", + "Module support is valid only after symbiont-side evidence for both M00023 and M00432 is validated in the selected pathway state" + ], + "freeze": { + "historical_window": "KEGG host–symbiont examples as objectively existing biological entities, using joint pathway, module, and genome replicon annotations as relatively stable structural information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only host–symbiont examples where the bacterial symbiont KEGG GENOME Created year is no later than 2005 and the genome carries a named extra replicon.", + "The names of these replicons must directly correspond to amino acid biosynthesis modules on the host–symbiont joint pathway page.", + "Finally, output all qualifying pathway–module–replicon records from the surviving case(s), sorted by pathway ID in ascending order." + ], + "exclusion_conditions": [ + "Exclude cases like bmy+wbm where the symbiont genome page does not satisfy the named-plasmid requirement.", + "Exclude results that only follow pathway names along pages such as 00380 without returning to the joint pathway page to verify module evidence.", + "Exclude records where the replicon–module relationship cannot be directly established on the joint pathway map." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "group", + "symbiont", + "pathway", + "module", + "replicon", + "created_year" + ], + "group": "Use the canonical host–symbiont group label from the source workflow, such as `api+buc`", + "symbiont": "Use the bare lowercase KEGG organism code", + "pathway": "Emit the numeric KEGG pathway ID without a `map` prefix", + "module": "Normalize the KEGG module identifier to the `Mxxxxx` form", + "replicon": "Preserve the named extra replicon exactly as displayed in the source, such as `pLeu` or `pTrp`", + "created_year": "Emit the four-digit created year", + "sorting_or_selection": "Pathway numeric ascending" + } + } +} diff --git a/data_en/goal/genome_003-g.json b/data_en/goal/genome_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..dc5d66c2090ae0a1b0fbc979c988629124622034 --- /dev/null +++ b/data_en/goal/genome_003-g.json @@ -0,0 +1,64 @@ +{ + "task_id": "genome_004-g", + "domain": "KEGG_BRITE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "I am compiling an ordered table of systemic drugs approved for plaque psoriasis in Japan. Include only active ingredients that were approved in Japan by the end of 2024, are used for systemic treatment of plaque psoriasis, and target the IL-17/IL-23 signaling axis. Exclude topical drugs and systemic drugs acting through other axes. Output multiple rows sorted by Japan first approval date from earliest to latest; for drugs approved on the same day, sort by DRUG_ID ascending. Each row format: ||||.", + "start_url": "https://www.kegg.jp/brite/br08301", + "output_format": "Output multiple rows sorted by Japan first approval date from earliest to latest; for drugs approved on the same day, sort by DRUG_ID ascending. Each row format: ||||.", + "oracle_answer": "D09967|Secukinumab|L04AC10|IL17A|2014/12/26\nD10061|Brodalumab|L04AC12|IL17RA|2016/7/4\nD10071|Ixekizumab|L04AC13|IL17A|2016/7/4\nD10438|Guselkumab|L04AC16|IL23A|2018/3/23\nD11052|Risankizumab|L04AC18|IL23A|2019/3/26\nD10400|Tildrakizumab|L04AC17|IL23A|2020/6/29\nD11550|Bimekizumab|L04AC21|IL17A/IL17F|2022/1/20\nD11817|Deucravacitinib|L04AF07|TYK2|2022/9/26", + "metadata": { + "State-Gated Retrieval": [ + "Retain only active ingredients that were approved in Japan by 2024-12-31, are used for systemic treatment of plaque psoriasis, and genuinely act on the IL-17/IL-23 signaling axis.", + "The candidate set must cover the ligand side, receptor side, and TYK2 kinase side, not only the interleukin ligand side.", + "Final entries sorted by Japan first approval date ascending; for the same date, sort by DRUG_ID ascending." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "KEGG disease/drug entry points yield the Japan-approved systemic plaque-psoriasis drug cohort through 2024-12-31", + "each drug entry yields target branch, ATC, systemic-use validity, and Japan approval date for IL-17/IL-23-axis candidates", + "final rows are produced only after ligand-side, receptor-side, and kinase-side candidates are jointly reconciled and re-sorted by Japan approval date" + ], + "control_dependency": [ + "entry-point coverage must include receptor-side IL17RA and kinase-side TYK2 mechanisms when downstream drug pages expose them, rather than staying ligand-only", + "Ustekinumab must be removed only when target interpretation shows IL12 + IL23A rather than the IL-17/IL-23-axis criterion required here", + "systemic-use, Japanese 3999, and PMDA-date filtering must be applied after each expansion of the candidate set rather than attached to the earlier ligand-only state" + ], + "freeze": { + "historical_window": "KEGG plaque-psoriasis systemic-drug entries as objectively existing drug entities, using target-branch and related drug-entry metadata as relatively stable annotations" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only active ingredients that were approved in Japan by 2024-12-31, are used for systemic treatment of plaque psoriasis, and genuinely act on the IL-17/IL-23 signaling axis.", + "The candidate set must cover the ligand side, receptor side, and TYK2 kinase side, not only the interleukin ligand side.", + "Final entries sorted by Japan first approval date ascending; for the same date, sort by DRUG_ID ascending." + ], + "exclusion_conditions": [ + "Exclude topical drugs, non-systemic drugs, or entries outside the specified historical freeze window.", + "Exclude Ustekinumab, whose actual target is IL12 + IL23A, because it does not meet the IL-17/IL-23 axis criterion required here.", + "Exclude results that miss Brodalumab or Deucravacitinib due to considering only the ligand side." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "DRUG_ID", + "Name", + "ATC", + "Target_branch", + "PMDA_date" + ], + "PMDA_date": "use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value", + "Target_branch": "emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`", + "sorting_or_selection": { + "primary": "PMDA_date ascending", + "secondary": "DRUG_ID ascending" + } + } + } +} diff --git a/data_en/goal/genome_004-g.json b/data_en/goal/genome_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..41dbdaa66211930250a33457fd1998ca23446d27 --- /dev/null +++ b/data_en/goal/genome_004-g.json @@ -0,0 +1,78 @@ +{ + "task_id": "genome_004-g", + "domain": "KEGG_GENOME", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am preparing a handout for a primate evolution course and want a two-row comparison table for this vitamin C metabolism exception pattern. Output two rows with columns rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year. The first row should be EXCEPTION_CLADE and the second row RETAINED_SISTER_CLADE. Use KEGG organism codes for the example species.", + "start_url": "https://www.genome.jp/kegg/kegg2.html", + "output_format": "Output a two-row comparison table with columns rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year.", + "oracle_answer": "1|EXCEPTION_CLADE|Primates|Haplorrhini|map00053|map00040|M00014|M00129|LOST|csyr|2022\n2|RETAINED_SISTER_CLADE|Primates|Strepsirrhini|map00053|map00040|M00014|M00129|RETAINED|oga|2022", + "metadata": { + "State-Gated Retrieval": [ + "Search only among primate genome entries established by the end of 2022, and isolate the anomalous lower-level clade that retains the upstream glucuronate module M00014 but lacks the animal-type vitamin C biosynthesis module M00129.", + "That anomalous clade must be paired with a sister branch under the same higher-level split, and the sister branch must still retain M00129.", + "The final output must place the anomalous branch and the retained sister branch into a two-row comparison table, including the required pathway, module, and example-species fields." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the KEGG primate clade pages and genome entries yield candidate subclades and example species established through the cutoff year", + "the pathway and module views yield M00014 and M00129 presence/absence evidence for the exception clade and its sister branch", + "final rows are produced only after the exception clade and retained sister branch are jointly validated under the same parent split and paired with example organisms" + ], + "control_dependency": [ + "the exception clade remains provisional until both the sister-branch contrast and the example-species checks succeed", + "the comparison view must make retained M00014 and missing M00129 visible together", + "the two output rows are emitted together only after the exception clade and retained sister branch are fixed under the same parent split" + ], + "freeze": { + "historical_window": "the objectively existing primate genome entries established on or before 2022, using current KEGG clade, pathway, and module pages as relatively stable reference information for comparing retained M00014 against lost M00129" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Search only among primate genome entries established by the end of 2022, and isolate the anomalous lower-level clade that retains the upstream glucuronate module M00014 but lacks the animal-type vitamin C biosynthesis module M00129.", + "That anomalous clade must have a contrastable sister branch, and that sister branch must still retain M00129.", + "The final output must place the anomalous branch and the retained sister branch into a two-row comparison table, including the required pathway, module, and example-species fields." + ], + "exclusion_conditions": [ + "Exclude results that stop at Simiiformes without checking the broader boundary and therefore miss Haplorrhini.", + "Exclude pathway views that do not make the M00014 versus M00129 contrast visible together.", + "Exclude candidate clades that have not been validated against a retained sister branch." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "clade_role", + "parent_clade", + "clade", + "anomaly_pathway", + "contrast_pathway", + "retained_upstream_module", + "vitamin_c_synthesis_module", + "vitamin_c_module_status", + "example_org", + "cutoff_year" + ], + "rank": "emit 1 for EXCEPTION_CLADE and 2 for RETAINED_SISTER_CLADE", + "clade_role": [ + "EXCEPTION_CLADE", + "RETAINED_SISTER_CLADE" + ], + "pathway_normalization": "emit KEGG pathway ids with the map prefix", + "module_normalization": "emit KEGG module ids with the leading M", + "vitamin_c_module_status": [ + "LOST", + "RETAINED" + ], + "organism_code": "use bare KEGG organism codes in lowercase, not species names", + "cutoff_year": "use a four-digit year; this task is frozen at 2022", + "sorting_or_selection": "emit rows in the fixed order EXCEPTION_CLADE then RETAINED_SISTER_CLADE" + } + } +} diff --git a/data_en/goal/nvd_001-g.json b/data_en/goal/nvd_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..d28c4498a3b5e48246c7a2016c18fdf3e6f7e243 --- /dev/null +++ b/data_en/goal/nvd_001-g.json @@ -0,0 +1,66 @@ +{ + "task_id": "nvd_001-g", + "domain": "NVD", + "autonomy_type": "ordered table", + "instruction": "Identify which milestone versions of Apache Tomcat 9.0.0, released before the final GA release, are both affected by all four specified CVEs and have a CPE name notation change in NVD history. A CPE name notation change means the same milestone version was recorded as mN in older records but changed to milestoneN in current records. The search scope is limited to Apache Tomcat 9.0.0 milestone versions; these versions must appear in the current NVD affected product configurations for CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797. Exclude milestone versions brought in only by other Tomcat 9.0.0 pre-release related vulnerabilities, and also exclude Tomcat 6, Tomcat 7, Tomcat 8, Tomcat 8.5, and all non-Tomcat products. Output a multi-row ordered table with columns: milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd, sorted by milestone number in ascending order.", + "start_url": "https://nvd.nist.gov/vuln/search#/nvd/home?resultType=records", + "output_format": "Output a multi-row ordered table with columns: milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd, sorted by milestone number in ascending order.", + "oracle_output_cardinality": 3, + "oracle_answer": "CVE:2018-7543|1.2.32|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2018-17207|1.2.42|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2020-11738|1.3.28|lite+pro|ModifiedAnalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02", + "metadata": { + "State-Gated Retrieval": [ + "Retain only Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator and whose deprecated vendor chain traces back to snapcreek:duplicator.", + "Each candidate CVE must satisfy all of the following in its Change History: the Initial Analysis was not yet lite/lite+pro; the first change to lite or lite+pro occurred in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurred on 2026-02-02.", + "The final output retains only CVE rows that meet all three conditions above." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "NVD product/CPE search pages yield the current awesomemotive:duplicator family and the deprecated snapcreek:duplicator lineage", + "each target CVE detail page and Change History yield the Initial Analysis state, the first lite/lite+pro analysis event, and the 2026-02-02 vendor-remap event", + "final rows are produced only after candidate CVEs are intersected on both snapcreek -> awesomemotive migration and later introduction of lite/lite+pro in NIST analysis history" + ], + "control_dependency": [ + "the search must include the deprecated snapcreek lineage rather than only the current product state", + "vendor migration alone is insufficient until detail-level history confirms that lite/lite+pro was introduced after Initial Analysis", + "candidate CVEs must be filtered against the full change-history chronology, excluding any whose Initial Analysis already contained lite" + ], + "freeze": { + "historical_window": "Duplicator CVEs published from 2018-01-01 through 2024-12-31, evaluated against NVD analysis history up to the 2026-02-02 snapcreek -> awesomemotive vendor-remap events" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator and whose deprecated vendor chain traces back to snapcreek:duplicator.", + "Each candidate CVE must satisfy all of the following in its Change History: the Initial Analysis was not yet lite/lite+pro; the first change to lite or lite+pro occurred in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurred on 2026-02-02.", + "The final output retains only CVE rows that meet all three conditions above." + ], + "exclusion_conditions": [ + "Exclude results that rely only on the current description or current product state without tracing back to the deprecated snapcreek chain and Change History.", + "Exclude CVEs whose Initial Analysis was already lite/lite+pro.", + "Exclude records without a 2026-02-02 vendor remap or that do not belong to the Duplicator product line." + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema_note": "the current source docx rubric, evidence, and oracle answer use a Duplicator CVE rowset, even though the instruction/output_format text still describes a Tomcat milestone task; normalization therefore follows the checked oracle row schema rather than the stale milestone wording", + "schema": [ + "CVE", + "lite_upper_version", + "lite_vs_lite+pro", + "analysis_event@date", + "snapcreek_to_awesomemotive@date" + ], + "CVE": "emit the identifier in the canonical `CVE:YYYY-NNNN` form used by the oracle", + "lite_vs_lite+pro": "emit `lite` or `lite+pro` exactly", + "analysis_event@date": "emit `Reanalysis@YYYY-MM-DD` or `ModifiedAnalysis@YYYY-MM-DD` exactly as supported by the source record", + "snapcreek_to_awesomemotive@date": "emit the ownership-transfer event as `snapcreek->awesomemotive@YYYY-MM-DD`", + "sorting_or_selection": { + "primary": "NVD published date ascending", + "secondary": "CVE ascending" + } + } + } +} diff --git a/data_en/goal/nvd_002-g.json b/data_en/goal/nvd_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..e9dfdec642acd6f0c4111ee52cd2db2de3e64d41 --- /dev/null +++ b/data_en/goal/nvd_002-g.json @@ -0,0 +1,62 @@ +{ + "task_id": "nvd_002-g", + "instruction": "We are compiling an exception list of legacy MySQL 5.1 assets left after Oracle's acquisition of MySQL. We need to identify which old CPE 2.3 entries whose name prefix still reads mysql:mysql were explicitly remapped by NIST to the corresponding oracle:mysql entries in the NVD history records for four InnoDB denial-of-service vulnerabilities. Start with CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680. For each vulnerability, examine the relevant CPE change records in NVD and find MySQL 5.1 entries where the prefix changed from mysql:mysql to oracle:mysql in all four vulnerabilities. During screening, retain only records that underwent this legacy-to-current prefix migration; exclude MySQL 5.0 branch entries and entries that only performed version alias normalization within the old mysql:mysql prefix. Finally, output a multi-row ordered table with columns version_update | legacy_cpe | current_cpe | remap_time_nvd, sorted by numeric version in ascending order; within the same version, records with an empty update field come before those with a non-empty update.", + "domain": "NVD", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 44, + "start_url": "https://nvd.nist.gov/products/cpe/search", + "output_format": "Output a multi-row ordered table with columns version_update | legacy_cpe | current_cpe | remap_time_nvd, sorted by numeric version in ascending order; within the same version, entries without an update come before entries with an update.", + "oracle_answer": "version_update|legacy_cpe|current_cpe|remap_time_nvd\n5.1.1|cpe:2.3:a:mysql:mysql:5.1.1:::::::*|cpe:2.3:a:oracle:mysql:5.1.1:::::::*|2019-12-17 15:04:33\n5.1.2|cpe:2.3:a:mysql:mysql:5.1.2:::::::*|cpe:2.3:a:oracle:mysql:5.1.2:::::::*|2019-12-17 15:04:39\n5.1.3|cpe:2.3:a:mysql:mysql:5.1.3:::::::*|cpe:2.3:a:oracle:mysql:5.1.3:::::::*|2019-12-17 15:04:46\n5.1.4|cpe:2.3:a:mysql:mysql:5.1.4:::::::*|cpe:2.3:a:oracle:mysql:5.1.4:::::::*|2019-12-17 15:04:53\n5.1.10|cpe:2.3:a:mysql:mysql:5.1.10:::::::*|cpe:2.3:a:oracle:mysql:5.1.10:::::::*|2019-12-17 15:05:30\n5.1.11|cpe:2.3:a:mysql:mysql:5.1.11:::::::*|cpe:2.3:a:oracle:mysql:5.1.11:::::::*|2019-12-17 15:05:37\n5.1.12|cpe:2.3:a:mysql:mysql:5.1.12:::::::*|cpe:2.3:a:oracle:mysql:5.1.12:::::::*|2019-12-17 15:05:45\n5.1.13|cpe:2.3:a:mysql:mysql:5.1.13:::::::*|cpe:2.3:a:oracle:mysql:5.1.13:::::::*|2019-12-17 15:05:52\n5.1.14|cpe:2.3:a:mysql:mysql:5.1.14:::::::*|cpe:2.3:a:oracle:mysql:5.1.14:::::::*|2019-12-17 15:05:59\n5.1.15|cpe:2.3:a:mysql:mysql:5.1.15:::::::*|cpe:2.3:a:oracle:mysql:5.1.15:::::::*|2019-12-17 15:06:07\n5.1.16|cpe:2.3:a:mysql:mysql:5.1.16:::::::*|cpe:2.3:a:oracle:mysql:5.1.16:::::::*|2019-12-17 15:06:14\n5.1.17|cpe:2.3:a:mysql:mysql:5.1.17:::::::*|cpe:2.3:a:oracle:mysql:5.1.17:::::::*|2019-12-17 15:06:21\n5.1.18|cpe:2.3:a:mysql:mysql:5.1.18:::::::*|cpe:2.3:a:oracle:mysql:5.1.18:::::::*|2019-12-17 15:06:27\n5.1.19|cpe:2.3:a:mysql:mysql:5.1.19:::::::*|cpe:2.3:a:oracle:mysql:5.1.19:::::::*|2019-12-17 15:06:34\n5.1.20|cpe:2.3:a:mysql:mysql:5.1.20:::::::*|cpe:2.3:a:oracle:mysql:5.1.20:::::::*|2019-12-17 15:06:42\n5.1.21|cpe:2.3:a:mysql:mysql:5.1.21:::::::*|cpe:2.3:a:oracle:mysql:5.1.21:::::::*|2019-12-17 15:06:50\n5.1.22|cpe:2.3:a:mysql:mysql:5.1.22:::::::*|cpe:2.3:a:oracle:mysql:5.1.22:::::::*|2019-12-17 15:06:56\n5.1.23:a|cpe:2.3:a:mysql:mysql:5.1.23:a::::::|cpe:2.3:a:oracle:mysql:5.1.23:a::::::|2019-12-17 15:23:28\n5.1.24|cpe:2.3:a:mysql:mysql:5.1.24:::::::*|cpe:2.3:a:oracle:mysql:5.1.24:::::::*|2019-12-17 15:07:03\n5.1.25|cpe:2.3:a:mysql:mysql:5.1.25:::::::*|cpe:2.3:a:oracle:mysql:5.1.25:::::::*|2019-12-17 15:07:10\n5.1.26|cpe:2.3:a:mysql:mysql:5.1.26:::::::*|cpe:2.3:a:oracle:mysql:5.1.26:::::::*|2019-12-17 15:07:17\n5.1.27|cpe:2.3:a:mysql:mysql:5.1.27:::::::*|cpe:2.3:a:oracle:mysql:5.1.27:::::::*|2019-12-17 15:07:24\n5.1.28|cpe:2.3:a:mysql:mysql:5.1.28:::::::*|cpe:2.3:a:oracle:mysql:5.1.28:::::::*|2019-12-17 15:07:31\n5.1.29|cpe:2.3:a:mysql:mysql:5.1.29:::::::*|cpe:2.3:a:oracle:mysql:5.1.29:::::::*|2019-12-17 15:07:38\n5.1.30|cpe:2.3:a:mysql:mysql:5.1.30:::::::*|cpe:2.3:a:oracle:mysql:5.1.30:::::::*|2019-12-17 15:07:46\n5.1.31:sp1|cpe:2.3:a:mysql:mysql:5.1.31:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.31:sp1::::::|2019-12-17 15:23:35\n5.1.33|cpe:2.3:a:mysql:mysql:5.1.33:::::::*|cpe:2.3:a:oracle:mysql:5.1.33:::::::*|2019-12-17 15:07:55\n5.1.34:sp1|cpe:2.3:a:mysql:mysql:5.1.34:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.34:sp1::::::|2019-12-17 15:23:42\n5.1.35|cpe:2.3:a:mysql:mysql:5.1.35:::::::*|cpe:2.3:a:oracle:mysql:5.1.35:::::::*|2019-12-17 15:08:03\n5.1.36|cpe:2.3:a:mysql:mysql:5.1.36:::::::*|cpe:2.3:a:oracle:mysql:5.1.36:::::::*|2019-12-17 15:08:10\n5.1.37:sp1|cpe:2.3:a:mysql:mysql:5.1.37:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.37:sp1::::::|2019-12-17 15:23:49\n5.1.38|cpe:2.3:a:mysql:mysql:5.1.38:::::::*|cpe:2.3:a:oracle:mysql:5.1.38:::::::*|2019-12-17 15:08:17\n5.1.39|cpe:2.3:a:mysql:mysql:5.1.39:::::::*|cpe:2.3:a:oracle:mysql:5.1.39:::::::*|2019-12-17 10:22:31\n5.1.40|cpe:2.3:a:mysql:mysql:5.1.40:::::::*|cpe:2.3:a:oracle:mysql:5.1.40:::::::*|2019-12-17 10:22:46\n5.1.40:sp1|cpe:2.3:a:mysql:mysql:5.1.40:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.40:sp1::::::|2019-12-17 10:22:39\n5.1.41|cpe:2.3:a:mysql:mysql:5.1.41:::::::*|cpe:2.3:a:oracle:mysql:5.1.41:::::::*|2019-12-17 10:22:52\n5.1.42|cpe:2.3:a:mysql:mysql:5.1.42:::::::*|cpe:2.3:a:oracle:mysql:5.1.42:::::::*|2019-12-17 10:22:59\n5.1.43|cpe:2.3:a:mysql:mysql:5.1.43:::::::*|cpe:2.3:a:oracle:mysql:5.1.43:::::::*|2019-12-17 10:23:06\n5.1.43:sp1|cpe:2.3:a:mysql:mysql:5.1.43:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.43:sp1::::::|2019-12-17 10:23:11\n5.1.44|cpe:2.3:a:mysql:mysql:5.1.44:::::::*|cpe:2.3:a:oracle:mysql:5.1.44:::::::*|2019-12-17 10:23:17\n5.1.45|cpe:2.3:a:mysql:mysql:5.1.45:::::::*|cpe:2.3:a:oracle:mysql:5.1.45:::::::*|2019-12-17 10:23:24\n5.1.46|cpe:2.3:a:mysql:mysql:5.1.46:::::::*|cpe:2.3:a:oracle:mysql:5.1.46:::::::*|2019-12-17 10:23:38\n5.1.46:sp1|cpe:2.3:a:mysql:mysql:5.1.46:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.46:sp1::::::|2019-12-17 10:23:31\n5.1.47|cpe:2.3:a:mysql:mysql:5.1.47:::::::*|cpe:2.3:a:oracle:mysql:5.1.47:::::::*|2019-12-17 10:23:45", + "metadata": { + "State-Gated Retrieval": [ + "Retain only CPE 2.3 entries in the MySQL 5.1 branch for which the vendor migration from mysql:mysql to oracle:mysql is clearly visible in the NVD Change History for all four vulnerabilities CVE-2010-3676, 3677, 3678, and 3680.", + "Every result must provide version_update, legacy_cpe, current_cpe, and remap_time_nvd.", + "Within the same version, entries without an update come before entries with an update, and output is sorted by numeric version in ascending order." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Current and deprecated MySQL 5.1 CPE search results yield candidate legacy/current CPE strings", + "The four target CVE pages and their Change History entries yield vendor-migration evidence, exact version_update strings, and remap timestamps", + "Final rows are produced only after taking the common mysql:mysql 5.1 -> oracle:mysql 5.1 migrations across all four CVEs and removing alias-only or 5.0 entries" + ], + "control_dependency": [ + "Legacy vendor mapping must be determined from Analysis Description plus Change History rather than from the current description/current CPE view", + "Include-deprecated results cannot be accepted wholesale because alias-only remaps must be filtered out", + "5.1-branch membership and sort order must be determined after the vendor-migration filter removes 5.0 and non-migration rows" + ], + "freeze": { + "historical_window": "The MySQL 5.1 branches visible in CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680, restricted to explicit mysql:mysql -> oracle:mysql vendor-migration events" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only CPE 2.3 entries in the MySQL 5.1 branch for which the vendor migration from mysql:mysql to oracle:mysql is clearly visible in the NVD Change History for all four vulnerabilities CVE-2010-3676, 3677, 3678, and 3680.", + "Every result must provide version_update, legacy_cpe, current_cpe, and remap_time_nvd.", + "Within the same version, entries without an update come before entries with an update, and output is sorted by numeric version in ascending order." + ], + "exclusion_conditions": [ + "Exclude MySQL 5.0 branch entries.", + "Exclude entries that still belong to the old vendor mysql:mysql and only underwent internal version alias normalization without a vendor migration.", + "Exclude results that only read from the current Oracle MySQL 5.1 CPE state without using legacy mapping and Change History." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "Required literal first row `version_update|legacy_cpe|current_cpe|remap_time_nvd`", + "schema": [ + "version_update", + "legacy_cpe", + "current_cpe", + "remap_time_nvd" + ], + "version_update": "Sort by numeric MySQL version ascending; within the same base version, the empty update comes before any non-empty update suffix", + "legacy_cpe": "Preserve the exact legacy CPE 2.3 string", + "current_cpe": "Preserve the exact current CPE 2.3 string", + "remap_time_nvd": "Emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form", + "dedup_key": "(legacy_cpe, current_cpe)" + } + } +} diff --git a/data_en/goal/nvd_003-g.json b/data_en/goal/nvd_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..5ce6f661374107bdf3bc8d3a015e772deb8c30ad --- /dev/null +++ b/data_en/goal/nvd_003-g.json @@ -0,0 +1,114 @@ +{ + "task_id": "nvd_004-g", + "domain": "NVD", + "autonomy_type": "ordered table", + "instruction": "Identify which milestone versions of Apache Tomcat 9.0.0 (prior to the final release) appear in the NVD current affected-product configurations for all four vulnerabilities CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797, and whose NVD change history shows a CPE identifier migration from the legacy mN form to the current milestoneN form. This step is intended to clean up SBOM rules that still use the old Apache Tomcat 9.0.0.Mx notation. Here, mN refers to forms such as m1, m2, etc., while milestoneN refers to the corresponding notation currently used by NVD. Retain only those Apache Tomcat 9.0.0 milestone versions that satisfy both conditions. Exclude two categories: (1) milestone versions that do not simultaneously meet the four-CVE condition and appear only because of other Tomcat 9.0.0 prerelease vulnerabilities; (2) Tomcat 6, Tomcat 7, Tomcat 8, Tomcat 8.5, and any non-Tomcat products. Output a multi-row ordered table with columns milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd, sorted by the numeric milestone value in ascending order.", + "start_url": "https://nvd.nist.gov/products/cpe/search", + "output_format": "Output a multi-row ordered table with columns milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd, sorted by the numeric milestone value in ascending order.", + "oracle_output_cardinality": 9, + "oracle_answer": "milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd\nM1|cpe:2.3:a:apache:tomcat:9.0.0:m1:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone1:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM2|cpe:2.3:a:apache:tomcat:9.0.0:m2:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone2:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM3|cpe:2.3:a:apache:tomcat:9.0.0:m3:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone3:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM4|cpe:2.3:a:apache:tomcat:9.0.0:m4:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone4:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM5|cpe:2.3:a:apache:tomcat:9.0.0:m5:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone5:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM6|cpe:2.3:a:apache:tomcat:9.0.0:m6:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone6:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM7|cpe:2.3:a:apache:tomcat:9.0.0:m7:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone7:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM8|cpe:2.3:a:apache:tomcat:9.0.0:m8:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone8:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM9|cpe:2.3:a:apache:tomcat:9.0.0:m9:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone9:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18", + "metadata": { + "State-Gated Retrieval": [ + "Retain only Apache Tomcat 9.0.0 milestone versions that appear in the current affected-product scope of all four target CVEs: CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797.", + "These versions must also show a CPE Deprecation Remap from mN to milestoneN in the NVD Change History.", + "Finally, output sorted by numeric milestone value in ascending order, and the required_cves field must contain exactly these four specified CVEs." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the current milestoneN CPE search and detail pages yield the Tomcat milestone family and the legacy mN mapping anchors", + "the four target CVE pages and Change History entries yield the exact mN -> milestoneN deprecation remaps and the required-CVE intersection", + "final rows are produced only after taking the remaps common to all four target CVEs and sorting by numeric milestone" + ], + "control_dependency": [ + "the candidate milestone set must be determined from the four-target-CVE intersection rather than from all prerelease Tomcat CVEs", + "later remapped milestones such as M10+ must be excluded by applying the specified four-CVE boundary", + "only explicit NVD CPE Deprecation Remap events from mN to milestoneN count, so generic Tomcat prerelease visibility cannot be accepted as evidence" + ], + "freeze": { + "historical_window": "the Tomcat 9.0.0 prerelease milestones jointly covered by CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797, with remap evidence fixed to the 2023-12-08 11:41:18 NVD deprecation events" + }, + "answer_type": "multi-row ordered table" + }, + "all_involved_urls": { + "fixed_entry_and_docs": [ + "https://nvd.nist.gov/products/cpe/search", + "https://nvd.nist.gov/vuln/vulnerability-detail-pages" + ], + "cpe_search_result_pages": [ + "https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL", + "https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED", + "https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20m&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED", + "https://nvd.nist.gov/products/cpe/search/results?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED" + ], + "representative_cpe_detail_pages": [ + "https://nvd.nist.gov/products/cpe/detail/615922?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED", + "https://nvd.nist.gov/products/cpe/detail/615947?keyword=cpe%3A2.3%3Aa%3Aapache&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED" + ], + "row_level_cpe_api_urls_m1_to_m9": [ + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone2%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone3%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone4%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone5%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone6%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone7%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone8%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone9%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A" + ], + "target_cve_detail_pages": [ + "https://nvd.nist.gov/vuln/detail/CVE-2016-5018", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6794", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6796", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6797" + ], + "negative_control_cve_detail_pages": [ + "https://nvd.nist.gov/vuln/detail/CVE-2016-6816", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6817", + "https://nvd.nist.gov/vuln/detail/CVE-2019-0221" + ], + "cve_change_history_api": [ + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-5018&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6794&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6796&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6797&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6816&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6817&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2019-0221&eventName=CPE%20Deprecation%20Remap" + ], + "representative_change_record_pages": [ + "https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=04%2F18%2F2022T13%3A57%3A03.500-0400", + "https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=08%2F24%2F2017T09%3A11%3A40.690-0400" + ] + }, + "rubric": { + "inclusion_conditions": [ + "Retain only Apache Tomcat 9.0.0 milestone versions that appear in the current affected-product scope of all four target CVEs: CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797.", + "These versions must also show a CPE Deprecation Remap from mN to milestoneN in the NVD Change History.", + "Finally, output sorted by numeric milestone value in ascending order, and the required_cves field must contain exactly these four specified CVEs." + ], + "exclusion_conditions": [ + "Exclude milestones that are included only because of other Tomcat 9.0.0 prerelease vulnerabilities, such as M10/M11 and later milestones.", + "Exclude Tomcat 6, 7, 8, 8.5, and any non-Tomcat products.", + "Exclude records that lack explicit NVD remap evidence and are merely visible on the current milestone page." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row `milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd`", + "schema": [ + "milestone", + "legacy_cpe", + "current_cpe", + "required_cves", + "remap_time_nvd" + ], + "milestone": "emit the canonical milestone label `M1` through `M9` and sort by the numeric suffix ascending", + "legacy_cpe": "preserve the exact legacy CPE 2.3 string containing the short milestone token such as `m1`", + "current_cpe": "preserve the exact current CPE 2.3 string containing the full milestone token such as `milestone1`", + "required_cves": "emit the fixed literal `CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797`", + "remap_time_nvd": "emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form" + } + } +} diff --git a/data_en/goal/reptile_001-g.json b/data_en/goal/reptile_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..4bbf66f0e7c914eaf3137ec2dda89a2947bbe3aa --- /dev/null +++ b/data_en/goal/reptile_001-g.json @@ -0,0 +1,61 @@ +{ + "task_id": "reptile_001-g", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "I am compiling a name concordance for early museum specimens of Indian snakes recorded in George A. Boulenger's 1890 work \"The Fauna of British India, Including Ceylon and Burma\". In the Reptile Database, identify entries that simultaneously satisfy the following conditions: the currently accepted name has been reassigned to a different genus compared with the name used in the book; the current species page still retains BMNH type specimen information; and the type locality still corresponds to India. For each qualifying entry, also retrieve the most recent historical binomial listed on the current species page that has not yet adopted the current genus name, and determine whether an exact search using that full old name uniquely identifies the entry. Output the results sorted alphabetically by accepted name in the format |||; join multiple entries with semicolons; if no qualifying entries exist, output NONE.", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "Output the results sorted alphabetically by accepted name in the format |||; join multiple entries with semicolons; if no qualifying entries exist, output NONE.", + "oracle_answer": "Argyrophis oatesii|Typhlops oatesii|UNIQUE|SYNTYPES;Dendrelaphis grandoculis|Ahaetulla grandoculis|UNIQUE|LECTOTYPE;Fowlea sanctijohannis|Xenochrophis sanctijohannis|UNIQUE|HOLOTYPE;Gerrhopilus beddomii|Typhlops beddomii|UNIQUE|SYNTYPES;Hebius khasiensis|Amphiesma khasiense|UNIQUE|LECTOTYPE;Hebius parallelus|Amphiesma parallelum|AMBIG|LECTOTYPE;Indotyphlops jerdoni|Typhlops jerdoni|UNIQUE|SYNTYPES;Myriopholis blanfordii|Leptotyphlops blanfordi|AMBIG|SYNTYPES", + "metadata": { + "State-Gated Retrieval": [ + "Candidates must come from the historical Indian snake collection entries in Boulenger 1890 \"Fauna of British India\".", + "The current Reptile Database species page must simultaneously satisfy: the species has been reassigned to a different genus; the page still retains BMNH type specimen information; and the type locality still corresponds to India.", + "On each qualifying page, select the most recent historical binomial that has not yet adopted the current genus name, perform an exact back-search using that old name, and then label it UNIQUE or AMBIG." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "The Boulenger 1890 historical sample and current accepted-species pages yield candidates that changed genus while retaining BMNH type data and India-compatible type locality.", + "Each accepted page yields the nearest pre-current-genus old label, the BMNH type status, and the historical/type-locality evidence anchoring the entity.", + "Final rows are produced only after the old-label exact back-search is evaluated for uniqueness without losing the original entity anchor." + ], + "control_dependency": [ + "When an exact old-label back-search now hits multiple species, the original anchored entity must be kept and the uniqueness label must be set to AMBIG.", + "Once a candidate has passed the historical-cluster, genus-shift, BMNH, and India-locality gates, later old-label ambiguity can only rewrite the uniqueness field, not the entity itself.", + "Candidate anchoring must be preserved across the two-stage workflow so that old-label search noise does not redirect the accepted-species row." + ], + "freeze": { + "historical_window": "The objectively existing reptile taxa in the George A. Boulenger 1890 British India sample, using Reptile Database accepted pages, synonym labels, BMNH type data, and type-locality text as nearly objective and highly stable reference information." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Candidates must come from the historical Indian snake collection entries in Boulenger 1890 \"Fauna of British India\".", + "The current Reptile Database species page must simultaneously satisfy: the species has been reassigned to a different genus; the page still retains BMNH type specimen information; and the type locality still corresponds to India.", + "On each qualifying page, select the most recent historical binomial that has not yet adopted the current genus name, perform an exact back-search using that old name, and then label it UNIQUE or AMBIG." + ], + "exclusion_conditions": [ + "Exclude entries where the current accepted name has not undergone a genus change, or where the page no longer retains BMNH type specimen information.", + "Exclude entries whose type locality does not correspond to India.", + "Do not discard candidates for which the exact old-name back-search is non-unique; such candidates should retain the original entity and be labeled AMBIG." + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "accepted name", + "old label", + "UNIQUE/AMBIG", + "BMNH status" + ], + "accepted_name": "Emit the current accepted binomial exactly as shown in the reconciled source.", + "old_label": "Preserve the historical label exactly as used on the legacy branch.", + "UNIQUE/AMBIG": "Emit `UNIQUE` or `AMBIG` in uppercase.", + "BMNH_status": "Normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or SYNTYPES.", + "sorting_or_selection": "Accepted name alphabetical ascending." + } + } +} diff --git a/data_en/goal/reptile_002-g.json b/data_en/goal/reptile_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..a7545ccd34274a609e6604e653419b775cc0e4f8 --- /dev/null +++ b/data_en/goal/reptile_002-g.json @@ -0,0 +1,63 @@ +{ + "task_id": "reptile_002-g", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "I am compiling name correspondences between old labels and current accepted names for early museum specimens of Southeast Asian Lygosoma. In the current Lygosoma checklist, identify all accepted species that satisfy both of the following conditions: the species page lists a Riopa combination used by Smith (1935/1937) in its Synonym section, and that old name corresponds to more than one accepted species under the current classification. For each qualifying species, output the first-listed type specimen number, type status, and the region corresponding to the final type locality on that page. Output in alphabetical order by accepted name, using the format ||||; join multiple entries with semicolons. If no qualifying items exist, output NONE.", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "Output in alphabetical order by accepted name, using the format ||||; join multiple entries with semicolons. If no qualifying items exist, output NONE.", + "oracle_answer": "Lygosoma bampfyldei|Riopa bampfyldei|BMNH 1946.8.10.84|SYNTYPES|East Malaysia;Lygosoma peninsulare|Riopa bampfyldei|LSUHC 13857|HOLOTYPE|Peninsular Malaysia;Lygosoma schneideri|Riopa bampfyldei|NMBA 4743|HOLOTYPE|Indonesia", + "metadata": { + "State-Gated Retrieval": [ + "Retain only accepted species that can be traced from the Smith 1937 old-name chain to a current Lygosoma record and for which the type accession, type status, and locality can be read on the current page.", + "For each accepted record, output the accepted name, the corresponding old label, the type accession, the type status, and the locality.", + "If the same exact old name appears on multiple accepted species, retain them as separate chains." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Smith 1937 old-name chain yields the three current Lygosoma accepted pages connected to Riopa bampfyldei / Lygosoma bampfyldei", + "each accepted page yields its own type accession, type status, and type locality needed to separate the homonymous old-name paths", + "final rows are produced only after the one-to-many old-name split is rebuilt and the three paths are re-anchored to their own type evidence" + ], + "control_dependency": [ + "same-specific-epithet matching cannot establish a one-to-one mapping when the same Smith 1937 old name appears on multiple accepted pages", + "once literal old-name reuse is exposed, the workflow must keep the original parallel three-chain state rather than collapsing to a one-to-one mapping", + "type accession and locality evidence must be read separately for each chain rather than patched onto the first stopping page" + ], + "freeze": { + "historical_window": "the objectively existing taxa linked to the Smith 1937 old-name cluster around Riopa bampfyldei, using Reptile Database accepted pages together with type accessions, statuses, and localities as nearly objective and highly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only accepted species that can be traced from the Smith 1937 old-name chain to a current Lygosoma record and for which the type accession, type status, and locality can be read on the current page.", + "For each accepted record, output the accepted name, the corresponding old label, the type accession, the type status, and the locality.", + "If the same exact old name appears on multiple accepted species, retain them as separate chains." + ], + "exclusion_conditions": [ + "Exclude results that assume the same species simply because the old name and current specific epithet match.", + "Exclude results that retain only the first chain when the same exact old name appears on multiple accepted pages.", + "Exclude results that do not re-verify the type accession and locality on each accepted page." + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "accepted", + "Smith-era Riopa label", + "first type code", + "type status", + "region" + ], + "accepted": "emit the current accepted binomial exactly as shown in the reconciled source", + "Smith-era_Riopa_label": "preserve the Smith-era Riopa label exactly as used on the legacy branch", + "first_type_code": "emit the first accession code that follows the selected type-status statement", + "type_status": "normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES", + "region": "emit the modern geographic region label from the source reconciliation, such as East Malaysia or Peninsular Malaysia", + "sorting_or_selection": "accepted name alphabetical ascending" + } + } +} diff --git a/data_en/goal/reptile_003-g.json b/data_en/goal/reptile_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..26f42752b6456f289da57e43cbdaffd94846bb0e --- /dev/null +++ b/data_en/goal/reptile_003-g.json @@ -0,0 +1,66 @@ +{ + "task_id": "reptile_003-g", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 10, + "instruction": "I am compiling a name cross-reference for a batch of old collection cards that were still cataloged under the names Mabuya or Mabuia around 1980 and now need to be merged into the current Eutropis checklist. In the current Eutropis list, identify all entries that meet the following conditions: the first 1980-era label on the species page has the genus written as Mabuya or Mabuia; and when that 1980-era label is searched by name in the current list, it does not uniquely correspond to a single Eutropis entry but instead matches multiple current Eutropis entries. For each qualifying entry, output the current accepted name, that 1980-era label, the qualifier for that label on the page, and the first type status and type code listed on the current page. Output sorted alphabetically by 1980-era label, and within the same label by current accepted name, in the format |<1980 label>|||; join multiple entries with semicolons; if no qualifying entries exist, output NONE.", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "Output sorted alphabetically by 1980-era label, and within the same label by current accepted name, in the format |<1980 label>|||; join multiple entries with semicolons; if no qualifying entries exist, output NONE.", + "oracle_answer": "Eutropis indeprensa|Mabuya indeprensa|NONE|HOLOTYPE|CAS 85664;Eutropis sahulinghangganan|Mabuya indeprensa|PART-MISID|HOLOTYPE|PNM 9867;Eutropis multifasciata|Mabuya multifasciata|NONE|NEOTYPE|MZB 11912;Eutropis multicarinata|Mabuya multicarinata|NONE|HOLOTYPE|BMNH 1946.8.15.13-15;Eutropis borealis|Mabuya multicarinata borealis|NONE|HOLOTYPE|CAS 15447;Eutropis islamaliit|Mabuya multicarinata borealis|PART-MISID|HOLOTYPE|PNM 9847;Eutropis caraga|Mabuya multicarinata multicarinata|PART-MISID|HOLOTYPE|PNM 9845;Eutropis palauensis|Mabuya multicarinata multicarinata|PART-BYIMPL|HOLOTYPE|CAS 248251;Eutropis dattaroyi|Mabuya rudis|PART|HOLOTYPE|ZSI 25118;Eutropis rudis|Mabuya rudis|NONE|LECTOTYPE|BMNH 1946.8.15.26", + "metadata": { + "State-Gated Retrieval": [ + "Retain only those current Eutropis records whose synonym block contains, scanning top-down, a first old label starting with Mabuya or Mabuia and having the year 1980.", + "Then use that 1980-era old label for a default name back-search, and output the accepted name, old label, back-search qualifier, type status, and type specimen.", + "If the subsequent back-search reveals additional matching entries, revisit the earlier results and include them in the final output." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current Eutropis detail pages yield the first 1980-tagged Mabuya/Mabuia synonym label for each accepted species", + "exact back-search on that 1980 old label yields the present accepted page, type status, and type specimen needed for the output row", + "final rows are produced only after the 1980-specific old-label anchor is rebuilt and the accepted-species set is expanded when back-search evidence reveals omitted entries" + ], + "control_dependency": [ + "the workflow must identify the first Mabuya/Mabuia label carrying the 1980 year rather than stopping at the first old label on the page", + "when old-label back-search reveals missing entries such as Eutropis dattaroyi, the accepted-species set must be expanded to include them rather than patched in place", + "accepted-page synonym parsing and back-search interpretation must stay coupled so that 1980 labels are not replaced by older but irrelevant names" + ], + "freeze": { + "historical_window": "the objectively existing Eutropis taxa represented in Reptile Database pages, using the synonym labels shown on each species page, especially the first Mabuya/Mabuia-form label tagged with the 1980 citation year, as nearly objective and highly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only those current Eutropis records whose synonym block contains, scanning top-down, a first old label starting with Mabuya or Mabuia and having the year 1980.", + "Then use that 1980-era old label for a default name back-search, and output the accepted name, old label, back-search qualifier, type status, and type specimen.", + "If the subsequent back-search reveals additional matching entries, revisit the earlier results and include them in the final output." + ], + "exclusion_conditions": [ + "Exclude results that mistakenly treat the first old label on the page as the first 1980-era old label.", + "Exclude results whose exact back-search on the 1980 old label points to only a single current Eutropis entry.", + "Exclude results that, when subsequent evidence reveals omitted entries, fail to revisit the earlier results and rebuild the accepted-species set." + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "accepted", + "1980 label", + "qualifier", + "type status", + "first type code" + ], + "accepted": "emit the current accepted binomial exactly as shown in the reconciled source", + "1980_label": "preserve the 1980-era label exactly as used on the legacy branch", + "qualifier": "normalize to one of `NONE`, `PART`, `PART-MISID`, or `PART-BYIMPL`", + "type_status": "normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES", + "first_type_code": "emit the first accession code that follows the selected type-status statement", + "sorting_or_selection": { + "primary": "1980 label alphabetical ascending", + "secondary": "accepted name alphabetical ascending" + } + } + } +} diff --git a/data_en/goal/reptile_004-g.json b/data_en/goal/reptile_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..7d7e56f96a93919e5410a40e6d64a4ad92bed8b7 --- /dev/null +++ b/data_en/goal/reptile_004-g.json @@ -0,0 +1,65 @@ +{ + "task_id": "reptile_004-g", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 6, + "instruction": "I am organizing a set of old Hemidactylus brookii museum cards that use the historical labels listed in the comments of the Hemidactylus brookii species page. Identify all old labels that are no longer considered synonyms of Hemidactylus brookii and for which the database provides a clear final synonym assignment. For each qualifying old label, output the currently accepted species it should be assigned to; if the synonym chain passes through an intermediate historical name, list that name, otherwise output DIRECT; also output the type status, type code, and the country of the type locality for that old label. Output the results in alphabetical order of the old labels, using the format |||||, with multiple entries separated by semicolons. If no qualifying entries exist, output NONE.", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "Output in alphabetical order of the old labels, using the format |||||, with multiple entries separated by semicolons. If no qualifying entries exist, output NONE.", + "oracle_answer": "Hemidactylus brooki leightoni|Hemidactylus angulatus|DIRECT|HOLOTYPE|BMNH 1946.8.25.65|Colombia;Hemidactylus brookii haitianus|Hemidactylus angulatus|DIRECT|LECTOTYPE|ZMH R22378|Haiti;Hemidactylus brookii parvimaculatus|Hemidactylus parvimaculatus|DIRECT|HOLOTYPE|NMSL No. RG. 15|Sri Lanka;Hemidactylus brookii subtriedroides|Hemidactylus murrayi|Hemidactylus tenkatei|LECTOTYPE|BMNH [subtriedroides] [tenkatei]|Myanmar;Hemidactylus gleadowi|Hemidactylus gleadowi|DIRECT|NEOTYPE|BMNH 1884.7.25.8|Pakistan;Hemidactylus tenkatei|Hemidactylus murrayi|DIRECT|LECTOTYPE|RMNH 4353|Indonesia", + "metadata": { + "State-Gated Retrieval": [ + "Each result must start from the specified old-label chain and ultimately determine the accepted name, bridge status, type status, type code, and locality from the current accepted species page.", + "For the subtriedroides branch, continue the chain through tenkatei to murrayi, output the final accepted name as Hemidactylus murrayi, and retain bridge=Hemidactylus tenkatei.", + "For branches such as haitianus and leightoni, read the locality and type lines specific to each branch, rather than borrowing the header information from the wrong accepted page." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the old-label chains from Hemidactylus angulatus and related names yield accepted pages, bridge names, and the type/locality lines for each path", + "comment, Types, and type-comment blocks yield the later evidence that tenkatei is further sunk into H. murrayi", + "final rows are produced only after each old-label path is re-anchored to its own locality/type line and the subtriedroides -> tenkatei -> murrayi bridge chain is completed" + ], + "control_dependency": [ + "type data must be taken from the locality/type line belonging to the actual old-label branch rather than from the header block of the wrong accepted page", + "stopping at the intermediate tenkatei bridge is insufficient; the workflow must continue to the later murrayi evidence and rewrite both tenkatei and subtriedroides final accepted names", + "bridge labels remain useful, but final accepted names and type lines must be determined from the deeper synonym chain" + ], + "freeze": { + "historical_window": "the objectively existing taxa in the Hemidactylus angulatus / brookii / murrayi complex, using Reptile Database locality, type, comment, and type-comment blocks as nearly objective and highly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Each result must start from the specified old-label chain and ultimately determine the accepted name, bridge status, type status, type code, and locality from the current accepted species page.", + "For the subtriedroides branch, continue the chain through tenkatei to murrayi, output the final accepted name as Hemidactylus murrayi, and retain bridge=Hemidactylus tenkatei.", + "For branches such as haitianus and leightoni, read the locality and type lines specific to each branch, rather than borrowing the header information from the wrong accepted page." + ], + "exclusion_conditions": [ + "Exclude results that follow the wrong page hierarchy and apply the Holotype/locality from the H. angulatus page header to other branches.", + "Exclude results that stop early on the subtriedroides -> tenkatei chain without continuing to read the subsequent murrayi evidence.", + "Exclude results that fail to align the locality/type lines with the specific old-label branches one by one." + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "legacy label", + "accepted", + "bridge", + "type status", + "type code", + "country" + ], + "legacy_label": "preserve the legacy label exactly as used on the source branch", + "accepted": "emit the current accepted binomial exactly as shown in the reconciled source", + "bridge": "emit `DIRECT` when no intermediate legacy bridge name is needed; otherwise emit the intermediate legacy name that links the branches", + "type_status": "normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or NEOTYPE", + "type_code": "take the type accession from the legacy-label branch rather than from a generic type line elsewhere on the page", + "country": "emit the modern English country name from the reconciled source branch", + "sorting_or_selection": "legacy label alphabetical ascending" + } + } +} diff --git a/data_en/goal/reptile_005-g.json b/data_en/goal/reptile_005-g.json new file mode 100644 index 0000000000000000000000000000000000000000..0e04b8a6f337e421a9d176c3d99bc0eb554da2c8 --- /dev/null +++ b/data_en/goal/reptile_005-g.json @@ -0,0 +1,68 @@ +{ + "task_id": "reptile_005-g", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I want to organize this synonymization record for an old Sri Lankan museum name in the current Naja list into a two-row comparison table. Output two rows with columns rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note. The first row should be ACCEPTED_NAME and the second row CONTESTED_NAME.", + "start_url": "https://reptile-database.reptarium.cz/advanced_search?genus=Naja&submit=Search", + "output_format": "Output a two-row comparison table with columns rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note.", + "oracle_answer": "1|ACCEPTED_NAME|Naja naja|SUBJECTIVE_JUNIOR_SYNONYM_OF_NAJA_NAJA|VALID_LECTOTYPE|ZMB 2796|restricted type locality: Sri Lanka\n2|CONTESTED_NAME|Naja polyocellata|SHI et al. 2022+SILVA et al. 2023|HOLOTYPE|BMNH 1946.1.18.50|invalid lectotype claim: NRM (= NHR) Lin-90", + "metadata": { + "State-Gated Retrieval": [ + "Within the current Naja list, identify the Sri Lanka contested-name branch: the name was recently reused as a distinct valid name, but the database now explicitly merges it back into the accepted name.", + "On the current Naja naja page, read the recent-use evidence, final synonym status, lectotype correction, restricted type locality, and the holotype information for the contested name itself.", + "The final output must organize the ACCEPTED_NAME side and the CONTESTED_NAME side into a two-row comparison table." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the current Naja species list and the Naja naja page yield the Sri Lanka contested-name branch, recent-use citations, and the accepted-name context", + "comment, Types, and type-comment blocks yield the final synonym treatment plus the valid and invalid lectotype assignments and the contested-name holotype", + "final rows are produced only after the accepted-name side and the contested-name side are reconciled on the current Naja naja page" + ], + "control_dependency": [ + "recent-use evidence for Naja polyocellata must be interpreted together with the current final synonym treatment shown on that page", + "lectotype status must be fixed from the combined Types and type-comment evidence rather than from a single provisional assignment", + "the accepted-name and contested-name rows are emitted together only after final status, type locality, and specimen roles are fixed" + ], + "freeze": { + "historical_window": "the objectively existing taxa in the Sri Lanka Naja branch, using current Reptile Database comment, Types, and type-comment blocks as nearly objective and highly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Within the current Naja list, identify the Sri Lanka contested-name record: the name was recently reused in the literature as a distinct valid name, but the database now explicitly states that it should still be merged into the accepted name.", + "On the current Naja naja page, the result must jointly recover the recent-use evidence, final synonym status, lectotype correction, restricted type locality, and the holotype information for the contested name itself.", + "The final output must organize the ACCEPTED_NAME side and the CONTESTED_NAME side into a two-row comparison table." + ], + "exclusion_conditions": [ + "Exclude results that treat the recently revived contested name as the current accepted name.", + "Exclude results that stop at the Wallach 2014 lectotype designation and do not continue to the later comment and type-comment correction.", + "Exclude results that fail to output both the restricted type locality and the contested-name holotype." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "name_role", + "name", + "status_or_evidence", + "specimen_role", + "specimen_code", + "supporting_note" + ], + "rank": "emit 1 for ACCEPTED_NAME and 2 for CONTESTED_NAME", + "name_role": [ + "ACCEPTED_NAME", + "CONTESTED_NAME" + ], + "name_fields": "use the current binomial spellings exactly", + "specimen_code_normalization": "preserve museum abbreviations, spaces, parentheses, and specimen punctuation exactly as the page shows", + "sorting_or_selection": "emit rows in the fixed order ACCEPTED_NAME then CONTESTED_NAME" + } + } +} diff --git a/data_en/goal/wateroffice_001-g.json b/data_en/goal/wateroffice_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..20d1a132b9012ce38a91f65be5ea0a2de604829c --- /dev/null +++ b/data_en/goal/wateroffice_001-g.json @@ -0,0 +1,67 @@ +{ + "task_id": "wateroffice_001-g", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am compiling historical daily flow comparison data for the Saint John River spring freshet and want to identify, along the Saint John River mainstem, the last station in the current monitoring network that still allows daily flow comparisons for March-April 1973 and March-April 2018, as well as the first downstream mainstem station that no longer satisfies that condition. Mark a station as PASS if the target windows have complete daily flow records, LEVEL_ONLY if only water level records are available, and FLOW_GAP if daily flow records exist but the target months are missing or incomplete. Output a two-row breakpoint table with columns rank|station_number|breakpoint_role|target_window_status|final_verdict. The first row should be LAST_USABLE and the second row should be FIRST_DOWNSTREAM_FAIL.", + "start_url": "https://wateroffice.ec.gc.ca/search/real_time_e.html", + "output_format": "Output a two-row breakpoint table with columns rank|station_number|breakpoint_role|target_window_status|final_verdict.", + "oracle_answer": "1|01AF002|LAST_USABLE|PASS|KEEP\n2|01AK003|FIRST_DOWNSTREAM_FAIL|LEVEL_ONLY|REJECT", + "metadata": { + "State-Gated Retrieval": [ + "Determine the last station still usable for the target historical-window comparison only within the Saint John River mainstem stations in the current monitoring network.", + "The historical availability page must distinguish Flow Data Availability from Daily Water Level Data Availability, and completeness for March-April 1973 and March-April 2018 must be checked.", + "The final output must provide both breakpoint rows, LAST_USABLE and FIRST_DOWNSTREAM_FAIL, under the same validation rule." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the current Saint John River mainstem station sequence provides the downstream order in which the breakpoints must be checked", + "per-station historical availability pages yield Flow Data Availability, Daily Water Level Data Availability, and target-month completeness for 1973 and 2018", + "the final breakpoint rows are produced only after the availability-page checks identify the last usable station and the first downstream failure under the same rule" + ], + "control_dependency": [ + "the breakpoint pair must be determined from historical availability that distinguishes flow from level-only evidence", + "target-year/month completeness must be checked on the availability page rather than inferred from the station list", + "the second row is emitted only after the first downstream failing mainstem station is fixed under the same validation rule" + ], + "freeze": { + "historical_window": "mainstem candidate stations evaluated within the fixed historical March/April daily-availability windows for 1973 and 2018, using station ordering and completeness signals as nearly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Determine the last station still usable for the target historical-window comparison only within the Saint John River mainstem stations in the current monitoring network.", + "The historical availability page must distinguish Flow Data Availability from Daily Water Level Data Availability, and completeness for March-April 1973 and March-April 2018 must be checked.", + "The final output must provide both breakpoint rows, LAST_USABLE and FIRST_DOWNSTREAM_FAIL, under the same validation rule." + ], + "exclusion_conditions": [ + "Exclude results that determine the breakpoint directly from the current Saint John River mainstem station sequence using only a reference index.", + "Exclude results that mistakenly treat level-only evidence as satisfying the flow condition.", + "Exclude results that do not check each station's availability page to verify target-month completeness." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "breakpoint_role", + "target_window_status", + "final_verdict" + ], + "rank": "emit `1` for LAST_USABLE and `2` for FIRST_DOWNSTREAM_FAIL", + "station_number": "preserve the station number exactly", + "breakpoint_role": "emit `LAST_USABLE` and `FIRST_DOWNSTREAM_FAIL` exactly", + "target_window_status": "emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly", + "final_verdict": "emit `KEEP` for the usable breakpoint row and `REJECT` for the downstream failing breakpoint row", + "stop_condition": [ + "the last usable mainstem station is fixed under the availability-page validation rule", + "the first downstream failing mainstem station is fixed under the same validation rule before the two-row output is emitted" + ] + } + } +} diff --git a/data_en/goal/wateroffice_002-g.json b/data_en/goal/wateroffice_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..8f3e6f2917900a0309ce1d98e62c3f2deeb00f2f --- /dev/null +++ b/data_en/goal/wateroffice_002-g.json @@ -0,0 +1,66 @@ +{ + "task_id": "wateroffice_002-g", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "I am compiling historical daily flow records for the Bulkley River reach from Houston to Hazelton and want to determine which candidate mainstem stations on this reach truly have complete daily flow records for April-July 1948 and April-July 1950. Mark a station as PASS if the target windows have complete daily flow records, LEVEL_ONLY if only water level records are available, and FLOW_GAP if daily flow records exist but any target month from April to July is incomplete. Output a table in downstream-to-upstream order with columns rank|station_number|target_window_status|final_verdict.", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "Output a table in downstream-to-upstream order with columns rank|station_number|target_window_status|final_verdict.", + "oracle_answer": "1|08EE004|PASS|KEEP\n2|08EE001|LEVEL_ONLY|REJECT\n3|08EE005|FLOW_GAP|REJECT\n4|08EE003|FLOW_GAP|REJECT", + "metadata": { + "State-Gated Retrieval": [ + "First identify mainstem candidate stations on the Historical Results list that appear to cover 1948/1950 and carry a Flow label.", + "A station qualifies only if its availability page shows the target years in the Flow section and all of April-July marked C.", + "The final output must report target_window_status and final_verdict for each station in the same station set, ordered from downstream to upstream." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Historical Results list yields four downstream-to-upstream mainstem candidates whose result rows span the target years and include Flow labels", + "each candidate's availability page yields whether the target years are in the Flow table and whether April–July is complete", + "the final ordered rows are produced only after all four stations are classified under the full Flow-table-and-Apr-Jul-C rule" + ], + "control_dependency": [ + "list-level year spans and coarse Flow tags must be confirmed by explicit target-month checks on the availability page", + "Hazelton, Smithers, and Houston candidate statuses must be fixed before the downstream-most KEEP row can be confirmed", + "row order and KEEP/REJECT labels must be emitted only after the full availability-page rule is applied to all four stations" + ], + "freeze": { + "historical_window": "the target mainstem stations tested within the fixed historical daily Flow-availability windows for 1948 and 1950, with April–July complete-C coverage used as nearly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "First identify mainstem candidate stations on the Historical Results list that appear to cover 1948/1950 and carry a Flow label.", + "A station qualifies only if its availability page shows the target years in the Flow section and all of April-July marked C.", + "The final output must report target_window_status and final_verdict for each station in the same station set, ordered from downstream to upstream." + ], + "exclusion_conditions": [ + "Exclude stations deemed usable solely from list-level year spans and coarse Flow labels.", + "Exclude results that mark any LEVEL_ONLY or FLOW_GAP station as KEEP.", + "Exclude results that do not apply the full availability-page rule to all initially screened stations." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "target_window_status", + "final_verdict" + ], + "rank": "emit 1 through 4 in downstream-to-upstream order within the validated station set", + "station_number": "preserve the station number exactly", + "target_window_status": "emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly", + "final_verdict": "emit `KEEP` or `REJECT` exactly", + "sorting_or_selection": "downstream to upstream within the validated Bulkley River mainstem station set", + "stop_condition": [ + "all four initially screened stations are classified under the full availability-page rule", + "the ordered table is emitted only after the downstream-to-upstream sequence is fixed" + ] + } + } +} diff --git a/data_en/goal/wateroffice_003-g.json b/data_en/goal/wateroffice_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..9597460066f5a9ec59ca1b8b5cdbb118768429b2 --- /dev/null +++ b/data_en/goal/wateroffice_003-g.json @@ -0,0 +1,62 @@ +{ + "task_id": "wateroffice_003-g", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "I am compiling historical snowmelt daily flow data for the Thompson River from Chase to Spences Bridge. I need to identify which mainstem stations along this reach actually had daily flow records for both 1958 and 1971 (May–July). For each mainstem station that appears in the station list as covering 1958 and 1971 and having flow information, verify it station by station in downstream order from Chase to Spences Bridge. Output a table with columns: rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict. If a station has only water level records (no daily flow) for a target year, mark it LEVEL_ONLY. If daily flow records are missing or any of the May–July months is incomplete, mark it FLOW_GAP. Only if both years meet the criteria should final_verdict be KEEP; otherwise mark it REJECT.", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "Output a table with columns: rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict.", + "oracle_answer": "1|08LE031|SOUTH THOMPSON RIVER AT CHASE|PASS|PASS|KEEP\n2|08LE069|SOUTH THOMPSON RIVER AT MONTE CREEK|FLOW_GAP|LEVEL_ONLY|REJECT\n3|08LF023|THOMPSON RIVER AT KAMLOOPS|LEVEL_ONLY|LEVEL_ONLY|REJECT\n4|08LF033|THOMPSON RIVER NEAR SAVONA|FLOW_GAP|FLOW_GAP|REJECT\n5|08LF051|THOMPSON RIVER NEAR SPENCES BRIDGE|PASS|PASS|KEEP", + "metadata": { + "State-Gated Retrieval": [ + "All five candidate stations must be verified on their availability page: check whether the target year appears in the Flow table and whether May–July is entirely marked C.", + "For each station, output a PASS, LEVEL_ONLY, or FLOW_GAP judgment for both target years, then label it KEEP or REJECT accordingly.", + "The result order must follow the river-path sequence specified in the task." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "The river-path ordering yields five South Thompson/Thompson mainstem candidates.", + "Each station's availability page indicates whether 1958 and 1971 are present in the Flow table and whether May–July is complete.", + "Final rows are produced only after every candidate is classified under the stricter target-year and target-month Flow rule." + ], + "control_dependency": [ + "Overall year coverage on the results list must be confirmed by the availability page inside the Flow table.", + "Monte Creek, Savona, and Kamloops must be rejected by LEVEL_ONLY/FLOW_GAP evidence before the KEEP rows are final.", + "The river-order sequence remains fixed, but station statuses must be assigned only after the availability-page rule is applied to all five stations." + ], + "freeze": { + "historical_window": "The ordered South Thompson/Thompson mainstem candidates are tested within the fixed historical Flow-availability windows for 1958 and 1971, with May–July complete-C coverage used as nearly stable reference information." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "All five candidate stations must be verified on their availability page: check whether the target year appears in the Flow table and whether May–July is entirely marked C.", + "For each station, output a PASS, LEVEL_ONLY, or FLOW_GAP judgment for both target years, then label it KEEP or REJECT accordingly.", + "The result order must follow the river-path sequence specified in the task." + ], + "exclusion_conditions": [ + "Exclude results that treat overall year coverage on the list page as sufficient evidence.", + "Exclude results that fail to distinguish between Flow-table target-year and month completeness versus Level-only evidence.", + "Exclude results that do not apply the same availability-page rule uniformly to all five stations." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "station_name", + "1958_MayJul", + "1971_MayJul", + "final_verdict" + ], + "rank": "use the fixed Chase-to-Spences-Bridge mainstem order from the reference index, not the transient search-result order", + "year_window_fields": "the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP", + "final_verdict": "emit `KEEP` or `REJECT` exactly" + } + } +} diff --git a/data_en/goal/wateroffice_004-g.json b/data_en/goal/wateroffice_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..566085397ec6c16d59109503ef210172831fbbbf --- /dev/null +++ b/data_en/goal/wateroffice_004-g.json @@ -0,0 +1,62 @@ +{ + "task_id": "wateroffice_004-g", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 13, + "instruction": "I am compiling historical daily flow records for the main stem of the Columbia River from Fairmont Hot Springs to the International Boundary. I want to check, station by station, which Wateroffice gauges have complete daily flow records for May–October of 1955 and 1956. The candidate set is limited to main-stem Columbia River stations whose overall period of record spans both 1955 and 1956. Please evaluate each station in upstream-to-downstream order and output a table with columns: rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict. If the target year has only water-level records and no daily flow records, mark it as LEVEL_ONLY. If daily flow records for May–October of that year are complete, mark it as PASS. If daily flow records are absent or any month from May to October has incomplete records, mark it as FLOW_GAP. Only when both 1955 and 1956 meet the complete daily flow condition should final_verdict be KEEP; otherwise, it should be REJECT.", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "Output a table with columns: rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict.", + "oracle_answer": "1|08NA045|COLUMBIA RIVER NEAR FAIRMONT HOT SPRINGS|PASS|PASS|KEEP\n2|08NA004|COLUMBIA RIVER AT ATHALMER|LEVEL_ONLY|LEVEL_ONLY|REJECT\n3|08NA052|COLUMBIA RIVER NEAR EDGEWATER|PASS|FLOW_GAP|REJECT\n4|08NA002|COLUMBIA RIVER AT NICHOLSON|PASS|PASS|KEEP\n5|08NB005|COLUMBIA RIVER AT DONALD|PASS|PASS|KEEP\n6|08NB006|COLUMBIA RIVER AT SURPRISE RAPIDS|PASS|PASS|KEEP\n7|08ND007|COLUMBIA RIVER ABOVE NAGLE CREEK|PASS|PASS|KEEP\n8|08ND011|COLUMBIA RIVER ABOVE STEAMBOAT RAPIDS|FLOW_GAP|PASS|REJECT\n9|08ND006|COLUMBIA RIVER AT TWELVE MILE FERRY|PASS|PASS|KEEP\n10|08NE002|COLUMBIA RIVER AT CASTLEGAR|LEVEL_ONLY|LEVEL_ONLY|REJECT\n11|08NE049|COLUMBIA RIVER AT BIRCHBANK|PASS|PASS|KEEP\n12|08NE003|COLUMBIA RIVER AT TRAIL|LEVEL_ONLY|LEVEL_ONLY|REJECT\n13|08NE058|COLUMBIA RIVER AT INTERNATIONAL BOUNDARY|PASS|PASS|KEEP", + "metadata": { + "State-Gated Retrieval": [ + "All candidate Columbia River stations must be checked on their availability page to confirm that the target years appear in the Flow table and that May–October is marked entirely as C.", + "For each station, provide the KEEP/REJECT basis for both 1955 and 1956, distinguishing LEVEL_ONLY and FLOW_GAP cases from stations that only appear eligible from their overall year span.", + "The final table must preserve the order and fields specified in the task." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Columbia River candidate ordering yields fourteen stations spanning the target years", + "each availability page yields whether 1955 and 1956 are present in the Flow table and whether May-October is complete", + "final rows are produced only after every station is classified under the stricter Flow-table-and-May-Oct-C rule" + ], + "control_dependency": [ + "list-level year spans must be confirmed by the availability page inside the Flow table", + "LEVEL_ONLY and FLOW_GAP evidence must be applied to each station before the KEEP/REJECT table is finalized", + "station-by-station verdicts and rejection reasons must be determined only after the full availability-page rule replaces the initial year-span screen" + ], + "freeze": { + "historical_window": "the ordered Columbia River candidates tested within the fixed historical Flow-availability windows for 1955 and 1956, with May-October complete-C coverage used as nearly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "All candidate Columbia River stations must be checked on their availability page to confirm that the target years appear in the Flow table and that May–October is marked entirely as C.", + "For each station, provide the KEEP/REJECT basis for both 1955 and 1956, distinguishing LEVEL_ONLY and FLOW_GAP cases from stations that only appear eligible from their overall year span.", + "The final table must preserve the order and fields specified in the task." + ], + "exclusion_conditions": [ + "Exclude results that retain a station solely because its overall period spans 1955/1956.", + "Exclude results that fail to distinguish, station by station, between Flow-available, Level-only, and incomplete-month cases.", + "Exclude results that do not apply the full availability-page rule uniformly to all 14 stations." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "station_name", + "1955_MayOct", + "1956_MayOct", + "final_verdict" + ], + "rank": "use the fixed upstream-to-downstream Columbia mainstem order from the reference index, not the transient search-result order", + "year_window_fields": "the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP", + "final_verdict": "emit `KEEP` or `REJECT` exactly" + } + } +} diff --git a/data_en/goal/wateroffice_005-g.json b/data_en/goal/wateroffice_005-g.json new file mode 100644 index 0000000000000000000000000000000000000000..feafd501d403ffea061e57d43ac77fcb3132d0fe --- /dev/null +++ b/data_en/goal/wateroffice_005-g.json @@ -0,0 +1,74 @@ +{ + "task_id": "wateroffice_005-g", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "I am organizing historical daily-flow records for the Peace River reach from Dunvegan Bridge to Fifth Meridian and want a three-row diagnostic table for the furthest-downstream reusable mainstem station, the first downstream failing station after it, and the provisional terminal station that an initial screen would misclassify as the downstream winner. If the target window satisfies the complete daily-flow condition, mark it as PASS. If the target year has only level records, mark it as LEVEL_ONLY. If daily-flow records exist but any target month from May through September is incomplete, mark it as FLOW_GAP. If the target year has neither daily-flow nor level records, mark it as NO_TARGET_RECORD. Output three rows with columns rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count.", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "Output a three-row diagnostic table with columns rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count.", + "oracle_answer": "1|07HA001|FINAL_STATION|PASS|5|2\n2|07HD001|FIRST_BREAK_AFTER_FINAL|FLOW_GAP|5|2\n3|07KA002|PROVISIONAL_STATION|FLOW_GAP|5|2", + "metadata": { + "State-Gated Retrieval": [ + "Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian.", + "A genuinely reusable station must satisfy the availability-page rule that both 1966 and 1967 appear in the Flow table and that every month from May through September is complete.", + "The final output must jointly report FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION, while repeating provisional_count and final_count in every row." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Peace River mainstem chain between Dunvegan Bridge and Fifth Meridian yields the initial station list and the downstream breakpoint positions that need revalidation", + "each availability page yields whether 1966 and 1967 are present in the Flow or Level tables and whether May-September is complete", + "final rows are produced only after the final station, the first downstream failure, and the provisional downstream winner are all fixed under the same availability-page validation rule" + ], + "control_dependency": [ + "station-level target-year Flow evidence must be validated by explicit May-September completeness checks on the availability page", + "the final downstream reusable station and the first downstream failure must be determined under the same validation rule rather than from the initial station screen", + "the provisional downstream winner is kept in the output only for reference after its FLOW_GAP status is confirmed on the availability page" + ], + "freeze": { + "historical_window": "the Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian, evaluated within the fixed historical 1966 and 1967 Flow-availability windows, with May-September complete-C coverage used as nearly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian.", + "A genuinely reusable station must satisfy the availability-page rule that both 1966 and 1967 appear in the Flow table and that every month from May through September is complete.", + "The final output must jointly report FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION, while repeating provisional_count and final_count in every row." + ], + "exclusion_conditions": [ + "Exclude results that treat a station as usable simply because the target years have Flow records.", + "Exclude results that do not verify completeness month by month from May through September.", + "Exclude results that mark a station such as 07KA002 as FINAL_STATION when availability-page evidence shows FLOW_GAP." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "diagnosis_role", + "target_window_status", + "provisional_count", + "final_count" + ], + "rank": "emit the fixed order 1, 2, 3 for FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION", + "station_number": "use uppercase WSC station codes exactly as the Reference Index and availability pages show", + "diagnosis_role": [ + "FINAL_STATION", + "FIRST_BREAK_AFTER_FINAL", + "PROVISIONAL_STATION" + ], + "target_window_status": [ + "PASS", + "LEVEL_ONLY", + "FLOW_GAP", + "NO_TARGET_RECORD" + ], + "count_fields": "repeat the global provisional_count and final_count in every row as plain integers", + "sorting_or_selection": "emit rows in the fixed diagnostic order FINAL_STATION, FIRST_BREAK_AFTER_FINAL, PROVISIONAL_STATION" + } + } +} diff --git a/data_en/goal/waterquality_001-g.json b/data_en/goal/waterquality_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..6734fee95a956fa189097429379df05591b3bd6d --- /dev/null +++ b/data_en/goal/waterquality_001-g.json @@ -0,0 +1,67 @@ +{ + "task_id": "waterquality_001-g", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am compiling historical monitoring data for the middle Rio Grande and need to identify two monitoring locations suitable as sentinel sites for main-channel wastewater impacts. From the monitoring locations downstream of RIO GRANDE AT EMBUDO, NM that are confirmed to be on the Rio Grande mainstem, select two qualifying stations: the upstream station must be downstream of the Town of Bernalillo wastewater treatment plant outfall; the downstream station must be downstream of both the Town of Bernalillo and Rio Rancho No. 2 wastewater treatment plant outfalls. Both stations must simultaneously meet the following conditions: the station itself is not an outfall, facility, well, canal, or drainage ditch; the station type is labeled as River/Stream; records for Microbiological, Nutrient, Organics, Other, and Physical are all complete for 2015—2020; and the start years for Microbiological and Physical records are both earlier than 2010. If multiple mainstem stations in a given segment meet the conditions, select the one farthest upstream along the main channel. Output a single line in upstream-to-downstream order in the format ||, with the two segments separated by a comma.", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "Output a single line in upstream-to-downstream order in the format ||, with the two segments separated by a comma.", + "oracle_answer": "SANDIAWQ_WQX-RG003|2004|2004,SANDIAWQ_WQX-RG008|2004|2004", + "metadata": { + "State-Gated Retrieval": [ + "Select two target stations only from Rio Grande mainstem monitoring stations downstream of RIO GRANDE AT EMBUDO, NM, and require both to be past the specified outfall locations.", + "The station detail page must explicitly indicate River/Stream, and records for Microbiological, Nutrient, Organics, Other, and Physical must fully cover 2015—2020, with start years for Microbiological and Physical both earlier than 2010.", + "Output the two stations in upstream-to-downstream order." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Provider/list views yield the Rio Grande mainstem candidates downstream of the Bernalillo and Rio Rancho No. 2 discharge points.", + "Detail pages yield flow position, location type, characteristic-group period-of-record coverage for 2015—2020, and the Microbiological/Physical baseline years.", + "Final rows are produced only after the corrected downstream sentry stations are fixed and ordered from upstream to downstream." + ], + "control_dependency": [ + "Provider-list stream tags are only provisional and must be confirmed on the detail page by both mainstem placement and location type.", + "Target-window presence is insufficient until full 2015—2020 coverage is confirmed on the detail page for all four groups.", + "Once RG002/RG007 fail the full detail-page checks, the workflow must continue downstream from the discharge-point starting position to RG003/RG008." + ], + "freeze": { + "historical_window": "Rio Grande mainstem stations downstream of the Town of Bernalillo and Rio Rancho No. 2 WWTP outfalls, validated against 2015—2020 coverage for Microbiological, Nutrient, Organics, Other, and Physical." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Select two target stations only from Rio Grande mainstem monitoring stations downstream of RIO GRANDE AT EMBUDO, NM, and require both to be past the specified outfall locations.", + "The station detail page must explicitly indicate River/Stream, and records for Microbiological, Nutrient, Organics, Other, and Physical must fully cover 2015—2020, with start years for Microbiological and Physical both earlier than 2010.", + "Output the two stations in upstream-to-downstream order." + ], + "exclusion_conditions": [ + "Exclude stations that have a shallow (Stream) tag on the provider list or records near the target window, but whose detail page does not satisfy flow position, location type, or full period-of-record conditions.", + "Exclude locations that are outfalls, facilities, wells, canals, or drainage ditches.", + "Exclude candidates such as RG002 and RG007 that are not qualified sentinel stations downstream of the corresponding outfalls." + ], + "normalization": { + "record_separator": ",", + "field_separator": "|", + "schema_per_record": [ + "MonitoringLocationIdentifier", + "Microbiological_start_year", + "Physical_start_year" + ], + "ordering": "emit exactly two records from upstream to downstream", + "station_id": "use uppercase MonitoringLocationIdentifier", + "year_fields": "emit four-digit years as plain integers", + "selection": { + "record_1": "the first qualifying mainstem station below the Bernalillo outfall", + "record_2": "the first qualifying mainstem station below both the Bernalillo and Rio Rancho No. 2 outfalls" + }, + "stop_condition": [ + "the Bernalillo branch stops only after its first qualifying mainstem station is fixed", + "the Rio Rancho No. 2 branch stops only after its first qualifying mainstem station is fixed", + "the two segments are emitted as one comma-joined line in upstream-to-downstream order" + ] + } + } +} diff --git a/data_en/goal/waterquality_002-g.json b/data_en/goal/waterquality_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..b73831d8b5926192fe9d7ff73283eb8d300a1591 --- /dev/null +++ b/data_en/goal/waterquality_002-g.json @@ -0,0 +1,67 @@ +{ + "task_id": "waterquality_002-g", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "I am analyzing trends in the lower Rio Grande from 2001 to 2010. From monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002, select one representative station for Hidalgo County and one for Cameron County. Each station must satisfy all of the following conditions: located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002; the monitoring location type on the station detail page must be River/Stream; and records for all four characteristic groups—Microbiological, Nutrient, Organics, Other, and Physical—must cover the period 2001–2010. If multiple stations in the same county qualify, select the one with the earliest year in which all four groups are simultaneously present. Output a single line with the Hidalgo segment first and the Cameron segment second, using the format :|||||, with the two segments separated by a comma.", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "Output a single line with the Hidalgo segment first and the Cameron segment second, using the format :|||||, with the two segments separated by a comma.", + "oracle_answer": "Hidalgo:TCEQMAIN-15808|1998|1998|1998|1998|1998,Cameron:TCEQMAIN-13177|1995|1981|1981|1995|1981", + "metadata": { + "State-Gated Retrieval": [ + "Select one representative station for Hidalgo County and one for Cameron County only from monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002.", + "Candidate detail pages must show River/Stream as the monitoring location type, and records for all four characteristic groups—Microbiological, Nutrient, Organics, Other, and Physical—must cover 2001–2010.", + "If multiple stations in the same county qualify, select the one with the earliest year in which all four groups are simultaneously present." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the fixed downstream starting point and county split yield Hidalgo and Cameron candidate mainstem stations within HUC 13090002", + "detail pages yield River/Stream validity, the four characteristic-group start years, and the earliest year when all four groups are simultaneously present for 2001-2010 coverage", + "final rows are produced only after the county-specific searches are rerun from the fixed downstream starting point and then ranked by common-start year" + ], + "control_dependency": [ + "the Hidalgo search must preserve the \"below TCEQMAIN-13664\" downstream starting point rather than returning to the anchor station itself", + "a station is only provisional until all four characteristic groups are confirmed for the same MonitoringLocationIdentifier and tidal/intake conflicts are excluded on the detail page", + "county winners are valid only after late-start and non-river candidates are removed and the common-start-year tie-break is recomputed" + ], + "freeze": { + "historical_window": "stations below RIO GRANDE BELOW ANZALDUAS within HUC 13090002, split by Hidalgo and Cameron County, with Microbiological, Nutrient, Organics, Other, and Physical coverage over 2001-2010" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Select one representative station for Hidalgo County and one for Cameron County only from monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002.", + "Candidate detail pages must show River/Stream as the monitoring location type, and records for all four characteristic groups—Microbiological, Nutrient, Organics, Other, and Physical—must cover 2001–2010.", + "If multiple stations in the same county qualify, select the one with the earliest year in which all four groups are simultaneously present." + ], + "exclusion_conditions": [ + "Exclude results where the Hidalgo search loses the downstream starting point and brings the starting station itself back into the candidate set.", + "Exclude results that treat a single multi-select of the four characteristic groups as sufficient without verifying that all four belong to the same station ID.", + "Exclude stations with tidal, intake, late-start, or other conflicts clearly indicated on the detail page." + ], + "normalization": { + "record_separator": ",", + "field_separator": "|", + "schema_per_record": [ + "County:MonitoringLocationIdentifier", + "common_start_year", + "Microbiological_start_year", + "Nutrient_start_year", + "Organics_Other_start_year", + "Physical_start_year" + ], + "ordering": "emit exactly two records, with Hidalgo first and Cameron second", + "county_prefix": "use the county label in title case, followed by : and the uppercase MonitoringLocationIdentifier", + "year_fields": "emit four-digit years as plain integers", + "common_start_year": "the earliest year in which all four required groups are simultaneously present for the chosen county station", + "stop_condition": [ + "each county branch is rerun until one River/Stream station survives all four group checks", + "the county winner is fixed only after late-start and non-river candidates are excluded on the detail page", + "the two county segments are emitted on one line in the fixed Hidalgo-then-Cameron order" + ] + } + } +} diff --git a/data_en/goal/waterquality_003-g.json b/data_en/goal/waterquality_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..82fcdd7125b2653c36287b48c3e22d5b0d934329 --- /dev/null +++ b/data_en/goal/waterquality_003-g.json @@ -0,0 +1,66 @@ +{ + "task_id": "waterquality_003-g", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "I am compiling 2012–2018 water-quality reference data for the Brazos River mainstem downstream of Brazos Rv at Waco, TX. For each of the three specified HUCs that include Waco (12060202, 12070101, 12070104), I need to identify one TCEQ monitoring station suitable as a long-term reference for 2012–2018 along the Brazos River mainstem downstream of Brazos Rv at Waco, TX. Candidate stations must satisfy all of the following: be located within the corresponding HUC; have a monitoring-location type of River/Stream on the station detail page; have a station name that still corresponds to the Brazos River mainstem, not a tributary or other named waterbody; and have records covering 2012–2018 for all five characteristic groups—Inorganics, Major, Non-metals; Microbiological; Nutrient; Organics, Other; and Physical—meaning the station’s start year is no later than 2012 and its end year is no earlier than 2018. List the three results in upstream-to-downstream order, one per line, using the format: |||||||.", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "List the three results in upstream-to-downstream order, one per line, using the format: |||||||.", + "oracle_answer": "12060202|TCEQMAIN-12037|2000|1991|2000|1991|1999|1991\n12070101|TCEQMAIN-12030|2006|1972|1972|1972|2006|1972\n12070104|TCEQMAIN-11848|1975|1974|1975|1974|1975|1974", + "metadata": { + "State-Gated Retrieval": [ + "The search must stay anchored downstream of Waco and look for Brazos mainstem monitoring stations within the three HUCs specified in the task.", + "Each candidate station must be checked separately across the five characteristic groups and then matched back to the same station ID, after which the detail page must verify full 2012–2018 coverage and mainstem semantics.", + "For each HUC, retain only the qualifying station with the earliest common start year, and output the start-year fields required by the task." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the fixed downstream starting point below Waco and the three target HUC searches yield the Brazos mainstem candidate stations", + "detail pages yield true downstream position, mainstem-vs-tributary semantics, and five-group period-of-record coverage across 2012-2018", + "final rows are produced only after the three HUC-specific searches are carried out, matched by station ID, and ranked by the earliest year when all five groups are jointly available" + ], + "control_dependency": [ + "the workflow must stay anchored downstream of Waco rather than reintroducing upstream stations such as TCEQMAIN-12044", + "name-based waterbody matches must be validated on the detail page by excluding tributaries such as LITTLE BRAZOS RIVER and confirming full-window coverage", + "station ranking must be determined after false positives from partial-window records are removed" + ], + "freeze": { + "historical_window": "Brazos River mainstem stations downstream of the Waco anchor evaluated within the fixed historical 2012-2018 window, using the HUC 12060202 / 12070101 / 12070104 split and five characteristic groups as largely stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "The search must stay anchored downstream of Waco and look for Brazos mainstem monitoring stations within the three HUCs specified in the task.", + "Each candidate station must be checked separately across the five characteristic groups and then matched back to the same station ID, after which the detail page must verify full 2012–2018 coverage and mainstem semantics.", + "For each HUC, retain only the qualifying station with the earliest common start year, and output the start-year fields required by the task." + ], + "exclusion_conditions": [ + "Exclude results that lose the downstream starting point below Waco and bring upstream stations back into the candidate set.", + "Exclude results that mistakenly treat tributaries such as LITTLE BRAZOS RIVER as the Brazos mainstem.", + "Exclude stations that have data near the query window but do not cover the entire 2012–2018 window." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "HUC", + "MonitoringLocationIdentifier", + "common_start_year", + "Inorganics_start", + "Microbiological_start", + "Nutrient_start", + "Organics_Other_start", + "Physical_start" + ], + "HUC": "preserve the HUC exactly as emitted in the source result", + "MonitoringLocationIdentifier": "preserve the monitoring-location identifier exactly, for example `TCEQMAIN-12037`", + "common_start_year": "emit the maximum of the five per-group start years", + "selection_rule": "only keep mainstem river/stream sites whose five required groups all cover the target 2012-2018 window", + "sorting_or_selection": "upstream to downstream along the mainstem" + } + } +} diff --git a/data_en/goal/waterquality_004-g.json b/data_en/goal/waterquality_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..f4a7ddf00c3c302acac59487fb8a7a90a888f1c6 --- /dev/null +++ b/data_en/goal/waterquality_004-g.json @@ -0,0 +1,67 @@ +{ + "task_id": "waterquality_004-g", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "I am reviewing toxic-pollutant-related water quality monitoring data for the Trinity River mainstem from 1993 to 2001, with the reach near FM 85 as the upstream boundary and the reach near Interstate 10 as the downstream boundary. I need to select one TCEQ long-term reference station for each of the upper, middle, and lower segments along the river.\nCandidate monitoring locations must simultaneously meet the following conditions: the monitoring location type in the station record is labeled River/Stream; the station name corresponds to the Trinity River mainstem, not a tributary, other named waterbody, or distributary channel; records for all six characteristic groups—Inorganics, Major, Non-metals; Microbiological; Nutrient; Organics, Other; Organics, PCBs; and Physical—must cover the period 1993–2001, specifically with a start year no later than 1993 and an end year no earlier than 2001. Output three rows in order from upstream to downstream along the river, each row formatted as ||||||||.", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "Output three rows in order from upstream to downstream along the river, each row formatted as ||||||||.", + "oracle_answer": "12030105|TCEQMAIN-10924|1983|1982|1983|1982|1983|1983|1982\n12030202|TCEQMAIN-10897|1993|1969|1972|1972|1993|1974|1969\n12030203|TCEQMAIN-10892|1976|1969|1971|1972|1974|1976|1969", + "metadata": { + "State-Gated Retrieval": [ + "Only retain candidate stations that satisfy the Trinity River mainstem semantics and require all six characteristic groups to cover 1993–2001.", + "The six groups must be searched separately and then matched back to the same station ID, after which the detail page must verify full time-window coverage and completeness of the legacy toxics groups.", + "For each target segment, retain only the station that meets all group requirements and has the best common start year." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Trinity River mainstem candidate stations are generated from the target HUC searches and the six characteristic-group searches", + "detail pages yield River/Stream validity, 1993–2001 full-window coverage, and the group-specific start years needed for ranking", + "final rows are produced only after all six groups have been matched by station ID and detail-page validation removes partial-group and non-mainstem false positives" + ], + "control_dependency": [ + "each of the six characteristic groups must be evaluated separately and confirmed against the same station ID before a multi-select result can be retained", + "station names and River/Stream tags are insufficient until the detail page confirms Trinity mainstem semantics and 1993–2001 full-window coverage", + "candidate rejection and final ranking must be determined after applying the PCBs / Organics, Other gap checks" + ], + "freeze": { + "historical_window": "Trinity River mainstem stations validated within the fixed historical 1993–2001 window, using six characteristic groups and ranking by earliest joint availability plus group start years as largely stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Only retain candidate stations that satisfy the Trinity River mainstem semantics and require all six characteristic groups to cover 1993–2001.", + "The six groups must be searched separately and then matched back to the same station ID, after which the detail page must verify full time-window coverage and completeness of the legacy toxics groups.", + "For each target segment, retain only the station that meets all group requirements and has the best common start year." + ], + "exclusion_conditions": [ + "Exclude results that mistakenly treat a single multi-select of characteristic groups as sufficient to satisfy the requirement.", + "Exclude results that only check station names and River/Stream tags without verifying 1993–2001 full-window coverage.", + "Exclude stations that ignore missing PCBs or Organics, Other groups." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "HUC", + "MonitoringLocationIdentifier", + "common_start_year", + "Inorganics_start", + "Microbiological_start", + "Nutrient_start", + "Organics_Other_start", + "Organics_PCBs_start", + "Physical_start" + ], + "HUC": "preserve the HUC exactly as emitted in the source result", + "MonitoringLocationIdentifier": "preserve the monitoring-location identifier exactly, for example `TCEQMAIN-10924`", + "common_start_year": "emit the maximum of the six per-group start years", + "selection_rule": "only keep mainstem river/stream sites whose six required groups all cover the target window", + "sorting_or_selection": "upstream to downstream along the mainstem" + } + } +} diff --git a/data_en/goal/waterquality_005-g.json b/data_en/goal/waterquality_005-g.json new file mode 100644 index 0000000000000000000000000000000000000000..676047bd271974b73bc252dc5a7f7da66757e36a --- /dev/null +++ b/data_en/goal/waterquality_005-g.json @@ -0,0 +1,68 @@ +{ + "task_id": "waterquality_005-g", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 9, + "instruction": "I am organizing integrated water-quality records for the lower Neches River during 1978-1984 and want a table of the nine Characteristic Group start years for the nearest qualifying TCEQ reference station downstream of NECHES RIVER AT CR 4915 that still represents the inland Neches River mainstem. Output a 9-row table with columns rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year, using the fixed nine-group order specified in the task.", + "start_url": "https://www.waterqualitydata.us/provider/STORET/TCEQMAIN/TCEQMAIN-10598/", + "output_format": "Output a 9-row table with columns rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year.", + "oracle_answer": "1|TCEQMAIN-10580|12020003|Hardin County|Biological, Algae, Phytoplankton|1972|1977\n2|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Major, Non-metals|1971|1977\n3|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Minor, Metals|1974|1977\n4|TCEQMAIN-10580|12020003|Hardin County|Microbiological|1972|1977\n5|TCEQMAIN-10580|12020003|Hardin County|Nutrient|1972|1977\n6|TCEQMAIN-10580|12020003|Hardin County|Organics, Other|1974|1977\n7|TCEQMAIN-10580|12020003|Hardin County|Organics, PCBs|1974|1977\n8|TCEQMAIN-10580|12020003|Hardin County|Organics, Pesticide|1977|1977\n9|TCEQMAIN-10580|12020003|Hardin County|Physical|1971|1977", + "metadata": { + "State-Gated Retrieval": [ + "Search only among TCEQ monitoring stations downstream of NECHES RIVER AT CR 4915 that still represent the inland Neches River mainstem.", + "A candidate station must cover 1978-1984 in all nine Characteristic Groups and, on the detail page, must still qualify as River/Stream, outside lake or reservoir waters, and outside the Sabine-Neches outlet boundary reach.", + "The final output must be centered on the single winning station and list group_start_year plus common_start_year row by row in the fixed nine-group order." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the fixed downstream starting point at NECHES RIVER AT CR 4915 yields candidate inland mainstem stations across successive downstream HUCs", + "detail pages yield River/Stream validity, inland-vs-boundary semantics, and nine-group period-of-record coverage across 1978-1984", + "final rows are produced only after one winning station survives the inland-mainstem checks and the requirement that all nine groups match the same station, after which its nine group start years are emitted in the required order" + ], + "control_dependency": [ + "the nearest downstream mainstem station remains provisional until all nine characteristic groups have been checked separately and matched back to the same station ID", + "the downstream search must continue to the next mainstem HUC when the first candidate fails the nine-group coverage requirement", + "location semantics remain valid only after detail-page exclusion of lake/reservoir and Sabine-Neches boundary stations" + ], + "freeze": { + "historical_window": "Neches River inland mainstem stations downstream of NECHES RIVER AT CR 4915, validated within the fixed 1978-1984 window against nine characteristic groups as largely stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Search only among TCEQ monitoring stations downstream of NECHES RIVER AT CR 4915 that still represent the inland Neches River mainstem.", + "A candidate station must cover 1978-1984 in all nine Characteristic Groups and, on the detail page, must still qualify as River/Stream, outside lake or reservoir waters, and outside the Sabine-Neches outlet boundary reach.", + "The final output must be centered on the single winning station and list group_start_year plus common_start_year row by row in the fixed nine-group order." + ], + "exclusion_conditions": [ + "Exclude results that retain TCEQMAIN-10591 merely because it appears to be the nearest downstream mainstem station.", + "Exclude results that do not check the nine Characteristic Groups separately and verify that they all belong to the same station ID.", + "Exclude stations located in lake or reservoir waters or in the Sabine-Neches outlet boundary reach." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "MonitoringLocationIdentifier", + "HUC", + "County", + "characteristic_group", + "group_start_year", + "common_start_year" + ], + "rank": "emit 1 through 9 in the fixed characteristic-group order required by the task", + "MonitoringLocationIdentifier": "use uppercase MonitoringLocationIdentifier", + "HUC": "emit the HUC as an 8-digit string with no separators", + "County": "use the county name exactly as shown on the detail page", + "characteristic_group": "preserve the group label exactly as listed in the task", + "year_fields": "emit four-digit years as plain integers", + "common_start_year": "repeat the earliest year in which all nine required groups are simultaneously present for the chosen station", + "sorting_or_selection": "emit rows in the fixed nine-group order stated in the task" + } + } +} diff --git a/data_en/goal/wonder_001-g.json b/data_en/goal/wonder_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..a103d0f167d12e956be65b015f5785e89136326a --- /dev/null +++ b/data_en/goal/wonder_001-g.json @@ -0,0 +1,64 @@ +{ + "task_id": "wonder_003-g", + "domain": "CDC_WONDER", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "For a public-health brief reviewing changes in U.S. home births in 2020, identify the months in which the home-birth rate among all mothers rose at least 25% compared with the same month in 2019. For those months, also provide the 2020 home-birth rates and relative changes for non-Hispanic Black and Hispanic mothers. Output a pipe-delimited table in calendar-month order with the fixed header row month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel. Write all values as plain numbers without percent signs.", + "start_url": "https://wonder.cdc.gov/natality-expanded-current.html", + "output_format": "Output a pipe-delimited table in calendar-month order with the fixed header row month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel. Write all values as plain numbers without percent signs.", + "oracle_answer": "month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel\nMay|1.03|1.49|45|0.74|54|0.55|57\nJune|1.04|1.31|26|0.66|20|0.48|30\nJuly|1.03|1.30|26|0.68|42|0.48|30\nAugust|1.02|1.29|26|0.69|50|0.48|26\nSeptember|1.01|1.31|30|0.73|43|0.54|54\nOctober|1.00|1.28|28|0.75|50|0.47|27\nNovember|0.99|1.30|31|0.73|43|0.55|67\nDecember|0.92|1.28|39|0.80|63|0.53|61", + "metadata": { + "State-Gated Retrieval": [ + "Compare the home-birth rates for all mothers in 2019 and 2020 by calendar month, retaining only months where the 2020 rate increased at least 25% relative to the same month in 2019.", + "The home-birth numerator must use the full home category, not Home intended alone.", + "For those qualifying months, also retrieve the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, along with their relative changes from the same month in 2019." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Monthly natality queries yield the 2019 vs 2020 home-birth rates for all mothers and the candidate month set.", + "Follow-up race/ethnicity queries yield the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, plus their same-month changes versus 2019.", + "Final rows are produced only after qualifying months are determined from rate growth, and the resulting month set is reused for both subgroup backfill chains." + ], + "control_dependency": [ + "Month selection must be based on relative rate increase rather than counts alone.", + "The home-birth numerator must use Residence or an equivalent full-home measure rather than Home intended alone before downstream subgroup queries run.", + "Subgroup columns must be generated from the resulting month set rather than appended to earlier rows." + ], + "freeze": { + "historical_window": "2019 and 2020 U.S. natality monthly home-birth rates for all mothers, non-Hispanic Black mothers, and Hispanic mothers." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Compare the home-birth rates for all mothers in 2019 and 2020 by calendar month, retaining only months where the 2020 rate increased at least 25% relative to the same month in 2019.", + "The home-birth numerator must use the full home category, not Home intended alone.", + "For those qualifying months, also retrieve the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, along with their relative changes from the same month in 2019." + ], + "exclusion_conditions": [ + "Exclude month-row sets that misinterpret \"rate increase of at least 25%\" as \"count increase of at least 25%.\"", + "Exclude results that use only the Home intended category instead of the full home numerator.", + "Exclude results that append subgroup columns based on an incorrect month set." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row `month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel`", + "schema": [ + "month", + "all_2019", + "all_2020", + "all_rel", + "black_2020", + "black_rel", + "hispanic_2020", + "hispanic_rel" + ], + "month": "use the English month name and keep calendar order", + "numeric_fields": "all numeric outputs are plain numbers without a percent sign", + "relative_change_fields": "all_rel, black_rel, and hispanic_rel are emitted as integer percentages without the `%` character" + } + } +} diff --git a/data_en/goal/wonder_002-g.json b/data_en/goal/wonder_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..04caad6a0b5bef5b0df9cdbe82519c3193d6ac6d --- /dev/null +++ b/data_en/goal/wonder_002-g.json @@ -0,0 +1,64 @@ +{ + "task_id": "wonder_004-g", + "domain": "CDC_WONDER", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "From the 2021 U.S. infant mortality statistics by mother's race and Hispanic origin, identify all groups that are reported separately, have an infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death. For each qualifying group, provide the infant mortality rate, neonatal mortality rate (under 28 days), postneonatal mortality rate (28 days and older), the group's leading cause of death, the cause-specific rate, and the rank of that cause among all infant causes. Output a multi-row pipe-delimited table sorted by infant mortality rate descending, using the format: group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank.", + "start_url": "https://wonder.cdc.gov/lbd-current-expanded.html", + "output_format": "Output a multi-row pipe-delimited table sorted by infant mortality rate descending, using the format: group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank.", + "oracle_answer": "group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank\nnon-Hispanic Black|10.55|6.35|4.19|Short gestation and low birth weight|196.4|2\nnon-Hispanic American Indian or Alaska Native|7.46|3.83|3.67|Congenital malformations|134.0|1\nPuerto Rican|6.05|3.93|2.13|Short gestation and low birth weight|108.9|2", + "metadata": { + "State-Gated Retrieval": [ + "Retain only groups that are reported separately in the 2021 U.S. infant mortality statistics, have an infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death.", + "For each qualifying group, provide the infant rate, neonatal rate, postneonatal rate, top cause, cause rate, and the rank of that cause among all infant causes.", + "The leading cause must be determined by a group-level leading-cause query and verified using notes/reliability flags." + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Infant-mortality queries yield group-level overall, neonatal, and postneonatal rates for reportable mother race/Hispanic-origin groups.", + "Leading-cause queries and reliability notes yield each eligible group's top cause, cause-specific rate, and U.S. rank.", + "Final rows are produced only after the eligible-group set is rebuilt using both overall-rate and cause-specific-identifiability criteria." + ], + "control_dependency": [ + "Groups above the U.S. overall rate cannot be accepted until cause-specific reliability checks are run, which removes NHOPI.", + "Leading cause must be queried at the group level rather than inherited from an all-infants cause table.", + "The cause-rate multiplier must be defined as per 100,000 live births before downstream ranking/output." + ], + "freeze": { + "historical_window": "2021 U.S. infant mortality by mother race and Hispanic origin, including the group-level leading-cause tables and reliability notes." + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "Retain only groups that are reported separately in the 2021 U.S. infant mortality statistics, have an infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death.", + "For each qualifying group, provide the infant rate, neonatal rate, postneonatal rate, top cause, cause rate, and the rank of that cause among all infant causes.", + "The leading cause must be determined by a group-level leading-cause query and verified using notes/reliability flags." + ], + "exclusion_conditions": [ + "Exclude groups that, despite having an infant mortality rate above the U.S. overall rate, cannot provide a clearly identifiable leading cause due to cause-specific reliability issues.", + "Exclude results that inherit the top cause only from the all-infants cause table without performing a group-level leading-cause query.", + "Exclude results where the cause rate uses an incorrect rate multiplier and is not read per 100,000 live births." + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row `group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank`", + "schema": [ + "group", + "infant_rate", + "neonatal_rate", + "postneonatal_rate", + "top_cause", + "cause_rate", + "us_rank" + ], + "sorting_or_selection": "infant_rate descending", + "rate_fields": "infant_rate, neonatal_rate, and postneonatal_rate are per 1,000 live births; cause_rate is per 100,000 live births, but all four are emitted as plain numbers without unit text", + "top_cause": "emit the short cause label used in the oracle, not an expanded prose description", + "us_rank": "emit the integer rank of that same cause in the overall infant leading-cause list" + } + } +} diff --git a/data_zh/constraint/arxiv_001.json b/data_zh/constraint/arxiv_001.json new file mode 100644 index 0000000000000000000000000000000000000000..cad56d8b33bd013299ead13dcd5a61b2302b674d --- /dev/null +++ b/data_zh/constraint/arxiv_001.json @@ -0,0 +1,94 @@ +{ + "task_id": "arxiv_001", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "我在整理 2019–2021 年 arXiv 上 dataset distillation 和 dataset condensation 这条研究线的论文脉络，想找出那些讨论如何用少量合成训练数据替代大规模训练集的机器学习论文。请在 2019–2021 年的 arXiv 记录中，同时检索 dataset distillation 和 dataset condensation 两组表述，只保留主分类确为 Machine Learning 的条目，不纳入仅被其他主分类论文交叉列入的记录；再从中筛出那些在首版提交后的下一自然年里确实更新过、且当前 arXiv 记录仍能直接看出后续发表去向的论文。最后，请按 v1 submitted 升序输出表格，列为 arXiv ID、term family、cue location、v1 submitted、first next-year version、date of that version、primary category、publication-trail source、current publication clue；若无则输出 NONE。", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "最后，请按 v1 submitted 升序输出表格，列为 arXiv ID、term family、cue location、v1 submitted、first next-year version、date of that version、primary category、publication-trail source、current publication clue；若无则输出 NONE。", + "oracle_answer": "arXiv ID|term family|cue location|v1 submitted|first next-year version|date of that version|primary category|publication-trail source|current publication clue\n1910.02551|Distillation|Title|2019-10-06|v3|2020-05-05|cs.LG|Related DOI|10.1109/IJCNN52387.2021.9533769\n2011.00050|Distillation|Abstract-only|2020-10-30|v2|2021-03-02|cs.LG|Comments|Accepted to ICLR 2021\n2107.13034|Distillation|Title|2021-07-27|v3|2022-01-17|cs.LG|Comments|NeurIPS 2021\n2110.04181|Condensation|Title|2021-10-08|v2|2022-04-21|cs.LG|Journal reference|Proceedings of the IEEE/CVF Winter Conference on Applications of Computer Vision 2023 (WACV)", + "metadata": { + "State-Gated Retrieval": [ + "只纳入 arXiv 记录中 v1 submitted 落在 2019-01-01 至 2021-12-31 的论文。", + "题名或摘要必须明确使用 dataset distillation 或 dataset condensation 家族表述，并且语义指向用少量合成训练数据替代大规模训练集。", + "当前主分类必须是 cs.LG，不纳入仅被其他主分类论文交叉列入 Machine Learning 的记录。", + "必须在首版提交后的下一自然年里确实更新过版本，并且当前记录仍能直接看出后续发表去向。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "root searches yield candidate arXiv IDs", + "each candidate abstract page yields primary category, v1 date, first next-year version, cue location, and publication-trail source", + "answer rows are produced only after deduplication and detail-page validation" + ], + "control_dependency": [ + "records must be filtered by original submission year, with per-record validation that a next-natural-year version exists", + "cross-listed-only hits must be excluded, and the current primary category must be validated on abstract pages", + "searches must cover both Title and Abstract because valid distillation hits can appear only in the abstract", + "topic matches without current publication trail still fail until Comments / Journal reference / Related DOI validation is added at detail depth" + ], + "freeze": { + "historical_window": "v1 year in {2019, 2020, 2021}" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只纳入 arXiv 记录中 v1 submitted 落在 2019-01-01 至 2021-12-31 的论文。", + "题名或摘要必须明确使用 dataset distillation 或 dataset condensation 家族表述，并且语义指向用少量合成训练数据替代大规模训练集。", + "当前主分类必须是 cs.LG，不纳入仅被其他主分类论文交叉列入 Machine Learning 的记录。", + "必须在首版提交后的下一自然年里确实更新过版本，并且当前记录仍能直接看出后续发表去向。" + ], + "exclusion_conditions": [ + "排除当前主分类不是 cs.LG、只是 cross-list 到 cs.LG 的记录。", + "排除题名或摘要出现 distillation / condensation 字样，但不对应数据集蒸馏或数据集凝缩研究线的记录。", + "排除没有 next-natural-year 版本更新、或当前记录中没有可直接读取的发表线索的记录。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "term family", + "cue location", + "v1 submitted", + "first next-year version", + "date of that version", + "primary category", + "publication-trail source", + "current publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "term_family_extraction": { + "allowed_families": [ + "Distillation", + "Condensation" + ], + "tie_break": "if both families appear, prefer the title hit; if both appear only in the abstract, keep the first abstract occurrence" + }, + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_trail_source": [ + "Comments", + "Journal reference", + "Related DOI" + ], + "current_publication_clue": "keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue", + "sorting_or_selection": { + "primary": "v1 submitted ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all four corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the abstract page, current browse context, and publication-trail fields are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_zh/constraint/arxiv_002.json b/data_zh/constraint/arxiv_002.json new file mode 100644 index 0000000000000000000000000000000000000000..1e17c3509280346f955b7c3d6ca553e602a7c28b --- /dev/null +++ b/data_zh/constraint/arxiv_002.json @@ -0,0 +1,88 @@ +{ + "task_id": "arxiv_002", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 10, + "instruction": "我在整理一份 2022 年大型语言模型推理提示研究的文献阅读清单，想找出首版提交于 2022 年、并明确围绕 chain-of-thought 或 self-consistency 推理方法展开的 arXiv 论文。请从首版提交时间为 2022 年的 arXiv 记录入手，先查看题名和摘要中是否明确出现 chain-of-thought 或 self-consistency 相关线索；再只保留主分类为 Computation and Language 的论文，不纳入仅由其他主分类交叉列入的记录。随后，核对这些论文是否在 2023 年确实更新过版本，并确认当前 arXiv 记录的备注中能够直接看出后续发表信息。最后，请按每篇论文在 2023 年最早更新版本的日期升序输出表格，列为 arXiv ID、cue family、cue location、v1 submitted、first 2023 version、date of that version、primary category、publication clue；若无符合项，输出 NONE。", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "最后，请按每篇论文在 2023 年最早更新版本的日期升序输出表格，列为 arXiv ID、cue family、cue location、v1 submitted、first 2023 version、date of that version、primary category、publication clue；若无符合项，输出 NONE。", + "oracle_answer": "arXiv ID|cue family|cue location|v1 submitted|first 2023 version|date of that version|primary category|publication clue\n2210.01240|Chain-of-thought|Title + Abstract|2022-10-03|v2|2023-01-25|cs.CL|Published as a conference paper at ICLR 2023\n2205.11916|Chain-of-thought|Abstract-only|2022-05-24|v4|2023-01-29|cs.CL|Accepted to NeurIPS2022\n2203.11171|Self-consistency; Chain-of-thought|Title + Abstract|2022-03-21|v4|2023-03-07|cs.CL|Published at ICLR 2023; camera ready version at ICLR 2023\n2210.03629|Chain-of-thought|Abstract-only|2022-10-06|v3|2023-03-10|cs.CL|v3 is the ICLR camera ready version\n2210.03350|Chain-of-thought|Abstract-only|2022-10-07|v2|2023-05-23|cs.CL|To appear at Findings of EMNLP 2023\n2212.10001|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-01|cs.CL|ACL-23 Camera Ready\n2212.08061|Chain-of-thought|Abstract-only|2022-12-15|v2|2023-06-04|cs.CL|ACL 2023 Main Conference\n2212.10071|Chain-of-thought|Abstract-only|2022-12-20|v2|2023-06-13|cs.CL|ACL 2023 camera-ready\n2212.10509|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-23|cs.CL|ACL'23 Camera Ready\n2211.12588|Chain-of-thought; Self-consistency|Abstract-only|2022-11-22|v4|2023-10-23|cs.CL|Published at TMLR 2023", + "metadata": { + "State-Gated Retrieval": [ + "只纳入 v1 submitted 在 2022 年内的 arXiv 论文。", + "题名或摘要中必须明确出现 chain-of-thought 或 self-consistency 相关线索。", + "当前主分类必须是 cs.CL，不纳入仅由其他主分类交叉列入的记录。", + "必须在 2023 年确实更新过版本，且当前备注中能够直接看出后续发表信息。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "root searches yield candidate arXiv IDs", + "each candidate abstract page yields primary category, v1 date, first 2023 version, comments/publication clue", + "answer rows are produced only after deduplication and detail-page validation" + ], + "control_dependency": [ + "searches must cover both Title and Abstract fields because valid rows can appear only in the abstract", + "cross-listed hits whose primary category is not cs.CL must be excluded, and the primary category must be validated at detail depth", + "topic-matched hits must be validated against a current Comments publication clue before they can be accepted", + "2023 candidates must be identified by original submission year and full version-history checks, rather than by latest-date proxies" + ], + "freeze": { + "historical_window": "v1 submitted in 2022; version-history event in 2023" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只纳入 v1 submitted 在 2022 年内的 arXiv 论文。", + "题名或摘要中必须明确出现 chain-of-thought 或 self-consistency 相关线索。", + "当前主分类必须是 cs.CL，不纳入仅由其他主分类交叉列入的记录。", + "必须在 2023 年确实更新过版本，且当前备注中能够直接看出后续发表信息。" + ], + "exclusion_conditions": [ + "排除当前主分类不是 cs.CL 的记录，即使它们出现在相关检索结果中。", + "排除只出现模糊缩写或弱相关提示、但题名和摘要中没有明确 CoT / self-consistency 语义的记录。", + "排除没有 2023 版本更新、或当前记录中没有直接发表线索的记录。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "cue family", + "cue location", + "v1 submitted", + "first 2023 version", + "date of that version", + "primary category", + "publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "cue_family": [ + "Chain-of-thought", + "Self-consistency" + ], + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_clue": { + "source": "Comments field only", + "extraction": "keep the shortest phrase that still preserves the current publication-status clue" + }, + "sorting_or_selection": { + "primary": "date of the earliest 2023 version ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the current browse context, Comments field, and full Submission history are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_zh/constraint/arxiv_003.json b/data_zh/constraint/arxiv_003.json new file mode 100644 index 0000000000000000000000000000000000000000..e2d62b90d3a4c627bdd9433991bdd5d725836fd5 --- /dev/null +++ b/data_zh/constraint/arxiv_003.json @@ -0,0 +1,89 @@ +{ + "task_id": "arxiv_003", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "1\n我在整理一份早期视觉 Transformer 研究的文献阅读清单，想找出首版提交于 2020 年第四季度、并在题名或摘要中明确使用视觉或图像领域 Transformer 表述的 arXiv 论文。请先从 arXiv 记录中筛选首版提交时间在 2020 年第四季度的论文，再核对其题名或摘要中是否明确出现与视觉或图像 Transformer 相关的表述；同时只保留主分类为 Computer Vision and Pattern Recognition 的论文。随后，确认这些论文是否在 2021 年确实更新过版本，并检查当前 arXiv 记录中是否能直接看出后续发表信息。最后，请按每篇论文在 2021 年最早更新版本的日期升序输出表格，列为 arXiv ID、cue family、cue location、v1 submitted、first 2021 version、date of that version、primary category、publication-trail source、current publication clue；若无符合项，输出 NONE。\n2\n我在整理一份早期视觉 Transformer 研究的文献阅读清单，想在首版提交于 2020 年第四季度的 arXiv 论文中，筛选出题名或摘要明确使用视觉或图像 Transformer 相关表述、且主分类为 Computer Vision and Pattern Recognition 的早期视觉 Transformer 论文。候选论文还需满足：在 2021 年确实发布过更新版本，且当前 arXiv 记录中仍能直接识别其后续发表去向。请按每篇论文在 2021 年最早更新版本的日期升序输出表格，列为 arXiv ID、cue family、cue location、v1 submitted、first 2021 version、date of that version、primary category、publication-trail source、current publication clue；如无符合条件的条目，输出 NONE。\n\n我在整理早期视觉 Transformer 文献的历史阅读表，想找出首版确实提交在 2020 年最后一个季度、真正归在 Computer Vision and Pattern Recognition、题名或摘要明确出现视觉或图像领域 Transformer 叫法、在 2021 年确实更新过版本、并且当前 arXiv 记录能直接看出后续发表去向的论文。请按每篇论文在 2021 年最早更新版本的日期升序输出表格，列为 arXiv ID、cue family、cue location、v1 submitted、first 2021 version、date of that version、primary category、publication-trail source、current publication clue；若无符合项，输出 NONE。", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "请按每篇论文在 2021 年最早更新版本的日期升序输出表格，列为 arXiv ID、cue family、cue location、v1 submitted、first 2021 version、date of that version、primary category、publication-trail source、current publication clue；若无符合项，输出 NONE。", + "oracle_answer": "arXiv ID|cue family|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication-trail source|current publication clue\n2101.01097|Vision Transformer|Abstract-only|2020-12-30|v2|2021-01-08|cs.CV|Journal reference|IEEE Int. Conf. on Image Processing (ICIP) 2021\n2012.12556|Visual Transformer; Vision Transformer|Title + Abstract|2020-12-23|v2|2021-01-15|cs.CV|Comments; Related DOI|Accepted by TPAMI 2022; 10.1109/TPAMI.2022.3152247\n2012.00364|Image Processing Transformer|Title + Abstract|2020-12-01|v3|2021-05-28|cs.CV|Comments|CVPR 2021\n2011.08019|Vision Transformer|Title + Abstract|2020-11-16|v2|2021-06-02|cs.CV|Comments|Accepted for Publication in IJCB2021\n2010.11929|Vision Transformer|Abstract-only|2020-10-22|v2|2021-06-03|cs.CV|Comments|ICLR camera-ready version", + "metadata": { + "State-Gated Retrieval": [ + "只纳入 v1 submitted 落在 2020 年第四季度的 arXiv 论文。", + "题名或摘要中必须明确出现视觉或图像领域 Transformer 相关表述。", + "当前主分类必须是 cs.CV。", + "必须在 2021 年确实更新过版本，且当前记录中仍能直接识别后续发表去向。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "root searches yield candidate arXiv IDs", + "candidate abstract pages yield v1 submitted date, first 2021 version, primary category, cue location, and publication-trail source", + "answer rows depend on deduplication plus detail-page validation" + ], + "control_dependency": [ + "searches must cover both Title and Abstract because valid positives can appear only in the abstract", + "candidate eligibility must be determined by the original-submission date window rather than by arXiv-ID or announcement intuition", + "candidate filtering must use full Submission-history validation rather than most-recent-submission filtering", + "searches must use the broader semantic cue state rather than a ViT-only entry point, because ViT-only hits can be false positives", + "publication-trail false positives still require Comments / Journal reference / Related DOI validation before final inclusion" + ], + "freeze": { + "historical_window": "v1 submitted from 2020-10-01 through 2020-12-31; version-history event in 2021" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只纳入 v1 submitted 落在 2020 年第四季度的 arXiv 论文。", + "题名或摘要中必须明确出现视觉或图像领域 Transformer 相关表述。", + "当前主分类必须是 cs.CV。", + "必须在 2021 年确实更新过版本，且当前记录中仍能直接识别后续发表去向。" + ], + "exclusion_conditions": [ + "排除当前主分类不是 cs.CV、只是交叉列入的记录。", + "排除只出现 Transformer / ViT 等弱线索、但题名和摘要中没有明确视觉或图像领域表述的记录。", + "排除没有 2021 年版本更新、或当前记录中没有直接发表线索的记录。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "cue family", + "cue location", + "v1 submitted", + "first 2021 version", + "date of that version", + "primary category", + "publication-trail source", + "current publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "cue_family_extraction": "record every qualifying family actually present and join multiple families with `; ` in the emitted field", + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_trail_source": [ + "Comments", + "Journal reference", + "Related DOI" + ], + "current_publication_clue": "keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue", + "sorting_or_selection": { + "primary": "date of the earliest 2021 version ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the abstract page, current browse context, Comments field, Journal reference, Related DOI, and full Submission history are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_zh/constraint/arxiv_004.json b/data_zh/constraint/arxiv_004.json new file mode 100644 index 0000000000000000000000000000000000000000..7e75df1eb1d9d0a07034325956ec9ac08c217eca --- /dev/null +++ b/data_zh/constraint/arxiv_004.json @@ -0,0 +1,84 @@ +{ + "task_id": "arxiv_004", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "我在整理一份 2020 年上半年可认证鲁棒性防御研究的文献阅读清单，想找出首版提交于 2020 年 1–6 月、并在题名或摘要中明确围绕平滑分类器、随机平滑及其变体、后门或投毒场景下的可认证防御，或 partition aggregation 展开的 arXiv 论文。请先从首版提交时间在 2020 年 1–6 月的 arXiv 记录入手，核对题名或摘要中是否明确出现 randomized smoothing、de-randomized smoothing、transformation-specific smoothing、smoothed classifiers、backdoor/poisoning 的可认证防御，或 partition aggregation 等研究线索；再只保留主分类为 Machine Learning 的论文，不纳入仅由其他主分类交叉列入的记录。随后确认这些论文是否在 2021 年确实更新过版本，并检查当前 arXiv 记录中是否能直接看出正式发表或录用信息。最后，请按每篇论文在 2021 年最早更新版本的日期升序输出表格，列为 arXiv ID、defense family、threat/topic cue、cue location、v1 submitted、first 2021 version、date of that version、primary category、publication clue；若无符合项，输出 NONE。", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "最后，请按每篇论文在 2021 年最早更新版本的日期升序输出表格，列为 arXiv ID、defense family、threat/topic cue、cue location、v1 submitted、first 2021 version、date of that version、primary category、publication clue；若无符合项，输出 NONE。", + "oracle_answer": "arXiv ID|defense family|threat/topic cue|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication clue\n2002.10733|De-randomized smoothing; Randomized smoothing|patch attacks|Title + Abstract|2020-02-25|v3|2021-01-08|cs.LG|NeurIPS 2020\n2006.04062|Smoothed classifiers; Randomized smoothing|certified L2 robustness|Title + Abstract|2020-06-07|v4|2021-01-08|cs.LG|NeurIPS 2020\n2003.08904|RAB; Randomized smoothing|backdoor attacks|Title + Abstract|2020-03-19|v4|2021-02-26|cs.LG|IEEE Symposium on Security and Privacy 2023\n2006.14768|Deep Partition Aggregation|general poisoning attacks; label-flipping poisoning attacks|Title + Abstract|2020-06-26|v2|2021-03-18|cs.LG|ICLR 2021\n2002.12398|Transformation-specific smoothing; Randomized smoothing|semantic transformations|Title + Abstract|2020-02-27|v4|2021-09-17|cs.LG|2021 ACM SIGSAC Conference on Computer and Communications Security (CCS '21)", + "metadata": { + "State-Gated Retrieval": [ + "只纳入 v1 submitted 落在 2020-01-01 至 2020-06-30 的 arXiv 论文。", + "题名或摘要中必须明确围绕 randomized smoothing、de-randomized smoothing、transformation-specific smoothing、smoothed classifiers、后门或投毒场景下的可认证防御，或 partition aggregation 展开。", + "当前主分类必须是 cs.LG。", + "必须在 2021 年确实更新过版本，并且当前记录中能够直接看出正式发表或录用信息。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "root searches yield candidate arXiv IDs", + "candidate abstract pages yield v1 date, primary category, full Submission history, cue location, and current publication clue", + "final rows depend on deduplication plus detail-page validation" + ], + "control_dependency": [ + "candidate filtering must use the original-submission window together with full 2021 version-history validation, because valid rows can have later newest versions", + "cross-listed hits whose primary category is not the target category must be excluded, with category validation on detail pages", + "searches must cover the broader certified-defense family, including partition-aggregation and backdoor/poisoning variants, rather than smoothing-only entries", + "topic+venue hits must be confirmed by detail-history validation that a 2021 version actually exists" + ], + "freeze": { + "historical_window": "v1 submitted from 2020-01-01 through 2020-06-30; version-history event in 2021" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只纳入 v1 submitted 落在 2020-01-01 至 2020-06-30 的 arXiv 论文。", + "题名或摘要中必须明确围绕 randomized smoothing、de-randomized smoothing、transformation-specific smoothing、smoothed classifiers、后门或投毒场景下的可认证防御，或 partition aggregation 展开。", + "当前主分类必须是 cs.LG。", + "必须在 2021 年确实更新过版本，并且当前记录中能够直接看出正式发表或录用信息。" + ], + "exclusion_conditions": [ + "排除当前主分类不是 cs.LG 的记录，即使语义相关。", + "排除只与鲁棒性、防御、backdoor/poisoning 泛相关，但不满足题目要求的可认证防御语义的记录。", + "排除没有 2021 年版本更新或没有当前发表线索的记录。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "defense family", + "threat/topic cue", + "cue location", + "v1 submitted", + "first 2021 version", + "date of that version", + "primary category", + "publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "defense_family_extraction": "record every qualifying defense family actually present and join multiple families with `; ` in the emitted field", + "threat_topic_cue": "keep the shortest qualifying threat or topic cue that justifies inclusion", + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_clue": "keep the shortest phrase that still preserves venue or publication-status information", + "sorting_or_selection": { + "primary": "date of the earliest 2021 version ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the abstract page, current browse context, Comments field, and full Submission history are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_zh/constraint/census_001.json b/data_zh/constraint/census_001.json new file mode 100644 index 0000000000000000000000000000000000000000..83bea3ed284e21e5f843a3649f49b6a28a35353f --- /dev/null +++ b/data_zh/constraint/census_001.json @@ -0,0 +1,68 @@ +{ + "task_id": "census_001", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 20, + "instruction": "我想用 2014–2018 年 American Community Survey 五年估计数据找出互联网接入不足、老年独居比例较高、交通条件较弱且收入偏低的县。请以这份数据中的北卡罗来纳州县级数据为范围，并使用同一份数据里的 North Carolina 全州值作为比较基准；先筛出无互联网接入住户不少于 4,000 户的县，再保留同时满足以下条件的县：无互联网接入住户占比高于全州；户主为 65 岁及以上且独居的住户占全部住户的比重高于全州；无车住户占比高于全州；家庭收入中位数低于全州。最后，请将所有符合条件的县按县名字母顺序输出为一行；每个县写成 County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome，县与县之间用英文逗号分隔。百分比字段保留三位小数，不加百分号。", + "start_url": "https://www.census.gov/data.html", + "output_format": "请将所有符合条件的县按县名字母顺序输出为一行；每个县写成 County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome，县与县之间用英文逗号分隔。百分比字段保留三位小数，不加百分号。", + "oracle_answer": "Beaufort County|5988|30.986|16.083|7.664|43688,Bladen County|4194|30.026|13.681|10.417|32378,Cleveland County|11599|31.449|12.469|7.825|40393,Columbus County|7371|33.045|15.148|7.958|36398,Duplin County|7574|34.773|14.370|7.424|38850,Edgecombe County|7454|34.879|13.720|11.225|35516,Halifax County|7575|35.873|14.657|11.565|34251,Lenoir County|4923|21.292|15.614|11.699|38387,Nash County|8617|23.467|13.597|7.917|48362,Richmond County|5193|28.001|13.706|9.269|36091,Robeson County|19814|43.103|11.312|9.854|33679,Rockingham County|9938|26.714|14.166|7.164|42490,Rutherford County|7583|28.783|16.033|6.335|40347,Sampson County|8216|34.907|14.088|7.686|39068,Scotland County|4971|37.909|13.910|11.470|35617,Surry County|7595|26.203|13.762|6.779|41068,Vance County|5131|30.444|12.347|11.600|37282,Wayne County|9709|20.163|11.742|8.456|42192,Wilkes County|7046|24.849|14.773|5.992|40829,Wilson County|7652|23.817|13.322|9.540|42850", + "metadata": { + "State-Gated Retrieval": [ + "只使用 2014-2018 American Community Survey 5-year estimates 的 North Carolina 县级数据，并使用同一发布中的 North Carolina 全州值作为比较基准。", + "只保留无互联网接入住户不少于 4,000 户，且无互联网接入住户占比、65 岁及以上独居户主占比、无车住户占比均高于全州，同时家庭收入中位数低于全州的县。", + "最终结果按县名字母顺序输出，并保留题目要求的 6 个字段。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2014-2018 ACS 5-year product and North Carolina county geography yield the full county candidate set plus the statewide baseline row", + "the relevant ACS tables yield no-internet households, senior-living-alone share, no-vehicle share, and median household income for each county and the state baseline", + "final rows are produced only after the 5-year product/geography setup is fixed consistently and the full county filtering chain is executed from B28002 through the downstream filters" + ], + "control_dependency": [ + "the 2018 ACS 5-year Detailed Tables product must be used instead of the 2018 ACS 1-year product", + "county coverage must be established under one consistent product-and-geography setup rather than by piecemeal fixes within the current table", + "all downstream county comparisons must use the same 5-year statewide baseline and the same all-counties geography" + ], + "freeze": { + "historical_window": "2014-2018 American Community Survey 5-year estimates for North Carolina counties, using the North Carolina statewide row from the same release as the comparison baseline" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只使用 2014-2018 American Community Survey 5-year estimates 的 North Carolina 县级数据，并使用同一发布中的 North Carolina 全州值作为比较基准。", + "只保留无互联网接入住户不少于 4,000 户，且无互联网接入住户占比、65 岁及以上独居户主占比、无车住户占比均高于全州，同时家庭收入中位数低于全州的县。", + "最终结果按县名字母顺序输出，并保留题目要求的 6 个字段。" + ], + "exclusion_conditions": [ + "排除误用 2018 ACS 1-Year Estimates Detailed Tables 或其他非 2014-2018 五年发布的数据。", + "排除没有使用同一发布中的 North Carolina 全州行作为比较基准的结果。", + "排除任一阈值或全州比较条件不满足的县。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "NoInternetHH", + "NoInternetRatePct", + "SeniorLivingAloneSharePct", + "NoVehicleRatePct", + "MedianIncome" + ], + "county": "use the county display name including the word `County` and excluding a trailing state suffix", + "dedup_key": "county FIPS / GEOID", + "percentage_fields": "all percentage fields are plain numbers with exactly three decimal places and no percent sign", + "numeric_fields": "household counts and median income are emitted as plain integers without commas", + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "the North Carolina statewide threshold is fixed once from the designated table", + "all 100 North Carolina counties are covered under the same table/product settings", + "every surviving county is validated against all four required tables before emission" + ] + } + } +} diff --git a/data_zh/constraint/census_002.json b/data_zh/constraint/census_002.json new file mode 100644 index 0000000000000000000000000000000000000000..94612e5986cfca49219faa1f0cdd2ae70ad6b843 --- /dev/null +++ b/data_zh/constraint/census_002.json @@ -0,0 +1,80 @@ +{ + "task_id": "census_002", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "我想基于 2015–2019 年 American Community Survey 五年估计数据，在新墨西哥州各县中筛选出同时具有较大租户规模、明显语言障碍、网络接入不足、交通不便、收入偏低和租住压力的县。请以这份数据中的新墨西哥州县级数据为范围，并使用同一份数据里的 New Mexico 全州值作为比较基准；先筛出至少有 2,500 个租房住户、且至少有 500 个英语能力有限住户的县，再保留同时满足以下条件的县：英语能力有限住户占比高于全州；无互联网接入住户占比高于全州；无车住户占比高于全州；家庭收入中位数低于全州。随后核对租房住户的住房压力指标，只保留满足以下至少一项的县：租房住户中租金收入比达到 35% 及以上的占比高于全州，或租房住户中每房间人数大于 1 的占比高于全州；如果两项都满足，需一并标出。最后，请将所有符合条件的县按县名字母顺序输出为一行；每个县写成 County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath，县与县之间用英文逗号分隔；其中 StressPath 只能写 RENT、CROWD 或 BOTH。百分比字段保留三位小数，不加百分号。", + "start_url": "https://data.census.gov/advanced", + "output_format": "请将所有符合条件的县按县名字母顺序输出为一行；每个县写成 County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath，县与县之间用英文逗号分隔；其中 StressPath 只能写 RENT、CROWD 或 BOTH。百分比字段保留三位小数，不加百分号。", + "oracle_answer": "Doña Ana County|28729|7883|10.127|22.612|6.079|44.172|6.391|40973|BOTH,Luna County|3482|1109|12.455|34.030|8.165|42.700|1.407|29360|RENT,McKinley County|6090|1610|7.688|50.587|10.978|27.568|16.256|33834|CROWD,San Miguel County|3443|1200|10.337|38.470|7.684|47.376|2.440|30946|RENT,Taos County|2854|652|5.387|28.844|5.726|48.823|4.555|38329|RENT", + "metadata": { + "State-Gated Retrieval": [ + "只使用 2015-2019 American Community Survey 5-year estimates 的 New Mexico 县级数据，并使用同一发布中的 New Mexico 全州值作为比较基准。", + "候选县必须至少有 2,500 个租房住户、至少 500 个英语能力有限住户，并且 LEP 占比、无互联网占比、无车占比均高于全州，同时家庭收入中位数低于全州。", + "LEPHH 必须由 C16002 中全部四个 limited-English 语言分组合并计算；最后只保留 Severe Rent Burden 或 Crowded Renter 至少一项高于全州的县，并按规则写出 StressPath。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2015-2019 ACS 5-year county geography yields New Mexico county candidates and the statewide baseline row", + "C16002 and the downstream housing/income tables yield LEPHH, LEP share, no-internet share, no-vehicle share, severe rent burden, crowded-renter share, and median income for counties and the state baseline", + "final rows are produced only after the LEPHH numerator is computed from all four limited-English language groups and the downstream stress-path filters are applied" + ], + "control_dependency": [ + "the LEPHH numerator must be computed from all four limited-English language groups in C16002 rather than from Spanish-only counts", + "county eligibility and StressPath labels must be determined from the LEPHH measure and statewide LEP baseline defined under that full four-group calculation", + "the RENT / CROWD / BOTH classification must be determined by evaluating the same county set against both downstream housing-stress branches" + ], + "freeze": { + "historical_window": "2015-2019 American Community Survey 5-year estimates for New Mexico counties, using the New Mexico statewide row from the same release as the comparison baseline" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只使用 2015-2019 American Community Survey 5-year estimates 的 New Mexico 县级数据，并使用同一发布中的 New Mexico 全州值作为比较基准。", + "候选县必须至少有 2,500 个租房住户、至少 500 个英语能力有限住户，并且 LEP 占比、无互联网占比、无车占比均高于全州，同时家庭收入中位数低于全州。", + "LEPHH 必须由 C16002 中全部四个 limited-English 语言分组合并计算；最后只保留 Severe Rent Burden 或 Crowded Renter 至少一项高于全州的县，并按规则写出 StressPath。" + ], + "exclusion_conditions": [ + "排除把西班牙语 limited-English 住户单独当作全部 LEPHH 的结果。", + "排除未使用同一发布中全州基准、或未重算 LEPHH/LEPSharePct/LEPShare_state 的结果。", + "排除不满足 RENT、CROWD 或 BOTH 最终压力路径条件的县。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "RenterHH", + "LEPHH", + "LEPSharePct", + "NoInternetPct", + "NoVehiclePct", + "SevereRentBurdenPct", + "CrowdedRenterPct", + "MedianIncome", + "StressPath" + ], + "county": "use the county display name including the word `County` and excluding a trailing state suffix", + "dedup_key": "county FIPS / GEOID", + "LEPHH": "sum the four designated limited-English-proficient renter-household cells before emitting the integer total", + "percentage_fields": "all percentage fields are plain numbers with exactly three decimal places and no percent sign", + "numeric_fields": "household counts and median income are emitted as plain integers without commas", + "StressPath": { + "allowed_values": [ + "RENT", + "CROWD", + "BOTH" + ], + "rule": "emit BOTH only when both the severe-rent-burden and crowded-renter signals survive; otherwise emit the single surviving label" + }, + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "all candidate counties are validated under the same geography and product settings", + "the renter scope and LEP aggregation are checked before the final line is emitted" + ] + } + } +} diff --git a/data_zh/constraint/census_003.json b/data_zh/constraint/census_003.json new file mode 100644 index 0000000000000000000000000000000000000000..61371d127d13c3dfcebbd145c7948ba07afae697 --- /dev/null +++ b/data_zh/constraint/census_003.json @@ -0,0 +1,73 @@ +{ + "task_id": "census_003", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "我在为加州教育部门整理一份疫情前县级筛选名单，用来判断哪些县在学校餐食申请和家长资料年度更新时，不能只依赖英文线上入口，仍需保留纸质材料和线下协助。请以 2013–2017 年 American Community Survey 五年估计中的加州县级数据为范围，并使用同一份数据中的 California 全州值作为比较基准；先筛出 5–17 岁人口不少于 75,000 人的县，再保留 保留 5–17 岁中英语说得 not well 或 not at all的人口不少于 2,000 人、且该占比高于全州的县。随后核对这些县的数字接入和收入条件：无互联网接入住户占比需高于全州，家庭收入中位数需低于全州。最后，在三类线下支持信号中，保留至少两类高于全州的县：无车住户占比、过去 12 个月内所在家庭领取过 SSI、现金公共援助、Food Stamps 或 SNAP 的未成年人占比、租房户中每间房超过 1 人的占比。请将所有符合条件的县按县名字母顺序输出为一行；每个县写成 County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath，县与县之间用英文逗号分隔。SupportPath 只使用 BENEFITS、CROWD、MOBILITY 三个标签：公共援助信号对应 BENEFITS，住房拥挤信号对应 CROWD，无车住户信号对应 MOBILITY；若多个标签同时适用，按 BENEFITS、CROWD、MOBILITY 的固定顺序用加号连接。", + "start_url": "https://data.census.gov/advanced", + "output_format": "请将所有符合条件的县按县名字母顺序输出为一行；每个县写成 County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath，县与县之间用英文逗号分隔。SupportPath 只使用 BENEFITS、CROWD、MOBILITY 三个标签：公共援助信号对应 BENEFITS，住房拥挤信号对应 CROWD，无车住户信号对应 MOBILITY；若多个标签同时适用，按 BENEFITS、CROWD、MOBILITY 的固定顺序用加号连接。", + "oracle_answer": "Fresno County|200205|5127|2.561|20.588|8.686|46.388|13.967|48730|BENEFITS+CROWD+MOBILITY,Kern County|185802|4130|2.223|21.739|7.058|37.285|14.394|50826|BENEFITS+CROWD,Los Angeles County|1641669|37540|2.287|16.338|9.204|27.238|16.741|61015|BENEFITS+CROWD+MOBILITY,Tulare County|104542|2703|2.586|25.738|6.274|49.347|14.535|44871|BENEFITS+CROWD", + "metadata": { + "State-Gated Retrieval": [ + "只使用 2013-2017 American Community Survey 5-year estimates 的 California 县级数据，并使用同一发布中的 California 全州值作为比较基准。", + "只保留 5-17 岁人口不少于 75,000、SchoolAgeLEP 不少于 2,000 且该占比高于全州、无互联网占比高于全州、家庭收入中位数低于全州的县。", + "SchoolAgeLEP 必须由 B16004 中四大语言组的 not well / not at all 八个单元格合计；最终县还需在 Mobility、Benefits、Crowd 三类线下支持信号中至少两类高于全州。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2013-2017 ACS 5-year county geography yields California county candidates and the statewide baseline row", + "B16004 and the downstream access/income/support tables yield SchoolAgeLEP, no-internet share, no-vehicle share, child-benefit share, crowded-renter share, and median income for counties and the statewide baseline", + "final rows are produced only after the SchoolAgeLEP numerator is computed from all eight 1980-target language cells and the downstream support-path branches are applied" + ], + "control_dependency": [ + "the SchoolAgeLEP numerator must be computed from the full eight-cell language set in B16004 rather than from only two Spanish LEP cells", + "county eligibility and SupportPath labels must be determined from the LEP numerator and candidate set defined under that full eight-cell calculation", + "the BENEFITS / CROWD / MOBILITY path labels must be determined by applying all three downstream support branches to the same county set" + ], + "freeze": { + "historical_window": "2013-2017 American Community Survey 5-year estimates for California counties, using the California statewide row from the same release as the comparison baseline" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只使用 2013-2017 American Community Survey 5-year estimates 的 California 县级数据，并使用同一发布中的 California 全州值作为比较基准。", + "只保留 5-17 岁人口不少于 75,000、SchoolAgeLEP 不少于 2,000 且该占比高于全州、无互联网占比高于全州、家庭收入中位数低于全州的县。", + "SchoolAgeLEP 必须由 B16004 中四大语言组的 not well / not at all 八个单元格合计；最终县还需在 Mobility、Benefits、Crowd 三类线下支持信号中至少两类高于全州。" + ], + "exclusion_conditions": [ + "排除只取 Spanish LEP 两行、未合并全部八个目标单元格的结果。", + "排除没有重新跑 B28011、B19013、B08201、B09010、B25014 支路的结果。", + "排除最终 SupportPath 不满足至少两类高于全州的县。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "SchoolAgePop", + "SchoolAgeLEP", + "LEPSharePct", + "NoInternetPct", + "NoVehiclePct", + "ChildBenefitSharePct", + "CrowdedRenterPct", + "MedianIncome", + "SupportPath" + ], + "county": "use the county display name including the word `County` and excluding a trailing state suffix", + "dedup_key": "county FIPS / GEOID", + "SchoolAgeLEP": "sum the eight designated school-age LEP cells before emitting the integer total", + "percentage_fields": "all percentage fields are plain numbers with exactly three decimal places and no percent sign", + "numeric_fields": "population counts and median income are emitted as plain integers without commas", + "SupportPath": "use only BENEFITS, CROWD, and MOBILITY, and when multiple labels apply join them with `+` in the fixed order BENEFITS+CROWD+MOBILITY", + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "all candidate counties are validated under the same geography and product settings", + "the school-age LEP aggregation and all three support-signal gates are checked before the final line is emitted" + ] + } + } +} diff --git a/data_zh/constraint/census_004.json b/data_zh/constraint/census_004.json new file mode 100644 index 0000000000000000000000000000000000000000..f3a3af1463b3215f8a26505a0a933cfee3398e54 --- /dev/null +++ b/data_zh/constraint/census_004.json @@ -0,0 +1,72 @@ +{ + "task_id": "census_004", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 7, + "instruction": "我想基于 2012–2016 年 American Community Survey 五年估计数据，在宾夕法尼亚州各县中筛选出老年人疏散支持需求较高、应在冬季风暴前提前开展线下外展的县。请以 2012–2016 年 American Community Survey 五年估计中的宾夕法尼亚州县级数据为范围，并使用同一份数据里的 Pennsylvania 全州值作为比较基准；先筛出 65 岁及以上人口不少于 15,000 人的县，再保留 65 岁及以上行走困难人口不少于 4,000 人、且该占比高于全州的县。在此基础上，家庭收入中位数还需低于全州。随后核对四类疏散支持障碍，只保留其中至少两类高于全州的县：户主为 65 岁及以上且独居的住户占比、无车住户占比、无车租房户占比、移动式住房占全部住房单元的比重。最后，请将所有符合条件的县按县名字母顺序写成一行；每个县写成 County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath，县与县之间用英文逗号分隔。BarrierPath 只使用 ALONE、MOBILE_HOME、NO_VEHICLE、RENTER_NO_VEHICLE 四个标签；若多个标签同时适用，按 ALONE、MOBILE_HOME、NO_VEHICLE、RENTER_NO_VEHICLE 的固定顺序用加号连接。", + "start_url": "https://www.census.gov/data.html", + "output_format": "请将所有符合条件的县按县名字母顺序写成一行；每个县写成 County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath，县与县之间用英文逗号分隔。BarrierPath 只使用 ALONE、MOBILE_HOME、NO_VEHICLE、RENTER_NO_VEHICLE 四个标签；若多个标签同时适用，按 ALONE、MOBILE_HOME、NO_VEHICLE、RENTER_NO_VEHICLE 的固定顺序用加号连接。", + "oracle_answer": "Blair County|23013|5576|24.230|14.917|9.440|24.316|6.388|44033|ALONE+MOBILE_HOME, Cambria County|27058|6308|23.313|15.243|10.309|26.627|4.070|42917|ALONE+MOBILE_HOME+RENTER_NO_VEHICLE, Fayette County|25186|5886|23.370|14.961|9.302|22.290|10.489|40511|ALONE+MOBILE_HOME, Lycoming County|19486|4311|22.124|12.164|9.257|23.312|6.726|48731|ALONE+MOBILE_HOME, Mercer County|21537|4799|22.283|14.090|9.572|24.413|7.912|45831|ALONE+MOBILE_HOME, Philadelphia County|188185|56935|30.255|11.553|30.954|44.924|0.250|39770|NO_VEHICLE+RENTER_NO_VEHICLE, Schuylkill County|26613|6465|24.293|14.357|9.676|23.652|4.080|46573|ALONE+MOBILE_HOME", + "metadata": { + "State-Gated Retrieval": [ + "只使用 2012-2016 American Community Survey 5-year estimates 的 Pennsylvania 县级数据，并使用同一发布中的 Pennsylvania 全州值作为比较基准。", + "只保留 65 岁及以上人口不少于 15,000、65 岁及以上行走困难人口不少于 4,000 且占比高于全州、并且家庭收入中位数低于全州的县。", + "65+ ambulatory difficulty 必须合并 B18105 中 65-74 / 75+、male / female 的四个目标单元格；最终县还需在 Alone、No Vehicle、Renter No Vehicle、Mobile Home 四类障碍中至少两类高于全州。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "ACS tables B01001 and B18105 yield county senior-population totals and the full 65+ ambulatory-difficulty numerator", + "statewide comparison tables yield Pennsylvania baselines plus county barrier metrics for living alone, no vehicle, renter no vehicle, mobile home, and median income", + "final rows are produced only after the county candidate set is defined from the full ambulatory-difficulty numerator and the downstream six-table filters are applied" + ], + "control_dependency": [ + "the ambulatory-difficulty numerator must include the full 65+ population across 65-74 / 75+ and male / female cells rather than only the 75+ cells", + "downstream county eligibility and barrier labels must be determined from the county candidate set defined under that full ambulatory numerator", + "the at-least-two-barriers test must compare every county metric against the same Pennsylvania statewide baselines from the same ACS release" + ], + "freeze": { + "historical_window": "2012-2016 American Community Survey 5-year estimates for Pennsylvania counties, with Pennsylvania statewide baselines taken from the same release" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只使用 2012-2016 American Community Survey 5-year estimates 的 Pennsylvania 县级数据，并使用同一发布中的 Pennsylvania 全州值作为比较基准。", + "只保留 65 岁及以上人口不少于 15,000、65 岁及以上行走困难人口不少于 4,000 且占比高于全州、并且家庭收入中位数低于全州的县。", + "65+ ambulatory difficulty 必须合并 B18105 中 65-74 / 75+、male / female 的四个目标单元格；最终县还需在 Alone、No Vehicle、Renter No Vehicle、Mobile Home 四类障碍中至少两类高于全州。" + ], + "exclusion_conditions": [ + "排除只取 75 years and over 行走困难单元格并把它误当成全部 65+ 的结果。", + "排除未使用同一发布中 Pennsylvania 全州基准的结果。", + "排除最终 BarrierPath 不满足至少两类障碍高于全州的县。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "SeniorPop", + "AmbulatoryDifficulty65Plus", + "AmbDiffPct", + "SeniorLivingAloneSharePct", + "NoVehiclePct", + "RenterNoVehiclePct", + "MobileHomePct", + "MedianIncome", + "BarrierPath" + ], + "county": "use the county display name including the word `County` and excluding a trailing state suffix", + "dedup_key": "county FIPS / GEOID", + "percentage_fields": "all percentage fields are plain numbers with exactly three decimal places and no percent sign", + "numeric_fields": "population counts and median income are emitted as plain integers without commas", + "BarrierPath": "use only ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE, and when multiple labels apply join them with `+` in the fixed order ALONE+MOBILE_HOME+NO_VEHICLE+RENTER_NO_VEHICLE", + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "all candidate counties are validated under the same geography and product settings", + "the senior ambulatory-difficulty gate and all barrier-signal gates are checked before the final line is emitted" + ] + } + } +} diff --git a/data_zh/constraint/climategov_001.json b/data_zh/constraint/climategov_001.json new file mode 100644 index 0000000000000000000000000000000000000000..066b3f365f3fdce1ebdca6ed5a091b2fc48562e5 --- /dev/null +++ b/data_zh/constraint/climategov_001.json @@ -0,0 +1,66 @@ +{ + "task_id": "climategov_001", + "domain": "NOAA_NCEI_CLIMATE_AT_A_GLANCE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "我想在得克萨斯州南部 (South Texas) 的四个气候分区中进行一项数据筛选，寻找那些在两个较长的时间段内气候保持在接近常态到偏湿润状态，但在1966年3月单月供暖需求依然较低的地区。请将查找范围严格限定在中南部 (South Central)、上海岸 (Upper Coast)、南部 (South) 以及下游河谷 (Lower Valley) 这四个分区，其具体的名称和编号顺序请以官方的得克萨斯州气候分区 (Texas divisional) 页面片段给出的信息为准。\n具体而言，我们需要保留同时满足以下三个特定气候指标的分区：首先，截至1966年2月的前10个月内，帕尔默Z指数距平 (Palmer Z-Index anomaly) 不得低于-0.05；其次，截至1966年12月的前24个月内，帕尔默Z指数距平 (Palmer Z-Index anomaly) 不得低于-0.10；此外，1966年3月单月的采暖度日数 (Heating Degree Days) 实际数值必须低于200°Df。\n在找出所有符合条件的分区后，请按照特定的优先级规则对它们进行排序。优先将1966年2月的10个月Z指数距平与1966年12月的24个月Z指数距平相加，并按此总和从大到小降序排列。如果遇到总和相同的情况，请将1966年3月采暖度日数 (Heating Degree Days) 实际值更小的分区排在前面；若依然存在并列，则让得克萨斯州分区号更小的优先。\n最后，请将处理好的结果整理为单行字符串进行输出，各个匹配项之间使用英文逗号进行连接。每个结果必须严格遵守这样的拼接格式：<得克萨斯州分区号>|<分区名>|<1966年2月10个月Z指数距平的原样文本>|<1966年12月24个月Z指数距平的原样文本>|<1966年3月单月采暖度日数实际值的原样文本>|<保留两位小数的湿度得分 (moisture score)>。这里的湿度得分 (moisture score) 也就是前面所说的1966年2月的10个月Z指数距平与1966年12月的24个月Z指数距平之和。如果在筛选后没有发现任何满足条件的分区，请直接输出 NONE。", + "start_url": "https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national", + "output_format": "最后，请将处理好的结果整理为单行字符串进行输出，各个匹配项之间使用英文逗号进行连接。每个结果必须严格遵守这样的拼接格式：<得克萨斯州分区号>|<分区名>|<1966年2月10个月Z指数距平的原样文本>|<1966年12月24个月Z指数距平的原样文本>|<1966年3月单月采暖度日数实际值的原样文本>|<保留两位小数的湿度得分 (moisture score)>。这里的湿度得分 (moisture score) 也就是前面所说的1966年2月的10个月Z指数距平与1966年12月的24个月Z指数距平之和。如果在筛选后没有发现任何满足条件的分区，请直接输出 NONE。", + "oracle_answer": "7|South Central|0.72|0.35|194°Df|1.07,10|Lower Valley|0.28|0.67|106°Df|0.95,9|South|0.03|0.37|148°Df|0.40", + "metadata": { + "State-Gated Retrieval": [ + "只在 Texas divisional 页面定义的四个 South Texas 分区内筛选：South Central、Upper Coast、South、Lower Valley。", + "保留同时满足以下条件的分区：1966-02 的 10-month Palmer Z-Index anomaly 不低于 -0.05；1966-12 的 24-month anomaly 不低于 -0.10；1966-03 的 1-month Heating Degree Days Value 小于 200°Df。", + "最终按两次 Z anomaly 之和降序、再按 1966-03 HDD Value 升序、再按分区号升序排序。" + ], + "dependency_type": "Data", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the official Texas climate-division reference fixes the four South Texas division IDs and names that must be tracked across all later pages", + "the 1966-02 10-month Palmer Z-Index anomaly page and the 1966-12 24-month Palmer Z-Index anomaly page jointly generate the four-division candidate set", + "the 1966-03 1-month Heating Degree Days Value page supplies the last filter; final rows are produced only after intersecting the three divisional screens and then sorting by summed Z-anomaly score, HDD value, and division number" + ], + "freeze": { + "historical_window": "Texas climate divisions South Central, Upper Coast, South, and Lower Valley; metrics are fixed to the 1966-02 10-month Palmer Z-Index anomaly, 1966-12 24-month anomaly, and 1966-03 1-month Heating Degree Days Value pages" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在 Texas divisional 页面定义的四个 South Texas 分区内筛选：South Central、Upper Coast、South、Lower Valley。", + "保留同时满足以下条件的分区：1966-02 的 10-month Palmer Z-Index anomaly 不低于 -0.05；1966-12 的 24-month anomaly 不低于 -0.10；1966-03 的 1-month Heating Degree Days Value 小于 200°Df。", + "最终按两次 Z anomaly 之和降序、再按 1966-03 HDD Value 升序、再按分区号升序排序。" + ], + "exclusion_conditions": [ + "排除四个指定 South Texas 分区之外的 Texas divisional 结果。", + "排除把 1966-03 HDD 页面的筛选字段误读成 Anomaly 而不是 Value 的结果。", + "排除任何一个时间窗或阈值条件不满足的分区。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "texas_division_no", + "division_name", + "feb_1966_10mo_z_text", + "dec_1966_24mo_z_text", + "mar_1966_hdd_text", + "moisture_score" + ], + "texas_division_no": "canonical output uses the short Texas climate-division number; the scorer may accept an equivalent four-digit form, but the emitted oracle uses the short number", + "raw_text_fields": "the two Z-index anomaly fields and the March 1966 HDD field preserve the raw displayed text; comparison may ignore optional trailing HDD unit text such as `°Df`", + "moisture_score": "compute as February 1966 10-month Z-index anomaly plus December 1966 24-month Z-index anomaly, formatted with exactly two decimal places", + "sorting_or_selection": { + "primary": "moisture_score descending", + "secondary": "March 1966 HDD actual value ascending after numeric normalization", + "tertiary": "Texas division number ascending" + }, + "eligibility_rule": "each Texas division is counted once per requested window; if any required window value is missing, exclude the division", + "stop_condition": [ + "all candidate Texas divisions are checked under the same base period and anomaly windows", + "the unique ordered output string is resolved before emission" + ] + } + } +} diff --git a/data_zh/constraint/climategov_002.json b/data_zh/constraint/climategov_002.json new file mode 100644 index 0000000000000000000000000000000000000000..b1a6dffa3bbc09262005006c30ae4c3f60a68e2c --- /dev/null +++ b/data_zh/constraint/climategov_002.json @@ -0,0 +1,73 @@ +{ + "task_id": "climategov_002", + "domain": "NOAA_NCEI_CLIMATE_AT_A_GLANCE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我最近在研究得州 (Texas) 历史上的气候模式，想为换季期（肩季）的运营规划找一些相似的历史年份作为参考。我特别想找出那些在 20 世纪早期曾经从偏干旱状态回升到接近常态或偏湿润，而且在两个换季窗口期供暖负荷都偏轻的区域。\n在 NOAA 的 Climate at a Glance 数据库中找出符合这些条件的分区。最终保留的区域必须同时满足这四个硬性指标：截至 1907 年 4 月的前 10 个月帕尔默 Z 指数距平 (Palmer Z-Index anomaly) 不高于 -0.30；截至 1923 年 4 月的前 10 个月 Z 指数距平不低于 -0.20；同时，截至 1915 年 5 月的 2 个月采暖度日数 (Heating Degree Days) 实际值低于 50°Df，且截至 1922 年 10 月的 5 个月采暖度日数实际值低于 20°Df。\n把这些符合条件的分区找出来之后，给它们排个序。先算一下每个分区的“反弹得分 (rebound score)”，也就是用 1923 年 4 月的 10 个月 Z 指数距平减去 1907 年 4 月的 10 个月 Z 指数距平。优先按这个得分从大到小降序排；如果得分一样，就把 1922 年 10 月的 5 个月 HDD 实际值更小的排在前面；要是这样还分不出先后，就让得州官方分区号更小的优先。\n最后，把整理好的结果拼成一整行字符串输出，不同的分区之间统一用英文逗号连起来。每个匹配项的数据严格套用这个格式：“|<四位分区ID>|<分区名>|<1907-04 10个月Z-Index距平原样文本>|<1923-04 10个月Z-Index距平原样文本>|<1915-05 2个月HDD实际值原样文本>|<1922-10 5个月HDD实际值原样文本>|<保留2位小数的反弹得分>”。如果在这批数据里没有任何一个分区符合这些条件，直接输出一个大写的 NONE。", + "start_url": "https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national", + "output_format": "把整理好的结果拼成一整行字符串输出，不同的分区之间统一用英文逗号连起来。每个匹配项的数据严格套用这个格式：“|<四位分区ID>|<分区名>|<1907-04 10个月Z-Index距平原样文本>|<1923-04 10个月Z-Index距平原样文本>|<1915-05 2个月HDD实际值原样文本>|<1922-10 5个月HDD实际值原样文本>|<保留2位小数的反弹得分>”。如果在这批数据里没有任何一个分区符合这些条件，直接输出一个大写的 NONE。", + "oracle_answer": "10|4110|Lower Valley|-0.36|1.46|10°Df|7°Df|1.82,9|4109|South|-0.33|0.53|23°Df|16°Df|0.86\n10|4110|Lower Valley|-0.36|1.46|10|7|1.82,9|4109|South|-0.33|0.53|23|16|0.86", + "metadata": { + "State-Gated Retrieval": [ + "只保留同时满足四个历史条件的 Texas 分区：1907-04 的 10-month Palmer Z-Index anomaly 不高于 -0.30；1923-04 的 10-month anomaly 不低于 -0.20；1915-05 的 2-month HDD Value 小于 50°Df；1922-10 的 5-month HDD Value 小于 20°Df。", + "rebound score 定义为 1923-04 的 10-month anomaly 减去 1907-04 的 10-month anomaly。", + "最终按 rebound score 降序、再按 1922-10 的 5-month HDD Value 升序、再按 Texas 分区号升序排序。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Texas divisional pages yield the 1907-04 and 1923-04 10-month Palmer Z-Index anomalies plus the 1915-05 2-month and 1922-10 5-month HDD values for each division", + "the rebound score and the two shoulder-season HDD values are computed only after the same divisional candidate set survives all four historical filters", + "the final output is produced after sorting the surviving divisions by rebound score, then 1922-10 HDD value, then division number" + ], + "control_dependency": [ + "the workflow must cover the 1907, 1923, and 1915 pages as well as the 1922-10 5-month HDD page", + "both HDD pages must be read from Value rather than Anomaly", + "the final rebound ranking must be determined after the 1922-10 5-month HDD page excludes 7 South Central and 8 Upper Coast, using ReboundScore as the ordering basis" + ], + "freeze": { + "historical_window": "Texas climate divisions evaluated on the 1907-04 and 1923-04 10-month Palmer Z-Index anomaly pages, the 1915-05 2-month HDD Value page, and the 1922-10 5-month HDD Value page" + }, + "answer_type": "mixed multi-line output" + }, + "rubric": { + "inclusion_conditions": [ + "只保留同时满足四个历史条件的 Texas 分区：1907-04 的 10-month Palmer Z-Index anomaly 不高于 -0.30；1923-04 的 10-month anomaly 不低于 -0.20；1915-05 的 2-month HDD Value 小于 50°Df；1922-10 的 5-month HDD Value 小于 20°Df。", + "rebound score 定义为 1923-04 的 10-month anomaly 减去 1907-04 的 10-month anomaly。", + "最终按 rebound score 降序、再按 1922-10 的 5-month HDD Value 升序、再按 Texas 分区号升序排序。" + ], + "exclusion_conditions": [ + "排除只做完 1907、1923 和 1915 三页过滤就提前停止、没有继续读取 1922-10 / 5-month / HDD 页面的结果。", + "排除把 1915 或 1922 的 HDD 页面误读成 Anomaly 而不是 Value 的结果。", + "排除任何一个历史窗口条件不满足的分区。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "texas_division_no", + "division_id_4digit", + "division_name", + "apr_1907_10mo_z_text", + "apr_1923_10mo_z_text", + "may_1915_2mo_hdd_text", + "oct_1922_5mo_hdd_text", + "rebound_score" + ], + "texas_division_no": "emit the short Texas climate-division number in field 1 and the four-digit division ID in field 2", + "raw_text_fields": "the two Z-index anomaly fields preserve the raw displayed text; the two HDD fields preserve the raw displayed text, but comparison may ignore an optional trailing `°Df` suffix", + "rebound_score": "compute as the April 1923 10-month Z-index anomaly minus the April 1907 10-month Z-index anomaly, formatted with exactly two decimal places", + "sorting_or_selection": { + "primary": "rebound_score descending", + "secondary": "October 1922 HDD actual value ascending after numeric normalization", + "tertiary": "Texas division number ascending" + }, + "answer_set_note": "the current oracle stores two equivalent answer sets: one preserves the HDD unit suffixes and one strips them; treat the two HDD columns as equivalent after optional `°Df` removal", + "stop_condition": [ + "all candidate Texas divisions are checked under the same anomaly and HDD windows", + "the unique ordered output string is resolved before emission" + ] + } + } +} diff --git a/data_zh/constraint/comptox_001.json b/data_zh/constraint/comptox_001.json new file mode 100644 index 0000000000000000000000000000000000000000..cfa66f61a787c6bacc82760aa3dc12ffabd9ff88 --- /dev/null +++ b/data_zh/constraint/comptox_001.json @@ -0,0 +1,76 @@ +{ + "task_id": "comptox_001", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "我想把五种在欧洲彩绘产品相关记录里出现过的物质，也就是aniline、cobalt、chromium、3,3'-dichlorobenzidine 和 dibenz[a,h]anthracene 这五种物质，提取出页面明确包含‘Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe’记录的合格目标，并为其生成一份整合了历史关键词状态与最深层级用途的综合清单。先只看以下五个带日期的关键词有没有出现过：Substances in Products - Canada (4/2014)、Indirect additives food contact (10/2018)、OEHHA Proposition 65 (3/2019)、WA Children's Safe Product Act (4/2020)、OEHHA Proposition 65 (1/2023)。只看\"有没有出现\"，不管关键词前面标的数字，同时记录命中项里最早和最晚的年月。然后在除了之前提到的彩绘产品记录之外，再选两个用途类别：一个从日常消费品的角度选，优先顺序是 Formulation → Article → Occupation；一个从生产原料的角度选，优先顺序是 Occupation → Article → Formulation。选定类别之后，沿着产品数最多的下一级分类一路往下走，直到不能再细分为止；如果同一层有并列，就取 PUC ID 更小的那个。", + "start_url": "https://comptox.epa.gov/chemexpo/", + "output_format": "最后按命中数从高到低排列，命中数相同的再按日常消费品侧入选节点的产品数从高到低排列，输出格式如下：|<命中数>|<最早年月>|<最晚年月>|<日常消费品侧PUC kind>|<日常消费品侧一般类别PUC ID>|<日常消费品侧入选节点PUC ID>|<日常消费品侧节点层级>|<日常消费品侧Products>|<生产原料侧PUC kind>|<生产原料侧一般类别PUC ID>|<生产原料侧入选节点PUC ID>|<生产原料侧节点层级>|<生产原料侧Products>结果之间用英文逗号分隔；若没有结果输出 NONE。", + "oracle_answer": "DTXSID8020090|5|2014-04|2023-01|Formulation|272|295|type|4|Occupation|301|356|family|27,DTXSID1031040|3|2018-10|2023-01|Formulation|77|94|type|7|Occupation|301|400|family|308,DTXSID9020409|2|2019-03|2023-01|Occupation|321|321|general|11|Occupation|321|321|general|11,DTXSID6020432|2|2019-03|2023-01|Article|313|313|general|1|Occupation|301|356|family|27,DTXSID3031022|1|2023-01|2023-01|Formulation|77|95|type|4|Occupation|301|356|family|185", + "metadata": { + "State-Gated Retrieval": [ + "只在题目指定的五个物质中筛选，并且目标物质页面必须明确包含 “Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe” 这条记录。", + "要统计五个指定 dated keywords 是否出现，并记录命中项中最早和最晚的年月。", + "随后必须分别选择一条日常消费品侧路线与一条生产原料侧路线，前者按 Formulation → Article → Occupation，后者按 Occupation → Article → Formulation 独立下钻。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "each chemical page yields the five dated historical keywords, the Europe body-paint/tattoo-ink qualifying record, and the earliest/latest dated-hit months", + "PUC drilldowns yield one consumer-side route chosen by Formulation -> Article -> Occupation and one source-side route chosen independently by Occupation -> Article -> Formulation", + "final rows are produced only after the consumer-side and source-side routes are selected and drilled separately for each chemical" + ], + "control_dependency": [ + "the source-side route must be selected independently from the consumer-side route", + "for each chemical, the second drilldown must follow the production-material priority order rather than the daily-consumer route", + "family/type/general outputs must be determined only after both route selections are made independently" + ], + "freeze": { + "historical_window": "current ChemExpo chemical pages and PUC drilldowns for the five named substances, using the dated keyword states through 2023-01 and the current Europe body-paint/tattoo-ink record" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在题目指定的五个物质中筛选，并且目标物质页面必须明确包含 “Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe” 这条记录。", + "要统计五个指定 dated keywords 是否出现，并记录命中项中最早和最晚的年月。", + "随后必须分别选择一条日常消费品侧路线与一条生产原料侧路线，前者按 Formulation → Article → Occupation，后者按 Occupation → Article → Formulation 独立下钻。" + ], + "exclusion_conditions": [ + "排除不含题目指定 Europe 彩绘/纹身墨水记录的物质。", + "排除把同一条日常消费品侧路线直接复用到生产原料侧的结果。", + "排除没有按指定优先顺序独立选择并下钻两条路线的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DTXSID", + "hit_count", + "earliest", + "latest", + "consumer_kind", + "consumer_general_puc_id", + "consumer_terminal_puc_id", + "consumer_level", + "consumer_products", + "material_kind", + "material_general_puc_id", + "material_terminal_puc_id", + "material_level", + "material_products" + ], + "dated_hits": "count only the exact dated keyword strings defined in the source rubric", + "date_format": "YYYY-MM", + "kind": "the kind fields use the canonical labels Article, Formulation, or Occupation", + "level": "the level fields use the canonical labels general, family, or type", + "products_source": "the Products counts come from the local chemical-detail node for the selected branch, not from an overall aggregate shown elsewhere on the site", + "sorting_or_selection": { + "primary": "hit_count descending", + "secondary": "consumer_products descending", + "tertiary": "DTXSID ascending" + } + } + } +} diff --git a/data_zh/constraint/comptox_002.json b/data_zh/constraint/comptox_002.json new file mode 100644 index 0000000000000000000000000000000000000000..036206146b7cf4a2de29d026645b130fc2bf263e --- /dev/null +++ b/data_zh/constraint/comptox_002.json @@ -0,0 +1,78 @@ +{ + "task_id": "comptox_002", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 6, + "instruction": "我想在 ChemExpo 里看看这六个物质，当前到底是更多出现在材料接触相关的用途里，还是制造来源相关的用途里，然后从对应的方向上各选出一个最能代表它的用途分类。请按下面的步骤来查。先把范围限定在这六个物质：Di(2-Ethylhexyl) Phthalate、Melamine、Tris(2-Ethylhexyl) Phosphate、4,5-Dihydro-2-Mercaptoimidazole、Phthalic Acid、Triphenyl Phosphates Tert-Butylated。然后，对每个物质先看五类跟材料接触有关的标签有没有出现过，每类出现了就记 1 分：Indirect additives food contact (10/2018);Europe, Food contact items;Food contact items, Japan;任何带有 Toys and children's products 字样的关键词;任何带有 artificial_saliva 或 artificial_sweat 字样的关键词接着，再看两类跟制造来源有关的标签有没有出现过，每类出现了也记 1 分：drinking_water, Europe, manufacturing, plastic_additive;Europe, plastic_additive。另外，再单独统计以下四个带日期的关键词有没有出现过：Indirect additives food contact (10/2018);OEHHA Proposition 65 (3/2019);WA Children's Safe Product Act (4/2020);OEHHA Proposition 65 (1/2023)。要记录命中了几个，以及命中项里最早和最晚的年月。然后看哪边分数高来决定方向：如果材料接触那边的得分严格大于制造来源那边，就按 Article → Formulation → Occupation 的顺序来找最能代表这个物质的类别；否则就按 Occupation → Article → Formulation 的顺序来找。确定了类别之后，从这一层开始，每一层都只沿着产品数最多的下一级分类往下走，一直走到不能再细分为止；如果同一层有并列，就取 PUC ID 更小的。", + "start_url": "https://comptox.epa.gov/chemexpo/", + "output_format": "最后，把所有物质按带日期命中数从高到低排列；命中数相同的，再按入选节点的产品数从高到低排列，输出格式如下：|||||||||||||结果之间用英文逗号分隔；如果带日期命中数为 0，则 earliest 和 latest 都写 NA。", + "oracle_answer": "DTXSID5020607|5|2|4|2018-10|2023-01|contact|Article|309|493|family|1|23|58,DTXSID5020601|4|1|3|2018-10|2023-01|contact|Article|309|309|general|1|5836|1827,DTXSID6020802|4|2|1|2018-10|2018-10|contact|Article|313|313|general|15|1104|675,DTXSID8021484|3|1|1|2018-10|2018-10|contact|Occupation|321|321|general|8|28313|4200,DTXSID0021414|5|0|1|2018-10|2018-10|contact|Article|309|309|general|3|5836|1827,DTXSID20872645|0|1|0|NA|NA|source|Occupation|318|381|family|5|274|107", + "metadata": { + "State-Gated Retrieval": [ + "只看题目指定的六个物质，并先在 chemical page 上计算 contactHits、sourceHits 和 datedHits。", + "prioritySide 必须先由这些历史信号决定，然后再沿对应方向挑选一个最能代表的当前用途分类。", + "当前路线选择必须按题目给定的 kind 优先级和同层更小 PUC ID 规则继续下钻。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "each chemical page yields contactHits, sourceHits, datedHits, and the earliest/latest dated-hit months from the historical keyword set", + "after the priority side is chosen, the corresponding current PUC drilldown yields the representative kind, PUC path, product counts, and curated-chemical counts", + "final rows are produced only after the historical hit scores determine the side first and the current route is then chosen with the side-specific priority and tie-break rules" + ], + "control_dependency": [ + "historical contact/source signal scores must take priority over current maximum-Products paths", + "the priority side must be determined from contactHits, sourceHits, and datedHits rather than from current visibility alone", + "PUC path tie-breaks are valid only after the correct side has been fixed and the route has been re-drilled under that side's rules" + ], + "freeze": { + "historical_window": "current ChemExpo chemical pages and PUC drilldowns for the six named substances, using the stated historical keyword families and dated hits through 2023-01" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只看题目指定的六个物质，并先在 chemical page 上计算 contactHits、sourceHits 和 datedHits。", + "prioritySide 必须先由这些历史信号决定，然后再沿对应方向挑选一个最能代表的当前用途分类。", + "当前路线选择必须按题目给定的 kind 优先级和同层更小 PUC ID 规则继续下钻。" + ], + "exclusion_conditions": [ + "排除忽略历史信号、直接在 chemical page 上选当前可见 Products 最大路径的结果。", + "排除未先确定 contact/source 方向就开始做 PUC 路线选择的结果。", + "排除同层 tie-break 不按更小 PUC ID 规则处理的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DTXSID", + "contactHits", + "sourceHits", + "datedHits", + "earliest", + "latest", + "prioritySide", + "PUCkind", + "generalPUCID", + "terminalPUCID", + "level", + "Products", + "PUCDocuments", + "PUCCuratedChemicals" + ], + "dated_hits": "count only the exact dated keyword strings defined in the source rubric", + "date_format": "YYYY-MM; if datedHits is 0, earliest and latest are both `NA`", + "prioritySide": "emit `contact` when contactHits > sourceHits; otherwise emit `source`", + "kind": "the PUCkind field uses the canonical labels Article, Formulation, or Occupation", + "level": "the level field uses the canonical labels general, family, or type", + "products_source": "Products comes from the selected terminal chemical-detail node", + "terminal_statistics": "PUCDocuments and PUCCuratedChemicals come from the selected terminal PUC detail page Additional Statistics block", + "sorting_or_selection": { + "primary": "datedHits descending", + "secondary": "Products descending", + "tertiary": "DTXSID ascending" + } + } + } +} diff --git a/data_zh/constraint/comptox_003.json b/data_zh/constraint/comptox_003.json new file mode 100644 index 0000000000000000000000000000000000000000..ae11299a80a38a716e44831d57ab9e8b37ceea08 --- /dev/null +++ b/data_zh/constraint/comptox_003.json @@ -0,0 +1,67 @@ +{ + "task_id": "comptox_003", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我想在 ChemExpo 里先筛出一些产品较多的配方大类，然后再从每个大类里，挑出一个带 child 或 aerosol 标签、最值得优先看的具体产品。请按下面步骤查。先筛选出总产品量达到 15,000 及以上的配方（Formulation）大类。接着，在每个大类中按网站默认的展示顺序，锁定第一个符合这些条件的产品家族：家族本身没有 默认属性（assumed attributes ）且总产品量至少为 3,000；此外，该家族下至少要有两个不同的具体产品类型，其中一个类型的 自选属性（allowed attributes） 包含 气雾剂类（aerosol），另一个包含 儿童用类（child），并且这两个类型自身的 assumed attributes 都必须为空。接着，分别在这两个具体产品类型里，找出该类型产品份额（该类型产品数除以家族累计产品数）的那个；如果遇到份额一样的情况，就比较它们的 Curated Chemicals，选数量多的那个；若数量依然相同，则最终选取 PUC ID 更小的类型。完成两侧筛选后，在这两个候选类型中只保留最终更优的一个：优先保留产品份额更高的那个；若两侧产品份额相同，则依次比较 产品数（Product Count），选择更高的；若仍相同，则比较 Curated Chemicals，选择更多的；若仍然相同，则选择 PUC ID 更小的。", + "start_url": "https://comptox.epa.gov/chemexpo/visualizations/", + "output_format": "请按最终 share 从高到低输出结果，格式写成：<一般类别PUC ID>|<家族PUC ID>|<具体产品类型PUC ID>|||结果之间用英文逗号连接，且不加空格；如果没有结果，就输出 NONE。", + "oracle_answer": "48|42|62|child|2160/3531|583,137|197|210|child|6934/16904|1135", + "metadata": { + "State-Gated Retrieval": [ + "先只保留总产品量达到 15,000 及以上的 Formulation 大类。", + "在每个候选 family 中，必须同时找到一条 aerosol 侧 type 和一条 child 侧 type：family 本身 assumed attributes 为空且总产品量至少 3,000；两个 type 的 assumed attributes 也都为空。", + "最终 family 内部与双侧之间的优先选择都必须按题目规定的 share、Product Count、Curated Chemicals、PUC ID 规则比较。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Formulation summary yields the high-product candidate families whose total product count is at least 15,000", + "within each family, lower-level type pages yield the aerosol and child candidates, their assumed/allowed attributes, product counts, shares, and curated-chemical counts", + "final rows are produced only after a family survives both aerosol and child branches and the winning type is selected by the layered share/product/chemical/PUC tie-break rules" + ], + "control_dependency": [ + "both the aerosol and child branches within the same family must be fully checked before that family can be retained", + "if one side is missing, the workflow must reject the family and continue to the next sibling family rather than stop at the first partial hit", + "the final winner can be selected only after both sides have been independently optimized within the family and then compared against each other" + ], + "freeze": { + "historical_window": "current ChemExpo Formulation families with total product count >= 15,000, evaluated on family/type attributes and current product/chemical counts" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先只保留总产品量达到 15,000 及以上的 Formulation 大类。", + "在每个候选 family 中，必须同时找到一条 aerosol 侧 type 和一条 child 侧 type：family 本身 assumed attributes 为空且总产品量至少 3,000；两个 type 的 assumed attributes 也都为空。", + "最终 family 内部与双侧之间的优先选择都必须按题目规定的 share、Product Count、Curated Chemicals、PUC ID 规则比较。" + ], + "exclusion_conditions": [ + "排除只要在任意一侧先找到可用 type 就停止、没有要求同一家族同时覆盖 aerosol 与 child 两侧的结果。", + "排除一侧缺失时没有继续回溯 sibling family 的结果。", + "排除未按题目指定的层层 tie-break 规则选出 family 内与最终优胜 type 的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "generalPUCID", + "familyPUCID", + "typePUCID", + "side", + "share", + "CuratedChemicals" + ], + "dedup_key": "(generalPUCID, familyPUCID, typePUCID, side)", + "side": "emit the lower-case branch label exactly as determined in the source workflow", + "share": "canonical output uses the raw fraction `type Products / family Cumulative Products` rather than a decimal", + "CuratedChemicals": "emit the integer count from the selected type-level node", + "sorting_or_selection": { + "primary": "share descending by numeric fraction value", + "secondary": "type-level Products descending", + "tertiary": "CuratedChemicals descending, then PUC IDs ascending as tie-breaks" + } + } + } +} diff --git a/data_zh/constraint/comptox_004.json b/data_zh/constraint/comptox_004.json new file mode 100644 index 0000000000000000000000000000000000000000..57ec8e664b2fb03d093f04c6ece6ff4f3a6e1fe1 --- /dev/null +++ b/data_zh/constraint/comptox_004.json @@ -0,0 +1,84 @@ +{ + "task_id": "comptox_004", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "在 ChemExpo 中，我们需要针对 Di(2-Ethylhexyl) Phthalate、Melamine、Phthalic Acid、Tris(2-Ethylhexyl) Phosphate 和 Triphenyl Phosphates Tert-Butylated 这五个物质，核对它们的历史标签与当前实际用途是否一致请按下面的步骤来查。先把范围限定在这五个物质：Di(2-Ethylhexyl) Phthalate、Melamine、Phthalic Acid、Tris(2-Ethylhexyl) Phosphate、Triphenyl Phosphates Tert-Butylated。首先，为每个物质收集三组基础评估数据。第一组为‘成品接触’得分：检查是否出现 Indirect additives food contact (10/2018)、Europe, Food contact items、Food contact items, Japan、含 Toys and children's products 字样的关键词，以及含 artificial_saliva 或 artificial_sweat 字样的关键词，这五类标签每命中一类记 1 分。第二组为‘生产来源’得分：检查是否出现 drinking_water, Europe, manufacturing, plastic_additive 与 Europe, plastic_additive 这两类标签，每命中一类也记 1 分。第三组为特定日期的监管概况：单独核查 Indirect additives food contact (10/2018)、OEHHA Proposition 65 (3/2019)、WA Children's Safe Product Act (4/2020)、OEHHA Proposition 65 (1/2023) 这四个关键词的命中总数，并记录所有命中项跨越的最早及最晚年月。有了这三组数据之后，看哪边分数高来决定历史方向：如果成品接触那边的分数严格大于生产来源那边，就按 Article → Formulation → Occupation 的顺序，为它选出一个历史线索推荐的类别；否则按 Occupation → Article → Formulation 的顺序来选。确定了类别之后，沿着产品数最多的下一级分类一路往下走，直到不能再细分；如果同一层有并列，就取 PUC ID 更小的。与此同时，再另外找出这个物质当前的主导类别，不看历史线索，直接在所有用途分类里找产品数最多的那条线，同样一路往下走到不能再细分；同层并列也取 PUC ID 更小的。最后把这两个结果放在一起比对：如果当前主导类别是 Article 或 Formulation，而历史线索判断也指向成品接触这一边，就记 ALIGNED；如果当前主导类别是 Occupation，而历史线索判断也指向生产来源那一边，也记 ALIGNED；其余情况都记 MISALIGNED。", + "start_url": "https://comptox.epa.gov/chemexpo/", + "output_format": "输出时先把 MISALIGNED 的排在前面；同一组里再按带日期命中数从高到低排；命中数也相同的，再按当前主导类别的产品数从高到低排。格式如下：|||||||||||||||||结果之间用英文逗号分隔；如果带日期命中数为 0，则 earliest 和 latest 都写 NA。", + "oracle_answer": "DTXSID6020802|4|2|1|2018-10|2018-10|material|Article|Furniture and furnishings|Furniture and furnishings|general|15|Occupation|Raw materials|fireproof coatings|type|24|MISALIGNED,DTXSID8021484|3|1|1|2018-10|2018-10|material|Occupation|Laboratory supplies|Laboratory supplies|general|8|Occupation|Laboratory supplies|Laboratory supplies|general|8|MISALIGNED,DTXSID5020607|5|2|4|2018-10|2023-01|material|Article|Construction and building materials|flooring|family|1|Formulation|Home maintenance|paint|type|112|ALIGNED,DTXSID0021414|5|0|1|2018-10|2018-10|material|Article|Construction and building materials|Construction and building materials|general|3|Article|Construction and building materials|Construction and building materials|general|3|ALIGNED,DTXSID20872645|0|1|0|NA|NA|source|Occupation|Industrial products|hydraulic fluid|family|5|Occupation|Industrial products|hydraulic fluid|family|5|ALIGNED", + "metadata": { + "State-Gated Retrieval": [ + "只在题目指定的五个物质上工作，并先根据 keyword-set 区块计算 materialHits、sourceHits 与 datedHits。", + "历史推荐类别必须由这些历史信号独立推出；当前主导类别则需要单独从当前用途路径中求出。", + "最终只比较历史推荐类别与当前主导类别所在的大类方向是否一致，并据此标记 ALIGNED 或 MISALIGNED。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "each chemical page yields materialHits, sourceHits, datedHits, and the historical recommendation side implied by the keyword set", + "independent current PUC drilldown yields the current dominant category, path labels, and classification counts for the same chemical", + "final rows are produced only after the historical recommendation and current dominant category are computed independently and then compared at the coarse side level" + ], + "control_dependency": [ + "the historical recommendation must be determined from the keyword-set evidence rather than from the current largest category", + "historical recommendation must be computed from the keyword-set evidence before alignment is judged", + "ALIGNED / MISALIGNED status is valid only after the historical and current category directions have been derived independently and then compared" + ], + "freeze": { + "historical_window": "current ChemExpo chemical pages and PUC drilldowns for the five named substances, using the specified historical keyword-set evidence through 2023-01" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在题目指定的五个物质上工作，并先根据 keyword-set 区块计算 materialHits、sourceHits 与 datedHits。", + "历史推荐类别必须由这些历史信号独立推出；当前主导类别则需要单独从当前用途路径中求出。", + "最终只比较历史推荐类别与当前主导类别所在的大类方向是否一致，并据此标记 ALIGNED 或 MISALIGNED。" + ], + "exclusion_conditions": [ + "排除只看当前最大类别、直接把它当成历史推荐类别的结果。", + "排除在没有独立求出历史推荐类别的情况下默认一律 ALIGNED 的结果。", + "排除未把历史与当前两条链路分开计算、而是在同一路线里混读信号的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DTXSID", + "materialHits", + "sourceHits", + "datedHits", + "earliest", + "latest", + "historySide", + "recommendedKind", + "recommendedGeneral", + "recommendedTerminal", + "recommendedLevel", + "recommendedProducts", + "currentKind", + "currentGeneral", + "currentTerminal", + "currentLevel", + "currentProducts", + "status" + ], + "dated_hits": "count only the exact dated keyword strings defined in the source rubric", + "date_format": "YYYY-MM; if datedHits is 0, earliest and latest are both `NA`", + "historySide": "emit the lower-case historical winner `material` or `source`", + "recommended_fields": "these fields describe the historically suggested path", + "current_fields": "these fields describe the current dominant path", + "kind": "the kind fields use the canonical labels Article, Formulation, or Occupation", + "level": "the level fields use the canonical labels general, family, or type", + "status": "emit `ALIGNED` or `MISALIGNED` exactly", + "sorting_or_selection": { + "primary": "status with MISALIGNED before ALIGNED", + "secondary": "datedHits descending", + "tertiary": "currentProducts descending", + "quaternary": "DTXSID ascending" + } + } + } +} diff --git a/data_zh/constraint/consumerfinance_001.json b/data_zh/constraint/consumerfinance_001.json new file mode 100644 index 0000000000000000000000000000000000000000..69c83849cf6f902be36229c5e9ff74bee56324e8 --- /dev/null +++ b/data_zh/constraint/consumerfinance_001.json @@ -0,0 +1,67 @@ +{ + "task_id": "consumerfinance_001", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "请你在 CFPB 网站的执法案件页面中，在 2022 到 2024 年这段时间内，分别针对 存款业务（Deposits）、征信信息报送业务（Furnishing） 和 预付类业务（Prepaid） 这三个业务类别，各找出一件符合条件的行政执法案件，然后到这件案件对应的 和解令（Consent Order）里，找出消费者补偿金额（consumer redress）和民事罚款金额（civil money penalty）第一次出现时的具体金额，以及它们所在的页码。\n具体来说，先把查找范围限定在 CFPB 的执法案件页面中，并且只看那些初始立案日期落在 2022-01-01 到 2024-12-31 之间的案件。\n然后，分别对 存款业务（Deposits）、征信信息报送业务（Furnishing） 和 预付类业务（Prepaid） 这三个业务类别单独查找。对每一个类别，都按照 CFPB 网站当前默认显示的案件顺序，从上往下依次查看，找到第一件同时满足下面条件的案件就可以：\n1. 这个案件页面同时提供和解令（Consent Order）和新闻稿（press release）；\n2. 业务类别标签目标类别一对一对应；\n3. 页面上明确写明有消费者补偿（consumer redress），而且补偿金额超过 500 万美元；\n4. 除了消费者补偿之外，页面上还明确写明有民事罚款（civil money penalty）。\n在每个业务类别下找到这样一件案件之后，再打开它对应的和解令（Consent Order），分别去定位两类金额信息：\n- 消费者补偿金额（consumer redress）第一次在正文中出现时，写出的具体金额是多少，它出现在第几页；\n- 民事罚款金额（civil money penalty）第一次在正文中出现时，写出的具体金额是多少，它出现在第几页。\n这里的页码要按照同意令 PDF 的物理页码来计算，也就是 PDF 的第一页记作 p1，第二页记作 p2，依此类推。", + "start_url": "https://www.consumerfinance.gov/enforcement/actions/", + "output_format": "最后，请把三个业务类别对应的结果按名称字母顺序整理输出。每个类别输出一段，格式如下：\n|||||p||p\n如果某个类别最终没有找到符合条件的案件，就输出：\n|NONE\n三个结果之间用英文逗号连接，不要加空格。", + "oracle_answer": "Deposits|Bank of America, N.A.|2023-CFPB-0006|2023-07-11|$80,400,000|p11|$60,000,000|p14,Furnishing|Hyundai Capital America|2022-CFPB-0005|2022-07-26|$13,200,000|p31|$6,000,000|p35,Prepaid|U.S. Bank National Association|2023-CFPB-0019|2023-12-19|$5,700,000|p22|$15,000,000|p26", + "metadata": { + "State-Gated Retrieval": [ + "只看 CFPB Enforcement actions 页面中 Initial filing date 落在 2022-01-01 至 2024-12-31 的 administrative enforcement actions。", + "对 Deposits、Furnishing、Prepaid 三个产品类别分别按当前默认顺序自上而下寻找第一件同时满足：页面提供 Consent Order 和 Press release；Products 与目标类别一对一对应；action detail page 明确写出 consumer redress > 5,000,000 美元且另有 civil money penalty。", + "最终从正确的 Consent Order 中提取 consumer redress 和 civil money penalty 第一次出现的金额及页码。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "enforcement-action list pages yield product-branch candidate actions in current default order", + "each action detail page and linked consent-order PDF yield product singularity, document-stack presence, redress / civil-money-penalty amounts, and first-occurrence pages", + "final rows are emitted only after identifying, for each product, the first action that survives detail-page and PDF validation" + ], + "control_dependency": [ + "list-level \"has Consent Order + Press release\" hits must be validated on the detail page for product singularity and money thresholds", + "Prepaid candidates force document-level disambiguation among Consent Order, Stipulation, and terminating-order PDFs", + "per-product first-match selection must explicitly skip rejected candidates and validate downstream PDFs before it is finalized" + ], + "freeze": { + "historical_window": "administrative enforcement actions with Initial filing date from 2022-01-01 through 2024-12-31; current default case ordering and currently linked action documents" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只看 CFPB Enforcement actions 页面中 Initial filing date 落在 2022-01-01 至 2024-12-31 的 administrative enforcement actions。", + "对 Deposits、Furnishing、Prepaid 三个产品类别分别按当前默认顺序自上而下寻找第一件同时满足：页面提供 Consent Order 和 Press release；Products 与目标类别一对一对应；action detail page 明确写出 consumer redress > 5,000,000 美元且另有 civil money penalty。", + "最终从正确的 Consent Order 中提取 consumer redress 和 civil money penalty 第一次出现的金额及页码。" + ], + "exclusion_conditions": [ + "排除 Products 不是单一目标类别、或仅在列表层看起来相关但 detail page 不成立的案件。", + "排除没有明确满足 redress > 5M 与独立 civil money penalty 条件的案件。", + "排除误用 Stipulation 或 Order Terminating the Consent Order 代替题目要求的 Consent Order。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Product", + "Respondent", + "Docket", + "FilingDate", + "RedressUSD", + "RedressPage", + "PenaltyUSD", + "PenaltyPage" + ], + "product_order": "alphabetical by Product name", + "fallback_row": "if a product has no qualifying case, emit `|NONE`", + "date_format": "FilingDate uses YYYY-MM-DD", + "money_fields": "canonical output preserves the dollar sign and commas from the oracle, but equivalent comparison may ignore `$` and commas and compare the numeric USD amount", + "page_fields": "page fields use the canonical `pN` form", + "document_scope": "extract both money amounts from the Consent Order PDF only; do not substitute a stipulation, termination order, or other companion document", + "selection_rule": "for each product, keep the first action in the default filtered order that fully satisfies every gate in the source rubric" + } + } +} diff --git a/data_zh/constraint/consumerfinance_002.json b/data_zh/constraint/consumerfinance_002.json new file mode 100644 index 0000000000000000000000000000000000000000..9da8456661fed419428b98d27902a1145a35b669 --- /dev/null +++ b/data_zh/constraint/consumerfinance_002.json @@ -0,0 +1,66 @@ +{ + "task_id": "consumerfinance_002", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我想整理一下 CFPB Reports 里那套一年一度的家庭财务稳定性调查报告，它的最新版页面上还能直接链回 2023 和 2022 两个旧版。我关心的是：2022 版里有些主题后来在后续年份的年报里被去掉了，我想看看这些被去掉的主题在站内还关联了哪些报告。具体查法是这样的。先在 CFPB Reports 栏目里锁定这套系列，确认最新版能直接链到 2023 和 2022 两个前序版本。然后以 2022 版为基准，找出那些在 2022 版里出现、但在后续年份年报中不再保留的主题。注意，那个专门用来标记\"属于同一调查系列\"的主题不算在内，把它排除掉。接着，对筛出的每个主题，帮我逐一确认以下内容：第一，这个主题最早是在哪一年的后续年报里消失的；第二，在 CFPB Reports 栏目里搜索这个主题，在 2022 年及之前的结果中，排在最前面的那份不属于这套系列的报告是哪一份；第三，打开这份报告，看它直接列出的 related resources 一共有几项；这些项目里，明确指回同一调查系列的有几项；而在这些指回来的报告当中，附录按字母编号且至少分了三个章节（比如 Appendix A、B、C 或更多）的又有几项；第四，经过上面这层层筛选最终剩下的那份报告，给出它的标题、发布日期，以及附录的字母编号范围。", + "start_url": "https://www.consumerfinance.gov/data-research/research-reports/", + "output_format": "最后按主题名称的字母顺序，输出一行字符串：|||||||||", + "oracle_answer": "Saving|2023|Consumer Savings App Strategies and Savings Outcomes|2022-12-07|4|2|1|Emergency Savings and Financial Security: Insights from the Making Ends Meet Survey and Consumer Credit Panel|2022-03-23|A-D,Student loans|2023|Report of the CFPB Education Loan Ombudsman|2022-10-20|0|0|0|NONE|NONE|NONE", + "metadata": { + "State-Gated Retrieval": [ + "先锁定当前最新版可直接链回 2023 和 2022 的那套 CFPB household financial well-being 年报系列。", + "以 2022 版为基准，只保留那些在 2022 出现、但在后续年度年报中不再保留的主题，并排除专门标记“属于同一调查系列”的主题。", + "对每个主题再按题目要求寻找 2022 年及以前最靠前的非本系列 pivot report，并依次统计 direct related resources、same-series 回链数、qualified report 及其 appendix span。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current CFPB Reports pages yield the 2024 -> 2023 -> 2022 annual-survey chain and the 2022 topic baseline", + "report detail pages and report-search results yield first-disappearance year, pivot report title/date, related-resource counts, and backlinks into the annual-survey series", + "final rows are produced only after separating the first jump target from later return-to-series counting" + ], + "control_dependency": [ + "binding the pivot report to same-series continuation forces an incorrect shrinkage of valid topic rows", + "title extraction must use the pivot detail page rather than search-result snippets", + "related-resource expansion must continue even when the first pivot page cannot itself continue the same-series chain" + ], + "freeze": { + "historical_window": "currently linked 2024, 2023, and 2022 CFPB household financial well-being annual reports; topic disappearance is judged over that three-year chain, and pivot-report search is restricted to 2022-and-earlier reports" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先锁定当前最新版可直接链回 2023 和 2022 的那套 CFPB household financial well-being 年报系列。", + "以 2022 版为基准，只保留那些在 2022 出现、但在后续年度年报中不再保留的主题，并排除专门标记“属于同一调查系列”的主题。", + "对每个主题再按题目要求寻找 2022 年及以前最靠前的非本系列 pivot report，并依次统计 direct related resources、same-series 回链数、qualified report 及其 appendix span。" + ], + "exclusion_conditions": [ + "排除仍在后续年度年报中保留的主题。", + "排除把“pivot report 必须还能继续回到同一系列”错误当成第 3 列硬条件的结果。", + "排除直接属于同一调查系列的搜索结果或 2022 年之后的报告。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "topic", + "first-missing-year", + "pivot-report-or-NONE", + "pivot-date-or-NONE", + "direct-related-count", + "same-series-count", + "qualified-count", + "representative-report-or-NONE", + "publication-date-or-NONE", + "appendix-span-or-NONE" + ], + "topic_order": "alphabetical by topic name", + "date_format": "pivot-date and publication-date use YYYY-MM-DD when present", + "appendix_span": "canonical span uses compact labels such as `A-D`", + "none_rule": "if qualified-count is 0, representative-report, publication-date, and appendix-span are all `NONE`" + } + } +} diff --git a/data_zh/constraint/consumerfinance_003.json b/data_zh/constraint/consumerfinance_003.json new file mode 100644 index 0000000000000000000000000000000000000000..6abeadcc6f5173a3729c557bdc2c0c2ab7c58748 --- /dev/null +++ b/data_zh/constraint/consumerfinance_003.json @@ -0,0 +1,69 @@ +{ + "task_id": "consumerfinance_003", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我想把 CFPB 在 2020 年发布的债务催收规则（ Debt Collection Rule）分别梳理清楚，包括提案来源、延后生效的安排、最终生效日，以及实施页面上配套的 quick-reference PDF 信息。请按下面的步骤来查。先确认 CFPB 在 2020 年分两波发布的那两份 Debt Collection Rule 最终规则各自是什么时候发布的。然后分别确认以下信息：1. 这波 final rule 的发布日期；2. 它是从哪个提案（或哪些提案）发展来的，以及各提案的公众评议截止日期；；3. 2021 年那次关于延后生效日的拟议规则有没有覆盖到这一波，那次征求意见最后截止到哪一天；4. 最终实际执行的生效日是哪天；5. 在实施页面上，这一波对应的是哪一份 quick-reference PDF；6. 这份 PDF 正文跳过引言段落后的第一个小标题是什么。", + "start_url": "https://www.consumerfinance.gov/rules-policy/final-rules/", + "output_format": "请把结果按 final-rule issue date 从早到晚输出一行字符串，每一波用它的 final rule 发布月份（YYYY-MM）来标识：||||||||", + "oracle_answer": "2020-10|2020-10-30|2019-05-07 main|2019-09-18|YES|2021-05-19|2021-11-30|Executive summary of the October 2020 final rule|Coverage and Definitions,2020-12|2020-12-18|2019-05-07 main+2020-02-21 supplemental|2019-09-18+2020-08-04|YES|2021-05-19|2021-11-30|Executive summary of the December 2020 final rule|Validation Information Requirements and Disclosures", + "metadata": { + "State-Gated Retrieval": [ + "必须分别处理 2020 年两波同名的 Debt Collection Practices (Regulation F) final rules，而不是合并成一条。", + "对每一波都要分别确认：发布日期、对应 proposal chain 及公众意见截止日、2021 年 delayed-effective-date proposed rule 是否覆盖及其截止日、最终生效日、对应 implementation quick-reference PDF，以及该 PDF 跳过引言后的第一个小标题。", + "October wave 与 December wave 的 detail page、proposal chain 和 summary PDF 都必须各自独立核验。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "final-rules index pages and rule-development pages yield the two 2020 Regulation F final-rule waves and their proposal branches", + "each final-rule detail page, delayed-effective-date proposal page, and implementation quick-reference PDF yields the wave-specific dates, linked proposals, comment deadlines, and first summary heading", + "final rows are produced only after the October and December waves are traced separately end to end" + ], + "control_dependency": [ + "two same-title final rules force correction from name-based collapsing to issue-date branching", + "proposal-chain validation must be done per wave; otherwise the later December chain contaminates the October row", + "implementation PDFs must be matched back to the correct wave rather than accepting the latest quick-reference page" + ], + "freeze": { + "historical_window": "the 2020-10 and 2020-12 Debt Collection Rule final-rule waves, their linked 2020 proposal pages, the 2021 delayed-effective-date proposal, and the current implementation-page quick-reference PDFs" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "必须分别处理 2020 年两波同名的 Debt Collection Practices (Regulation F) final rules，而不是合并成一条。", + "对每一波都要分别确认：发布日期、对应 proposal chain 及公众意见截止日、2021 年 delayed-effective-date proposed rule 是否覆盖及其截止日、最终生效日、对应 implementation quick-reference PDF，以及该 PDF 跳过引言后的第一个小标题。", + "October wave 与 December wave 的 detail page、proposal chain 和 summary PDF 都必须各自独立核验。" + ], + "exclusion_conditions": [ + "排除把两条同名 2020 final rule 合并为一条的结果。", + "排除把 December wave 的 proposal chain 或 executive-summary heading 投射给 October wave 的结果。", + "排除未单独回到各自 final-rule detail page 和对应 PDF 核验的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "wave", + "final-rule-date", + "proposal-chain", + "proposal-comment-closes", + "delay-proposal-applied", + "delay-proposal-comments-close", + "controlling-effective-date", + "quick-reference-pdf", + "summary-heading" + ], + "wave": "wave is the final-rule issue month in YYYY-MM", + "date_format": "all standalone date fields use YYYY-MM-DD", + "proposal_chain": "canonical chain joins proposal milestones with `+`, using pieces such as `2019-05-07 main` or `2020-02-21 supplemental` in chronological order", + "proposal_comment_closes": "join multiple comment-close dates with `+` in the same order as proposal_chain", + "delay_proposal_applied": "emit `YES` when a delay proposal is part of the chain; otherwise emit `NO`", + "quick_reference_pdf": "use the displayed quick-reference PDF title, not the filename", + "summary_heading": "use the first substantive heading from the final-rule PDF", + "sorting_or_selection": "final-rule-date ascending" + } + } +} diff --git a/data_zh/constraint/consumerfinance_004.json b/data_zh/constraint/consumerfinance_004.json new file mode 100644 index 0000000000000000000000000000000000000000..671b6a3042926922c83b313d33cb359a41a7c396 --- /dev/null +++ b/data_zh/constraint/consumerfinance_004.json @@ -0,0 +1,68 @@ +{ + "task_id": "consumerfinance_004", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我想在 CFPB 的执法案件页面里，分别为 信用卡业务（Credit Cards）和存款业务（Deposits） 这两个业务类别找出 2024 年立案、并且后来已经结束的行政执法案件，再把它的终止令和原始的和解令（Consent Order）之间对应到的条款信息整理出来。具体来说，先把查找范围限定在 CFPB 的执法案件页面（Enforcement actions）里的行政执法案件，并且只看那些初始立案日期落在 2024-01-01 到 2024-12-31 之间的案件。然后，分别对信用卡业务（Credit Cards）和存款业务（Deposits）这两个业务类别进行筛选。对每一个类别，只保留那些同时满足以下条件的案件：案件页面显示这个案子后来已经结束，状态是 已失效、已终止 或 已撤销之一；案件页面同时提供这四类材料：和解令（Consent Order）、协议文件（Stipulation）、终止和解令（Order Terminating the Consent Order） 和 新闻稿（Press release）；页面中的业务类别只列出一个项目，而且这个唯一的项目正好就是你当前正在找的那个类别本身。也就是说，如果你在找信用卡业务（Credit Cards），那页面里就只能标这一项，不能再同时标别的类别；找存款业务（Deposits）时也是同样的要求。在完成筛选之后，每个业务类别下面可能还会剩下不止一件案件。对于每个类别，你只保留其中最新立案的那一件，如果还有多件案件的立案日期相同，就选择案号更小的那一件。接下来，打开你选中的这件案件对应的终止和解令（Order Terminating the Consent Order），从中记录以下三项信息：这份文件上的终止日期；文件中那段说明“依据什么法律授权来终止这份和解令”的话，也就是终止依据（termination authority），并且只记录它第一次出现时的原文；这段终止依据第一次出现所在的 PDF 物理页码。同时，在这份终止令正文里，找到它第一次明确引用到的原始 Consent Order paragraph 编号；如果写成 “Paragraphs X and Y”，就只取 X。然后，再回到这起案件的原始和解令 Consent Order 文件中，找到这个 paragraph 所在的位置，并记下它所属的小节标题。", + "start_url": "https://www.consumerfinance.gov/enforcement/actions/", + "output_format": "最后，请按产品名字母顺序输出一行字符串：||||||p||如果某个产品没有符合条件的案件，就输出：|NONE", + "oracle_answer": "Credit Cards|Apple Inc.|2024-CFPB-0012|2024-10-23|2025-09-22|12 U.S.C. § 5563(b)(3)|p1|83|ADMINISTRATIVE PROVISIONS,Deposits|Navy Federal Credit Union|2024-CFPB-0014|2024-11-07|2025-07-01|12 U.S.C. § 5563(b)(3)|p1|106|ADMINISTRATIVE PROVISIONS", + "metadata": { + "State-Gated Retrieval": [ + "只看 2024 年 Initial filing date 的 administrative enforcement actions，并分别在 Credit Cards 与 Deposits 类别中找案件。", + "案件必须状态为已失效、已终止或已撤销之一，并且页面同时提供 Consent Order、Stipulation、Order Terminating the Consent Order 和 Press release，且 Products 与目标类别一对一对应。", + "最终每个类别只保留按 Initial filing date 判定为最新的合格案件，并整理终止令与原始 Consent Order 的对应条款信息。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "enforcement-action list pages yield 2024 candidate actions by product branch", + "each action detail page and linked Consent Order / Stipulation / Order Terminating the Consent Order / Press release documents yield status, initial filing date, single-product validity, and clause references", + "final rows are selected only after per-product comparison on Initial filing date and document-stack validation" + ], + "control_dependency": [ + "\"latest\" must be determined by Initial filing date rather than termination date", + "product filters on the list page are insufficient until the action detail page confirms a single matching product", + "clause extraction in the terminating order must stay aligned with the original Consent Order rather than a superficially similar section" + ], + "freeze": { + "historical_window": "administrative enforcement actions with Initial filing date from 2024-01-01 through 2024-12-31; current action status and currently linked Consent Order / Stipulation / terminating-order / Press release documents" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只看 2024 年 Initial filing date 的 administrative enforcement actions，并分别在 Credit Cards 与 Deposits 类别中找案件。", + "案件必须状态为已失效、已终止或已撤销之一，并且页面同时提供 Consent Order、Stipulation、Order Terminating the Consent Order 和 Press release，且 Products 与目标类别一对一对应。", + "最终每个类别只保留按 Initial filing date 判定为最新的合格案件，并整理终止令与原始 Consent Order 的对应条款信息。" + ], + "exclusion_conditions": [ + "排除用 termination date 而不是 Initial filing date 来判定“最新”的结果。", + "排除文档栈不完整或 Products 不是单一目标类别的案件。", + "排除无法在 terminating order 与原始 Consent Order 之间建立题目要求条款对应关系的案件。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Product", + "Respondent", + "Docket", + "InitialFilingDate", + "TerminationDate", + "TerminationAuthority", + "TermAuthorityPage", + "ReferencedParagraph", + "ConsentSectionHeading" + ], + "product_order": "alphabetical by Product name", + "fallback_row": "if a product has no qualifying case, emit `|NONE`", + "date_format": "InitialFilingDate and TerminationDate use YYYY-MM-DD", + "termination_authority": "use the canonical statute string extracted from the termination order", + "page_fields": "TermAuthorityPage uses the canonical `pN` form", + "ReferencedParagraph": "emit the paragraph number as a plain numeric string", + "ConsentSectionHeading": "emit the uppercase heading of the consent-order section containing the referenced paragraph" + } + } +} diff --git a/data_zh/constraint/consumerfinance_005.json b/data_zh/constraint/consumerfinance_005.json new file mode 100644 index 0000000000000000000000000000000000000000..70c0cc107b4364275fff46c2f5a8ab8a43737def --- /dev/null +++ b/data_zh/constraint/consumerfinance_005.json @@ -0,0 +1,75 @@ +{ + "task_id": "consumerfinance_005", + "domain": "CFPB_COMPLAINT_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我在做一份历史投诉簇的内部 outreach memo，想追踪一组比较特殊的投诉：在 CFPB Complaint Database 里，找出当前那个覆盖 credit reporting 和其他 personal consumer reports 的产品桶下、2018-01-01 到 2021-12-31 之间、标签是 Servicemember、有公开 narrative、并且文本里明确提到 medical bills 或 doctors 的投诉。请给我两条代表性投诉簇：第一条是这个 cohort 的峰值月份；第二条是这个 cohort 里最新、且投诉量仍至少达到峰值一半的月份。对每条投诉簇，请告诉我该月的总投诉量、该月投诉量最高的州及其投诉量、在这个州里该月投诉量最高的公司及其投诉量、以及这家公司在这个州和这个月里最早收到的那条投诉的编号、日期、Issue 和 Sub-issue。请按 Peak 在前、LatestHalfPeak 在后输出一行字符串：||||||||||。", + "start_url": "https://www.consumerfinance.gov/data-research/consumer-complaints/", + "output_format": "请按 Peak 在前、LatestHalfPeak 在后输出一行字符串：||||||||||。Peak 簇与 LatestHalfPeak 簇用英文逗号连接；若存在并列，月份按时间顺序判定，州按州缩写字母序升序取首位，公司按公司名称字母序升序取首位，最早投诉若同日并列则取 Complaint ID 最小者。", + "oracle_answer": "Peak|2018-02|46|CA|28|TRANSUNION INTERMEDIATE HOLDINGS, INC.|9|2806154|2018-02-07|Improper use of your report|Reporting company used your report improperly,LatestHalfPeak|2021-11|23|CA|12|EQUIFAX, INC.|3|4928768|2021-11-19|Problem with a credit reporting company's investigation into an existing problem|Their investigation did not fix an error on your report", + "metadata": { + "State-Gated Retrieval": [ + "只看当前 product bucket 下 credit reporting / other personal consumer reports 相关产品中，2018-01-01 至 2021-12-31、标签为 Servicemember、带公开 narrative 且文本明确提到 medical bills 或 doctors 的投诉。", + "第一条 cluster 必须是该 cohort 的 peak month；第二条 cluster 必须是该 cohort 中最新且投诉量仍至少达到峰值一半的月份。", + "对每个 cluster，都必须在对应的 month + state 子集中重算 TopCompany，再定位该公司在该州该月最早收到的 complaint。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current complaint-form taxonomy yields the product bucket that contains credit reporting / other personal consumer reports", + "filtered complaint records yield month counts, month-state subsets, top companies, and earliest complaint details inside each chosen subset", + "final rows are produced only after peak month and latest-half-peak month are determined, and each downstream aggregate is computed inside its narrower month-state cohort" + ], + "control_dependency": [ + "the latest month must be defined as the latest month whose count is at least ceil(PeakCount / 2)", + "overall top-company counts cannot be projected into a month-state subset without recomputation", + "earliest complaint selection is only valid after the month, state, and company filters are all frozen" + ], + "freeze": { + "historical_window": "Complaint Database records received from 2018-01-01 through 2021-12-31 under the current product-bucket mapping for the credit-reporting / other personal consumer reports family; Servicemember + public narrative + medical bills/doctors text cohort" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只看当前 product bucket 下 credit reporting / other personal consumer reports 相关产品中，2018-01-01 至 2021-12-31、标签为 Servicemember、带公开 narrative 且文本明确提到 medical bills 或 doctors 的投诉。", + "第一条 cluster 必须是该 cohort 的 peak month；第二条 cluster 必须是该 cohort 中最新且投诉量仍至少达到峰值一半的月份。", + "对每个 cluster，都必须在对应的 month + state 子集中重算 TopCompany，再定位该公司在该州该月最早收到的 complaint。" + ], + "exclusion_conditions": [ + "排除把“最新有投诉的月份”直接当成第二条 cluster 的结果。", + "排除先在全 cohort 中找 overall top company 再投射到 month-state 子集的结果。", + "排除没有先用 PeakCount 推出 half-peak threshold 的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Cluster", + "Month", + "MonthComplaints", + "TopState", + "StateComplaints", + "TopCompany", + "CompanyComplaints", + "EarliestComplaintID", + "EarliestDate", + "Issue", + "SubIssue" + ], + "cluster_order": [ + "Peak", + "LatestHalfPeak" + ], + "date_format": { + "Month": "YYYY-MM", + "EarliestDate": "YYYY-MM-DD" + }, + "TopState": "use the uppercase two-letter state abbreviation", + "TopCompany": "use the company display name as shown in the source data", + "tie_breaks": "for tied months use chronological order; for tied states use state-code alphabetical order; for tied companies use company-name alphabetical order; for the earliest complaint use EarliestDate ascending then Complaint ID ascending", + "SubIssue": "emit `NONE` when the complaint row has no sub-issue value" + } + } +} diff --git a/data_zh/constraint/consumerfinance_006.json b/data_zh/constraint/consumerfinance_006.json new file mode 100644 index 0000000000000000000000000000000000000000..d8ddd8dd08356c548f3ac566e5a4684c087e9847 --- /dev/null +++ b/data_zh/constraint/consumerfinance_006.json @@ -0,0 +1,78 @@ +{ + "task_id": "consumerfinance_006", + "domain": "CFPB_COMPLAINT_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我正在撰写一份加密货币投诉“重灾区”分析报告（crypto-complaint concentration memo），为了核实一个固定三年窗口期内的投诉高峰是否仅由少数头部平台拉高，需要你协助我通过 CFPB 投诉数据库按步骤排查并提取相关数据。\n首先，我们需要界定分析的底层数据范围。请先根据 CFPB 当前投诉表单（complaint form）的产品分类口径，确认虚拟货币“Virtual currency”目前归属的产品大类（Product bucket）。在确定确切归属后，需将时间范围严格锁定在 2019-08-26 至 2022-08-26 之间，且仅提取该产品大类下“Virtual currency”子类的投诉记录，以此形成本次分析的初始群体（cohort）。\n其次，我们需要在这个初始群体中推演并锁定两个特征峰值月。第一步，需按月统计整体投诉量，锁定该初始群体在未移除任何公司时的原始峰值月（AllCompanies）。第二步，需精准识别出上述原始峰值月中投诉量最高的前两家公司，并将这两家公司在整个三年初始群体中的所有投诉记录彻底整体移除（不是仅移除单月记录），随后基于这批残余数据重新按月统计，沉淀出剔除头部影响后的残余峰值月（ResidualAfterTop2）。\n再次，针对上述锁定的这两个特征月份，我们需要分别提取详尽的数据。对于这两条投诉簇，除必须获取该月的总投诉量外，还需分别查实被移除的那两家头部巨头公司名称，以及它们在“原始峰值月”中的合计投诉量。同时，需明确该特征月份内投诉量最高的州及其投诉量、该州内被投诉最多的公司及其投诉规模，以及这家公司在该州、该特征月范围内收到的最早一条投诉的完整细节（包含投诉编号、日期、Issue 和 Sub-issue）。\n最后，在完成上述所有维度的排查与信息梳理后，若将提取到的这两组核心参数，严格按照 AllCompanies 在前、ResidualAfterTop2 在后的顺序，拼接成没有任何空格的格式化字符串（每行的字段拼接顺序务必固定为：||||||||||||），最终生成的这组数据记录内容是什么？为保证答案唯一：两条记录按 AllCompanies、ResidualAfterTop2 的顺序输出；ExcludedTop2Companies 按原始峰值月投诉量从高到低排列；如任何排序指标出现并列，则按字段值字母序升序排列；若最早投诉日期并列，则取 Complaint ID 数值最小者。", + "start_url": "https://www.consumerfinance.gov/data-research/consumer-complaints/", + "output_format": "严格按照 AllCompanies 在前、ResidualAfterTop2 在后的顺序，拼接成没有任何空格的格式化字符串。每行的字段拼接顺序务必固定为：||||||||||||。", + "oracle_answer": "AllCompanies|2021-05|336|Coinbase, Inc.+BAM Management US Holdings Inc.|226|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,ResidualAfterTop2|2020-06|180|Coinbase, Inc.+BAM Management US Holdings Inc.|226|OH|28|PNC Bank N.A.|22|3687376|2020-06-07|Other transaction problem|NONE", + "metadata": { + "State-Gated Retrieval": [ + "只看当前 product bucket 下 Virtual currency 子类、接收日期在 2019-08-26 至 2022-08-26 的 Complaint Database 记录。", + "先确定 AllCompanies 原始峰值月，再识别该峰值月中投诉量最高的前两家公司。", + "这两家公司必须从整个三年 cohort 中整体移除，然后基于残余 cohort 重新计算 residual peak month 及所有 downstream 字段。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current complaint-form taxonomy yields the product bucket for Virtual currency", + "complaint records within the fixed three-year cohort yield the all-company peak month, per-month top companies, and residual-cohort recomputations after company removal", + "final rows are produced only after the top-2 companies from the original peak month are removed from the full cohort and downstream aggregates are computed on the resulting cohort" + ], + "control_dependency": [ + "peak-month top companies must be removed from the entire cohort, not only from the original peak month", + "residual peak detection must be computed from the rewritten cohort rather than by local patching of the original month", + "downstream state / company / earliest-complaint fields are valid only after the global company-removal step is locked" + ], + "freeze": { + "historical_window": "Complaint Database records received from 2019-08-26 through 2022-08-26 under the current product-bucket mapping for Virtual currency" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只看当前 product bucket 下 Virtual currency 子类、接收日期在 2019-08-26 至 2022-08-26 的 Complaint Database 记录。", + "先确定 AllCompanies 原始峰值月，再识别该峰值月中投诉量最高的前两家公司。", + "这两家公司必须从整个三年 cohort 中整体移除，然后基于残余 cohort 重新计算 residual peak month 及所有 downstream 字段。" + ], + "exclusion_conditions": [ + "排除只从原始峰值月局部删除 top-2 公司记录的结果。", + "排除没有把 top-2 company set 回写到整个 cohort 后再重算 residual peak 的结果。", + "排除基于未重算残余 cohort 的 downstream 州、公司或 earliest complaint 字段。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Cluster", + "Month", + "MonthComplaints", + "ExcludedTop2Companies", + "ExcludedTop2PeakMonthComplaints", + "TopState", + "StateComplaints", + "TopCompany", + "CompanyComplaints", + "EarliestComplaintID", + "EarliestDate", + "Issue", + "SubIssue" + ], + "cluster_order": [ + "AllCompanies", + "ResidualAfterTop2" + ], + "date_format": { + "Month": "YYYY-MM", + "EarliestDate": "YYYY-MM-DD" + }, + "ExcludedTop2Companies": "join the two excluded company names with `+` in source-peak complaint-count descending order, breaking ties alphabetically", + "TopState": "use the uppercase two-letter state abbreviation", + "TopCompany": "use the company display name as shown in the source data", + "tie_breaks": "for the earliest complaint use EarliestDate ascending then Complaint ID ascending", + "SubIssue": "emit `NONE` when the complaint row has no sub-issue value" + } + } +} diff --git a/data_zh/constraint/consumerfinance_007.json b/data_zh/constraint/consumerfinance_007.json new file mode 100644 index 0000000000000000000000000000000000000000..7747a434bda8862ecdae77b669c84306196b8252 --- /dev/null +++ b/data_zh/constraint/consumerfinance_007.json @@ -0,0 +1,82 @@ +{ + "task_id": "consumerfinance_007", + "domain": "CFPB_COMPLAINT_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "我正在起草一份关于加密货币投诉批次的核心因素逐层分析报告，需要你协助我通过 CFPB 投诉数据库，按步骤验证这波投诉高峰的真实成因。\n首先，我们需要界定分析的底层范围。请根据 CFPB 现行的产品与 Issue 口径文档，确认“Virtual currency”目前归属的产品大类（Product bucket）。在确定归属后，需将时间范围严格锁定在 2020-01-01 至 2022-08-26 之间，且仅针对该产品大类下的“Virtual currency”子类，提取出这个初始投诉群体的原始峰值月份（BaselinePeak）及其总投诉量。\n其次，我们需要通过层层剔除核心影响因素来推演峰值的转移情况。第一轮，需在上述原始峰值月里识别出出现频次最高的“Company public response”取值，并从整个初始群体中彻底移除该取值对应的所有投诉，从而获取重新计算后的第二个峰值月（AfterDominantPublicResponse）。第二轮，需在第二个峰值月里识别出出现频次最高的“Issue”类型，从上一轮残余数据中将其剔除，以锁定第三个涌现出的峰值月（AfterDominantPublicResponseAndIssue）。第三轮，需在第三个峰值月里识别出被投诉最多的单一公司（Company），并在剔除该公司后进行终轮统计，沉淀出最终的残余峰值月（AfterDominantPublicResponseIssueAndCompany）。\n再次，针对上述每一个识别出的特征月份，我们需要提取详尽的数据。对于这四个投诉簇（Cluster），除了必须获取该月总投诉量外，还需分别查实：本轮新增的移除维度及其具体的排除值，以及该排除值在它原本作为“参照来源”的那个月份里出现的次数。同时，还需明确该月份内投诉量最高的州及其投诉量、该州内被投诉最多的公司及其投诉规模，以及该州内投诉量最高的公司在该州、该特征月内收到的最早一条投诉的完整信息（包含投诉编号、日期、Issue 和 Sub-issue）。\n最后，在完成上述所有维度的排查与信息梳理后，若将这四个投诉簇的所有提取参数，严格按照 BaselinePeak、AfterDominantPublicResponse、AfterDominantPublicResponseAndIssue、AfterDominantPublicResponseIssueAndCompany 的先后顺序，分别拼接成四行没有任何空格的字符串（每行字段顺序严格固定为：|||||||||||||），最终生成的这组数据记录内容是什么？若出现并列，一律按字典序升序选择；日期相同的最早投诉，再按 Complaint ID 数值升序选择。所有空值先统一为 NONE 后再排序。", + "start_url": "https://www.consumerfinance.gov/data-research/consumer-complaints/", + "output_format": "严格按照 BaselinePeak、AfterDominantPublicResponse、AfterDominantPublicResponseAndIssue、AfterDominantPublicResponseIssueAndCompany 的先后顺序，分别拼接成四行没有任何空格的字符串；每行字段顺序严格固定为：|||||||||||||。若出现并列，一律按字典序升序选择；日期相同的最早投诉，再按 Complaint ID 数值升序选择。所有空值先统一为 NONE 后再排序。", + "oracle_answer": "BaselinePeak|2021-05|336|NONE|NONE|0|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,AfterDominantPublicResponse|2022-07|31|Company public response|NONE|321|CA|6|BANK OF AMERICA, NATIONAL ASSOCIATION|4|5735227|2022-07-05|Other transaction problem|NONE,AfterDominantPublicResponseAndIssue|2021-10|13|Issue|Fraud or scam|26|TX|2|BANK OF AMERICA, NATIONAL ASSOCIATION|1|4821611|2021-10-18|Other transaction problem|NONE,AfterDominantPublicResponseIssueAndCompany|2021-06|8|Company|Foris DAX, Inc.|5|NC|3|TRUIST FINANCIAL CORPORATION|2|4462160|2021-06-15|Money was not available when promised|NONE", + "metadata": { + "State-Gated Retrieval": [ + "只看当前 product bucket 下 Virtual currency 子类、接收日期在 2020-01-01 至 2022-08-26 的 Complaint Database 记录。", + "按题目要求依次确定 BaselinePeak、AfterDominantPublicResponse、AfterDominantIssue、AfterDominantCompany 四个阶段的峰值月。", + "每一轮识别出的 dominant Company public response、dominant Issue、dominant Company，都必须回写到对应上游 residual cohort 中整体删除后，再重跑下一轮统计。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current complaint-form taxonomy yields the product bucket for Virtual currency", + "complaint records yield the baseline peak plus the dominant Company public response, dominant Issue, and dominant Company at successive residual-peak states", + "final rows are produced only after each dominant value is applied to the full upstream residual cohort and then used to determine the next peak" + ], + "control_dependency": [ + "dominant values found in a peak month cannot be deleted only inside that month; each must be propagated to the full upstream cohort", + "each new residual peak depends on the prior round's global rewrite, so local month-by-month deletion gives the wrong chain", + "downstream counts and exemplar complaints are valid only after the full three-stage waterfall is executed" + ], + "freeze": { + "historical_window": "Complaint Database records received from 2020-01-01 through 2022-08-26 under the current product-bucket mapping for Virtual currency" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只看当前 product bucket 下 Virtual currency 子类、接收日期在 2020-01-01 至 2022-08-26 的 Complaint Database 记录。", + "按题目要求依次确定 BaselinePeak、AfterDominantPublicResponse、AfterDominantIssue、AfterDominantCompany 四个阶段的峰值月。", + "每一轮识别出的 dominant Company public response、dominant Issue、dominant Company，都必须回写到对应上游 residual cohort 中整体删除后，再重跑下一轮统计。" + ], + "exclusion_conditions": [ + "排除只在当前峰值月局部删记录、没有回写到整个上游 cohort 的结果。", + "排除没有在每一轮 residual cohort 上重新寻找下一峰值月的结果。", + "排除基于未整体重跑 downstream 统计得到的中间或最终字段。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Cluster", + "Month", + "MonthComplaints", + "NewExclusionType", + "NewExclusionValue", + "NewExclusionCountInSourcePeak", + "TopState", + "StateComplaints", + "TopCompany", + "CompanyComplaints", + "EarliestComplaintID", + "EarliestDate", + "Issue", + "SubIssue" + ], + "cluster_order": [ + "BaselinePeak", + "AfterDominantPublicResponse", + "AfterDominantPublicResponseAndIssue", + "AfterDominantPublicResponseIssueAndCompany" + ], + "date_format": { + "Month": "YYYY-MM", + "EarliestDate": "YYYY-MM-DD" + }, + "NewExclusionType": "emit the canonical exclusion-type label from the source workflow; when no new exclusion is applied, emit `NONE`", + "NewExclusionValue": "emit the canonical excluded value; when no value exists, emit `NONE`", + "TopState": "use the uppercase two-letter state abbreviation", + "TopCompany": "use the company display name as shown in the source data", + "tie_breaks": "normalize empty values to `NONE` before sorting; for other ties use lexicographic order ascending, and for the earliest complaint use EarliestDate ascending then Complaint ID ascending", + "SubIssue": "emit `NONE` when the complaint row has no sub-issue value" + } + } +} diff --git a/data_zh/constraint/europemc_001.json b/data_zh/constraint/europemc_001.json new file mode 100644 index 0000000000000000000000000000000000000000..542ffcaaff2732a871fff5f44b468accde1d6991 --- /dev/null +++ b/data_zh/constraint/europemc_001.json @@ -0,0 +1,67 @@ +{ + "task_id": "europemc_001", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 21, + "instruction": "我想把这篇 2020 年 COVID‑19 死亡风险预测论文里几套预测方案实际用到的入院变量统一整理成一行，方便看清哪些变量彼此重叠，哪些只出现在对照方案里。\n请按下面的步骤来查。先找到目标论文——这是一篇 2020 年的、全文可以免费看到的综述，标题同时包含 prognosis model、mortality risk、COVID‑19，正文讨论的是 Wuhan 的住院患者。\n然后只整理两类变量：
第一类，是同时出现在 Random Forest 和 XGBoost 变量重要性排序中的入院变量；
第二类，是没有同时进入这两份排序、但出现在作者用来对照的 CURB‑65 或 NEWS 里的额外入院变量。\n接着，对每个要保留的变量，按下面的格式记录：
变量~RF位次或0~XGB位次或0~F~C~N~X\n各项的意思是：\n\t•\tRF位次：这个变量在 Random Forest 排序中的名次；如果没有进入，就写 0；\n\t•\tXGB位次：这个变量在本文用于排序的 XGBoost 排序中的名次；如果没有进入，就写 0；\n\t•\tF：这个变量是否进入了作者最后的逻辑回归模型；\n\t•\tC：这个变量是否属于 CURB‑65；\n\t•\tN：这个变量是否属于 NEWS；\n\t•\tX：这个变量是否属于文中拿来做对照的那套 XGBoost 模型。\n最后，请把所有变量按变量名字母序排列，并用 | 连接成一行；如果找不到这篇论文，就输出 NONE。", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "接着，对每个要保留的变量，按下面的格式记录：
变量~RF位次或0~XGB位次或0~F~C~N~X\n各项的意思是：\n\t•\tRF位次：这个变量在 Random Forest 排序中的名次；如果没有进入，就写 0；\n\t•\tXGB位次：这个变量在本文用于排序的 XGBoost 排序中的名次；如果没有进入，就写 0；\n\t•\tF：这个变量是否进入了作者最后的逻辑回归模型；\n\t•\tC：这个变量是否属于 CURB‑65；\n\t•\tN：这个变量是否属于 NEWS；\n\t•\tX：这个变量是否属于文中拿来做对照的那套 XGBoost 模型。\n最后，请把所有变量按变量名字母序排列，并用 | 连接成一行；如果找不到这篇论文，就输出 NONE。", + "oracle_answer": "Age~4~2~1~1~0~0|Alanine aminotransferase~17~11~0~0~0~0|Aspartate transaminase~6~4~0~0~0~0|Blood urea nitrogen~5~7~0~1~0~0|Confusion~0~0~0~1~1~0|CRP~2~6~1~0~0~1|Creatinine~9~13~0~0~0~0|Diastolic pressure~16~17~0~1~0~0|Heart rate~15~14~0~0~1~0|LDH~1~1~1~0~0~1|Lymphocyte count~3~5~0~0~0~1|Monocytes~12~16~0~0~0~0|Neutrophil~7~3~0~0~0~0|Normal platelet~10~9~0~0~0~0|Oxygen inhalation~0~0~0~0~1~0|Respiratory rate~11~10~0~1~1~0|SPO2~0~0~0~0~1~0|Systolic pressure~13~12~0~1~1~0|Temperature~18~18~0~0~1~0|Total bilirubin~14~15~0~0~0~0|White blood cell~8~8~0~0~0~0", + "metadata": { + "State-Gated Retrieval": [ + "先找到那篇 2020 年、全文可免费获取、标题同时包含 prognosis model、mortality risk、COVID-19，且正文讨论 Wuhan 住院患者的目标论文。", + "只保留两类变量：同时进入 Random Forest 与 XGBoost 排序的入院变量；或虽未同时进入这两份排序，但属于 CURB-65 或 NEWS 额外变量的对照项。", + "每个变量都要按题目要求标注 RF rank、XGB rank、以及是否属于最终逻辑回归、CURB-65、NEWS、对照 XGBoost，并按变量名字母序输出。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Europe PMC search results and the target open-access article yield the candidate Wuhan COVID mortality-risk review", + "article tables and discussion sections yield RF/XGBoost rankings, final logistic-regression inclusion, and comparator-variable memberships for CURB-65 / NEWS / external XGBoost", + "final rows are produced only after overlapping variables and comparator-only variables are merged into one normalized variable table" + ], + "control_dependency": [ + "comparator-only variables must be captured from the discussion definitions rather than from Table 2 + Table 3 alone", + "comparator membership must be read from the article's explicit scheme definitions rather than inferred from common clinical usage", + "variable normalization must wait until RF/XGBoost overlap and comparator-only additions are both complete" + ], + "freeze": { + "historical_window": "the 2020 open-access COVID-19 mortality-risk review about Wuhan inpatients; variable inclusion and comparator definitions are taken from the article's current full-text tables and discussion" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先找到那篇 2020 年、全文可免费获取、标题同时包含 prognosis model、mortality risk、COVID-19，且正文讨论 Wuhan 住院患者的目标论文。", + "只保留两类变量：同时进入 Random Forest 与 XGBoost 排序的入院变量；或虽未同时进入这两份排序，但属于 CURB-65 或 NEWS 额外变量的对照项。", + "每个变量都要按题目要求标注 RF rank、XGB rank、以及是否属于最终逻辑回归、CURB-65、NEWS、对照 XGBoost，并按变量名字母序输出。" + ], + "exclusion_conditions": [ + "排除没有同时进入 RF 和 XGB、且也不属于 CURB-65 / NEWS 额外变量的入院变量。", + "排除停在 Table 2 + Table 3、不继续到 discussion 读取 comparator 定义的结果。", + "排除凭常识推断 comparator 变量、而不是按论文显式定义核验的结果。" + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "variable", + "RF_rank_or_0", + "XGB_rank_or_0", + "F", + "C", + "N", + "X" + ], + "variable": "use the variable wording normalized in the article tables; keep `Systolic pressure` and `Diastolic pressure` as separate variables", + "rank_fields": "RF_rank_or_0 and XGB_rank_or_0 are positive integer ranks when present, otherwise 0", + "boolean_fields": "F, C, N, and X are emitted as 1 or 0 only", + "sorting_or_selection": "variable name alphabetical ascending", + "stop_condition": [ + "the shared variable set from Table 2 and Table 3 is fully resolved", + "the comparator definitions for CURB-65, NEWS, and the comparison XGBoost model are fixed before the final line is emitted" + ] + } + } +} diff --git a/data_zh/constraint/europemc_002.json b/data_zh/constraint/europemc_002.json new file mode 100644 index 0000000000000000000000000000000000000000..aa0ae60c2c475ffa7a5f81a754f82a893e0347c9 --- /dev/null +++ b/data_zh/constraint/europemc_002.json @@ -0,0 +1,62 @@ +{ + "task_id": "europemc_002", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 6, + "instruction": "我想按 ClinicalTrials.gov 编号追踪 2021 年阿尔茨海默病药物研发综述里处于 Phase 1 的研究，看看它们在 2022 和 2023 年同系列综述中是否还能连续找到。\n请按下面的步骤来查。先找到这三篇文章：2021 年那篇《Alzheimer's disease drug development pipeline》，以及 2022 年和 2023 年同系列的、全文可以免费获取的综述。\n然后在 2021 年那篇综述里，只保留当时被列为 Phase 1 的研究。
接着，再到 2022 年和 2023 年那两篇综述里逐一核对这些研究，但必须按同一个 ClinicalTrials.gov 编号来匹配，不要只根据药物名称判断，因为药物名称在不同年份里可能会变化。\n最后，只保留那些在 2022 和 2023 两年里都还能按同一个 ClinicalTrials.gov 编号继续找到的研究，并把结果整理成一行，格式写成：
NCT号
~2021药名~
2022阶段
~2022药名~
2023阶段~2023药名
按 NCT 号升序排列，并用 | 连接；如果找不到这组三篇论文，就输出 NONE。", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "最后，只保留那些在 2022 和 2023 两年里都还能按同一个 ClinicalTrials.gov 编号继续找到的研究，并把结果整理成一行，格式写成：
NCT号
~2021药名~
2022阶段
~2022药名~
2023阶段~2023药名
按 NCT 号升序排列，并用 | 连接；如果找不到这组三篇论文，就输出 NONE。", + "oracle_answer": "NCT03277573~Salsalate~P1~Salsalate~P1~Salsalate|NCT03634007~AAVrh.10hAPOE2~P1~LX1001~P2~LX1001|NCT03748303~Allopregnanolone (Allo)~P1~Allopregnanolone~P1~Allopregnanolone|NCT04149860~Lu AF87908~P1~Lu AF87908~P1~Lu AF87908|NCT04451408~LY3372993~P1~LY3372993~P1~LY3372993|NCT04500847~Emtricitabine~P1~Emtricitabine~P1~Emtricitabine", + "metadata": { + "State-Gated Retrieval": [ + "只以 2021 年 Alzheimer's disease drug development pipeline 文章中 Phase 1 的研究作为基线。", + "2022 年和 2023 年是否继续保留，必须按同一个 ClinicalTrials.gov NCT 编号精确匹配，而不是只看药物名。", + "最终只保留在 2022 和 2023 两年里都还能按同一 NCT 找到的研究，并按 NCT 升序输出。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2021, 2022, and 2023 pipeline reviews yield the 2021 Phase 1 baseline cohort and the later-year lookup tables", + "article tables yield exact ClinicalTrials.gov NCT IDs, yearly phase labels, and yearly drug names for the same study", + "final rows are produced only after 2021 baseline studies are re-identified in both later reviews by exact NCT matching" + ], + "control_dependency": [ + "continuation must be matched by exact NCT rather than by drug name, because drug names drift across years", + "2022 and 2023 lookups must use the fixed 2021 Phase 1 NCT set as the starting cohort rather than later-year table membership alone", + "yearly phase/name fields are only valid after the same NCT is confirmed across all three reviews" + ], + "freeze": { + "historical_window": "the 2021, 2022, and 2023 open-access Alzheimer's disease drug development pipeline reviews; the baseline is the 2021 Phase 1 cohort and continuation is matched by exact ClinicalTrials.gov NCT" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只以 2021 年 Alzheimer's disease drug development pipeline 文章中 Phase 1 的研究作为基线。", + "2022 年和 2023 年是否继续保留，必须按同一个 ClinicalTrials.gov NCT 编号精确匹配，而不是只看药物名。", + "最终只保留在 2022 和 2023 两年里都还能按同一 NCT 找到的研究，并按 NCT 升序输出。" + ], + "exclusion_conditions": [ + "排除只凭药物名称延续、没有按同一 ClinicalTrials.gov 编号精确匹配的结果。", + "排除只在 2022 或只在 2023 中找到、未同时连续保留的研究。", + "排除不属于 2021 基线 Phase 1 集合的研究。" + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "NCT", + "agent_2021", + "phase_2022", + "agent_2022", + "phase_2023", + "agent_2023" + ], + "NCT": "use the exact ClinicalTrials.gov identifier as the cross-year identity key", + "phase_fields": "normalize phases to P1, P2, or P3; if the same NCT appears multiple times in a year, keep the highest phase for that year", + "agent_fields": "keep the agent text as shown in each year-specific table", + "sorting_or_selection": "NCT ascending" + } + } +} diff --git a/data_zh/constraint/europemc_003.json b/data_zh/constraint/europemc_003.json new file mode 100644 index 0000000000000000000000000000000000000000..b5a965e6f436ff1fbac27969a7baca2b0cc38e45 --- /dev/null +++ b/data_zh/constraint/europemc_003.json @@ -0,0 +1,63 @@ +{ + "task_id": "europemc_003", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "我想看看 2023 年《Antibodies to Watch》里被预测会在 2022–2023 提交首次上市申请的那批候选分子，在 2024 年同系列文章里哪些真的已经获批或进入了首次监管审评。\n请按下面的步骤来查。先在 Europe PMC 里找到 2023 和 2024 两篇同系列的《Antibodies to Watch》开放获取的全文。\n然后在 2023 年那篇文章里，找出所有被列为**\"预计会在 2022–2023 提交首次上市申请\"**的候选分子。
接着，再到 2024 年那篇同系列文章里逐一核对这批分子，只保留那些已经获批，或已进入首次监管审评的。\n最后，把每个符合条件的分子写成下面这个格式：
INN~2023类别~2023预测标签~2024状态~2024适应证~2024地区\n其中：\n\t•\t2023类别 用 NC/CA 表示 非癌症 / 癌症；\n\t•\t2024状态 用 A/R 表示 首次获批 / 首次监管审评中。\n请按 INN 字母序排列，并用 | 连接成一行输出；如果找不到这两篇论文，就输出 NONE。", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "最后，把每个符合条件的分子写成下面这个格式：
INN~2023类别~2023预测标签~2024状态~2024适应证~2024地区\n其中：\n\t•\t2023类别 用 NC/CA 表示 非癌症 / 癌症；\n\t•\t2024状态 用 A/R 表示 首次获批 / 首次监管审评中。\n请按 INN 字母序排列，并用 | 连接成一行输出；如果找不到这两篇论文，就输出 NONE。", + "oracle_answer": "Cosibelimab~CA~MAA,Q2 2023~R~Squamous cell carcinoma~US|Elranatamab~CA~2023~A~Multiple myeloma~US,EU,Switzerland,Brazil|Garadacimab~NC~BLA,2023~R~Hereditary angioedema~EU|Odronextamab~CA~BLA,H2 2022~R~Diffuse large B-cell lymphoma~US,EU|Pozelimab~NC~BLA,H2 2022~A~CHAPLE disease~US|Suciraslimab~NC~NDA,2023~R~Rheumatoid arthritis~China|Talquetamab~CA~2023–25~A~Multiple myeloma~US,EU,UK,Switzerland|Zolbetuximab~CA~BLA,2023~R~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China", + "metadata": { + "State-Gated Retrieval": [ + "先在 2023 年 Antibodies to Watch 中找出所有被预测会在 2022-2023 提交首次上市申请的候选分子。", + "再在 2024 年同系列文章里逐一核对这些分子，只保留已经首次获批，或已进入首次监管审评的候选。", + "2024 状态必须区分 A=首次获批 与 R=首次监管审评中，并补充 2024 适应证和地区。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2023 Antibodies to Watch article yields the forecast baseline of candidates expected to file in 2022-2023", + "the 2024 article tables yield first-approval outcomes, first-regulatory-review outcomes, indications, and regions for the same INNs", + "final rows are produced only after Table 1 approvals and Table 2 first-review candidates are merged back onto the 2023 forecast cohort" + ], + "control_dependency": [ + "both 2024 Table 1 and Table 2 must be read so that first-review-but-not-yet-approved candidates are retained", + "2024 status coding must distinguish approval from first regulatory review instead of collapsing both into a single positive match", + "region and indication fields are valid only after the 2023 forecast cohort is reconciled against both 2024 tables" + ], + "freeze": { + "historical_window": "the 2023 and 2024 open-access Antibodies to Watch articles; baseline candidates come from the 2023 forecast set and 2024 outcomes come from current Table 1 plus Table 2" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先在 2023 年 Antibodies to Watch 中找出所有被预测会在 2022-2023 提交首次上市申请的候选分子。", + "再在 2024 年同系列文章里逐一核对这些分子，只保留已经首次获批，或已进入首次监管审评的候选。", + "2024 状态必须区分 A=首次获批 与 R=首次监管审评中，并补充 2024 适应证和地区。" + ], + "exclusion_conditions": [ + "排除只在 2024 Table 1 中查 approvals、不继续到 Table 2 补 first regulatory review 候选的结果。", + "排除不在 2023 forecast baseline 中的分子。", + "排除 2024 年既未首次获批、也未进入首次监管审评的候选。" + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "INN", + "category_2023", + "prediction_label_2023", + "status_2024", + "indication_2024", + "region_2024" + ], + "category_2023": "emit `NC` or `CA` exactly", + "prediction_label_2023": "keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H2 2022`", + "status_2024": "emit `A` for first approval and `R` for first regulatory review", + "region_2024": "preserve the raw region string but remove spaces after commas, for example `US,EU`", + "sorting_or_selection": "INN alphabetical ascending" + } + } +} diff --git a/data_zh/constraint/europemc_004.json b/data_zh/constraint/europemc_004.json new file mode 100644 index 0000000000000000000000000000000000000000..457f9ae3485babebdec6d5d861e9e9c7371fb7ed --- /dev/null +++ b/data_zh/constraint/europemc_004.json @@ -0,0 +1,67 @@ +{ + "task_id": "europemc_004", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 9, + "instruction": "我正在评估抗体药物年度 watchlist 预测的准确性，想回头追溯一下 2022 年那批《Antibodies to Watch》里的候选药物是否仅仅是经历了进度的自然延迟，需要你协助我基于 Europe PMC 数据库按步骤梳理出这批候选药物的跨年份状态变化。\n首先，我们需要锁定分析的文献基准与初始候选群体。请在 Europe PMC 中精准定位 2022、2023 和 2024 年发表的三篇《Antibodies to Watch》系列开放获取（Open Access）全文。在找齐这三篇文章的前提下，需从中筛选出一批具有特定延期特征的抗体（INN）：曾以 INN、药物代码、项目名或其他可识别名称在 2022 年的文章中被明确列入“预计即将提交审评”的相关名单，但由于进度滞后，在 2023 年的文章中依然作为候选者留存在当年的 watchlist 里。\n其次，我们需要确认这批连续延期候选药物的最新走向。针对上述锁定出的抗体群体，需查实它们在 2024 年那篇文章里呈现的最终状态，明确查清它们到底是终于获得了首次批准（First approved）、正处于首次审评阶段（In first regulatory review）、继续留在 2024 年的后续 watchlist 中，还是已经从 2024 年的主文名单里彻底消失。\n最后，在完成上述跨年份的文献排查与状态确认后，需要将提取到的参数汇总为特定的格式化单行记录。如果在检索中未能找齐这三篇目标文章，请直接输出 NONE。若已顺利找齐，需将每个符合条件的抗体内部参数按“INN~2022类别~2022阶段~2023预测标签~2024状态~2024阶段或NA~2024适应证或NA~2024地区或NA”的固定顺序进行拼接；随后，将所有排查出的候选药物严格按照 INN 的字母顺序，用“|”符号连接成一行没有任何空格的字符串，最终生成的这组数据台账内容是什么？", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "如果在检索中未能找齐这三篇目标文章，请直接输出 NONE。若已顺利找齐，需将每个符合条件的抗体内部参数按“INN~2022类别~2022阶段~2023预测标签~2024状态~2024阶段或NA~2024适应证或NA~2024地区或NA”的固定顺序进行拼接；随后，将所有排查出的候选药物严格按照 INN 的字母顺序，用“|”符号连接成一行没有任何空格的字符串。", + "oracle_answer": "Apamistamab-I-131~CA~P3~BLA,H1 2023~F~P3~Ablation of bone marrow prior to transplantation in AML patients~NA|Bentracimab~NC~P3~BLA,Q4 2022~F~P3~Reversal of the antiplatelet effects of ticagrelor~NA|Cosibelimab~CA~P3~MAA,Q2 2023~R~NA~Squamous cell carcinoma~US|Erfonrilimab~CA~P3~NDA~F~P3~Pancreatic ductal adenocarcinoma~NA|Odronextamab~CA~P2~BLA,H2 2022~R~NA~Diffuse large B-cell lymphoma~US,EU|Talquetamab~CA~P2~2023-25~A~NA~Multiple myeloma~US,EU,UK,Switzerland|Tiragolumab~CA~P3~2023~F~P3~NSCLC~NA|Zanidatamab~CA~P2~2023~D~NA~NA~NA|Zolbetuximab~CA~P3~BLA,2023~R~NA~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China", + "metadata": { + "State-Gated Retrieval": [ + "先以 2022 年 Antibodies to Watch 中“预计即将提交审评”的候选为基线，但只保留在 2023 年同系列中仍然作为 watchlist 候选保留的分子。", + "对这批连续延期候选，再到 2024 年文章中确定其最终状态：首次获批、首次审评中，或在 Tables 1-4 中完全缺席。", + "名称比对时必须处理 Apamistamab 的命名漂移；2024 完全缺席必须显式编码为 D。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2022, 2023, and 2024 Antibodies to Watch articles yield the 2022 soon-to-file baseline, 2023 carry-over membership, and 2024 status tables", + "article tables and full-text naming context yield name normalizations, 2024 table presence/absence, and final status labels for each carried-over INN", + "final rows are produced only after 2022 candidates are filtered by 2023 carry-over status and then resolved against 2024 Tables 1-4 plus explicit absence" + ], + "control_dependency": [ + "2022 candidates must first be filtered by 2023 carry-over status before they are matched against the 2024 tables", + "Apamistamab naming drift forces explicit normalization before 2024 lookup", + "complete 2024 absence must be emitted as D rather than treated as a lookup failure" + ], + "freeze": { + "historical_window": "the 2022, 2023, and 2024 open-access Antibodies to Watch articles; the 2022 baseline is filtered by 2023 carry-over status and then checked against 2024 Tables 1-4, with explicit absence retained as a status" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先以 2022 年 Antibodies to Watch 中“预计即将提交审评”的候选为基线，但只保留在 2023 年同系列中仍然作为 watchlist 候选保留的分子。", + "对这批连续延期候选，再到 2024 年文章中确定其最终状态：首次获批、首次审评中，或在 Tables 1-4 中完全缺席。", + "名称比对时必须处理 Apamistamab 的命名漂移；2024 完全缺席必须显式编码为 D。" + ], + "exclusion_conditions": [ + "排除直接拿 2022 基线去 2024 做字面匹配、未经过 2023 carry-over 过滤的结果。", + "排除未处理 Apamistamab 命名漂移的匹配结果。", + "排除把 2024 完全缺席当成查找失败，而不是一个需要输出的状态。" + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "INN", + "category_2022", + "phase_2022", + "prediction_label_2023", + "status_2024", + "phase_or_NA_2024", + "indication_or_NA_2024", + "region_or_NA_2024" + ], + "category_2022": "emit `NC` or `CA` exactly", + "phase_2022": "normalize stage labels such as `Phase 3` to `P3` and `Pivotal Phase 2` to `P2`", + "prediction_label_2023": "keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H1 2023`", + "status_2024": "emit one of `A`, `R`, `F`, or `D` exactly", + "conditional_fields_2024": "if status is A or R, phase_or_NA_2024 must be `NA` and region_or_NA_2024 must carry the raw region string; if status is F, region_or_NA_2024 is `NA` and phase_or_NA_2024 carries the normalized phase; if status is D, all three trailing 2024 fields are `NA`", + "naming_exception": "preserve the fixed source exception around the Apamistamab-I-131 naming variant instead of over-normalizing the INN", + "sorting_or_selection": "INN alphabetical ascending" + } + } +} diff --git a/data_zh/constraint/europemc_005.json b/data_zh/constraint/europemc_005.json new file mode 100644 index 0000000000000000000000000000000000000000..a6a3990c667b99568bd712f8dccdcbd9c76611bc --- /dev/null +++ b/data_zh/constraint/europemc_005.json @@ -0,0 +1,69 @@ +{ + "task_id": "europemc_005", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 20, + "instruction": "我在整理一份关于 COVID‑19 住院病情预测核心指标跨平台对应关系的核对清单，需要借助 Europe PMC 数据库，按步骤梳理出特定模型实际采用的变量清单及其匹配属性。\n首先，我们需要明确评估的文献基准。请在 Europe PMC 中精准定位到那篇发表于 2024 年的 WHO 全球个体患者数据验证论文，并从中识别出最终真正在低中收入国家数据里成功完成外部验证的 4 个预后模型。在此基础上，需进一步追溯并锁定这 4 个模型所对应的 3 篇原始模型论文。\n锁定这 4 篇目标文献后，下一步的核心工作是提取并核验变量的具体特征。需查清这 4 个模型在实际评估中分别用到了哪些不同的入院变量。针对梳理出的每一个变量，需明确它在 WHO 平台基线表中的获取途径，即是可以直接或实质同名匹配（记为 E），还是需要进行固定的映射转换才能对上（记为 M）。同时，还需追溯这些变量的模型来源属性，查实它们是否归属于在外部验证中表现最强（TopAUC）的模型、校准度最接近理想值（BestCal）的模型，或是来自明确使用了动态数据（Dyn）的原始模型。\n为保证判定口径一致，模型归属、性能归属和变量冲突均以目标文献中可复核的模型描述、性能汇总和字段定义为准；当同一概念存在多种命名或映射方式时，优先采用能够保持跨模型解释一致性的保守映射，并对可能影响解释一致性的映射差异进行标记。\n在完成上述文献追踪与变量特征梳理的基础上，最后需要提取这些参数以生成格式化的单行汇总记录。状态标记方面，所有布尔类型请统一用 1 代表是、0 代表否；如果在检索中未能找齐这 1 篇验证论文和 3 篇原始模型论文，请直接输出 NONE。若已顺利找齐，在将所有不同的变量严格按照变量名的字母顺序排布后，把每个变量内部的参数按“变量~类别~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict”的固定顺序进行拼接，最后用“|”符号将所有变量连接成一行没有任何空格的字符串，最终生成的这条标准记录内容是什么？", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "如果在检索中未能找齐这 1 篇验证论文和 3 篇原始模型论文，请直接输出 NONE。若已顺利找齐，在将所有不同的变量严格按照变量名的字母顺序排布后，把每个变量内部的参数按“变量~类别~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict”的固定顺序进行拼接，最后用“|”符号将所有变量连接成一行没有任何空格的字符串。所有布尔类型请统一用 1 代表是、0 代表否。", + "oracle_answer": "Age~DEM~1~1~1~1~Age~E~1~1~1~0|Cancer~COM~0~0~1~0~Cancer~E~1~0~0~0|Chronic kidney disease~COM~0~0~0~1~CKD~M~0~0~0~1|Chronic lung disease~COM~0~0~1~0~Pulmonary disease~M~1~0~0~0|Chronic renal disease~COM~0~0~1~0~CKD~M~1~0~0~1|Coronary heart disease~COM~0~1~0~0~CHD~M~0~0~0~1|Cough~SYM~0~0~1~0~Cough~E~1~0~0~0|Diabetes mellitus~COM~0~0~1~0~Diabetes~M~1~0~0~0|Diarrhea~SYM~0~0~1~0~Diarrhea~E~1~0~0~0|Dyspnea~SYM~0~0~1~0~Dyspnea~E~1~0~0~0|Fever~VIT~0~0~0~1~Body temperature~M~0~0~0~0|Heart disease~COM~0~0~1~0~CHD~M~1~0~0~1|Hypertension~COM~0~1~1~0~Hypertension~E~1~0~0~0|Immunocompromised status~COM~0~0~1~0~Immunosuppression~M~1~0~0~0|O2 saturation~VIT~1~0~0~0~Oxygen saturation~M~0~1~1~0|Respiratory rate~VIT~1~0~0~1~Respiratory rate~E~0~1~1~0|Sex~DEM~0~0~1~0~Men~M~1~0~0~0|Smoking~DEM~1~0~0~0~Smoking~E~0~1~1~1|Smoking status~DEM~0~0~0~1~Smoking~M~0~0~0~1|Systolic blood pressure~VIT~0~0~0~1~Systolic blood pressure~E~0~0~0~0", + "metadata": { + "State-Gated Retrieval": [ + "先在 2024 WHO 全球个体患者数据验证论文中锁定最终在 LMIC 数据中成功完成外部验证的 4 个预后模型，并追溯到对应的 3 篇原始模型论文。", + "对每个 predictor，要保留 WHO Table 1 的原始 wording，并标注它在 WHO 基线表中的匹配方式 E/M，以及是否来自 TopAUC、BestCal、Dyn 模型。", + "遇到 WHO 侧概念合并的 predictor 时，必须回溯 Wang / Zhou 等原始论文拆分后再重算相关字段。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2024 WHO global validation paper yields the four externally validated models and the WHO-side predictor wording/mapping baseline", + "the three original model papers yield model-specific predictor wordings, dynamic-data flags, and conflicts hidden by WHO-side conceptual merging", + "final rows are produced only after WHO predictors are kept separate, traced back to the original papers, and then re-annotated for mapping and model provenance" + ], + "control_dependency": [ + "conceptually merged WHO predictors must be split back out when the original Wang/Zhou papers expose distinct variables", + "Table 2 mapping decisions are not valid until Table 1 wording and original-paper predictor sets are reconciled", + "TopAUC / BestCal / Dyn flags must be determined after the predictor split is applied correctly" + ], + "freeze": { + "historical_window": "the 2024 WHO global IPD validation paper and the three linked original COVID prognosis-model papers, using their current open-access full texts and tables" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先在 2024 WHO 全球个体患者数据验证论文中锁定最终在 LMIC 数据中成功完成外部验证的 4 个预后模型，并追溯到对应的 3 篇原始模型论文。", + "对每个 predictor，要保留 WHO Table 1 的原始 wording，并标注它在 WHO 基线表中的匹配方式 E/M，以及是否来自 TopAUC、BestCal、Dyn 模型。", + "遇到 WHO 侧概念合并的 predictor 时，必须回溯 Wang / Zhou 等原始论文拆分后再重算相关字段。" + ], + "exclusion_conditions": [ + "排除在 WHO Table 1 之后就把概念相近 predictor 直接合并、未回溯原始论文拆分的结果。", + "排除只凭 WHO Table 2 做宽松映射、未结合原始论文 wording 的结果。", + "排除在 predictor 拆分修正前就固定 TopAUC / BestCal / Dyn 标注的结果。" + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "variable", + "category", + "B", + "W", + "Zh", + "Zo", + "WHOfield", + "WHOx", + "TopAUC", + "BestCal", + "Dyn", + "Conflict" + ], + "variable_set": "the candidate variable set comes only from the WHO validation Table 1 and remains at the original 20 predictors", + "conflict_groups": "do not pre-merge the three source conflict groups `Smoking`/`Smoking status`, `Chronic renal disease`/`Chronic kidney disease`, and `Coronary heart disease`/`Heart disease` before applying the conflict flag", + "boolean_fields": "B, W, Zh, Zo, TopAUC, BestCal, Dyn, and Conflict are emitted as 1 or 0 only", + "WHOx": "emit `E` for exact or substantively same-name WHO matches, `M` for the fixed mapped match, and `NA` when no WHO field matches", + "sorting_or_selection": "variable name alphabetical ascending" + } + } +} diff --git a/data_zh/constraint/genome_001.json b/data_zh/constraint/genome_001.json new file mode 100644 index 0000000000000000000000000000000000000000..2a4564e2dccc2b3960901c9c8f1365dcdc6a99fa --- /dev/null +++ b/data_zh/constraint/genome_001.json @@ -0,0 +1,64 @@ +{ + "task_id": "genome_001", + "domain": "KEGG_BRITE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "我在整理一份供院内参考的溃疡性结肠炎用药梳理，想从 KEGG 收录的相关免疫抑制剂中，筛出截至 2025 年 6 月底已在日本获批、且带有明确 CYP 相关代谢信息或 CYP 抑制提示的药物条目。请按以下顺序处理：先以 KEGG 中用于溃疡性结肠炎的免疫抑制剂为范围，筛选截至 2025 年 6 月底前已在日本获批的药物条目；再查看其中是否带有明确的 CYP 相关代谢信息或 CYP 抑制提示，只保留符合条件的条目。随后，记录这些条目在日本治疗分类中的代码、ATC 码、对应的靶点支系，以及日本首次获批日期。最后，请按日本首次获批日期从早到晚输出一行字符串，格式为 ||||；不同条目之间用英文逗号分隔；如无符合条件的条目，则输出 NONE。", + "start_url": "https://www.genome.jp/kegg/brite.html", + "output_format": "请按日本首次获批日期从早到晚输出一行字符串，格式为 ||||；不同条目之间用英文逗号分隔；如无符合条件的条目，则输出 NONE。", + "oracle_answer": "D09783|3999|L04AF01|JAK1/JAK2/JAK3/TYK2|2013/3/25,D11048|3999|L04AF03|JAK1|2020/1/23,D10931|2399|L04AE05|S1PR1/S1PR4/S1PR5|2025/6/24", + "metadata": { + "State-Gated Retrieval": [ + "以 KEGG 中用于溃疡性结肠炎的免疫抑制剂为范围，只保留截至 2025-06-30 已在日本获批、且带有明确 CYP 相关代谢信息或 CYP 抑制提示的条目。", + "候选药物必须在纠正后的 UC drug list 中重新核验日本治疗分类、ATC、靶点支系、CYP 证据和日本首次批准日期。", + "最终按日本首次获批日期从早到晚输出。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "KEGG disease H01466 and linked drug entries yield the ulcerative-colitis immunosuppressant candidate set", + "each candidate drug entry yields Japanese class, ATC, target branch, CYP metabolism/inhibition evidence, and Japan approval date", + "final rows are produced only after the full UC candidate set is determined and every candidate is checked against CYP evidence and PMDA timing" + ], + "control_dependency": [ + "the candidate set must include Japanese class 3999 UC drugs when the disease page exposes them rather than being limited to 2399 alone", + "target / CYP / PMDA validation must be applied across the full candidate set rather than only the old 2399 subset", + "entries without explicit CYP evidence may be dropped only after the full candidate set has been established" + ], + "freeze": { + "historical_window": "KEGG ulcerative-colitis drug candidates with Japan approvals on or before 2025-06-30; current drug-entry annotations provide target, CYP, and Japan-class metadata" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "以 KEGG 中用于溃疡性结肠炎的免疫抑制剂为范围，只保留截至 2025-06-30 已在日本获批、且带有明确 CYP 相关代谢信息或 CYP 抑制提示的条目。", + "候选药物必须在纠正后的 UC drug list 中重新核验日本治疗分类、ATC、靶点支系、CYP 证据和日本首次批准日期。", + "最终按日本首次获批日期从早到晚输出。" + ], + "exclusion_conditions": [ + "排除把上游范围错误锁在 2399 消化器分支、未回退到完整 UC drug list 的结果。", + "排除没有明确 CYP 相关代谢信息或 CYP 抑制提示的条目。", + "排除日本获批日期晚于 2025-06-30 或不属于 KEGG UC 免疫抑制剂范围的条目。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DRUG_ID", + "JP_class", + "ATC", + "Target_branch", + "JP_date" + ], + "dedup_key": "DRUG_ID", + "JP_date": "use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value", + "Target_branch": "emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`", + "sorting_or_selection": { + "primary": "JP_date ascending", + "secondary": "DRUG_ID ascending" + } + } + } +} diff --git a/data_zh/constraint/genome_002.json b/data_zh/constraint/genome_002.json new file mode 100644 index 0000000000000000000000000000000000000000..00f13e9c4e8c8f08ffab7ab4ec888752e780842c --- /dev/null +++ b/data_zh/constraint/genome_002.json @@ -0,0 +1,65 @@ +{ + "task_id": "genome_002", + "domain": "KEGG_GENOME", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我在为学生准备一页介绍经典动物内共生案例的讲义，想在 KEGG 的宿主—共生体示例中找出符合以下条件的那个案例：截至 2005 年底已收录，其细菌共生体基因组含有已命名的额外复制子，且这些复制子的名称在宿主—共生体联合通路图中可直接对应到氨基酸合成模块。请按以下顺序处理：先在 KEGG 的宿主—共生体示例中，按细菌共生体 KEGG GENOME 条目的 Created 年份筛选出 2005 年底前已收录的组合；再保留其细菌共生体基因组中带有已命名额外复制子的案例；随后核对这些复制子名称在宿主—共生体联合通路图中的对应关系，确认其可直接对应到氨基酸合成模块；最后，在该宿主—共生体组合对应的联合通路图范围内，把该案例中所有符合条件的通路—模块列出，并输出一行字符串：|||||（按 pathway 编号升序排列，英文逗号分隔；若无则输出 NONE）。", + "start_url": "https://www.genome.jp/kegg/genome/", + "output_format": "请输出一行字符串：|||||（按 pathway 编号升序排列，英文逗号分隔；若无则输出 NONE）。", + "oracle_answer": "api+buc|buc|00290|M00432|pLeu|2000,api+buc|buc|00400|M00023|pTrp|2000", + "metadata": { + "State-Gated Retrieval": [ + "只保留宿主—共生体示例中，细菌共生体 KEGG GENOME Created 年份不晚于 2005 年底、且其基因组带有已命名额外复制子的案例。", + "这些复制子的名称必须能在宿主—共生体联合 pathway 页面上直接对应到氨基酸合成模块。", + "最终输出 surviving 案例中所有符合条件的 pathway-module-replicon 记录，并按 pathway 编号升序排列。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "KEGG host-symbiont examples and symbiont genome pages yield the pre-2006 candidate pairs and named extra replicons", + "joint pathway maps, module pages, and genome annotations yield the pathway-module-replicon links attributable to the symbiont side", + "final rows are produced only after the surviving host-symbiont pair is validated against both replicon existence and module support on the joint pathway page" + ], + "control_dependency": [ + "only branches satisfying the named-plasmid requirement may be retained, so the bmy+wbm branch must be excluded when the wbm genome page fails that requirement", + "module retrieval must use the api+buc pathway state and the 00400 view, because that view is the one that actually exposes M00023", + "module support is valid only after symbiont-side evidence for both M00023 and M00432 is validated in the selected pathway state" + ], + "freeze": { + "historical_window": "KEGG host-symbiont examples whose symbiont GENOME Created year is on or before 2005; current joint pathway, module, and genome replicon annotations" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只保留宿主—共生体示例中，细菌共生体 KEGG GENOME Created 年份不晚于 2005 年底、且其基因组带有已命名额外复制子的案例。", + "这些复制子的名称必须能在宿主—共生体联合 pathway 页面上直接对应到氨基酸合成模块。", + "最终输出 surviving 案例中所有符合条件的 pathway-module-replicon 记录，并按 pathway 编号升序排列。" + ], + "exclusion_conditions": [ + "排除像 bmy+wbm 这样共生体 genome 页并没有满足命名 plasmid 要求的案例。", + "排除只按 pathway 名称沿 00380 等页面追查、没有回到联合 pathway 面核验 module 证据的结果。", + "排除复制子名称与模块关系不能在联合 pathway 图上直接成立的记录。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "group", + "symbiont", + "pathway", + "module", + "replicon", + "created_year" + ], + "group": "use the canonical host-symbiont group label from the source workflow, such as `api+buc`", + "symbiont": "use the bare lowercase KEGG organism code", + "pathway": "emit the numeric KEGG pathway ID without a `map` prefix", + "module": "normalize the KEGG module identifier to the `Mxxxxx` form", + "replicon": "preserve the named extra replicon exactly as displayed in the source, such as `pLeu` or `pTrp`", + "created_year": "emit the four-digit created year", + "sorting_or_selection": "pathway numeric ascending" + } + } +} diff --git a/data_zh/constraint/genome_003.json b/data_zh/constraint/genome_003.json new file mode 100644 index 0000000000000000000000000000000000000000..a074dd5941ef039da2738145ff6c6f52022ebeb9 --- /dev/null +++ b/data_zh/constraint/genome_003.json @@ -0,0 +1,64 @@ +{ + "task_id": "genome_003", + "domain": "KEGG_BRITE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "我在整理一张日本斑块状银屑病系统用药获批顺序表。请按以下顺序处理：先以截至 2024 年底前已在日本获批、用于斑块状银屑病的系统用药为范围，筛出其中作用于 IL‑17/IL‑23 信号轴的活性成分；再排除所有外用药，以及其他作用轴的系统药物。随后，按这些活性成分在日本的首次批准日期从早到晚排序；如同日获批，则按 DRUG_ID 升序排列。最后，请输出一个多行表，每行格式为 ||||。", + "start_url": "https://www.kegg.jp/brite/br08301", + "output_format": "请输出一个多行表，每行格式为 ||||。", + "oracle_answer": "D09967|Secukinumab|L04AC10|IL17A|2014/12/26\nD10061|Brodalumab|L04AC12|IL17RA|2016/7/4\nD10071|Ixekizumab|L04AC13|IL17A|2016/7/4\nD10438|Guselkumab|L04AC16|IL23A|2018/3/23\nD11052|Risankizumab|L04AC18|IL23A|2019/3/26\nD10400|Tildrakizumab|L04AC17|IL23A|2020/6/29\nD11550|Bimekizumab|L04AC21|IL17A/IL17F|2022/1/20\nD11817|Deucravacitinib|L04AF07|TYK2|2022/9/26", + "metadata": { + "State-Gated Retrieval": [ + "只保留截至 2024-12-31 前已在日本获批、用于斑块状银屑病的系统用药中，真正作用于 IL-17/IL-23 信号轴的活性成分。", + "候选集合必须覆盖 ligand side、receptor side 和 TYK2 kinase side，而不是只看 interleukin ligand 一侧。", + "最终条目按日本首次批准日期升序排列；如同日则按 DRUG_ID 升序。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "KEGG disease/drug entry points yield the Japan-approved systemic plaque-psoriasis drug cohort through 2024-12-31", + "each drug entry yields target branch, ATC, systemic-use validity, and Japan approval date for IL-17/IL-23-axis candidates", + "final rows are produced only after ligand-side, receptor-side, and kinase-side candidates are jointly reconciled and re-sorted by Japan approval date" + ], + "control_dependency": [ + "entry-point coverage must include receptor-side IL17RA and kinase-side TYK2 mechanisms when downstream drug pages expose them, rather than staying ligand-only", + "Ustekinumab must be removed only when target interpretation shows IL12 + IL23A rather than the IL-17/IL-23-axis criterion required here", + "systemic-use, Japanese 3999, and PMDA-date filtering must be applied after each candidate-space expansion rather than attached to the earlier ligand-only state" + ], + "freeze": { + "historical_window": "Japanese plaque-psoriasis systemic drugs approved on or before 2024-12-31; current KEGG drug-entry annotations supply target branches and Japan approval dates" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只保留截至 2024-12-31 前已在日本获批、用于斑块状银屑病的系统用药中，真正作用于 IL-17/IL-23 信号轴的活性成分。", + "候选集合必须覆盖 ligand side、receptor side 和 TYK2 kinase side，而不是只看 interleukin ligand 一侧。", + "最终条目按日本首次批准日期升序排列；如同日则按 DRUG_ID 升序。" + ], + "exclusion_conditions": [ + "排除外用药、非系统用药或不在指定历史冻结窗口内的条目。", + "排除 Ustekinumab 这类实际暴露为 IL12 + IL23A、但不满足本题 IL-17/IL-23 轴口径的条目。", + "排除因为只看 ligand side 而漏掉 Brodalumab 或 Deucravacitinib 的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "DRUG_ID", + "Name", + "ATC", + "Target_branch", + "PMDA_date" + ], + "PMDA_date": "use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value", + "Target_branch": "emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`", + "sorting_or_selection": { + "primary": "PMDA_date ascending", + "secondary": "DRUG_ID ascending" + } + } + } +} diff --git a/data_zh/constraint/genome_004.json b/data_zh/constraint/genome_004.json new file mode 100644 index 0000000000000000000000000000000000000000..03123803e4d1399d9e5afbbd138df038f55196e0 --- /dev/null +++ b/data_zh/constraint/genome_004.json @@ -0,0 +1,78 @@ +{ + "task_id": "genome_004", + "domain": "KEGG_GENOME", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我在为灵长类进化课准备一页讲义，想把“为什么这一支系必须从食物中获取维生素 C”的异常模式整理成一张两行对照表。请先在截至 2022 年底前已建立的灵长类基因组条目中，定位上游糖醛酸模块 M00014 仍然保留、但动物型维生素 C 合成模块 M00129 已在该下一级类群中缺失的异常类群；再核对与其对应的姐妹分支，确认该姐妹分支仍保留 M00129。最后，请输出两行对照表，列为 rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year。第一行为 EXCEPTION_CLADE，第二行为 RETAINED_SISTER_CLADE；其中 vitamin_c_synthesis_module 固定填写 M00129，vitamin_c_module_status 分别写 LOST 和 RETAINED。示例物种请使用 KEGG organism code。", + "start_url": "https://www.genome.jp/kegg/kegg2.html", + "output_format": "请输出两行对照表，列为 rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year。", + "oracle_answer": "1|EXCEPTION_CLADE|Primates|Haplorrhini|map00053|map00040|M00014|M00129|LOST|csyr|2022\n2|RETAINED_SISTER_CLADE|Primates|Strepsirrhini|map00053|map00040|M00014|M00129|RETAINED|oga|2022", + "metadata": { + "State-Gated Retrieval": [ + "只在截至 2022 年底已建立的灵长类基因组条目中筛选：保留上游糖醛酸模块 M00014、但缺失动物型维生素 C 合成模块 M00129 的异常下一级类群。", + "该异常类群必须能在同一上一级分裂下找到可对照的姐妹分支，且该姐妹分支仍保留 M00129。", + "最终输出要把异常分支和保留姐妹分支并排整理成两行对照表，并给出路径、模块与示例物种字段。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "KEGG primate clade pages and genome entries yield candidate subclades and example species established through the cutoff year", + "pathway and module views yield M00014 and M00129 presence/absence evidence for the exception clade and its sister branch", + "final rows are produced only after the exception clade and retained sister are jointly validated under the same parent split and paired with example organisms" + ], + "control_dependency": [ + "the exception clade remains provisional until both the sister-branch contrast and the example-species checks succeed", + "the comparison pathway must make both retained M00014 and missing M00129 visible in the same view", + "the two output rows are emitted together only after the exception clade and retained sister branch are fixed under the same parent split" + ], + "freeze": { + "historical_window": "primate genome entries established on or before 2022, with current KEGG clade, pathway, and module pages used as relatively stable reference information for comparing retained M00014 against lost M00129" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在截至 2022 年底已建立的灵长类基因组条目中筛选：上游糖醛酸模块 M00014 仍保留、但动物型维生素 C 合成模块 M00129 缺失的异常下一级类群。", + "该异常类群必须存在可对照的姐妹分支，且该姐妹分支仍保留 M00129。", + "最终输出必须把异常分支和保留姐妹分支并排整理成两行对照表，并给出路径、模块与示例物种字段。" + ], + "exclusion_conditions": [ + "排除停在 Simiiformes、没有继续检查更外层边界而漏掉 Haplorrhini 的结果。", + "排除使用不能同时展示 M00014 与 M00129 差异的 pathway 视图。", + "排除没有完成姐妹分支保留对照验证的候选类群。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "clade_role", + "parent_clade", + "clade", + "anomaly_pathway", + "contrast_pathway", + "retained_upstream_module", + "vitamin_c_synthesis_module", + "vitamin_c_module_status", + "example_org", + "cutoff_year" + ], + "rank": "emit 1 for EXCEPTION_CLADE and 2 for RETAINED_SISTER_CLADE", + "clade_role": [ + "EXCEPTION_CLADE", + "RETAINED_SISTER_CLADE" + ], + "pathway_normalization": "emit KEGG pathway ids with the map prefix", + "module_normalization": "emit KEGG module ids with the leading M", + "vitamin_c_module_status": [ + "LOST", + "RETAINED" + ], + "organism_code": "use bare KEGG organism codes in lowercase, not species names", + "cutoff_year": "use a four-digit year; this task is frozen at 2022", + "sorting_or_selection": "emit rows in the fixed order EXCEPTION_CLADE then RETAINED_SISTER_CLADE" + } + } +} diff --git a/data_zh/constraint/nvd_001.json b/data_zh/constraint/nvd_001.json new file mode 100644 index 0000000000000000000000000000000000000000..ccdf78691303e86974e10fb449c6ecd52e27e34d --- /dev/null +++ b/data_zh/constraint/nvd_001.json @@ -0,0 +1,66 @@ +{ + "task_id": "nvd_001", + "domain": "NVD", + "autonomy_type": "ordered table", + "instruction": "我们在清理一批旧 SBOM 匹配规则，其中有些规则仍把 Apache Tomcat 9.0.0 发布前的 milestone 版本写成 9.0.0.Mx这种旧版 CPE 形式；现在需要确认哪些 milestone 版本同时出现在 CVE-2016-5018、CVE-2016-6794、CVE-2016-6796 和 CVE-2016-6797 这四个 CVE 的 NVD 当前受影响产品版本范围中，并且能在 NVD 历史记录里看到从 m1、m2 这类旧 CPE 写法改为 milestone1、milestone2 这类完整 CPE 写法的记录。请从 Apache Tomcat 9.0.0 的 milestone 版本入手，逐一核对这四个 CVE 在 NVD 当前列出的受影响产品版本范围，只保留同时被四个 CVE 覆盖的 milestone 版本；再查看相应的 NVD 历史记录，确认是否存在旧 CPE 写法到完整 CPE 写法的变更，并记录该变更时间。筛选时请排除只由其他 Tomcat 9.0.0 发布前版本问题带入的 milestone，也不要纳入 Tomcat 6、7、8、8.5 或任何非 Tomcat 产品。最后，请按 milestone 编号的数值升序输出多行有序表，列为 milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd。", + "start_url": "https://nvd.nist.gov/vuln/search#/nvd/home?resultType=records", + "output_format": "最后，请按 milestone 编号的数值升序输出多行有序表，列为 milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd。", + "oracle_output_cardinality": 3, + "oracle_answer": "CVE:2018-7543|1.2.32|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2018-17207|1.2.42|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2020-11738|1.3.28|lite+pro|ModifiedAnalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02", + "metadata": { + "State-Gated Retrieval": [ + "只保留当前产品线属于 awesomemotive:duplicator、且在 deprecated 旧厂商链中能回溯到 snapcreek:duplicator 的 Duplicator 相关 CVE。", + "每个候选 CVE 都必须在 Change History 中同时满足：Initial Analysis 还不是 lite/lite+pro；后续在 2021-10-18 的 NIST 分析事件里第一次改到 lite 或 lite+pro；并在 2026-02-02 发生 snapcreek -> awesomemotive 的 vendor remap。", + "最终输出只保留满足上述三重条件的 CVE 行。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "NVD product/CPE search pages yield the current awesomemotive:duplicator family and the deprecated snapcreek:duplicator lineage", + "each target CVE detail page and Change History yield the Initial Analysis state, the first lite/lite+pro analysis event, and the 2026-02-02 vendor-remap event", + "final rows are produced only after candidate CVEs are intersected on both snapcreek -> awesomemotive migration and later introduction of lite/lite+pro in NIST analysis history" + ], + "control_dependency": [ + "the search must include the deprecated snapcreek lineage rather than only the current product state", + "vendor migration alone is insufficient until detail-level history confirms that lite/lite+pro was introduced after Initial Analysis", + "candidate CVEs must be filtered against the full change-history chronology, excluding any whose Initial Analysis already contained lite" + ], + "freeze": { + "historical_window": "Duplicator CVEs published from 2018-01-01 through 2024-12-31, evaluated against NVD analysis history up to the 2026-02-02 snapcreek -> awesomemotive vendor-remap events" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只保留当前产品线属于 awesomemotive:duplicator、且在 deprecated 旧厂商链中能回溯到 snapcreek:duplicator 的 Duplicator 相关 CVE。", + "每个候选 CVE 都必须在 Change History 中同时满足：Initial Analysis 还不是 lite/lite+pro；后续在 2021-10-18 的 NIST 分析事件里第一次改到 lite 或 lite+pro；并在 2026-02-02 发生 snapcreek -> awesomemotive 的 vendor remap。", + "最终输出只保留满足上述三重条件的 CVE 行。" + ], + "exclusion_conditions": [ + "排除只看 current description 或 current product state、没有回退到 deprecated snapcreek 链和 Change History 的结果。", + "排除 Initial Analysis 就已经是 lite/lite+pro 的 CVE。", + "排除没有 2026-02-02 vendor remap、或不属于 Duplicator 产品线的记录。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema_note": "the current source docx rubric, evidence, and oracle answer use a Duplicator CVE rowset, even though the instruction/output_format text still describes a Tomcat milestone task; normalization therefore follows the checked oracle row schema rather than the stale milestone wording", + "schema": [ + "CVE", + "lite_upper_version", + "lite_vs_lite+pro", + "analysis_event@date", + "snapcreek_to_awesomemotive@date" + ], + "CVE": "emit the identifier in the canonical `CVE:YYYY-NNNN` form used by the oracle", + "lite_vs_lite+pro": "emit `lite` or `lite+pro` exactly", + "analysis_event@date": "emit `Reanalysis@YYYY-MM-DD` or `ModifiedAnalysis@YYYY-MM-DD` exactly as supported by the source record", + "snapcreek_to_awesomemotive@date": "emit the ownership-transfer event as `snapcreek->awesomemotive@YYYY-MM-DD`", + "sorting_or_selection": { + "primary": "NVD published date ascending", + "secondary": "CVE ascending" + } + } + } +} diff --git a/data_zh/constraint/nvd_002.json b/data_zh/constraint/nvd_002.json new file mode 100644 index 0000000000000000000000000000000000000000..31174c699cb8e4355c61fef9c95d54f99244dcaa --- /dev/null +++ b/data_zh/constraint/nvd_002.json @@ -0,0 +1,62 @@ +{ + "task_id": "nvd_002", + "instruction": "我想确认 MySQL 5.1 分支中，哪些采用旧厂商命名 mysql:mysql 的 CPE 2.3 产品标识，在 NVD（国家漏洞数据库）里 CVE-2010-3676、CVE-2010-3677、CVE-2010-3678 和 CVE-2010-3680 这四个 InnoDB 拒绝服务漏洞的记录中，均被 NIST 明确迁移为对应的 oracle:mysql CPE 2.3 产品标识。这里的迁移仅指 CPE 中厂商字段从旧厂商 mysql 变更为新厂商 oracle，不包括仍在旧厂商名下、只是对版本别名做归一化的情况。请仅保留 MySQL 5.1 分支中的这类条目，排除 MySQL 5.0 分支，以及所有未发生厂商迁移、仅做旧厂商内部版本别名归一化的条目。请输出多行有序表，列为 version_update | legacy_cpe | current_cpe | remap_time_nvd，按版本号数值升序排列；同一版本下，不带 update 的条目排在带 update 的条目前。", + "domain": "NVD", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 44, + "start_url": "https://nvd.nist.gov/products/cpe/search", + "output_format": "请输出多行有序表，列为 version_update | legacy_cpe | current_cpe | remap_time_nvd，按版本号数值升序排列；同一版本下，不带 update 的条目排在带 update 的条目前。", + "oracle_answer": "version_update|legacy_cpe|current_cpe|remap_time_nvd\n5.1.1|cpe:2.3:a:mysql:mysql:5.1.1:::::::*|cpe:2.3:a:oracle:mysql:5.1.1:::::::*|2019-12-17 15:04:33\n5.1.2|cpe:2.3:a:mysql:mysql:5.1.2:::::::*|cpe:2.3:a:oracle:mysql:5.1.2:::::::*|2019-12-17 15:04:39\n5.1.3|cpe:2.3:a:mysql:mysql:5.1.3:::::::*|cpe:2.3:a:oracle:mysql:5.1.3:::::::*|2019-12-17 15:04:46\n5.1.4|cpe:2.3:a:mysql:mysql:5.1.4:::::::*|cpe:2.3:a:oracle:mysql:5.1.4:::::::*|2019-12-17 15:04:53\n5.1.10|cpe:2.3:a:mysql:mysql:5.1.10:::::::*|cpe:2.3:a:oracle:mysql:5.1.10:::::::*|2019-12-17 15:05:30\n5.1.11|cpe:2.3:a:mysql:mysql:5.1.11:::::::*|cpe:2.3:a:oracle:mysql:5.1.11:::::::*|2019-12-17 15:05:37\n5.1.12|cpe:2.3:a:mysql:mysql:5.1.12:::::::*|cpe:2.3:a:oracle:mysql:5.1.12:::::::*|2019-12-17 15:05:45\n5.1.13|cpe:2.3:a:mysql:mysql:5.1.13:::::::*|cpe:2.3:a:oracle:mysql:5.1.13:::::::*|2019-12-17 15:05:52\n5.1.14|cpe:2.3:a:mysql:mysql:5.1.14:::::::*|cpe:2.3:a:oracle:mysql:5.1.14:::::::*|2019-12-17 15:05:59\n5.1.15|cpe:2.3:a:mysql:mysql:5.1.15:::::::*|cpe:2.3:a:oracle:mysql:5.1.15:::::::*|2019-12-17 15:06:07\n5.1.16|cpe:2.3:a:mysql:mysql:5.1.16:::::::*|cpe:2.3:a:oracle:mysql:5.1.16:::::::*|2019-12-17 15:06:14\n5.1.17|cpe:2.3:a:mysql:mysql:5.1.17:::::::*|cpe:2.3:a:oracle:mysql:5.1.17:::::::*|2019-12-17 15:06:21\n5.1.18|cpe:2.3:a:mysql:mysql:5.1.18:::::::*|cpe:2.3:a:oracle:mysql:5.1.18:::::::*|2019-12-17 15:06:27\n5.1.19|cpe:2.3:a:mysql:mysql:5.1.19:::::::*|cpe:2.3:a:oracle:mysql:5.1.19:::::::*|2019-12-17 15:06:34\n5.1.20|cpe:2.3:a:mysql:mysql:5.1.20:::::::*|cpe:2.3:a:oracle:mysql:5.1.20:::::::*|2019-12-17 15:06:42\n5.1.21|cpe:2.3:a:mysql:mysql:5.1.21:::::::*|cpe:2.3:a:oracle:mysql:5.1.21:::::::*|2019-12-17 15:06:50\n5.1.22|cpe:2.3:a:mysql:mysql:5.1.22:::::::*|cpe:2.3:a:oracle:mysql:5.1.22:::::::*|2019-12-17 15:06:56\n5.1.23:a|cpe:2.3:a:mysql:mysql:5.1.23:a::::::|cpe:2.3:a:oracle:mysql:5.1.23:a::::::|2019-12-17 15:23:28\n5.1.24|cpe:2.3:a:mysql:mysql:5.1.24:::::::*|cpe:2.3:a:oracle:mysql:5.1.24:::::::*|2019-12-17 15:07:03\n5.1.25|cpe:2.3:a:mysql:mysql:5.1.25:::::::*|cpe:2.3:a:oracle:mysql:5.1.25:::::::*|2019-12-17 15:07:10\n5.1.26|cpe:2.3:a:mysql:mysql:5.1.26:::::::*|cpe:2.3:a:oracle:mysql:5.1.26:::::::*|2019-12-17 15:07:17\n5.1.27|cpe:2.3:a:mysql:mysql:5.1.27:::::::*|cpe:2.3:a:oracle:mysql:5.1.27:::::::*|2019-12-17 15:07:24\n5.1.28|cpe:2.3:a:mysql:mysql:5.1.28:::::::*|cpe:2.3:a:oracle:mysql:5.1.28:::::::*|2019-12-17 15:07:31\n5.1.29|cpe:2.3:a:mysql:mysql:5.1.29:::::::*|cpe:2.3:a:oracle:mysql:5.1.29:::::::*|2019-12-17 15:07:38\n5.1.30|cpe:2.3:a:mysql:mysql:5.1.30:::::::*|cpe:2.3:a:oracle:mysql:5.1.30:::::::*|2019-12-17 15:07:46\n5.1.31:sp1|cpe:2.3:a:mysql:mysql:5.1.31:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.31:sp1::::::|2019-12-17 15:23:35\n5.1.33|cpe:2.3:a:mysql:mysql:5.1.33:::::::*|cpe:2.3:a:oracle:mysql:5.1.33:::::::*|2019-12-17 15:07:55\n5.1.34:sp1|cpe:2.3:a:mysql:mysql:5.1.34:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.34:sp1::::::|2019-12-17 15:23:42\n5.1.35|cpe:2.3:a:mysql:mysql:5.1.35:::::::*|cpe:2.3:a:oracle:mysql:5.1.35:::::::*|2019-12-17 15:08:03\n5.1.36|cpe:2.3:a:mysql:mysql:5.1.36:::::::*|cpe:2.3:a:oracle:mysql:5.1.36:::::::*|2019-12-17 15:08:10\n5.1.37:sp1|cpe:2.3:a:mysql:mysql:5.1.37:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.37:sp1::::::|2019-12-17 15:23:49\n5.1.38|cpe:2.3:a:mysql:mysql:5.1.38:::::::*|cpe:2.3:a:oracle:mysql:5.1.38:::::::*|2019-12-17 15:08:17\n5.1.39|cpe:2.3:a:mysql:mysql:5.1.39:::::::*|cpe:2.3:a:oracle:mysql:5.1.39:::::::*|2019-12-17 10:22:31\n5.1.40|cpe:2.3:a:mysql:mysql:5.1.40:::::::*|cpe:2.3:a:oracle:mysql:5.1.40:::::::*|2019-12-17 10:22:46\n5.1.40:sp1|cpe:2.3:a:mysql:mysql:5.1.40:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.40:sp1::::::|2019-12-17 10:22:39\n5.1.41|cpe:2.3:a:mysql:mysql:5.1.41:::::::*|cpe:2.3:a:oracle:mysql:5.1.41:::::::*|2019-12-17 10:22:52\n5.1.42|cpe:2.3:a:mysql:mysql:5.1.42:::::::*|cpe:2.3:a:oracle:mysql:5.1.42:::::::*|2019-12-17 10:22:59\n5.1.43|cpe:2.3:a:mysql:mysql:5.1.43:::::::*|cpe:2.3:a:oracle:mysql:5.1.43:::::::*|2019-12-17 10:23:06\n5.1.43:sp1|cpe:2.3:a:mysql:mysql:5.1.43:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.43:sp1::::::|2019-12-17 10:23:11\n5.1.44|cpe:2.3:a:mysql:mysql:5.1.44:::::::*|cpe:2.3:a:oracle:mysql:5.1.44:::::::*|2019-12-17 10:23:17\n5.1.45|cpe:2.3:a:mysql:mysql:5.1.45:::::::*|cpe:2.3:a:oracle:mysql:5.1.45:::::::*|2019-12-17 10:23:24\n5.1.46|cpe:2.3:a:mysql:mysql:5.1.46:::::::*|cpe:2.3:a:oracle:mysql:5.1.46:::::::*|2019-12-17 10:23:38\n5.1.46:sp1|cpe:2.3:a:mysql:mysql:5.1.46:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.46:sp1::::::|2019-12-17 10:23:31\n5.1.47|cpe:2.3:a:mysql:mysql:5.1.47:::::::*|cpe:2.3:a:oracle:mysql:5.1.47:::::::*|2019-12-17 10:23:45", + "metadata": { + "State-Gated Retrieval": [ + "只保留 MySQL 5.1 分支中，在 CVE-2010-3676、3677、3678、3680 四个漏洞的 NVD Change History 中都能明确看到 mysql:mysql -> oracle:mysql vendor migration 的 CPE 2.3 条目。", + "每个结果都必须给出 version_update、legacy_cpe、current_cpe 和 remap_time_nvd。", + "同一版本下，不带 update 的条目排在带 update 的条目前，并按版本号数值升序输出。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current and deprecated MySQL 5.1 CPE search results yield candidate legacy/current CPE strings", + "the four target CVE pages and their Change History entries yield vendor-migration evidence, exact version_update strings, and remap timestamps", + "final rows are produced only after taking the common mysql:mysql 5.1 -> oracle:mysql 5.1 migrations across all four CVEs and removing alias-only or 5.0 entries" + ], + "control_dependency": [ + "legacy vendor mapping must be determined from Analysis Description plus Change History rather than from the current description/current CPE view", + "include-deprecated results cannot be accepted wholesale because alias-only remaps must be filtered out", + "5.1-branch membership and sort order must be determined after the vendor-migration filter removes 5.0 and non-migration rows" + ], + "freeze": { + "historical_window": "the MySQL 5.1 branches visible in CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680, restricted to explicit mysql:mysql -> oracle:mysql vendor-migration events" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只保留 MySQL 5.1 分支中，在 CVE-2010-3676、3677、3678、3680 四个漏洞的 NVD Change History 中都能明确看到 mysql:mysql -> oracle:mysql vendor migration 的 CPE 2.3 条目。", + "每个结果都必须给出 version_update、legacy_cpe、current_cpe 和 remap_time_nvd。", + "同一版本下，不带 update 的条目排在带 update 的条目前，并按版本号数值升序输出。" + ], + "exclusion_conditions": [ + "排除 MySQL 5.0 分支条目。", + "排除仍属于旧厂商 mysql:mysql、只是内部版本别名归一化、并未发生 vendor migration 的条目。", + "排除只从 current Oracle MySQL 5.1 CPE state 读取、没有利用 legacy mapping 与 Change History 的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row `version_update|legacy_cpe|current_cpe|remap_time_nvd`", + "schema": [ + "version_update", + "legacy_cpe", + "current_cpe", + "remap_time_nvd" + ], + "version_update": "sort by numeric MySQL version ascending; within the same base version, the empty update comes before any non-empty update suffix", + "legacy_cpe": "preserve the exact legacy CPE 2.3 string", + "current_cpe": "preserve the exact current CPE 2.3 string", + "remap_time_nvd": "emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form", + "dedup_key": "(legacy_cpe, current_cpe)" + } + } +} diff --git a/data_zh/constraint/nvd_003.json b/data_zh/constraint/nvd_003.json new file mode 100644 index 0000000000000000000000000000000000000000..91a774f663344302b5d08ae4d289eb6f7b01738f --- /dev/null +++ b/data_zh/constraint/nvd_003.json @@ -0,0 +1,114 @@ +{ + "task_id": "nvd_003", + "domain": "NVD", + "autonomy_type": "ordered table", + "instruction": "我们在清理一批旧 SBOM 匹配规则，这些规则仍把 Apache Tomcat 9.0.0 发布前的 milestone 版本写成 9.0.0.Mx 这种旧 CPE 写法。现在需要确认，哪些 milestone 版本同时满足两项条件：一是它们都出现在 CVE-2016-5018、CVE-2016-6794、CVE-2016-6796 和 CVE-2016-6797 这四个历史漏洞当前在 NVD 中列出的受影响产品版本范围里；二是能够在 NVD 的历史变更记录中看到，这些版本对应的 CPE 曾从 m1、m2 这类旧写法改成 milestone1、milestone2 这类完整写法。请从 Apache Tomcat 9.0.0 的 milestone 版本入手，逐一核对这四个漏洞当前在 NVD 中列出的受影响产品版本范围，再查看相应的历史变更记录，只保留同时满足这两项条件的 milestone 版本。筛选时，请排除那些只是因为其他 Tomcat 9.0.0 发布前漏洞才被带入的 milestone，也不要纳入 Tomcat 6、7、8、8.5 或任何非 Tomcat 产品。最后，请按 milestone 编号的数值升序输出多行有序表，列为 milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd。", + "start_url": "https://nvd.nist.gov/products/cpe/search", + "output_format": "输出为 Markdown 多行表，列名固定为：milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd。排序按 M1, M2, ..., M9 的数字升序。", + "oracle_output_cardinality": 9, + "oracle_answer": "milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd\nM1|cpe:2.3:a:apache:tomcat:9.0.0:m1:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone1:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM2|cpe:2.3:a:apache:tomcat:9.0.0:m2:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone2:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM3|cpe:2.3:a:apache:tomcat:9.0.0:m3:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone3:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM4|cpe:2.3:a:apache:tomcat:9.0.0:m4:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone4:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM5|cpe:2.3:a:apache:tomcat:9.0.0:m5:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone5:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM6|cpe:2.3:a:apache:tomcat:9.0.0:m6:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone6:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM7|cpe:2.3:a:apache:tomcat:9.0.0:m7:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone7:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM8|cpe:2.3:a:apache:tomcat:9.0.0:m8:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone8:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM9|cpe:2.3:a:apache:tomcat:9.0.0:m9:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone9:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18", + "metadata": { + "State-Gated Retrieval": [ + "只保留 Apache Tomcat 9.0.0 milestone 版本中，同时出现在 CVE-2016-5018、6794、6796、6797 四个目标 CVE 当前受影响产品范围里的版本。", + "并且这些版本必须能在 NVD Change History 中看到 mN -> milestoneN 的 CPE Deprecation Remap。", + "最终按 milestone 编号数值升序输出，且 required_cves 必须对应这四个指定 CVE。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current milestoneN CPE search/detail pages yield the Tomcat milestone family and the legacy mN mapping anchors", + "the four target CVE pages and Change History entries yield the exact mN -> milestoneN deprecation remaps and the required-CVE intersection", + "final rows are produced only after taking the remaps common to all four target CVEs and sorting by numeric milestone" + ], + "control_dependency": [ + "the candidate milestone set must be determined from the four-target-CVE intersection rather than from all prerelease Tomcat CVEs", + "later remapped milestones such as M10+ must be excluded by applying the specified four-CVE boundary", + "only explicit NVD CPE Deprecation Remap events from mN to milestoneN count, so generic Tomcat prerelease visibility cannot be accepted as evidence" + ], + "freeze": { + "historical_window": "the Tomcat 9.0.0 prerelease milestones jointly covered by CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797, with remap evidence fixed to the 2023-12-08 11:41:18 NVD deprecation events" + }, + "answer_type": "multi-row ordered table" + }, + "all_involved_urls": { + "fixed_entry_and_docs": [ + "https://nvd.nist.gov/products/cpe/search", + "https://nvd.nist.gov/vuln/vulnerability-detail-pages" + ], + "cpe_search_result_pages": [ + "https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL", + "https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED", + "https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20m&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED", + "https://nvd.nist.gov/products/cpe/search/results?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED" + ], + "representative_cpe_detail_pages": [ + "https://nvd.nist.gov/products/cpe/detail/615922?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED", + "https://nvd.nist.gov/products/cpe/detail/615947?keyword=cpe%3A2.3%3Aa%3Aapache&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED" + ], + "row_level_cpe_api_urls_m1_to_m9": [ + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone2%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone3%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone4%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone5%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone6%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone7%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone8%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone9%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A" + ], + "target_cve_detail_pages": [ + "https://nvd.nist.gov/vuln/detail/CVE-2016-5018", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6794", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6796", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6797" + ], + "negative_control_cve_detail_pages": [ + "https://nvd.nist.gov/vuln/detail/CVE-2016-6816", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6817", + "https://nvd.nist.gov/vuln/detail/CVE-2019-0221" + ], + "cve_change_history_api": [ + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-5018&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6794&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6796&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6797&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6816&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6817&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2019-0221&eventName=CPE%20Deprecation%20Remap" + ], + "representative_change_record_pages": [ + "https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=04%2F18%2F2022T13%3A57%3A03.500-0400", + "https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=08%2F24%2F2017T09%3A11%3A40.690-0400" + ] + }, + "rubric": { + "inclusion_conditions": [ + "只保留 Apache Tomcat 9.0.0 milestone 版本中，同时出现在 CVE-2016-5018、6794、6796、6797 四个目标 CVE 当前受影响产品范围里的版本。", + "并且这些版本必须能在 NVD Change History 中看到 mN -> milestoneN 的 CPE Deprecation Remap。", + "最终按 milestone 编号数值升序输出，且 required_cves 必须对应这四个指定 CVE。" + ], + "exclusion_conditions": [ + "排除只因为其他 Tomcat 9.0.0 预发布漏洞才被带入的 milestone，例如 M10/M11 及更晚 milestone。", + "排除 Tomcat 6、7、8、8.5 或任何非 Tomcat 产品。", + "排除没有明确 NVD remap 证据、只是 current milestone 页面可见的记录。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row `milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd`", + "schema": [ + "milestone", + "legacy_cpe", + "current_cpe", + "required_cves", + "remap_time_nvd" + ], + "milestone": "emit the canonical milestone label `M1` through `M9` and sort by the numeric suffix ascending", + "legacy_cpe": "preserve the exact legacy CPE 2.3 string containing the short milestone token such as `m1`", + "current_cpe": "preserve the exact current CPE 2.3 string containing the full milestone token such as `milestone1`", + "required_cves": "emit the fixed literal `CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797`", + "remap_time_nvd": "emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form" + } + } +} diff --git a/data_zh/constraint/reptile_001.json b/data_zh/constraint/reptile_001.json new file mode 100644 index 0000000000000000000000000000000000000000..1b52489c654980122551847d3dd90a2d45f2d695 --- /dev/null +++ b/data_zh/constraint/reptile_001.json @@ -0,0 +1,61 @@ +{ + "task_id": "reptile_001", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "我在为 George A. Boulenger 1890 年《The Fauna of British India, Including Ceylon and Burma》中记载的印度蛇类早期馆藏标本整理名称对照。请按以下顺序处理：先以这批标本为范围，在 Reptile Database 中逐条查看对应的当前物种页，筛出同时满足以下条件的条目：现已改归其他属；该页仍保留 BMNH 的模式标本信息；模式产地（type locality）仍可对应 India。再对每个符合条件的条目，在该页列出的名称中找出时间上最接近现在、但尚未改用当前属名的那个旧双名学名。随后，将这个完整旧名作为名称再次检索，判断检索结果是否只指向这一条记录。最后，请按当前接受名的字母顺序将结果输出为一行，格式为 |||；不同条目之间用英文分号连接；如无符合条件的条目，则输出 NONE。", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "请按当前接受名的字母顺序将结果输出为一行，格式为 |||；不同条目之间用英文分号连接；如无符合条件的条目，则输出 NONE。", + "oracle_answer": "Argyrophis oatesii|Typhlops oatesii|UNIQUE|SYNTYPES;Dendrelaphis grandoculis|Ahaetulla grandoculis|UNIQUE|LECTOTYPE;Fowlea sanctijohannis|Xenochrophis sanctijohannis|UNIQUE|HOLOTYPE;Gerrhopilus beddomii|Typhlops beddomii|UNIQUE|SYNTYPES;Hebius khasiensis|Amphiesma khasiense|UNIQUE|LECTOTYPE;Hebius parallelus|Amphiesma parallelum|AMBIG|LECTOTYPE;Indotyphlops jerdoni|Typhlops jerdoni|UNIQUE|SYNTYPES;Myriopholis blanfordii|Leptotyphlops blanfordi|AMBIG|SYNTYPES", + "metadata": { + "State-Gated Retrieval": [ + "候选必须来自 Boulenger 1890《Fauna of British India》中的印度蛇类历史馆藏条目。", + "当前 Reptile Database 物种页必须同时满足：现已改归其他属；页面仍保留 BMNH 的模式标本信息；type locality 仍可对应 India。", + "在每个合格页面中，要选出时间上最接近现在、但尚未改用当前属名的旧双名学名，并用这个旧名做 exact 回查，再标记 UNIQUE 或 AMBIG。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Boulenger 1890 historical sample and current accepted-species pages yield candidates that changed genus while retaining BMNH type data and India-compatible type locality", + "each accepted page yields the nearest pre-current-genus old label, the BMNH type status, and the historical/type-locality evidence anchoring the entity", + "final rows are produced only after the old-label exact back-search is evaluated for uniqueness without losing the original entity anchor" + ], + "control_dependency": [ + "when an exact old-label back-search now hits multiple species, the original anchored entity must be kept and the uniqueness label must be set to AMBIG", + "once a candidate has passed the historical-cluster, genus-shift, BMNH, and India-locality gates, later old-label ambiguity can only rewrite the uniqueness field, not the entity itself", + "candidate anchoring must be preserved across the two-stage workflow so that old-label search noise does not redirect the accepted-species row" + ], + "freeze": { + "historical_window": "the George A. Boulenger 1890 British India sample, evaluated against current Reptile Database accepted pages, synonym labels, BMNH type data, and present type-locality text" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "候选必须来自 Boulenger 1890《Fauna of British India》中的印度蛇类历史馆藏条目。", + "当前 Reptile Database 物种页必须同时满足：现已改归其他属；页面仍保留 BMNH 的模式标本信息；type locality 仍可对应 India。", + "在每个合格页面中，要选出时间上最接近现在、但尚未改用当前属名的旧双名学名，并用这个旧名做 exact 回查，再标记 UNIQUE 或 AMBIG。" + ], + "exclusion_conditions": [ + "排除当前接受名未发生换属、或页面不再保留 BMNH 模式标本信息的条目。", + "排除 type locality 不能对应 India 的条目。", + "排除把 exact 旧名回查非唯一的候选直接丢弃；这类候选应保留原实体并标记为 AMBIG。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "accepted name", + "old label", + "UNIQUE/AMBIG", + "BMNH status" + ], + "accepted_name": "emit the current accepted binomial exactly as shown in the reconciled source", + "old_label": "preserve the historical label exactly as used on the legacy branch", + "UNIQUE/AMBIG": "emit `UNIQUE` or `AMBIG` in uppercase", + "BMNH_status": "normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or SYNTYPES", + "sorting_or_selection": "accepted name alphabetical ascending" + } + } +} diff --git a/data_zh/constraint/reptile_002.json b/data_zh/constraint/reptile_002.json new file mode 100644 index 0000000000000000000000000000000000000000..0c4a10c83fb6334151f0bb0c23e96970c3bb83f5 --- /dev/null +++ b/data_zh/constraint/reptile_002.json @@ -0,0 +1,63 @@ +{ + "task_id": "reptile_002", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "我在为东南亚 Lygosoma 的早期馆藏标本整理现行名称对照。旧标签对应的是各物种页面 Synonym 栏中标为 Smith（1935/1937）的 Riopa 组合名，但其中部分旧名在当前分类下会同时对应多个现行物种。请按以下顺序处理：先以当前的 Lygosoma 名录为范围，逐一查看各现行物种页面，在 Synonym 栏中定位这些 Smith（1935/1937）的 Riopa 组合名；再比较这些旧名，筛出会同时指向多个现行物种的情况，并列出所有涉及的现行物种。随后，对每个符合条件的现行物种，记录其页面中最先列出的模式标本编号、模式类别，以及该页模式产地（type locality）最终对应的地区。最后，请按当前接受名的字母顺序将结果输出为一行，格式为 ||||；不同条目之间用英文分号连接；如无符合条件的条目，则输出 NONE。", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "请按当前接受名的字母顺序将结果输出为一行，格式为 ||||；不同条目之间用英文分号连接；如无符合条件的条目，则输出 NONE。", + "oracle_answer": "Lygosoma bampfyldei|Riopa bampfyldei|BMNH 1946.8.10.84|SYNTYPES|East Malaysia;Lygosoma peninsulare|Riopa bampfyldei|LSUHC 13857|HOLOTYPE|Peninsular Malaysia;Lygosoma schneideri|Riopa bampfyldei|NMBA 4743|HOLOTYPE|Indonesia", + "metadata": { + "State-Gated Retrieval": [ + "只保留能从 Smith 1937 的旧名链追溯到当前 Lygosoma 记录，并且可在当前页面读取 type accession、type status 与 locality 的 accepted 物种。", + "对每条 accepted 记录，都要输出该 accepted name、对应旧标签、type accession、type status 和 locality。", + "若同一个精确旧名同时挂在多个 accepted 物种上，必须把它们作为不同链条分别保留。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Smith 1937 old-name chain yields the three current Lygosoma accepted pages connected to Riopa bampfyldei / Lygosoma bampfyldei", + "each accepted page yields its own type accession, type status, and type locality needed to separate the homonymous old-name paths", + "final rows are produced only after the one-to-many old-name split is rebuilt and the three paths are re-anchored to their own type evidence" + ], + "control_dependency": [ + "same-specific-epithet matching cannot establish a one-to-one mapping when the same Smith 1937 old name appears on multiple accepted pages", + "once literal old-name reuse is exposed, the workflow must keep the original parallel three-chain state rather than collapsing to a one-to-one mapping", + "type accession and locality evidence must be read separately for each chain rather than patched onto the first stopping page" + ], + "freeze": { + "historical_window": "the current Reptile Database accepted pages linked to the Smith 1937 old-name cluster around Riopa bampfyldei, using current type accessions, statuses, and localities" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只保留能从 Smith 1937 的旧名链追溯到当前 Lygosoma 记录，并且可在当前页面读取 type accession、type status 与 locality 的 accepted 物种。", + "对每条 accepted 记录，都要输出该 accepted name、对应旧标签、type accession、type status 和 locality。", + "若同一个精确旧名同时挂在多个 accepted 物种上，必须把它们作为不同链条分别保留。" + ], + "exclusion_conditions": [ + "排除凭“旧名与现行种加词相同”就直接认定还是同一物种的结果。", + "排除发现同一精确旧名同时出现在多个 accepted 页后，仍只保留第一条链的结果。", + "排除没有回到各 accepted 页重新核验 type accession 与 locality 的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "accepted", + "Smith-era Riopa label", + "first type code", + "type status", + "region" + ], + "accepted": "emit the current accepted binomial exactly as shown in the reconciled source", + "Smith-era_Riopa_label": "preserve the Smith-era Riopa label exactly as used on the legacy branch", + "first_type_code": "emit the first accession code that follows the selected type-status statement", + "type_status": "normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES", + "region": "emit the modern geographic region label from the source reconciliation, such as East Malaysia or Peninsular Malaysia", + "sorting_or_selection": "accepted name alphabetical ascending" + } + } +} diff --git a/data_zh/constraint/reptile_003.json b/data_zh/constraint/reptile_003.json new file mode 100644 index 0000000000000000000000000000000000000000..17161de6d7e114fc0fd4a53964a0e6cfcf2d3ff6 --- /dev/null +++ b/data_zh/constraint/reptile_003.json @@ -0,0 +1,66 @@ +{ + "task_id": "reptile_003", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 10, + "instruction": "我在为一批 1980 年前后仍以 Mabuya 或 Mabuia 名称编目的早期馆藏卡片整理现行名称对照，需将其归入当前的 Eutropis 名录。请按以下顺序处理：先在当前 Eutropis 名录中逐一查看各物种页面，找出页面中最先列出的那条 1980 年所用的 Mabuya 或 Mabuia 旧标签；再用这个旧标签直接按名称检索，筛出那些回查结果会同时指向不止一个当前 Eutropis 条目的物种。随后，对每个符合条件的条目，记录其当前接受名、这个 1980 旧标签、该旧标签在页面中的限定标注，以及当前页面最先列出的模式类别和编号。最后，请按旧标签字母顺序、同一旧标签下按当前接受名字母顺序输出一行：|<1980 label>|||；不同条目之间用英文分号连接；如无符合条件的条目，则输出 NONE。", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "请按旧标签字母顺序、同一旧标签下按当前接受名字母顺序输出一行：|<1980 label>|||；不同条目之间用英文分号连接；如无符合条件的条目，则输出 NONE。", + "oracle_answer": "Eutropis indeprensa|Mabuya indeprensa|NONE|HOLOTYPE|CAS 85664;Eutropis sahulinghangganan|Mabuya indeprensa|PART-MISID|HOLOTYPE|PNM 9867;Eutropis multifasciata|Mabuya multifasciata|NONE|NEOTYPE|MZB 11912;Eutropis multicarinata|Mabuya multicarinata|NONE|HOLOTYPE|BMNH 1946.8.15.13-15;Eutropis borealis|Mabuya multicarinata borealis|NONE|HOLOTYPE|CAS 15447;Eutropis islamaliit|Mabuya multicarinata borealis|PART-MISID|HOLOTYPE|PNM 9847;Eutropis caraga|Mabuya multicarinata multicarinata|PART-MISID|HOLOTYPE|PNM 9845;Eutropis palauensis|Mabuya multicarinata multicarinata|PART-BYIMPL|HOLOTYPE|CAS 248251;Eutropis dattaroyi|Mabuya rudis|PART|HOLOTYPE|ZSI 25118;Eutropis rudis|Mabuya rudis|NONE|LECTOTYPE|BMNH 1946.8.15.26", + "metadata": { + "State-Gated Retrieval": [ + "只保留当前 Eutropis 记录中，能够在 synonym 区块里自上而下找到第一条以 Mabuya 或 Mabuia 开头、且年份为 1980 的旧标签的 accepted 物种。", + "再用这条 1980 旧标签按默认名字匹配回查，并输出 accepted name、old label、回查判定、type status 与 type specimen。", + "若后续回查暴露出新的候选链，也必须回退并把它纳入最终结果。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current Eutropis detail pages yield the first 1980-tagged Mabuya/Mabuia synonym label for each accepted species", + "exact back-search on that 1980 old label yields the present accepted page, type status, and type specimen needed for the output row", + "final rows are produced only after the 1980-specific old-label anchor is rebuilt and the accepted-species candidate pool is expanded when back-search evidence reveals omitted chains" + ], + "control_dependency": [ + "the workflow must identify the first Mabuya/Mabuia label carrying the 1980 year rather than stopping at the first old label on the page", + "when old-label back-search reveals missing chains such as Eutropis dattaroyi, the candidate pool must be expanded to include them rather than patched in place", + "accepted-page synonym parsing and back-search interpretation must stay coupled so that 1980 labels are not replaced by older but irrelevant names" + ], + "freeze": { + "historical_window": "current Reptile Database Eutropis pages, restricted to the first synonym label that is both Mabuya/Mabuia-form and tagged with the 1980 citation year" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只保留当前 Eutropis 记录中，能够在 synonym 区块里自上而下找到第一条以 Mabuya 或 Mabuia 开头、且年份为 1980 的旧标签的 accepted 物种。", + "再用这条 1980 旧标签按默认名字匹配回查，并输出 accepted name、old label、回查判定、type status 与 type specimen。", + "若后续回查暴露出新的候选链，也必须回退并把它纳入最终结果。" + ], + "exclusion_conditions": [ + "排除把“最先出现的旧名”误当成“最先出现的 1980 旧标签”的结果。", + "排除只抓 Spanish? no", + "排除在后续证据暴露出遗漏链条时，没有回退重建候选池的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "accepted", + "1980 label", + "qualifier", + "type status", + "first type code" + ], + "accepted": "emit the current accepted binomial exactly as shown in the reconciled source", + "1980_label": "preserve the 1980-era label exactly as used on the legacy branch", + "qualifier": "normalize to one of `NONE`, `PART`, `PART-MISID`, or `PART-BYIMPL`", + "type_status": "normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES", + "first_type_code": "emit the first accession code that follows the selected type-status statement", + "sorting_or_selection": { + "primary": "1980 label alphabetical ascending", + "secondary": "accepted name alphabetical ascending" + } + } + } +} diff --git a/data_zh/constraint/reptile_004.json b/data_zh/constraint/reptile_004.json new file mode 100644 index 0000000000000000000000000000000000000000..f5d4a96c79d562b1c5d322a03dac77937d57dfa4 --- /dev/null +++ b/data_zh/constraint/reptile_004.json @@ -0,0 +1,65 @@ +{ + "task_id": "reptile_004", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 6, + "instruction": "我在整理一批半趾虎早期馆藏卡片，卡片上使用的仍是 Hemidactylus brookii 物种页注释部分列出的那些旧标签。请按以下顺序处理：先查看 Hemidactylus brookii 当前物种页注释部分列出的旧标签，筛出其中当前已不再归入 Hemidactylus brookii、且数据库已经明确给出其现行归属的标签。随后，对每个符合条件的标签，确定其最终应归入的现行物种；若从该标签归并到现行物种时必须先经过一个中间旧名，则写出该中间名，否则写 DIRECT。同时，记录该标签本身对应的模式类别、模式编号，以及其模式产地（type locality）所在国家。最后，请按旧标签字母顺序输出一行：|||||；不同条目之间用英文分号连接；如无符合条件的条目，则输出 NONE。", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "请按旧标签字母顺序输出一行：|||||；不同条目之间用英文分号连接；如无符合条件的条目，则输出 NONE。", + "oracle_answer": "Hemidactylus brooki leightoni|Hemidactylus angulatus|DIRECT|HOLOTYPE|BMNH 1946.8.25.65|Colombia;Hemidactylus brookii haitianus|Hemidactylus angulatus|DIRECT|LECTOTYPE|ZMH R22378|Haiti;Hemidactylus brookii parvimaculatus|Hemidactylus parvimaculatus|DIRECT|HOLOTYPE|NMSL No. RG. 15|Sri Lanka;Hemidactylus brookii subtriedroides|Hemidactylus murrayi|Hemidactylus tenkatei|LECTOTYPE|BMNH [subtriedroides] [tenkatei]|Myanmar;Hemidactylus gleadowi|Hemidactylus gleadowi|DIRECT|NEOTYPE|BMNH 1884.7.25.8|Pakistan;Hemidactylus tenkatei|Hemidactylus murrayi|DIRECT|LECTOTYPE|RMNH 4353|Indonesia", + "metadata": { + "State-Gated Retrieval": [ + "每条结果都必须从题目指定的旧标签链条出发，最终在当前 accepted 页中核定 accepted name、bridge 状态、type status、type accession 和 locality。", + "对 subtriedroides 分支，必须继续沿 tenkatei 再追到 murrayi，输出最终 accepted 为 Hemidactylus murrayi，并保留 bridge=Hemidactylus tenkatei。", + "对 haitianus、leightoni 等分支，必须读取各自 locality / type 行，而不是借用错误页面的页首信息。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the old-label chains from Hemidactylus angulatus and related names yield accepted pages, bridge names, and the type/locality lines for each path", + "comment, Types, and type-comment blocks yield the later evidence that tenkatei is further sunk into H. murrayi", + "final rows are produced only after each old-label path is re-anchored to its own locality/type line and the subtriedroides -> tenkatei -> murrayi bridge chain is completed" + ], + "control_dependency": [ + "type data must be taken from the locality/type line belonging to the actual old-label branch rather than from the page-top block of the wrong accepted page", + "stopping at the intermediate tenkatei bridge is insufficient; the workflow must continue to the later murrayi evidence and rewrite both tenkatei and subtriedroides final accepted names", + "bridge labels remain useful, but final accepted names and type lines must be determined from the deeper synonym chain" + ], + "freeze": { + "historical_window": "current Reptile Database pages for the Hemidactylus angulatus / brookii / murrayi complex, using present locality, type, comment, and type-comment blocks" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "每条结果都必须从题目指定的旧标签链条出发，最终在当前 accepted 页中核定 accepted name、bridge 状态、type status、type accession 和 locality。", + "对 subtriedroides 分支，必须继续沿 tenkatei 再追到 murrayi，输出最终 accepted 为 Hemidactylus murrayi，并保留 bridge=Hemidactylus tenkatei。", + "对 haitianus、leightoni 等分支，必须读取各自 locality / type 行，而不是借用错误页面的页首信息。" + ], + "exclusion_conditions": [ + "排除读取了错误页内层级、把 H. angulatus 页首的 Holotype / locality 套到其他分支的结果。", + "排除在 subtriedroides -> tenkatei 链上提前停止、未继续读取 murrayi 后续证据的结果。", + "排除未把 locality / type 行与具体旧标签分支逐一对齐的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "legacy label", + "accepted", + "bridge", + "type status", + "type code", + "country" + ], + "legacy_label": "preserve the legacy label exactly as used on the source branch", + "accepted": "emit the current accepted binomial exactly as shown in the reconciled source", + "bridge": "emit `DIRECT` when no intermediate legacy bridge name is needed; otherwise emit the intermediate legacy name that links the branches", + "type_status": "normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or NEOTYPE", + "type_code": "take the type accession from the legacy-label branch rather than a generic page-level type line", + "country": "emit the modern English country name from the reconciled source branch", + "sorting_or_selection": "legacy label alphabetical ascending" + } + } +} diff --git a/data_zh/constraint/reptile_005.json b/data_zh/constraint/reptile_005.json new file mode 100644 index 0000000000000000000000000000000000000000..821d946c22230a7686413217740a2e37bca40779 --- /dev/null +++ b/data_zh/constraint/reptile_005.json @@ -0,0 +1,68 @@ +{ + "task_id": "reptile_005", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我在核对当前 Naja 物种名录中一条涉及斯里兰卡早期馆藏名称的归并记录，想把 accepted 侧与 contested-name 侧的关键信息整理成一张两行对照表。请先在当前 Naja 名录中定位来自 Sri Lanka 的相关 contested name 记录，再核对该名称的近年使用证据、数据库给出的最终处理意见，以及记录中关于 lectotype 归属的更正信息，并整理限制后的模式产地和该争议名称自身的 holotype 信息。最后，请输出两行对照表，列为 rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note。第一行填写 ACCEPTED_NAME，给出 accepted name、final status、valid lectotype 以及 restricted type locality；第二行填写 CONTESTED_NAME，给出 contested name、recent-use evidence、holotype，以及被纠正的 invalid lectotype claim。", + "start_url": "https://reptile-database.reptarium.cz/advanced_search?genus=Naja&submit=Search", + "output_format": "请输出两行对照表，列为 rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note。", + "oracle_answer": "1|ACCEPTED_NAME|Naja naja|SUBJECTIVE_JUNIOR_SYNONYM_OF_NAJA_NAJA|VALID_LECTOTYPE|ZMB 2796|restricted type locality: Sri Lanka\n2|CONTESTED_NAME|Naja polyocellata|SHI et al. 2022+SILVA et al. 2023|HOLOTYPE|BMNH 1946.1.18.50|invalid lectotype claim: NRM (= NHR) Lin-90", + "metadata": { + "State-Gated Retrieval": [ + "必须在当前 Naja 名录中锁定来自 Sri Lanka 的 contested-name 分支：该名称近年曾被重新当作独立有效名使用，但数据库当前又明确并入 accepted name。", + "同一 accepted 页中还必须同时读取 recent-use evidence、final synonym status、lectotype 更正信息、restricted type locality，以及 contested name 自身的 holotype 信息。", + "最终输出必须把 ACCEPTED_NAME 与 CONTESTED_NAME 两侧信息整理成两行对照表。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the current Naja species list and the Naja naja page yield the Sri Lanka contested-name branch, recent-use citations, and the accepted-name context", + "comment, Types, and type-comment blocks yield the final synonym treatment plus the valid and invalid lectotype assignments and the contested-name holotype", + "final rows are produced only after the accepted-name and contested-name sides are reconciled on the same accepted page" + ], + "control_dependency": [ + "recent-use evidence for Naja polyocellata must be interpreted together with the current page-level final synonym treatment", + "lectotype status must be fixed from the combined Types and type-comment evidence rather than from a single provisional assignment", + "the accepted-name and contested-name rows are emitted together only after final status, type locality, and specimen roles are fixed" + ], + "freeze": { + "historical_window": "the objectively existing taxa in the Sri Lanka Naja branch, using current Reptile Database comment, Types, and type-comment blocks as nearly objective and highly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "必须在当前 Naja 名录中锁定来自 Sri Lanka 的 contested name 记录，该名称近年曾被文献重新作为独立有效名使用，但数据库当前又明确说明其仍应并入 accepted name。", + "同一 accepted 页中还必须同时能读取 recent-use evidence、final synonym status、lectotype 更正信息、restricted type locality，以及 contested name 自身的 holotype 信息。", + "最终输出必须把 ACCEPTED_NAME 与 CONTESTED_NAME 两侧信息整理成两行对照表。" + ], + "exclusion_conditions": [ + "排除把近年恢复使用的 contested name 直接当作当前 accepted name 的结果。", + "排除只读到 Wallach 2014 的 lectotype 指定、没有继续读取 comment 与 type comment 修正的结果。", + "排除未同时输出 restricted type locality 与 contested-name holotype 的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "name_role", + "name", + "status_or_evidence", + "specimen_role", + "specimen_code", + "supporting_note" + ], + "rank": "emit 1 for ACCEPTED_NAME and 2 for CONTESTED_NAME", + "name_role": [ + "ACCEPTED_NAME", + "CONTESTED_NAME" + ], + "name_fields": "use the current binomial spellings exactly", + "specimen_code_normalization": "preserve museum abbreviations, spaces, parentheses, and specimen punctuation exactly as the page shows", + "sorting_or_selection": "emit rows in the fixed order ACCEPTED_NAME then CONTESTED_NAME" + } + } +} diff --git a/data_zh/constraint/wateroffice_001.json b/data_zh/constraint/wateroffice_001.json new file mode 100644 index 0000000000000000000000000000000000000000..ed9741c35b05b049b98226c67558c963d65100cc --- /dev/null +++ b/data_zh/constraint/wateroffice_001.json @@ -0,0 +1,67 @@ +{ + "task_id": "wateroffice_001", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我在整理圣约翰河春季汛期的历史日流量对比资料，想沿主河道确认当前实时站网中，哪一站是最后一个仍可同时比较 1973 年和 2018 年 3–4 月日流量的站点，以及在它下游方向遇到的第一个不再满足该条件的主河道站点。请先以 Wateroffice 在 2026 年 4 月 16 日页面上显示的当前实时监测站网为准，只保留属于 Saint John River 主河道的站点；再逐站下钻历史 availability 页面，区分 Flow Data Availability 与 Daily Water Level Data Availability，并核对 1973 年和 2018 年 3–4 月是否都具备完整日流量记录。若目标窗口满足完整日流量条件，则 target_window_status 记为 PASS，final_verdict 写 KEEP；若目标年份只有水位记录、没有日流量记录，则 target_window_status 记为 LEVEL_ONLY，final_verdict 写 REJECT；若有日流量记录，但 1973 年 3–4 月或 2018 年 3–4 月中任一目标月份缺失或不完整，则 target_window_status 记为 FLOW_GAP，final_verdict 写 REJECT。最后，请输出两行 breakpoint table，列为 rank|station_number|breakpoint_role|target_window_status|final_verdict。第一行填写最后一个仍可用站点，breakpoint_role 固定写 LAST_USABLE；第二行填写其下游方向遇到的第一个失败站点，breakpoint_role 固定写 FIRST_DOWNSTREAM_FAIL。", + "start_url": "https://wateroffice.ec.gc.ca/search/real_time_e.html", + "output_format": "请输出两行 breakpoint table，列为 rank|station_number|breakpoint_role|target_window_status|final_verdict。", + "oracle_answer": "1|01AF002|LAST_USABLE|PASS|KEEP\n2|01AK003|FIRST_DOWNSTREAM_FAIL|LEVEL_ONLY|REJECT", + "metadata": { + "State-Gated Retrieval": [ + "只在当前实时站网中的 Saint John River 主河道候选站里判断最后一个仍可用于目标历史窗口比较的站点。", + "历史 availability 页面必须区分 Flow Data Availability 与 Daily Water Level Data Availability，并核对 1973/2018 年 3–4 月完整性。", + "最终要在同一验证规则下同时给出 LAST_USABLE 与 FIRST_DOWNSTREAM_FAIL 两个断点行。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the current live mainstem candidate list yields the Saint John River candidate chain whose downstream breakpoints must be checked", + "per-station historical availability pages yield Flow Data Availability, Daily Water Level Data Availability, and target-month completeness for 1973 and 2018", + "the final breakpoint rows are produced only after deep availability checks identify the last usable station and the first downstream failure under the same rule" + ], + "control_dependency": [ + "the breakpoint pair must be determined from historical availability that distinguishes flow from level-only evidence", + "target-year/month completeness must be checked on the availability page rather than inferred from the live-station list", + "the second row is emitted only after the first downstream failing mainstem station is fixed under the same deep rule" + ], + "freeze": { + "historical_window": "mainstem candidate stations evaluated within the fixed historical March/April daily-availability windows for 1973 and 2018, using station ordering and completeness signals as nearly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在当前实时站网中的 Saint John River 主河道候选站里判断最后一个仍可用于目标历史窗口比较的站点。", + "历史 availability 页面必须区分 Flow Data Availability 与 Daily Water Level Data Availability，并核对 1973/2018 年 3–4 月完整性。", + "最终要在同一验证规则下同时给出 LAST_USABLE 与 FIRST_DOWNSTREAM_FAIL 两个断点行。" + ], + "exclusion_conditions": [ + "排除只看当前实时主河道候选集、按参考索引直接确定断点的浅层结果。", + "排除把 level-only 证据误当成满足 Flow 的结果。", + "排除没有逐站下钻 availability 页核验目标月份完整性的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "breakpoint_role", + "target_window_status", + "final_verdict" + ], + "rank": "emit `1` for LAST_USABLE and `2` for FIRST_DOWNSTREAM_FAIL", + "station_number": "preserve the station number exactly", + "breakpoint_role": "emit `LAST_USABLE` and `FIRST_DOWNSTREAM_FAIL` exactly", + "target_window_status": "emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly", + "final_verdict": "emit `KEEP` for the usable breakpoint row and `REJECT` for the downstream failing breakpoint row", + "stop_condition": [ + "the last usable mainstem station is fixed under the deep availability rule", + "the first downstream failing mainstem station is fixed under the same rule before the two-row output is emitted" + ] + } + } +} diff --git a/data_zh/constraint/wateroffice_002.json b/data_zh/constraint/wateroffice_002.json new file mode 100644 index 0000000000000000000000000000000000000000..e6d7bfe25f93ba3f749a478d7af0bd1e416a550c --- /dev/null +++ b/data_zh/constraint/wateroffice_002.json @@ -0,0 +1,66 @@ +{ + "task_id": "wateroffice_002", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "我整理 Bulkley River 从 Houston 到 Hazelton 河段的历史日流量，想逐站核对 Bulkley River 主河道候选站在 1948 年和 1950 年 4–7 月是否真正具备完整日流量记录。请先在 Historical Results 列表中筛出位于 Bulkley River 主河道、且位于 Houston 到 Hazelton 河段内、表面上看起来覆盖 1948 年和 1950 年并带有 Flow 标签的候选站点；再逐站打开 availability 页面，核对目标年份是否位于 Flow 区，以及 April-July 是否全部为 C。若目标窗口满足完整日流量条件，则 target_window_status 记为 PASS，final_verdict 写 KEEP；若目标年份只有水位记录、没有日流量记录，则 target_window_status 记为 LEVEL_ONLY，final_verdict 写 REJECT；若有日流量记录，但 4–7 月中任一目标月份不是完整月份，则 target_window_status 记为 FLOW_GAP，final_verdict 写 REJECT。最后，请按从下游到上游的顺序输出一张表，列为 rank|station_number|target_window_status|final_verdict。", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "请按从下游到上游的顺序输出一张表，列为 rank|station_number|target_window_status|final_verdict。", + "oracle_answer": "1|08EE004|PASS|KEEP\n2|08EE001|LEVEL_ONLY|REJECT\n3|08EE005|FLOW_GAP|REJECT\n4|08EE003|FLOW_GAP|REJECT", + "metadata": { + "State-Gated Retrieval": [ + "先在 Historical Results 列表层找出表面上看起来覆盖 1948/1950 且带 Flow 标签的主河道候选站。", + "真正合格的站点必须在 availability 页面上同时满足：目标年份位于 Flow 区，且 April-July 全部为 C。", + "最终必须按同一候选集逐站给出 target_window_status 和 final_verdict，并按从下游到上游输出。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Historical Results list yields four downstream-to-upstream mainstem candidates whose result rows span the target years and include Flow labels", + "each candidate availability page yields whether the target years are in the Flow table and whether April-July is complete", + "the final ordered rows are produced only after all four candidates are classified under the stricter Flow-table-and-Apr-Jul-C rule" + ], + "control_dependency": [ + "list-level year spans and coarse Flow tags must be confirmed by explicit target-month checks on the availability page", + "Hazelton, Smithers, and Houston candidate statuses must be fixed before the downstream-most KEEP row can be confirmed", + "row order and KEEP/REJECT labels must be emitted only after the stricter availability rule is applied to all four stations" + ], + "freeze": { + "historical_window": "the target mainstem stations tested within the fixed historical daily Flow-availability windows for 1948 and 1950, with April-July complete-C coverage used as nearly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先在 Historical Results 列表层找出表面上看起来覆盖 1948/1950 且带 Flow 标签的主河道候选站。", + "真正合格的站点必须在 availability 页面上同时满足：目标年份位于 Flow 区，且 April-July 全部为 C。", + "最终必须按同一候选集逐站给出 target_window_status 和 final_verdict，并按从下游到上游输出。" + ], + "exclusion_conditions": [ + "排除只依据列表层“年份跨度 + 粗 Flow 标签”就认定可用的站点。", + "排除把 LEVEL_ONLY 或 FLOW_GAP 站点标成 KEEP 的结果。", + "排除没有把更强的 availability 规则重新施加到所有浅层候选的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "target_window_status", + "final_verdict" + ], + "rank": "emit 1 through 4 in downstream-to-upstream order within the validated candidate set", + "station_number": "preserve the station number exactly", + "target_window_status": "emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly", + "final_verdict": "emit `KEEP` or `REJECT` exactly", + "sorting_or_selection": "downstream to upstream within the validated Bulkley River mainstem candidate set", + "stop_condition": [ + "all four shallow candidates are classified under the stricter availability rule", + "the ordered table is emitted only after the downstream-to-upstream sequence is fixed" + ] + } + } +} diff --git a/data_zh/constraint/wateroffice_003.json b/data_zh/constraint/wateroffice_003.json new file mode 100644 index 0000000000000000000000000000000000000000..5f1981a69abfe4ad64db17af6eb459d1ba286c66 --- /dev/null +++ b/data_zh/constraint/wateroffice_003.json @@ -0,0 +1,62 @@ +{ + "task_id": "wateroffice_003", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "我在整理 Thompson River 从 Chase 到 Spences Bridge 河段的历史融雪期日流量资料，想逐站核对这一路径上的主河道站点是否真正具备 1958 年和 1971 年 5–7 月的日流量记录。先按从 Chase 下游到 Spences Bridge 的河道顺序，筛选站点列表中显示可覆盖 1958 年和 1971 年、且带有流量记录的 Thompson River 主河道站点；再逐站核对这些站点在 1958 年和 1971 年两个年份的 5–7 月期间，是否确实提供完整的日流量记录。若某站在目标年份只有水位记录、没有日流量记录，则记为 LEVEL_ONLY；若有日流量记录但 5–7 月窗口缺失，或任一目标月份不完整，则记为 FLOW_GAP。只有两个年份的 5–7 月日流量记录都满足要求时，final_verdict 才写 KEEP，否则写 REJECT。最后，请按从 Chase 下游到 Spences Bridge 的河道顺序输出一张表，列为 rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict。", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "请按从 Chase 下游到 Spences Bridge 的河道顺序输出一张表，列为 rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict。", + "oracle_answer": "1|08LE031|SOUTH THOMPSON RIVER AT CHASE|PASS|PASS|KEEP\n2|08LE069|SOUTH THOMPSON RIVER AT MONTE CREEK|FLOW_GAP|LEVEL_ONLY|REJECT\n3|08LF023|THOMPSON RIVER AT KAMLOOPS|LEVEL_ONLY|LEVEL_ONLY|REJECT\n4|08LF033|THOMPSON RIVER NEAR SAVONA|FLOW_GAP|FLOW_GAP|REJECT\n5|08LF051|THOMPSON RIVER NEAR SPENCES BRIDGE|PASS|PASS|KEEP", + "metadata": { + "State-Gated Retrieval": [ + "题目涉及的 5 个候选站都必须在 availability 页核验目标年份是否位于 Flow 表中，且 May-July 是否全部为 C。", + "每个站最终都要输出对两个目标年份的 PASS / LEVEL_ONLY / FLOW_GAP 等判定，并据此标记 KEEP 或 REJECT。", + "结果顺序必须保持题目要求的河道路径排序。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the river-path ordering yields five South Thompson / Thompson mainstem candidates", + "each station's availability page yields whether 1958 and 1971 are present in the Flow table and whether May-July is complete", + "final rows are produced only after every candidate is classified under the stricter target-year and target-month Flow rule" + ], + "control_dependency": [ + "overall year coverage on the results list must be confirmed by the availability page inside the Flow table", + "Monte Creek, Savona, and Kamloops must be rejected by LEVEL_ONLY / FLOW_GAP evidence before the KEEP rows are final", + "candidate ordering remains fixed, but status labels must be rewritten after the deeper availability rule is applied to all five stations" + ], + "freeze": { + "historical_window": "the ordered South Thompson / Thompson mainstem candidates tested against 1958 and 1971 Flow availability, with May-July requiring complete C coverage" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "题目涉及的 5 个候选站都必须在 availability 页核验目标年份是否位于 Flow 表中，且 May-July 是否全部为 C。", + "每个站最终都要输出对两个目标年份的 PASS / LEVEL_ONLY / FLOW_GAP 等判定，并据此标记 KEEP 或 REJECT。", + "结果顺序必须保持题目要求的河道路径排序。" + ], + "exclusion_conditions": [ + "排除把列表层整体年份覆盖当成足够证据的浅层结果。", + "排除没有区分 Flow 表内目标年、月份完整性与 Level-only 证据的结果。", + "排除未对全部 5 个候选统一应用同一深层规则的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "station_name", + "1958_MayJul", + "1971_MayJul", + "final_verdict" + ], + "rank": "use the fixed Chase-to-Spences-Bridge mainstem order from the reference index, not the transient search-result order", + "year_window_fields": "the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP", + "final_verdict": "emit `KEEP` or `REJECT` exactly" + } + } +} diff --git a/data_zh/constraint/wateroffice_004.json b/data_zh/constraint/wateroffice_004.json new file mode 100644 index 0000000000000000000000000000000000000000..a8df91908f6a24bdedcaf45f736b7897998b2472 --- /dev/null +++ b/data_zh/constraint/wateroffice_004.json @@ -0,0 +1,62 @@ +{ + "task_id": "wateroffice_004", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 13, + "instruction": "我在整理 Columbia River 主河道从 Fairmont Hot Springs 到 International Boundary 河段的历史日流量资料，想逐站核对 Wateroffice 中哪些测站在 1955 年和 1956 年的 5–10 月具备完整日流量记录。请在 Wateroffice 中先定位位于 Columbia River 主河道、介于 Fairmont Hot Springs 和 International Boundary 之间，且站点记录覆盖 1955 年和 1956 年的测站，再按河道从上游到下游逐站检查 1955 年和 1956 年 5–10 月的日流量可用性。若某站在某个目标年份只有水位记录、没有日流量记录，则该年份记为 LEVEL_ONLY；若该年 5–10 月日流量均完整，记为 PASS‘除这种情况外，只要该年份没有可用的日流量记录，或 5–10 月中任一月份不是完整月份，就记为 FLOW_GAP。只有两个年份都满足条件时，final_verdict 才写 KEEP，否则写 REJEC。最后，请按从上游到下游的河道顺序输出一张表，列为 rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict。", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "请按从上游到下游的河道顺序输出一张表，列为 rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict。", + "oracle_answer": "1|08NA045|COLUMBIA RIVER NEAR FAIRMONT HOT SPRINGS|PASS|PASS|KEEP\n2|08NA004|COLUMBIA RIVER AT ATHALMER|LEVEL_ONLY|LEVEL_ONLY|REJECT\n3|08NA052|COLUMBIA RIVER NEAR EDGEWATER|PASS|FLOW_GAP|REJECT\n4|08NA002|COLUMBIA RIVER AT NICHOLSON|PASS|PASS|KEEP\n5|08NB005|COLUMBIA RIVER AT DONALD|PASS|PASS|KEEP\n6|08NB006|COLUMBIA RIVER AT SURPRISE RAPIDS|PASS|PASS|KEEP\n7|08ND007|COLUMBIA RIVER ABOVE NAGLE CREEK|PASS|PASS|KEEP\n8|08ND011|COLUMBIA RIVER ABOVE STEAMBOAT RAPIDS|FLOW_GAP|PASS|REJECT\n9|08ND006|COLUMBIA RIVER AT TWELVE MILE FERRY|PASS|PASS|KEEP\n10|08NE002|COLUMBIA RIVER AT CASTLEGAR|LEVEL_ONLY|LEVEL_ONLY|REJECT\n11|08NE049|COLUMBIA RIVER AT BIRCHBANK|PASS|PASS|KEEP\n12|08NE003|COLUMBIA RIVER AT TRAIL|LEVEL_ONLY|LEVEL_ONLY|REJECT\n13|08NE058|COLUMBIA RIVER AT INTERNATIONAL BOUNDARY|PASS|PASS|KEEP", + "metadata": { + "State-Gated Retrieval": [ + "所有候选 Columbia River 站点都必须下钻 availability 页，确认目标年份位于 Flow 表中且 May-October 全为 C。", + "每个站都要给出 1955、1956 两年的 KEEP / REJECT 依据，并区分 LEVEL_ONLY、FLOW_GAP 与整体年份跨度陷阱。", + "最终表格要保持题目规定的顺序与字段。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Columbia River candidate ordering yields fourteen stations spanning the target years", + "each availability page yields whether 1955 and 1956 are present in the Flow table and whether May-October is complete", + "final rows are produced only after every station is classified under the stricter Flow-table-and-May-Oct-C rule" + ], + "control_dependency": [ + "list-level year spans must be confirmed by the availability page inside the Flow table", + "LEVEL_ONLY and FLOW_GAP evidence must be applied to each station before the KEEP/REJECT table is finalized", + "candidate counts and rejection reasons must be determined after the stricter availability rule replaces the shallow year-span heuristic" + ], + "freeze": { + "historical_window": "the ordered Columbia River candidates tested against 1955 and 1956 Flow availability, with May-October requiring complete C coverage" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "所有候选 Columbia River 站点都必须下钻 availability 页，确认目标年份位于 Flow 表中且 May-October 全为 C。", + "每个站都要给出 1955、1956 两年的 KEEP / REJECT 依据，并区分 LEVEL_ONLY、FLOW_GAP 与整体年份跨度陷阱。", + "最终表格要保持题目规定的顺序与字段。" + ], + "exclusion_conditions": [ + "排除只凭“整体年份跨过 1955/1956”就保留候选站的浅层结果。", + "排除未逐站区分 Flow 可用、Level-only 和月份不完整的结果。", + "排除没有统一把深层 availability 规则施加到所有 14 个候选站的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "station_name", + "1955_MayOct", + "1956_MayOct", + "final_verdict" + ], + "rank": "use the fixed upstream-to-downstream Columbia mainstem order from the reference index, not the transient search-result order", + "year_window_fields": "the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP", + "final_verdict": "emit `KEEP` or `REJECT` exactly" + } + } +} diff --git a/data_zh/constraint/wateroffice_005.json b/data_zh/constraint/wateroffice_005.json new file mode 100644 index 0000000000000000000000000000000000000000..33d16b63656d1b99fb2005251ecfad2f5075e87b --- /dev/null +++ b/data_zh/constraint/wateroffice_005.json @@ -0,0 +1,74 @@ +{ + "task_id": "wateroffice_005", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "我在整理 Peace River 从 Dunvegan Bridge 到 Fifth Meridian 河段的历史日流量资料，想同时核对三件事：真正最下游可复用站、该站之后沿主河道向下游遇到的第一个失效站，以及只按站点层面的年份覆盖和数据类型初筛时会被误判为最下游可用站的 provisional 末端站。请只在位于 Dunvegan Bridge 与 Fifth Meridian 之间的 Peace River 主河道测站中筛选；先根据站点列表中的年份覆盖和数据类型找出表面上看起来同时覆盖 1966 和 1967 且带有日流量记录类型的浅层候选，再逐站打开 availability 页面，核对 1966 年和 1967 年的 5–9 月是否都位于 Flow 表中且每个月均为完整月。若两个年份的目标窗口都满足完整日流量条件，则 target_window_status 记为 PASS；若目标年份只有水位记录、没有日流量记录，则记为 LEVEL_ONLY；若有日流量记录，但 5–9 月中任一目标月份不是完整月份，则记为 FLOW_GAP；若目标年份既没有日流量记录，也没有水位记录，则记为 NO_TARGET_RECORD。最后，请输出三行诊断表，列为 rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count。三行依次填写 FINAL_STATION、FIRST_BREAK_AFTER_FINAL、PROVISIONAL_STATION，其中后两列在三行中都重复填写全局的 provisional_count 与 final_count。", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "请输出三行诊断表，列为 rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count。", + "oracle_answer": "1|07HA001|FINAL_STATION|PASS|5|2\n2|07HD001|FIRST_BREAK_AFTER_FINAL|FLOW_GAP|5|2\n3|07KA002|PROVISIONAL_STATION|FLOW_GAP|5|2", + "metadata": { + "State-Gated Retrieval": [ + "只在位于 Dunvegan Bridge 与 Fifth Meridian 之间的 Peace River 主河道测站中筛选。", + "真正可用的站点必须在 availability 页满足：1966 与 1967 两年都位于 Flow 表中，且 May-September 每个月都是完整月份。", + "最终输出必须同时给出 FINAL_STATION、FIRST_BREAK_AFTER_FINAL 与 PROVISIONAL_STATION 三行，并在每行重复填写 provisional_count 与 final_count。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Peace River mainstem chain between Dunvegan Bridge and Fifth Meridian yields the shallow candidate set and the downstream breakpoint positions that need revalidation", + "each availability page yields whether 1966 and 1967 are present in the Flow or Level tables and whether May-September is complete", + "final rows are produced only after the final station, the first downstream failure, and the provisional downstream winner are all fixed under the same deep availability rule" + ], + "control_dependency": [ + "station-level target-year Flow evidence must be validated by explicit May-September completeness checks on the availability page", + "the final downstream reusable station and the first downstream failure must be determined under the same deep rule rather than from the shallow candidate screen", + "the provisional downstream winner stays in the output only as a diagnostic row after its FLOW_GAP status is confirmed on the availability page" + ], + "freeze": { + "historical_window": "Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian, evaluated within the fixed historical 1966 and 1967 Flow-availability windows, with May-September complete-C coverage used as nearly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在位于 Dunvegan Bridge 与 Fifth Meridian 之间的 Peace River 主河道测站中筛选。", + "真正可用的站点必须在 availability 页满足：1966 与 1967 两年都位于 Flow 表中，且 May-September 每个月都是完整月份。", + "最终输出必须同时给出 FINAL_STATION、FIRST_BREAK_AFTER_FINAL 与 PROVISIONAL_STATION 三行，并在每行重复填写 provisional_count 与 final_count。" + ], + "exclusion_conditions": [ + "排除只凭“目标年份有 Flow 记录”就认定站点可用的浅层判断。", + "排除未逐站检查 May-September 全部完整性的结果。", + "排除把 07KA002 这类 availability 深层证据显示为 FLOW_GAP 的站点标成 FINAL_STATION 的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "diagnosis_role", + "target_window_status", + "provisional_count", + "final_count" + ], + "rank": "emit the fixed order 1, 2, 3 for FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION", + "station_number": "use uppercase WSC station codes exactly as the Reference Index and availability pages show", + "diagnosis_role": [ + "FINAL_STATION", + "FIRST_BREAK_AFTER_FINAL", + "PROVISIONAL_STATION" + ], + "target_window_status": [ + "PASS", + "LEVEL_ONLY", + "FLOW_GAP", + "NO_TARGET_RECORD" + ], + "count_fields": "repeat the global provisional_count and final_count in every row as plain integers", + "sorting_or_selection": "emit rows in the fixed diagnostic order FINAL_STATION, FIRST_BREAK_AFTER_FINAL, PROVISIONAL_STATION" + } + } + } diff --git a/data_zh/constraint/waterquality_001.json b/data_zh/constraint/waterquality_001.json new file mode 100644 index 0000000000000000000000000000000000000000..98e1cb03a8d87d85f6a7fa5cbe9f0814e9effc30 --- /dev/null +++ b/data_zh/constraint/waterquality_001.json @@ -0,0 +1,67 @@ +{ + "task_id": "waterquality_001", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我在梳理里约格兰德中游一段既往监测期的记录，想选出两处适合用于观察主河道污水影响的监测站点。先从 RIO GRANDE AT EMBUDO, NM 开始沿下游方向查找，只保留确实位于 Rio Grande 主河道上的监测站点。然后，找到 Town of Bernalillo 污水处理厂排放口下游第一个满足以下条件的主河道监测点；再继续向下游，找到已经同时越过 Town of Bernalillo 污水处理厂排放口和 Rio Rancho No. 2 污水处理厂排放口后的第一个满足相同条件的主河道监测点。两处站点都必须满足：站点本身不是排放口、设施、井、运河或排水渠；站点详情页中的类型标注为 River/Stream；Microbiological、Nutrient、Organics, Other 和 Physical 四类记录完整覆盖 2015–2020 年；且 Microbiological 与 Physical 两类记录的起始年份均早于 2010 年。最后，请按从上游到下游的顺序输出一行字符串：<主河道站点ID>||，两段之间用英文逗号分隔。", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "请按从上游到下游的顺序输出一行字符串：<主河道站点ID>||，两段之间用英文逗号分隔。", + "oracle_answer": "SANDIAWQ_WQX-RG003|2004|2004,SANDIAWQ_WQX-RG008|2004|2004", + "metadata": { + "State-Gated Retrieval": [ + "只从 RIO GRANDE AT EMBUDO, NM 下游的 Rio Grande 主河道监测站中找两处目标站点，并要求都已越过题目指定排放口位置。", + "站点 detail page 必须明确为 River/Stream，且 Microbiological、Nutrient、Organics, Other、Physical 四类记录完整覆盖 2015-2020，同时 Microbiological 与 Physical 的起始年都早于 2010。", + "最终两处站点按上游到下游顺序输出。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "provider/list views yield the Rio Grande mainstem candidates downstream of the Bernalillo and Rio Rancho No. 2 discharge points", + "detail pages yield flow position, object layer, characteristic-group period-of-record coverage for 2015-2020, and the Microbiological/Physical baseline years", + "final rows are produced only after the corrected downstream sentry stations are fixed and ordered from upstream to downstream" + ], + "control_dependency": [ + "provider-list stream tags are only provisional and must be corrected by detail-page mainstem and object-layer validation", + "target-window presence is insufficient until full 2015-2020 coverage is confirmed on the detail page for all four groups", + "once RG002/RG007 fail the deeper checks, the workflow must keep the discharge-point downstream root state and continue to RG003/RG008" + ], + "freeze": { + "historical_window": "Rio Grande mainstem stations downstream of the Town of Bernalillo and Rio Rancho No. 2 WWTP outfalls, validated against 2015-2020 coverage for Microbiological, Nutrient, Organics, Other, and Physical" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只从 RIO GRANDE AT EMBUDO, NM 下游的 Rio Grande 主河道监测站中找两处目标站点，并要求都已越过题目指定排放口位置。", + "站点 detail page 必须明确为 River/Stream，且 Microbiological、Nutrient、Organics, Other、Physical 四类记录完整覆盖 2015-2020，同时 Microbiological 与 Physical 的起始年都早于 2010。", + "最终两处站点按上游到下游顺序输出。" + ], + "exclusion_conditions": [ + "排除 provider list 上浅层的 (Stream) 标签或目标窗口附近有记录、但 detail page 不能满足 flow position、object layer 或完整 period-of-record 条件的站点。", + "排除排放口、设施、井、运河或排水渠类位置。", + "排除 RG002、RG007 这类不是相应排口下游合格哨点的候选。" + ], + "normalization": { + "record_separator": ",", + "field_separator": "|", + "schema_per_record": [ + "MonitoringLocationIdentifier", + "Microbiological_start_year", + "Physical_start_year" + ], + "ordering": "emit exactly two records from upstream to downstream", + "station_id": "use uppercase MonitoringLocationIdentifier", + "year_fields": "emit four-digit years as plain integers", + "selection": { + "record_1": "the first qualifying mainstem station below the Bernalillo outfall", + "record_2": "the first qualifying mainstem station below both the Bernalillo and Rio Rancho No. 2 outfalls" + }, + "stop_condition": [ + "the Bernalillo branch stops only after its first qualifying mainstem station is fixed", + "the Rio Rancho No. 2 branch stops only after its first qualifying mainstem station is fixed", + "the two segments are emitted as one comma-joined line in upstream-to-downstream order" + ] + } + } +} diff --git a/data_zh/constraint/waterquality_002.json b/data_zh/constraint/waterquality_002.json new file mode 100644 index 0000000000000000000000000000000000000000..2c9dbf8eedf5b7bf2b04523910c67f371d5f2107 --- /dev/null +++ b/data_zh/constraint/waterquality_002.json @@ -0,0 +1,67 @@ +{ + "task_id": "waterquality_002", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我在梳理里奥格兰德河下游 2001–2010 年的变化趋势，想从位于 RIO GRANDE BELOW ANZALDUAS 下游且仍属于 HUC 13090002 的监测站点中，为 Hidalgo County 和 Cameron County 各选出一个代表站点。先在上述范围内分别筛选两县的候选站点，只保留站点详情页中类型标注为 River/Stream 的监测站点，并要求其 Microbiological、Nutrient、Organics, Other 和 Physical 四类记录均覆盖 2001–2010 年；若同一县有多个站点符合条件，则选择四类记录首次同时齐备时间更早的那个站点。随后，记录入选站点的 MonitoringLocationIdentifier、四类记录最早同时齐备的年份，以及 Microbiological、Nutrient、Organics, Other、Physical 各自的起始年份。最后，请按 Hidalgo、Cameron 的顺序输出一行字符串：:|<四类同时具备的最早年份>||||，两段之间用英文逗号分隔。", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "请按 Hidalgo、Cameron 的顺序输出一行字符串：:|<四类同时具备的最早年份>||||，两段之间用英文逗号分隔。", + "oracle_answer": "Hidalgo:TCEQMAIN-15808|1998|1998|1998|1998|1998,Cameron:TCEQMAIN-13177|1995|1981|1981|1995|1981", + "metadata": { + "State-Gated Retrieval": [ + "只在 RIO GRANDE BELOW ANZALDUAS 下游且仍属于 HUC 13090002 的监测站点中，为 Hidalgo County 与 Cameron County 各选一个代表站。", + "候选 detail page 必须为 River/Stream，且 Microbiological、Nutrient、Organics, Other、Physical 四类记录都覆盖 2001-2010。", + "若同县有多个合格站，则取四类记录首次同时齐备年份更早的站点。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the downstream root station and county split yield Hidalgo and Cameron candidate mainstem stations within HUC 13090002", + "detail pages yield River/Stream validity, the four characteristic-group start years, and the earliest year when all four groups are simultaneously present for 2001-2010 coverage", + "final rows are produced only after county-specific candidate chains are rerun under the preserved downstream root state and then ranked by common-start year" + ], + "control_dependency": [ + "the Hidalgo branch must preserve the “below TCEQMAIN-13664” downstream root state rather than flowing back to the anchor itself", + "a multi-select characteristic-group hit is only provisional until all four groups are fanned in to one MonitoringLocationIdentifier and tidal/intake conflicts are excluded on the detail page", + "county winners are valid only after late-start and non-river candidates are removed and the common-start-year tie-break is recomputed" + ], + "freeze": { + "historical_window": "stations below RIO GRANDE BELOW ANZALDUAS within HUC 13090002, split by Hidalgo and Cameron County, with Microbiological, Nutrient, Organics, Other, and Physical coverage over 2001-2010" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在 RIO GRANDE BELOW ANZALDUAS 下游且仍属于 HUC 13090002 的监测站点中，为 Hidalgo County 与 Cameron County 各选一个代表站。", + "候选 detail page 必须为 River/Stream，且 Microbiological、Nutrient、Organics, Other、Physical 四类记录都覆盖 2001-2010。", + "若同县有多个合格站，则取四类记录首次同时齐备年份更早的站点。" + ], + "exclusion_conditions": [ + "排除在 Hidalgo 分支丢失 downstream 根状态、把起始站自身回流进候选集的结果。", + "排除把四个 Characteristic Group 一次多选就当成同时满足，而没有按站点 ID 扇入核验的结果。", + "排除 tidal、intake、late-start 等 detail page 明确冲突的站点。" + ], + "normalization": { + "record_separator": ",", + "field_separator": "|", + "schema_per_record": [ + "County:MonitoringLocationIdentifier", + "common_start_year", + "Microbiological_start_year", + "Nutrient_start_year", + "Organics_Other_start_year", + "Physical_start_year" + ], + "ordering": "emit exactly two records, with Hidalgo first and Cameron second", + "county_prefix": "use the county label in title case, followed by : and the uppercase MonitoringLocationIdentifier", + "year_fields": "emit four-digit years as plain integers", + "common_start_year": "the earliest year in which all four required groups are simultaneously present for the chosen county station", + "stop_condition": [ + "each county branch is rerun until one River/Stream station survives all four group checks", + "the county winner is fixed only after late-start and non-river candidates are excluded at detail depth", + "the two county segments are emitted on one line in the fixed Hidalgo-then-Cameron order" + ] + } + } +} diff --git a/data_zh/constraint/waterquality_003.json b/data_zh/constraint/waterquality_003.json new file mode 100644 index 0000000000000000000000000000000000000000..4eaa37b97d6b0467562a830c9ccaa6d13976e7cf --- /dev/null +++ b/data_zh/constraint/waterquality_003.json @@ -0,0 +1,66 @@ +{ + "task_id": "waterquality_003", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "我在整理 Brazos River 自 Brazos Rv at Waco, TX 向下游延伸的主干河段 2012–2018 年水质对照资料，想在主干河段经过的三个 HUC（12060202、12070101、12070104）中，各选出一处适合作为长期对照点的 TCEQ 监测站。请按以下顺序处理：先以 Brazos Rv at Waco, TX 下游的 Brazos River 主干河段为范围，分别在 12060202、12070101 和 12070104 三个 HUC 中筛选候选站点；只保留站点详情页标注为 River/Stream、且站名仍对应 Brazos River 主干而不是其他命名水体的监测位置。随后，核对这些站点的记录类别，只保留 Inorganics, Major, Non-metals、Microbiological、Nutrient、Organics, Other 和 Physical 五类记录均覆盖 2012–2018 年的站点，具体指站点起始年不晚于 2012、结束年不早于 2018。最后，请按从上游到下游的顺序列出 3 个结果，每行格式为：||<五类同时具备的最早年份>|||||。", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "请按从上游到下游的顺序列出 3 个结果，每行格式为：||<五类同时具备的最早年份>|||||。", + "oracle_answer": "12060202|TCEQMAIN-12037|2000|1991|2000|1991|1999|1991\n12070101|TCEQMAIN-12030|2006|1972|1972|1972|2006|1972\n12070104|TCEQMAIN-11848|1975|1974|1975|1974|1975|1974", + "metadata": { + "State-Gated Retrieval": [ + "必须保持 Waco 锚点以下的 downstream 根状态，并在题目指定的 3 个 HUC 内寻找 Brazos 主干监测站。", + "每个候选站都要在 5 个 Characteristic Group 上完成分支检索与扇入，再在 detail page 核验 2012-2018 全窗口覆盖与主干语义。", + "每个 HUC 只保留共同起始年最早的合格站，并输出题目要求的起始年字段。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Waco downstream root state and three target HUC branches yield the Brazos mainstem candidate stations", + "detail pages yield true downstream position, mainstem-vs-tributary semantics, and five-group period-of-record coverage across 2012-2018", + "final rows are produced only after the three HUC branches are executed, merged by station, and ranked by the earliest year when all five groups are jointly available" + ], + "control_dependency": [ + "the workflow must preserve the downstream root state below Waco rather than reintroducing upstream stations like TCEQMAIN-12044", + "name-based waterbody matches must be validated on the detail page by excluding tributaries such as LITTLE BRAZOS RIVER and confirming full-window coverage", + "station ranking must be determined after false positives from partial-window records are removed" + ], + "freeze": { + "historical_window": "Brazos River mainstem stations downstream of the Waco anchor, split across HUC 12060202, 12070101, and 12070104, with five characteristic groups covering 2012-2018" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "必须保持 Waco 锚点以下的 downstream 根状态，并在题目指定的 3 个 HUC 内寻找 Brazos 主干监测站。", + "每个候选站都要在 5 个 Characteristic Group 上完成分支检索与扇入，再在 detail page 核验 2012-2018 全窗口覆盖与主干语义。", + "每个 HUC 只保留共同起始年最早的合格站，并输出题目要求的起始年字段。" + ], + "exclusion_conditions": [ + "排除丢掉 Waco 以下 downstream 根状态、把上游站带回候选集的结果。", + "排除把 LITTLE BRAZOS RIVER 等支流误当成 Brazos 主干的结果。", + "排除只因为查询窗口附近有数据、却未覆盖整个 2012-2018 窗口的站点。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "HUC", + "MonitoringLocationIdentifier", + "common_start_year", + "Inorganics_start", + "Microbiological_start", + "Nutrient_start", + "Organics_Other_start", + "Physical_start" + ], + "HUC": "preserve the HUC exactly as emitted in the source result", + "MonitoringLocationIdentifier": "preserve the monitoring-location identifier exactly, for example `TCEQMAIN-12037`", + "common_start_year": "emit the maximum of the five per-group start years", + "selection_rule": "only keep mainstem river/stream sites whose five required groups all cover the target 2012-2018 window", + "sorting_or_selection": "upstream to downstream along the mainstem" + } + } +} diff --git a/data_zh/constraint/waterquality_004.json b/data_zh/constraint/waterquality_004.json new file mode 100644 index 0000000000000000000000000000000000000000..95ee73446618bbcad2827373d7c0029a8bdcac6d --- /dev/null +++ b/data_zh/constraint/waterquality_004.json @@ -0,0 +1,67 @@ +{ + "task_id": "waterquality_004", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "我在核对 Trinity River 主河道上以 FM 85 附近河段为上游端、以 Interstate 10 附近河段为下游端的 1993–2001 年有毒污染物相关水质监测资料，想沿河为上游、中游和下游三段各选一处 TCEQ 长期对照站。\n请以 Trinity River 主河道在 FM 85 附近河段至 Interstate 10 附近河段之间的范围为起点，沿河分别在上游、中游和下游三段筛选候选监测位置；只保留站点记录中标注为 River/Stream，且站名仍对应 Trinity River 主干、而不是其他命名水体或分汊的监测位置。随后核对这些站点的记录类别，保留六类记录均覆盖 1993–2001 年的站点（具体指起始年不晚于 1993 且结束年不早于 2001），并按上游到下游输出结果。\n最后，请沿河流方向从上游到下游列出三行，每行格式为：||<六类同时具备的最早年份>||||||。", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "请沿河流方向从上游到下游列出三行，每行格式为：||<六类同时具备的最早年份>||||||。", + "oracle_answer": "12030105|TCEQMAIN-10924|1983|1982|1983|1982|1983|1983|1982\n12030202|TCEQMAIN-10897|1993|1969|1972|1972|1993|1974|1969\n12030203|TCEQMAIN-10892|1976|1969|1971|1972|1974|1976|1969", + "metadata": { + "State-Gated Retrieval": [ + "只在 Trinity River 主干语义成立的候选站中筛选，并要求 6 个 Characteristic Group 都覆盖 1993-2001。", + "必须把六个组别拆开检索并按站点 ID 扇入，再在 detail page 核验 full-window coverage 与 legacy toxics 组别完整性。", + "最终每个目标分区只保留满足全部组别要求且共同起始年最优的站。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Trinity River mainstem candidate stations are generated from the target HUC branches and six characteristic-group searches", + "detail pages yield River/Stream validity, 1993-2001 full-window coverage, and the group-specific start years needed for ranking", + "final rows are produced only after six-group fan-in and detail-page validation remove partial-group and non-mainstem false positives" + ], + "control_dependency": [ + "each of the six characteristic groups must be evaluated separately and intersected by station ID before a multi-select hit can be retained", + "station names and River/Stream tags are insufficient until the detail page confirms Trinity mainstem semantics and 1993-2001 full-window coverage", + "candidate rejection and final ranking must be determined after applying the PCBs / Organics, Other gap checks" + ], + "freeze": { + "historical_window": "Trinity River mainstem stations validated against six characteristic groups over 1993-2001, with ranking based on the earliest joint availability and group start years" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在 Trinity River 主干语义成立的候选站中筛选，并要求 6 个 Characteristic Group 都覆盖 1993-2001。", + "必须把六个组别拆开检索并按站点 ID 扇入，再在 detail page 核验 full-window coverage 与 legacy toxics 组别完整性。", + "最终每个目标分区只保留满足全部组别要求且共同起始年最优的站。" + ], + "exclusion_conditions": [ + "排除把 Characteristic Group 多选误当成同时满足的浅层结果。", + "排除只看站名和 River/Stream，不核验 1993-2001 全窗口覆盖的结果。", + "排除忽略 PCBs 或 Organics, Other 缺失的站点。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "HUC", + "MonitoringLocationIdentifier", + "common_start_year", + "Inorganics_start", + "Microbiological_start", + "Nutrient_start", + "Organics_Other_start", + "Organics_PCBs_start", + "Physical_start" + ], + "HUC": "preserve the HUC exactly as emitted in the source result", + "MonitoringLocationIdentifier": "preserve the monitoring-location identifier exactly, for example `TCEQMAIN-10924`", + "common_start_year": "emit the maximum of the six per-group start years", + "selection_rule": "only keep mainstem river/stream sites whose six required groups all cover the target window", + "sorting_or_selection": "upstream to downstream along the mainstem" + } + } +} diff --git a/data_zh/constraint/waterquality_005.json b/data_zh/constraint/waterquality_005.json new file mode 100644 index 0000000000000000000000000000000000000000..00183853636cb67a8e6ca8b3872c9038eb18d93a --- /dev/null +++ b/data_zh/constraint/waterquality_005.json @@ -0,0 +1,68 @@ +{ + "task_id": "waterquality_005", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 9, + "instruction": "我在整理 Neches River 下游 1978–1984 年的综合水质资料，想从 NECHES RIVER AT CR 4915 下游开始，找出离这一起点最近、且仍能代表 Neches River 内陆主河道的 TCEQ 长期对照站，并把该站九类 Characteristic Group 的起始年份整理成表。请沿主河道向下游查找，只保留站点详情页中类型标注为 River/Stream 的监测站点；同时排除位于湖库水体或 Sabine-Neches 出口边界河段的站点。然后在符合这些位置条件的站点中，锁定 Biological, Algae, Phytoplankton、Inorganics, Major, Non-metals、Inorganics, Minor, Metals、Microbiological、Nutrient、Organics, Other、Organics, PCBs、Organics, Pesticide 和 Physical 这九类记录都覆盖 1978–1984 年、且距离起点最近的那个最终站点。最后，请围绕该最终站点按九类 Characteristic Group 输出一张表，列为 rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year。行顺序固定为 Biological, Algae, Phytoplankton；Inorganics, Major, Non-metals；Inorganics, Minor, Metals；Microbiological；Nutrient；Organics, Other；Organics, PCBs；Organics, Pesticide；Physical。", + "start_url": "https://www.waterqualitydata.us/provider/STORET/TCEQMAIN/TCEQMAIN-10598/", + "output_format": "请输出一张 9 行表，列为 rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year。", + "oracle_answer": "1|TCEQMAIN-10580|12020003|Hardin County|Biological, Algae, Phytoplankton|1972|1977\n2|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Major, Non-metals|1971|1977\n3|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Minor, Metals|1974|1977\n4|TCEQMAIN-10580|12020003|Hardin County|Microbiological|1972|1977\n5|TCEQMAIN-10580|12020003|Hardin County|Nutrient|1972|1977\n6|TCEQMAIN-10580|12020003|Hardin County|Organics, Other|1974|1977\n7|TCEQMAIN-10580|12020003|Hardin County|Organics, PCBs|1974|1977\n8|TCEQMAIN-10580|12020003|Hardin County|Organics, Pesticide|1977|1977\n9|TCEQMAIN-10580|12020003|Hardin County|Physical|1971|1977", + "metadata": { + "State-Gated Retrieval": [ + "只在 NECHES RIVER AT CR 4915 下游、且仍能代表 Neches River 内陆主河道的 TCEQ 监测站中筛选。", + "候选站必须在 9 个 Characteristic Group 上都覆盖 1978-1984，并在 detail page 中继续满足 River/Stream、非湖库、非 Sabine-Neches 出口边界河段条件。", + "最终输出必须围绕唯一获胜站点，按固定的九类 Characteristic Group 顺序逐行列出 group_start_year 与 common_start_year。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the downstream root state from NECHES RIVER AT CR 4915 yields candidate inland mainstem stations across successive downstream HUCs", + "detail pages yield River/Stream validity, inland-vs-boundary semantics, and nine-group period-of-record coverage across 1978-1984", + "final rows are produced only after one winning station survives the inland-mainstem and nine-group fan-in checks and its nine group start years are emitted in the required order" + ], + "control_dependency": [ + "the nearest downstream mainstem station remains provisional until all nine characteristic groups are split, rerun, and intersected by station ID", + "the downstream search must continue to the next mainstem HUC when the first branch fails the nine-group coverage gate", + "location semantics remain valid only after detail-page exclusion of lake/reservoir and Sabine-Neches boundary stations" + ], + "freeze": { + "historical_window": "Neches River inland mainstem stations downstream of NECHES RIVER AT CR 4915, validated within the fixed 1978-1984 window against nine characteristic groups as largely stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在 NECHES RIVER AT CR 4915 下游、且仍能代表 Neches River 内陆主河道的 TCEQ 监测站中筛选。", + "候选站必须在 9 个 Characteristic Group 上都覆盖 1978-1984，并在 detail page 中继续满足 River/Stream、非湖库、非 Sabine-Neches 出口边界河段条件。", + "最终输出必须围绕唯一获胜站点，按固定的九类 Characteristic Group 顺序逐行列出 group_start_year 与 common_start_year。" + ], + "exclusion_conditions": [ + "排除只凭“最近下游主干站”语义就保留 TCEQMAIN-10591 的浅层结果。", + "排除没有把 9 个 Characteristic Group 拆开检索并按站点 ID 扇入核验的结果。", + "排除位于湖库水体或 Sabine-Neches 出口边界河段的站点。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "MonitoringLocationIdentifier", + "HUC", + "County", + "characteristic_group", + "group_start_year", + "common_start_year" + ], + "rank": "emit 1 through 9 in the fixed characteristic-group order required by the task", + "MonitoringLocationIdentifier": "use uppercase MonitoringLocationIdentifier", + "HUC": "emit the HUC as an 8-digit string with no separators", + "County": "use the county name exactly as shown on the detail page", + "characteristic_group": "preserve the group label exactly as listed in the task", + "year_fields": "emit four-digit years as plain integers", + "common_start_year": "repeat the earliest year in which all nine required groups are simultaneously present for the chosen station", + "sorting_or_selection": "emit rows in the fixed nine-group order stated in the task" + } + } +} diff --git a/data_zh/constraint/wonder_001.json b/data_zh/constraint/wonder_001.json new file mode 100644 index 0000000000000000000000000000000000000000..607621fe455b7fae1093c72fec6d3731b0e6a561 --- /dev/null +++ b/data_zh/constraint/wonder_001.json @@ -0,0 +1,64 @@ +{ + "task_id": "wonder_001", + "domain": "CDC_WONDER", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "我在准备一页关于 2020 年美国居家分娩变化的公共卫生简报，想找出与 2019 年同月相比，全体产妇居家分娩比例上升至少 25% 的月份，并同时查看这些月份在非西班牙裔黑人产妇和西班牙裔产妇中的对应变化。请先按日历月份比较 2019 年和 2020 年全体产妇的居家分娩比例，筛出 2020 年中较 2019 年同月上升至少 25% 的月份；再对这些月份补充非西班牙裔黑人产妇和西班牙裔产妇在 2020 年的居家分娩比例，以及相对 2019 年同月的变化。最后，请按日历月份顺序输出多行管道分隔表，表头固定为 month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel；所有数值直接写数字，不加百分号。", + "start_url": "https://wonder.cdc.gov/natality-expanded-current.html", + "output_format": "请按日历月份顺序输出多行管道分隔表，表头固定为 month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel；所有数值直接写数字，不加百分号。", + "oracle_answer": "month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel\nMay|1.03|1.49|45|0.74|54|0.55|57\nJune|1.04|1.31|26|0.66|20|0.48|30\nJuly|1.03|1.30|26|0.68|42|0.48|30\nAugust|1.02|1.29|26|0.69|50|0.48|26\nSeptember|1.01|1.31|30|0.73|43|0.54|54\nOctober|1.00|1.28|28|0.75|50|0.47|27\nNovember|0.99|1.30|31|0.73|43|0.55|67\nDecember|0.92|1.28|39|0.80|63|0.53|61", + "metadata": { + "State-Gated Retrieval": [ + "先按日历月份比较 2019 年与 2020 年全体产妇的居家分娩比例，只保留 2020 年较 2019 年同月上升至少 25% 的月份。", + "居家分娩分子必须使用完整 home 类别而不是单独 Home intended。", + "对这些月份，再补充 2020 年 Black non-Hispanic 与 Hispanic 产妇的居家分娩比例及相对 2019 年同月的变化。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "monthly natality queries yield the 2019 vs 2020 all-mother home-birth rates and the candidate month set", + "follow-up race/ethnicity queries yield 2020 Black non-Hispanic and Hispanic home-birth rates plus their same-month changes versus 2019", + "final rows are produced only after qualifying months are determined from rate growth and the resulting month set is reused for both subgroup backfill chains" + ], + "control_dependency": [ + "month selection must be based on relative rate increase rather than counts alone", + "the home-birth numerator must use Residence or an equivalent full-home measure rather than Home intended alone before downstream subgroup queries run", + "subgroup columns must be generated from the resulting month set rather than appended to earlier rows" + ], + "freeze": { + "historical_window": "2019 and 2020 U.S. natality monthly home-birth rates for all mothers, Black non-Hispanic mothers, and Hispanic mothers" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先按日历月份比较 2019 年与 2020 年全体产妇的居家分娩比例，只保留 2020 年较 2019 年同月上升至少 25% 的月份。", + "居家分娩分子必须使用完整 home 类别而不是单独 Home intended。", + "对这些月份，再补充 2020 年 Black non-Hispanic 与 Hispanic 产妇的居家分娩比例及相对 2019 年同月的变化。" + ], + "exclusion_conditions": [ + "排除把“比例上升至少 25%”误读为“人数上升至少 25%”的月份行集。", + "排除只用 Home intended 单类而不是完整 home numerator 的结果。", + "排除在错误月份集上补 subgroup 列的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row `month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel`", + "schema": [ + "month", + "all_2019", + "all_2020", + "all_rel", + "black_2020", + "black_rel", + "hispanic_2020", + "hispanic_rel" + ], + "month": "use the English month name and keep calendar order", + "numeric_fields": "all numeric outputs are plain numbers without a percent sign", + "relative_change_fields": "all_rel, black_rel, and hispanic_rel are emitted as integer percentages without the `%` character" + } + } +} diff --git a/data_zh/constraint/wonder_002.json b/data_zh/constraint/wonder_002.json new file mode 100644 index 0000000000000000000000000000000000000000..d205de418da729034a97b064d6ac3b10c6014879 --- /dev/null +++ b/data_zh/constraint/wonder_002.json @@ -0,0 +1,64 @@ +{ + "task_id": "wonder_002", + "domain": "CDC_WONDER", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "我在准备一页关于 2021 年美国婴儿死亡差异的公共卫生简报，想找出按母亲种族和西班牙裔来源划分、在报告中单独列示、婴儿死亡率高于全美总体水平且首位死因能够明确识别的群体。请先从报告中单独列出的相关群体入手，筛出婴儿死亡率高于全美总体水平、且能够明确给出首位死因的群体；再为每个符合条件的群体记录全年婴儿死亡率，以及新生儿期（出生后不满 28 天）和后新生儿期（出生后 28 天及以后）的死亡率，同时给出该群体的首位死因、该死因率，以及该死因在全体婴儿死因中的排名。最后，请按全年婴儿死亡率从高到低输出多行管道分隔表：group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank。", + "start_url": "https://wonder.cdc.gov/lbd-current-expanded.html", + "output_format": "最后，请按全年婴儿死亡率从高到低输出多行管道分隔表：group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank。", + "oracle_answer": "group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank\nBlack non-Hispanic|10.55|6.35|4.19|Short gestation and low birth weight|196.4|2\nAmerican Indian or Alaska Native non-Hispanic|7.46|3.83|3.67|Congenital malformations|134.0|1\nPuerto Rican Hispanic|6.05|3.93|2.13|Short gestation and low birth weight|108.9|2", + "metadata": { + "State-Gated Retrieval": [ + "只保留在 2021 年美国婴儿死亡统计中单独列示、全年 infant mortality rate 高于全美总体水平、且首位死因能够明确识别的群体。", + "对每个合格群体，都要给出 infant rate、neonatal rate、postneonatal rate、top cause、cause rate 以及该死因在全体婴儿死因中的排名。", + "首位死因必须按群体自己的 leading-cause 查询确定，并结合 notes / reliability 标记核验可用性。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "infant-mortality queries yield group-level overall, neonatal, and postneonatal rates for reportable mother race/Hispanic-origin groups", + "leading-cause queries and reliability notes yield each eligible group's top cause, cause-specific rate, and U.S. rank", + "final rows are produced only after the eligible-group set is rebuilt using both overall-rate and cause-specific-identifiability criteria" + ], + "control_dependency": [ + "groups above the U.S. overall rate cannot be accepted until cause-specific reliability checks are run, which removes NHOPI", + "leading cause must be queried at the group level rather than inherited from an all-infants cause table", + "the cause-rate multiplier must be defined as per 100,000 live births before downstream ranking/output" + ], + "freeze": { + "historical_window": "2021 U.S. infant mortality by mother race and Hispanic origin, including the group-level leading-cause tables and reliability notes" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只保留在 2021 年美国婴儿死亡统计中单独列示、全年 infant mortality rate 高于全美总体水平、且首位死因能够明确识别的群体。", + "对每个合格群体，都要给出 infant rate、neonatal rate、postneonatal rate、top cause、cause rate 以及该死因在全体婴儿死因中的排名。", + "首位死因必须按群体自己的 leading-cause 查询确定，并结合 notes / reliability 标记核验可用性。" + ], + "exclusion_conditions": [ + "排除虽然全年死亡率高于全美总体、但因 cause-specific reliability 问题不能明确给出首位死因的群体。", + "排除只从全体婴儿死因表继承 top cause、没有做群体级 leading-cause 查询的结果。", + "排除 cause_rate 使用错误 rate multiplier、未按每 100,000 live births 口径读取的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row `group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank`", + "schema": [ + "group", + "infant_rate", + "neonatal_rate", + "postneonatal_rate", + "top_cause", + "cause_rate", + "us_rank" + ], + "sorting_or_selection": "infant_rate descending", + "rate_fields": "infant_rate, neonatal_rate, and postneonatal_rate are per 1,000 live births; cause_rate is per 100,000 live births, but all four are emitted as plain numbers without unit text", + "top_cause": "emit the short cause label used in the oracle, not an expanded prose description", + "us_rank": "emit the integer rank of that same cause in the overall infant leading-cause list" + } + } +} diff --git a/data_zh/goal/arxiv_001-g.json b/data_zh/goal/arxiv_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..2f285471ecb62a02d6487be8a97a01ad435953cd --- /dev/null +++ b/data_zh/goal/arxiv_001-g.json @@ -0,0 +1,94 @@ +{ + "task_id": "arxiv_001-g", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "我在整理 2019–2021 年 arXiv 上 dataset distillation 和 dataset condensation 这条研究线的论文脉络，想找出那些讨论如何用少量合成训练数据替代大规模训练集的机器学习论文。请在 2019–2021 年的 arXiv 记录中，只保留主分类为 Machine Learning 的条目；若论文只是被其他主分类交叉列入 Machine Learning，则不纳入。同时要求这些论文在首版提交后的下一自然年内确有更新，且当前记录仍能直接看出后续发表去向。请按 v1 submitted 升序输出表格，列为 arXiv ID、term family、cue location、v1 submitted、first next-year version、date of that version、primary category、publication-trail source、current publication clue；如无符合条件的条目，输出 NONE。", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "请按 v1 submitted 升序输出表格，列为 arXiv ID、term family、cue location、v1 submitted、first next-year version、date of that version、primary category、publication-trail source、current publication clue；如无符合条件的条目，输出 NONE。", + "oracle_answer": "arXiv ID|term family|cue location|v1 submitted|first next-year version|date of that version|primary category|publication-trail source|current publication clue\n1910.02551|Distillation|Title|2019-10-06|v3|2020-05-05|cs.LG|Related DOI|10.1109/IJCNN52387.2021.9533769\n2011.00050|Distillation|Abstract-only|2020-10-30|v2|2021-03-02|cs.LG|Comments|Accepted to ICLR 2021\n2107.13034|Distillation|Title|2021-07-27|v3|2022-01-17|cs.LG|Comments|NeurIPS 2021\n2110.04181|Condensation|Title|2021-10-08|v2|2022-04-21|cs.LG|Journal reference|Proceedings of the IEEE/CVF Winter Conference on Applications of Computer Vision 2023 (WACV)", + "metadata": { + "State-Gated Retrieval": [ + "只纳入 arXiv 记录中 v1 submitted 落在 2019-01-01 至 2021-12-31 的论文。", + "题名或摘要必须明确使用 dataset distillation 或 dataset condensation 家族表述，并且语义指向用少量合成训练数据替代大规模训练集。", + "当前主分类必须为 cs.LG；若论文只是被其他主分类交叉列入 Machine Learning，则不纳入。", + "必须在首版提交后的下一自然年里确实更新过版本，并且当前记录仍能直接看出后续发表去向。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "root searches yield candidate arXiv IDs", + "each candidate abstract page yields primary category, v1 date, first next-year version, cue location, and publication-trail source", + "answer rows are produced only after deduplication and detail-page validation" + ], + "control_dependency": [ + "records must be filtered by original submission year, with per-record validation that a next-natural-year version exists", + "cross-listed-only hits must be excluded, and the current primary category must be validated on abstract pages", + "searches must cover both Title and Abstract because valid distillation hits can appear only in the abstract", + "topic matches without current publication trail still fail until Comments / Journal reference / Related DOI validation is added at detail depth" + ], + "freeze": { + "historical_window": "v1 year in {2019, 2020, 2021}" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只纳入 arXiv 记录中 v1 submitted 落在 2019-01-01 至 2021-12-31 的论文。", + "题名或摘要必须明确使用 dataset distillation 或 dataset condensation 家族表述，并且语义指向用少量合成训练数据替代大规模训练集。", + "当前主分类必须为 cs.LG；若论文只是被其他主分类交叉列入 Machine Learning，则不纳入。", + "必须在首版提交后的下一自然年里确实更新过版本，并且当前记录仍能直接看出后续发表去向。" + ], + "exclusion_conditions": [ + "排除当前主分类不是 cs.LG、只是 cross-list 到 cs.LG 的记录。", + "排除题名或摘要出现 distillation / condensation 字样，但不对应数据集蒸馏或数据集凝缩研究线的记录。", + "排除没有 next-natural-year 版本更新、或当前记录中没有可直接读取的发表线索的记录。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "term family", + "cue location", + "v1 submitted", + "first next-year version", + "date of that version", + "primary category", + "publication-trail source", + "current publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "term_family_extraction": { + "allowed_families": [ + "Distillation", + "Condensation" + ], + "tie_break": "if both families appear, prefer the title hit; if both appear only in the abstract, keep the first abstract occurrence" + }, + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_trail_source": [ + "Comments", + "Journal reference", + "Related DOI" + ], + "current_publication_clue": "keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue", + "sorting_or_selection": { + "primary": "v1 submitted ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all four corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the abstract page, current browse context, and publication-trail fields are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_zh/goal/arxiv_002-g.json b/data_zh/goal/arxiv_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..0c2974490802afd1af3af7db7c04c651fbc62b08 --- /dev/null +++ b/data_zh/goal/arxiv_002-g.json @@ -0,0 +1,88 @@ +{ + "task_id": "arxiv_002-g", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 10, + "instruction": "我在整理一份 2022 年大型语言模型推理提示研究的文献阅读清单，想在首版提交于 2022 年的 arXiv 论文中，筛选出题名或摘要明确聚焦 chain-of-thought 或 self-consistency 推理、且主分类为 Computation and Language 的大语言模型推理提示研究论文。候选论文还需满足：在 2023 年确实发布过更新版本，且当前 arXiv 记录中的备注能够直接显示其后续发表去向。请按每篇论文在 2023 年最早更新版本的日期升序输出表格，列为 arXiv ID、cue family、cue location、v1 submitted、first 2023 version、date of that version、primary category、publication clue；如无符合条件的条目，输出 NONE。", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "请按每篇论文在 2023 年最早更新版本的日期升序输出表格，列为 arXiv ID、cue family、cue location、v1 submitted、first 2023 version、date of that version、primary category、publication clue；如无符合条件的条目，输出 NONE。", + "oracle_answer": "arXiv ID|cue family|cue location|v1 submitted|first 2023 version|date of that version|primary category|publication clue\n2210.01240|Chain-of-thought|Title + Abstract|2022-10-03|v2|2023-01-25|cs.CL|Published as a conference paper at ICLR 2023\n2205.11916|Chain-of-thought|Abstract-only|2022-05-24|v4|2023-01-29|cs.CL|Accepted to NeurIPS2022\n2203.11171|Self-consistency; Chain-of-thought|Title + Abstract|2022-03-21|v4|2023-03-07|cs.CL|Published at ICLR 2023; camera ready version at ICLR 2023\n2210.03629|Chain-of-thought|Abstract-only|2022-10-06|v3|2023-03-10|cs.CL|v3 is the ICLR camera ready version\n2210.03350|Chain-of-thought|Abstract-only|2022-10-07|v2|2023-05-23|cs.CL|To appear at Findings of EMNLP 2023\n2212.10001|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-01|cs.CL|ACL-23 Camera Ready\n2212.08061|Chain-of-thought|Abstract-only|2022-12-15|v2|2023-06-04|cs.CL|ACL 2023 Main Conference\n2212.10071|Chain-of-thought|Abstract-only|2022-12-20|v2|2023-06-13|cs.CL|ACL 2023 camera-ready\n2212.10509|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-23|cs.CL|ACL'23 Camera Ready\n2211.12588|Chain-of-thought; Self-consistency|Abstract-only|2022-11-22|v4|2023-10-23|cs.CL|Published at TMLR 2023", + "metadata": { + "State-Gated Retrieval": [ + "只纳入 v1 submitted 在 2022 年内的 arXiv 论文。", + "题名或摘要中必须明确出现 chain-of-thought 或 self-consistency 相关线索。", + "当前主分类必须是 cs.CL，不纳入仅由其他主分类交叉列入的记录。", + "必须在 2023 年确实更新过版本，且当前备注中能够直接看出后续发表信息。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "root searches yield candidate arXiv IDs", + "each candidate abstract page yields primary category, v1 date, first 2023 version, comments/publication clue", + "answer rows are produced only after deduplication and detail-page validation" + ], + "control_dependency": [ + "searches must cover both Title and Abstract fields because valid rows can appear only in the abstract", + "cross-listed hits whose primary category is not cs.CL must be excluded, and the primary category must be validated at detail depth", + "topic-matched hits must be validated against a current Comments publication clue before they can be accepted", + "2023 candidates must be identified by original submission year and full version-history checks, rather than by latest-date proxies" + ], + "freeze": { + "historical_window": "v1 submitted in 2022; version-history event in 2023" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只纳入 v1 submitted 在 2022 年内的 arXiv 论文。", + "题名或摘要中必须明确出现 chain-of-thought 或 self-consistency 相关线索。", + "当前主分类必须是 cs.CL，不纳入仅由其他主分类交叉列入的记录。", + "必须在 2023 年确实更新过版本，且当前备注中能够直接看出后续发表信息。" + ], + "exclusion_conditions": [ + "排除当前主分类不是 cs.CL 的记录，即使它们出现在相关检索结果中。", + "排除只出现模糊缩写或弱相关提示、但题名和摘要中没有明确 CoT / self-consistency 语义的记录。", + "排除没有 2023 版本更新、或当前记录中没有直接发表线索的记录。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "cue family", + "cue location", + "v1 submitted", + "first 2023 version", + "date of that version", + "primary category", + "publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "cue_family": [ + "Chain-of-thought", + "Self-consistency" + ], + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_clue": { + "source": "Comments field only", + "extraction": "keep the shortest phrase that still preserves the current publication-status clue" + }, + "sorting_or_selection": { + "primary": "date of the earliest 2023 version ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the current browse context, Comments field, and full Submission history are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_zh/goal/arxiv_003-g.json b/data_zh/goal/arxiv_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..f1578dc1cb29ca3afddec94182212404b184b54c --- /dev/null +++ b/data_zh/goal/arxiv_003-g.json @@ -0,0 +1,89 @@ +{ + "task_id": "arxiv_003-g", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "我在整理一份早期视觉 Transformer 研究的文献阅读清单，想在首版提交于 2020 年第四季度的 arXiv 论文中，筛选出题名或摘要明确使用视觉或图像 Transformer 相关表述、且主分类为 Computer Vision and Pattern Recognition 的早期视觉 Transformer 论文。候选论文还需满足：在 2021 年确实发布过更新版本，且当前 arXiv 记录中仍能直接识别其后续发表去向。请按每篇论文在 2021 年最早更新版本的日期升序输出表格，列为 arXiv ID、cue family、cue location、v1 submitted、first 2021 version、date of that version、primary category、publication-trail source、current publication clue；如无符合条件的条目，输出 NONE。", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "请按每篇论文在 2021 年最早更新版本的日期升序输出表格，列为 arXiv ID、cue family、cue location、v1 submitted、first 2021 version、date of that version、primary category、publication-trail source、current publication clue；如无符合条件的条目，输出 NONE。", + "oracle_answer": "arXiv ID|cue family|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication-trail source|current publication clue\n2101.01097|Vision Transformer|Abstract-only|2020-12-30|v2|2021-01-08|cs.CV|Journal reference|IEEE Int. Conf. on Image Processing (ICIP) 2021\n2012.12556|Visual Transformer; Vision Transformer|Title + Abstract|2020-12-23|v2|2021-01-15|cs.CV|Comments; Related DOI|Accepted by TPAMI 2022; 10.1109/TPAMI.2022.3152247\n2012.00364|Image Processing Transformer|Title + Abstract|2020-12-01|v3|2021-05-28|cs.CV|Comments|CVPR 2021\n2011.08019|Vision Transformer|Title + Abstract|2020-11-16|v2|2021-06-02|cs.CV|Comments|Accepted for Publication in IJCB2021\n2010.11929|Vision Transformer|Abstract-only|2020-10-22|v2|2021-06-03|cs.CV|Comments|ICLR camera-ready version", + "metadata": { + "State-Gated Retrieval": [ + "只纳入 v1 submitted 落在 2020 年第四季度的 arXiv 论文。", + "题名或摘要中必须明确出现视觉或图像领域 Transformer 相关表述。", + "当前主分类必须是 cs.CV。", + "必须在 2021 年确实更新过版本，且当前记录中仍能直接识别后续发表去向。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "root searches yield candidate arXiv IDs", + "candidate abstract pages yield v1 submitted date, first 2021 version, primary category, cue location, and publication-trail source", + "answer rows depend on deduplication plus detail-page validation" + ], + "control_dependency": [ + "searches must cover both Title and Abstract because valid positives can appear only in the abstract", + "candidate eligibility must be determined by the original-submission date window rather than by arXiv-ID or announcement intuition", + "candidate filtering must use full Submission-history validation rather than most-recent-submission filtering", + "searches must use the broader semantic cue state rather than a ViT-only entry point, because ViT-only hits can be false positives", + "publication-trail false positives still require Comments / Journal reference / Related DOI validation before final inclusion" + ], + "freeze": { + "historical_window": "v1 submitted from 2020-10-01 through 2020-12-31; version-history event in 2021" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只纳入 v1 submitted 落在 2020 年第四季度的 arXiv 论文。", + "题名或摘要中必须明确出现视觉或图像领域 Transformer 相关表述。", + "当前主分类必须是 cs.CV。", + "必须在 2021 年确实更新过版本，且当前记录中仍能直接识别后续发表去向。" + ], + "exclusion_conditions": [ + "排除当前主分类不是 cs.CV、只是交叉列入的记录。", + "排除只出现 Transformer / ViT 等弱线索、但题名和摘要中没有明确视觉或图像领域表述的记录。", + "排除没有 2021 年版本更新、或当前记录中没有直接发表线索的记录。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "cue family", + "cue location", + "v1 submitted", + "first 2021 version", + "date of that version", + "primary category", + "publication-trail source", + "current publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "cue_family_extraction": "record every qualifying family actually present and join multiple families with `; ` in the emitted field", + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_trail_source": [ + "Comments", + "Journal reference", + "Related DOI" + ], + "current_publication_clue": "keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue", + "sorting_or_selection": { + "primary": "date of the earliest 2021 version ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the abstract page, current browse context, Comments field, Journal reference, Related DOI, and full Submission history are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_zh/goal/arxiv_004-g.json b/data_zh/goal/arxiv_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..393a45ac63a73d2b4976f19affd785be03362ea1 --- /dev/null +++ b/data_zh/goal/arxiv_004-g.json @@ -0,0 +1,84 @@ +{ + "task_id": "arxiv_004-g", + "domain": "ARXIV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "我想在首版提交于 2020 年上半年的 arXiv 论文中，筛选出主分类为 Machine Learning、且题名或摘要明确聚焦可认证鲁棒性防御方法的论文。候选论文的研究对象应明确涉及以下至少一类线索：randomized smoothing、de-randomized smoothing、transformation-specific smoothing、smoothed classifiers、针对 backdoor/poisoning 的可认证防御，或 partition aggregation。同时，这些论文需在 2021 年确实发布过更新版本，且当前 arXiv 记录中仍能直接看出其正式发表或录用去向。请按每篇论文在 2021 年最早更新版本的日期升序输出表格，列为 arXiv ID、defense family、threat/topic cue、cue location、v1 submitted、first 2021 version、date of that version、primary category、publication clue；如无符合条件的条目，输出 NONE。", + "start_url": "https://arxiv.org/search/advanced", + "output_format": "请按每篇论文在 2021 年最早更新版本的日期升序输出表格，列为 arXiv ID、defense family、threat/topic cue、cue location、v1 submitted、first 2021 version、date of that version、primary category、publication clue；如无符合条件的条目，输出 NONE。", + "oracle_answer": "arXiv ID|defense family|threat/topic cue|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication clue\n2002.10733|De-randomized smoothing; Randomized smoothing|patch attacks|Title + Abstract|2020-02-25|v3|2021-01-08|cs.LG|NeurIPS 2020\n2006.04062|Smoothed classifiers; Randomized smoothing|certified L2 robustness|Title + Abstract|2020-06-07|v4|2021-01-08|cs.LG|NeurIPS 2020\n2003.08904|RAB; Randomized smoothing|backdoor attacks|Title + Abstract|2020-03-19|v4|2021-02-26|cs.LG|IEEE Symposium on Security and Privacy 2023\n2006.14768|Deep Partition Aggregation|general poisoning attacks; label-flipping poisoning attacks|Title + Abstract|2020-06-26|v2|2021-03-18|cs.LG|ICLR 2021\n2002.12398|Transformation-specific smoothing; Randomized smoothing|semantic transformations|Title + Abstract|2020-02-27|v4|2021-09-17|cs.LG|2021 ACM SIGSAC Conference on Computer and Communications Security (CCS '21)", + "metadata": { + "State-Gated Retrieval": [ + "只纳入 v1 submitted 落在 2020-01-01 至 2020-06-30 的 arXiv 论文。", + "题名或摘要中必须明确围绕 randomized smoothing、de-randomized smoothing、transformation-specific smoothing、smoothed classifiers、后门或投毒场景下的可认证防御，或 partition aggregation 展开。", + "当前主分类必须是 cs.LG。", + "必须在 2021 年确实更新过版本，并且当前记录中能够直接看出正式发表或录用信息。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "root searches yield candidate arXiv IDs", + "candidate abstract pages yield v1 date, primary category, full Submission history, cue location, and current publication clue", + "final rows depend on deduplication plus detail-page validation" + ], + "control_dependency": [ + "candidate filtering must use the original-submission window together with full 2021 version-history validation, because valid rows can have later newest versions", + "cross-listed hits whose primary category is not the target category must be excluded, with category validation on detail pages", + "searches must cover the broader certified-defense family, including partition-aggregation and backdoor/poisoning variants, rather than smoothing-only entries", + "topic+venue hits must be confirmed by detail-history validation that a 2021 version actually exists" + ], + "freeze": { + "historical_window": "v1 submitted from 2020-01-01 through 2020-06-30; version-history event in 2021" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只纳入 v1 submitted 落在 2020-01-01 至 2020-06-30 的 arXiv 论文。", + "题名或摘要中必须明确围绕 randomized smoothing、de-randomized smoothing、transformation-specific smoothing、smoothed classifiers、后门或投毒场景下的可认证防御，或 partition aggregation 展开。", + "当前主分类必须是 cs.LG。", + "必须在 2021 年确实更新过版本，并且当前记录中能够直接看出正式发表或录用信息。" + ], + "exclusion_conditions": [ + "排除当前主分类不是 cs.LG 的记录，即使语义相关。", + "排除只与鲁棒性、防御、backdoor/poisoning 泛相关，但不满足题目要求的可认证防御语义的记录。", + "排除没有 2021 年版本更新或没有当前发表线索的记录。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row shown in the oracle", + "schema": [ + "arXiv ID", + "defense family", + "threat/topic cue", + "cue location", + "v1 submitted", + "first 2021 version", + "date of that version", + "primary category", + "publication clue" + ], + "dedup_key": "bare arXiv ID without version suffix", + "date_format": "YYYY-MM-DD", + "defense_family_extraction": "record every qualifying defense family actually present and join multiple families with `; ` in the emitted field", + "threat_topic_cue": "keep the shortest qualifying threat or topic cue that justifies inclusion", + "cue_location": { + "Title": "qualifying cue appears only in the title", + "Abstract-only": "qualifying cue appears only in the abstract", + "Title + Abstract": "qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name" + }, + "publication_clue": "keep the shortest phrase that still preserves venue or publication-status information", + "sorting_or_selection": { + "primary": "date of the earliest 2021 version ascending", + "secondary": "arXiv ID ascending" + }, + "stop_condition": [ + "all corrected result pages are exhausted", + "all unique candidate IDs are opened to abstract-page depth", + "for every surviving candidate, the abstract page, current browse context, Comments field, and full Submission history are checked before emitting the final ordered table" + ] + } + } +} diff --git a/data_zh/goal/census_001-g.json b/data_zh/goal/census_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..3e988ce4e46dbf534b464186f9d63816e8f8e2d5 --- /dev/null +++ b/data_zh/goal/census_001-g.json @@ -0,0 +1,68 @@ +{ + "task_id": "census_001-g", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 20, + "instruction": "我想依据 2014–2018 年 American Community Survey 五年估计数据，在北卡罗来纳州各县中筛选出兼具互联网接入不足、老年独居比例较高、出行条件较弱和收入水平较低特征的县。候选县需同时满足以下条件：未接入互联网的住户不少于 4,000 户；未接入互联网住户占比高于全州水平；户主为 65 岁及以上且独居的住户占全部住户的比重高于全州水平；无车住户占比高于全州水平；家庭收入中位数低于全州水平。所有全州比较均以同一份数据中 North Carolina 的全州估计值为准。请列出所有符合条件的县，并按县名字母顺序输出一行；每个县写成 County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome，县与县之间用英文逗号分隔。百分比字段保留三位小数，不加百分号。", + "start_url": "https://www.census.gov/data.html", + "output_format": "请列出所有符合条件的县，并按县名字母顺序输出一行；每个县写成 County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome，县与县之间用英文逗号分隔。百分比字段保留三位小数，不加百分号。", + "oracle_answer": "Beaufort County|5988|30.986|16.083|7.664|43688,Bladen County|4194|30.026|13.681|10.417|32378,Cleveland County|11599|31.449|12.469|7.825|40393,Columbus County|7371|33.045|15.148|7.958|36398,Duplin County|7574|34.773|14.370|7.424|38850,Edgecombe County|7454|34.879|13.720|11.225|35516,Halifax County|7575|35.873|14.657|11.565|34251,Lenoir County|4923|21.292|15.614|11.699|38387,Nash County|8617|23.467|13.597|7.917|48362,Richmond County|5193|28.001|13.706|9.269|36091,Robeson County|19814|43.103|11.312|9.854|33679,Rockingham County|9938|26.714|14.166|7.164|42490,Rutherford County|7583|28.783|16.033|6.335|40347,Sampson County|8216|34.907|14.088|7.686|39068,Scotland County|4971|37.909|13.910|11.470|35617,Surry County|7595|26.203|13.762|6.779|41068,Vance County|5131|30.444|12.347|11.600|37282,Wayne County|9709|20.163|11.742|8.456|42192,Wilkes County|7046|24.849|14.773|5.992|40829,Wilson County|7652|23.817|13.322|9.540|42850", + "metadata": { + "State-Gated Retrieval": [ + "只使用 2014-2018 American Community Survey 5-year estimates 的 North Carolina 县级数据，并使用同一发布中的 North Carolina 全州值作为比较基准。", + "只保留无互联网接入住户不少于 4,000 户，且无互联网接入住户占比、65 岁及以上独居户主占比、无车住户占比均高于全州，同时家庭收入中位数低于全州的县。", + "最终结果按县名字母顺序输出，并保留题目要求的 6 个字段。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2014-2018 ACS 5-year product and North Carolina county geography yield the full county candidate set plus the statewide baseline row", + "the relevant ACS tables yield no-internet households, senior-living-alone share, no-vehicle share, and median household income for each county and the state baseline", + "final rows are produced only after the 5-year product/geography setup is fixed consistently and the full county filtering chain is executed from B28002 through the downstream filters" + ], + "control_dependency": [ + "the 2018 ACS 5-year Detailed Tables product must be used instead of the 2018 ACS 1-year product", + "county coverage must be established under one consistent product-and-geography setup rather than by piecemeal fixes within the current table", + "all downstream county comparisons must use the same 5-year statewide baseline and the same all-counties geography" + ], + "freeze": { + "historical_window": "2014-2018 American Community Survey 5-year estimates for North Carolina counties, using the North Carolina statewide row from the same release as the comparison baseline" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只使用 2014-2018 American Community Survey 5-year estimates 的 North Carolina 县级数据，并使用同一发布中的 North Carolina 全州值作为比较基准。", + "只保留无互联网接入住户不少于 4,000 户，且无互联网接入住户占比、65 岁及以上独居户主占比、无车住户占比均高于全州，同时家庭收入中位数低于全州的县。", + "最终结果按县名字母顺序输出，并保留题目要求的 6 个字段。" + ], + "exclusion_conditions": [ + "排除误用 2018 ACS 1-Year Estimates Detailed Tables 或其他非 2014-2018 五年发布的数据。", + "排除没有使用同一发布中的 North Carolina 全州行作为比较基准的结果。", + "排除任一阈值或全州比较条件不满足的县。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "NoInternetHH", + "NoInternetRatePct", + "SeniorLivingAloneSharePct", + "NoVehicleRatePct", + "MedianIncome" + ], + "county": "use the county display name including the word `County` and excluding a trailing state suffix", + "dedup_key": "county FIPS / GEOID", + "percentage_fields": "all percentage fields are plain numbers with exactly three decimal places and no percent sign", + "numeric_fields": "household counts and median income are emitted as plain integers without commas", + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "the North Carolina statewide threshold is fixed once from the designated table", + "all 100 North Carolina counties are covered under the same table/product settings", + "every surviving county is validated against all four required tables before emission" + ] + } + } +} diff --git a/data_zh/goal/census_002-g.json b/data_zh/goal/census_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..74d7f92e94beffd9692b2b221db244c9af08bd60 --- /dev/null +++ b/data_zh/goal/census_002-g.json @@ -0,0 +1,80 @@ +{ + "task_id": "census_002-g", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "我想基于 2015–2019 年 American Community Survey 五年估计数据，在新墨西哥州各县中筛选出同时具有较大租户规模、明显语言障碍、网络接入不足、交通不便、收入偏低和租住压力的县。这些县用于评估疫情前哪些地区不适合仅以线上自助服务替代线下租客法律援助。候选县需同时满足以下条件：租住住户（renter-occupied households）不少于 2,500 户；英语能力受限住户（limited-English-speaking households）不少于 500 户；英语能力受限住户占比高于全州水平；无互联网接入住户占比高于全州水平；无车住户占比高于全州水平；家庭收入中位数低于全州水平；且租住压力高于全州水平。租住压力高于全州水平需由以下至少一种情形构成：租住住户中租金收入比不低于 35% 的占比高于全州水平，或租住住户中每房间居住人数大于 1 的占比高于全州水平。所有“高于全州”或“低于全州”的比较，均以同一份数据中的 New Mexico 全州值为准。请将所有符合条件的县按县名字母顺序输出一行；每个县写成 County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath，其中 StressPath 只能写 RENT、CROWD 或 BOTH；多个县之间用英文逗号分隔。百分比字段保留三位小数，不加百分号。", + "start_url": "https://data.census.gov/advanced", + "output_format": "请将所有符合条件的县按县名字母顺序输出一行；每个县写成 County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath，其中 StressPath 只能写 RENT、CROWD 或 BOTH；多个县之间用英文逗号分隔。百分比字段保留三位小数，不加百分号。", + "oracle_answer": "Doña Ana County|28729|7883|10.127|22.612|6.079|44.172|6.391|40973|BOTH,Luna County|3482|1109|12.455|34.030|8.165|42.700|1.407|29360|RENT,McKinley County|6090|1610|7.688|50.587|10.978|27.568|16.256|33834|CROWD,San Miguel County|3443|1200|10.337|38.470|7.684|47.376|2.440|30946|RENT,Taos County|2854|652|5.387|28.844|5.726|48.823|4.555|38329|RENT", + "metadata": { + "State-Gated Retrieval": [ + "只使用 2015-2019 American Community Survey 5-year estimates 的 New Mexico 县级数据，并使用同一发布中的 New Mexico 全州值作为比较基准。", + "候选县必须至少有 2,500 个租房住户、至少 500 个英语能力有限住户，并且 LEP 占比、无互联网占比、无车占比均高于全州，同时家庭收入中位数低于全州。", + "LEPHH 必须由 C16002 中全部四个 limited-English 语言分组合并计算；最后只保留 Severe Rent Burden 或 Crowded Renter 至少一项高于全州的县，并按规则写出 StressPath。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2015-2019 ACS 5-year county geography yields New Mexico county candidates and the statewide baseline row", + "C16002 and the downstream housing/income tables yield LEPHH, LEP share, no-internet share, no-vehicle share, severe rent burden, crowded-renter share, and median income for counties and the state baseline", + "final rows are produced only after the LEPHH numerator is computed from all four limited-English language groups and the downstream stress-path filters are applied" + ], + "control_dependency": [ + "the LEPHH numerator must be computed from all four limited-English language groups in C16002 rather than from Spanish-only counts", + "county eligibility and StressPath labels must be determined from the LEPHH measure and statewide LEP baseline defined under that full four-group calculation", + "the RENT / CROWD / BOTH classification must be determined by evaluating the same county set against both downstream housing-stress branches" + ], + "freeze": { + "historical_window": "2015-2019 American Community Survey 5-year estimates for New Mexico counties, using the New Mexico statewide row from the same release as the comparison baseline" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只使用 2015-2019 American Community Survey 5-year estimates 的 New Mexico 县级数据，并使用同一发布中的 New Mexico 全州值作为比较基准。", + "候选县必须至少有 2,500 个租房住户、至少 500 个英语能力有限住户，并且 LEP 占比、无互联网占比、无车占比均高于全州，同时家庭收入中位数低于全州。", + "LEPHH 必须由 C16002 中全部四个 limited-English 语言分组合并计算；最后只保留 Severe Rent Burden 或 Crowded Renter 至少一项高于全州的县，并按规则写出 StressPath。" + ], + "exclusion_conditions": [ + "排除把西班牙语 limited-English 住户单独当作全部 LEPHH 的结果。", + "排除未使用同一发布中全州基准、或未重算 LEPHH/LEPSharePct/LEPShare_state 的结果。", + "排除不满足 RENT、CROWD 或 BOTH 最终压力路径条件的县。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "RenterHH", + "LEPHH", + "LEPSharePct", + "NoInternetPct", + "NoVehiclePct", + "SevereRentBurdenPct", + "CrowdedRenterPct", + "MedianIncome", + "StressPath" + ], + "county": "use the county display name including the word `County` and excluding a trailing state suffix", + "dedup_key": "county FIPS / GEOID", + "LEPHH": "sum the four designated limited-English-proficient renter-household cells before emitting the integer total", + "percentage_fields": "all percentage fields are plain numbers with exactly three decimal places and no percent sign", + "numeric_fields": "household counts and median income are emitted as plain integers without commas", + "StressPath": { + "allowed_values": [ + "RENT", + "CROWD", + "BOTH" + ], + "rule": "emit BOTH only when both the severe-rent-burden and crowded-renter signals survive; otherwise emit the single surviving label" + }, + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "all candidate counties are validated under the same geography and product settings", + "the renter scope and LEP aggregation are checked before the final line is emitted" + ] + } + } +} diff --git a/data_zh/goal/census_003-g.json b/data_zh/goal/census_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..55b6e1a88eade527301b98d887539ce45b049a0a --- /dev/null +++ b/data_zh/goal/census_003-g.json @@ -0,0 +1,73 @@ +{ + "task_id": "census_003-g", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "我想基于 2013–2017 年 American Community Survey 五年估计数据，在加州各县中筛选出学校餐食相关材料更新和家长资料年度更新时，不适合仅依赖英文在线入口、仍需保留纸质材料与线下协助的县。候选县需同时满足以下条件：5–17 岁人口不少于 75,000 人；5–17 岁人口中，英语能力为“不太好”或“完全不会”的人数不少于 2,000 人，且其占比高于全州水平；未接入互联网住户占比高于全州水平；家庭收入中位数低于全州水平；并且在三类支持需求信号中至少有两类高于全州水平。这三类支持需求信号分别为：无车住户占比、居住在过去 12 个月领取 SSI、现金公共援助或 Food Stamps/SNAP 家庭中的未成年人占比，以及租房住户中每间房超过 1 人的住户占比。所有“高于全州”或“低于全州”的比较，均以同一份数据中的 California 全州值为准。请将所有符合条件的县按县名字母顺序输出一行；每个县写成 County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath，其中 SupportPath 只使用 BENEFITS、CROWD、MOBILITY 三个标签，并按该固定顺序用加号连接；多个县之间用英文逗号分隔。", + "start_url": "https://data.census.gov/advanced", + "output_format": "请将所有符合条件的县按县名字母顺序输出一行；每个县写成 County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath，其中 SupportPath 只使用 BENEFITS、CROWD、MOBILITY 三个标签，并按该固定顺序用加号连接；多个县之间用英文逗号分隔。", + "oracle_answer": "Fresno County|200205|5127|2.561|20.588|8.686|46.388|13.967|48730|BENEFITS+CROWD+MOBILITY,Kern County|185802|4130|2.223|21.739|7.058|37.285|14.394|50826|BENEFITS+CROWD,Los Angeles County|1641669|37540|2.287|16.338|9.204|27.238|16.741|61015|BENEFITS+CROWD+MOBILITY,Tulare County|104542|2703|2.586|25.738|6.274|49.347|14.535|44871|BENEFITS+CROWD", + "metadata": { + "State-Gated Retrieval": [ + "只使用 2013-2017 American Community Survey 5-year estimates 的 California 县级数据，并使用同一发布中的 California 全州值作为比较基准。", + "只保留 5-17 岁人口不少于 75,000、SchoolAgeLEP 不少于 2,000 且该占比高于全州、无互联网占比高于全州、家庭收入中位数低于全州的县。", + "SchoolAgeLEP 必须由 B16004 中四大语言组的 not well / not at all 八个单元格合计；最终县还需在 Mobility、Benefits、Crowd 三类线下支持信号中至少两类高于全州。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2013-2017 ACS 5-year county geography yields California county candidates and the statewide baseline row", + "B16004 and the downstream access/income/support tables yield SchoolAgeLEP, no-internet share, no-vehicle share, child-benefit share, crowded-renter share, and median income for counties and the statewide baseline", + "final rows are produced only after the SchoolAgeLEP numerator is computed from all eight 1980-target language cells and the downstream support-path branches are applied" + ], + "control_dependency": [ + "the SchoolAgeLEP numerator must be computed from the full eight-cell language set in B16004 rather than from only two Spanish LEP cells", + "county eligibility and SupportPath labels must be determined from the LEP numerator and candidate set defined under that full eight-cell calculation", + "the BENEFITS / CROWD / MOBILITY path labels must be determined by applying all three downstream support branches to the same county set" + ], + "freeze": { + "historical_window": "2013-2017 American Community Survey 5-year estimates for California counties, using the California statewide row from the same release as the comparison baseline" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只使用 2013-2017 American Community Survey 5-year estimates 的 California 县级数据，并使用同一发布中的 California 全州值作为比较基准。", + "只保留 5-17 岁人口不少于 75,000、SchoolAgeLEP 不少于 2,000 且该占比高于全州、无互联网占比高于全州、家庭收入中位数低于全州的县。", + "SchoolAgeLEP 必须由 B16004 中四大语言组的 not well / not at all 八个单元格合计；最终县还需在 Mobility、Benefits、Crowd 三类线下支持信号中至少两类高于全州。" + ], + "exclusion_conditions": [ + "排除只取 Spanish LEP 两行、未合并全部八个目标单元格的结果。", + "排除没有重新跑 B28011、B19013、B08201、B09010、B25014 支路的结果。", + "排除最终 SupportPath 不满足至少两类高于全州的县。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "SchoolAgePop", + "SchoolAgeLEP", + "LEPSharePct", + "NoInternetPct", + "NoVehiclePct", + "ChildBenefitSharePct", + "CrowdedRenterPct", + "MedianIncome", + "SupportPath" + ], + "county": "use the county display name including the word `County` and excluding a trailing state suffix", + "dedup_key": "county FIPS / GEOID", + "SchoolAgeLEP": "sum the eight designated school-age LEP cells before emitting the integer total", + "percentage_fields": "all percentage fields are plain numbers with exactly three decimal places and no percent sign", + "numeric_fields": "population counts and median income are emitted as plain integers without commas", + "SupportPath": "use only BENEFITS, CROWD, and MOBILITY, and when multiple labels apply join them with `+` in the fixed order BENEFITS+CROWD+MOBILITY", + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "all candidate counties are validated under the same geography and product settings", + "the school-age LEP aggregation and all three support-signal gates are checked before the final line is emitted" + ] + } + } +} diff --git a/data_zh/goal/census_004-g.json b/data_zh/goal/census_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..9ced517bc734ebb4d390c2328baa70b2cbe478c3 --- /dev/null +++ b/data_zh/goal/census_004-g.json @@ -0,0 +1,72 @@ +{ + "task_id": "census_004-g", + "domain": "CENSUS_GOV", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 7, + "instruction": "我想基于 2012–2016 年 American Community Survey 五年估计数据，在宾夕法尼亚州各县中筛选出老年人疏散支持需求较高、应在冬季风暴前提前开展线下外展的县。候选县需同时满足以下条件：65 岁及以上人口不少于 15,000 人；65 岁及以上且有行走困难的人口不少于 4,000 人，且其占 65 岁及以上人口的比重高于全州水平；家庭收入中位数低于全州水平；并且在四类疏散支持障碍中至少有两类高于全州水平。这四类障碍分别为：65 岁及以上独居户主住户占比、无车住户占比、无车租房住户占比，以及移动式住房占全部住房单元的比重。所有“高于全州”或“低于全州”的比较，均以同一份数据中的 Pennsylvania 全州值为准。请将所有符合条件的县按县名字母顺序写成一行；每个县写成 County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath，县与县之间用英文逗号分隔；BarrierPath 只使用 ALONE、MOBILE_HOME、NO_VEHICLE、RENTER_NO_VEHICLE，并按这一固定顺序用加号连接。", + "start_url": "https://www.census.gov/data.html", + "output_format": "请将所有符合条件的县按县名字母顺序写成一行；每个县写成 County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath，县与县之间用英文逗号分隔；BarrierPath 只使用 ALONE、MOBILE_HOME、NO_VEHICLE、RENTER_NO_VEHICLE，并按这一固定顺序用加号连接。", + "oracle_answer": "Blair County|23013|5576|24.230|14.917|9.440|24.316|6.388|44033|ALONE+MOBILE_HOME, Cambria County|27058|6308|23.313|15.243|10.309|26.627|4.070|42917|ALONE+MOBILE_HOME+RENTER_NO_VEHICLE, Fayette County|25186|5886|23.370|14.961|9.302|22.290|10.489|40511|ALONE+MOBILE_HOME, Lycoming County|19486|4311|22.124|12.164|9.257|23.312|6.726|48731|ALONE+MOBILE_HOME, Mercer County|21537|4799|22.283|14.090|9.572|24.413|7.912|45831|ALONE+MOBILE_HOME, Philadelphia County|188185|56935|30.255|11.553|30.954|44.924|0.250|39770|NO_VEHICLE+RENTER_NO_VEHICLE, Schuylkill County|26613|6465|24.293|14.357|9.676|23.652|4.080|46573|ALONE+MOBILE_HOME", + "metadata": { + "State-Gated Retrieval": [ + "只使用 2012-2016 American Community Survey 5-year estimates 的 Pennsylvania 县级数据，并使用同一发布中的 Pennsylvania 全州值作为比较基准。", + "只保留 65 岁及以上人口不少于 15,000、65 岁及以上行走困难人口不少于 4,000 且占比高于全州、并且家庭收入中位数低于全州的县。", + "65+ ambulatory difficulty 必须合并 B18105 中 65-74 / 75+、male / female 的四个目标单元格；最终县还需在 Alone、No Vehicle、Renter No Vehicle、Mobile Home 四类障碍中至少两类高于全州。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "ACS tables B01001 and B18105 yield county senior-population totals and the full 65+ ambulatory-difficulty numerator", + "statewide comparison tables yield Pennsylvania baselines plus county barrier metrics for living alone, no vehicle, renter no vehicle, mobile home, and median income", + "final rows are produced only after the county candidate set is defined from the full ambulatory-difficulty numerator and the downstream six-table filters are applied" + ], + "control_dependency": [ + "the ambulatory-difficulty numerator must include the full 65+ population across 65-74 / 75+ and male / female cells rather than only the 75+ cells", + "downstream county eligibility and barrier labels must be determined from the county candidate set defined under that full ambulatory numerator", + "the at-least-two-barriers test must compare every county metric against the same Pennsylvania statewide baselines from the same ACS release" + ], + "freeze": { + "historical_window": "2012-2016 American Community Survey 5-year estimates for Pennsylvania counties, with Pennsylvania statewide baselines taken from the same release" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只使用 2012-2016 American Community Survey 5-year estimates 的 Pennsylvania 县级数据，并使用同一发布中的 Pennsylvania 全州值作为比较基准。", + "只保留 65 岁及以上人口不少于 15,000、65 岁及以上行走困难人口不少于 4,000 且占比高于全州、并且家庭收入中位数低于全州的县。", + "65+ ambulatory difficulty 必须合并 B18105 中 65-74 / 75+、male / female 的四个目标单元格；最终县还需在 Alone、No Vehicle、Renter No Vehicle、Mobile Home 四类障碍中至少两类高于全州。" + ], + "exclusion_conditions": [ + "排除只取 75 years and over 行走困难单元格并把它误当成全部 65+ 的结果。", + "排除未使用同一发布中 Pennsylvania 全州基准的结果。", + "排除最终 BarrierPath 不满足至少两类障碍高于全州的县。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "County", + "SeniorPop", + "AmbulatoryDifficulty65Plus", + "AmbDiffPct", + "SeniorLivingAloneSharePct", + "NoVehiclePct", + "RenterNoVehiclePct", + "MobileHomePct", + "MedianIncome", + "BarrierPath" + ], + "county": "use the county display name including the word `County` and excluding a trailing state suffix", + "dedup_key": "county FIPS / GEOID", + "percentage_fields": "all percentage fields are plain numbers with exactly three decimal places and no percent sign", + "numeric_fields": "population counts and median income are emitted as plain integers without commas", + "BarrierPath": "use only ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE, and when multiple labels apply join them with `+` in the fixed order ALONE+MOBILE_HOME+NO_VEHICLE+RENTER_NO_VEHICLE", + "sorting_or_selection": "county name alphabetical ascending", + "stop_condition": [ + "all candidate counties are validated under the same geography and product settings", + "the senior ambulatory-difficulty gate and all barrier-signal gates are checked before the final line is emitted" + ] + } + } +} diff --git a/data_zh/goal/climategov_001-g.json b/data_zh/goal/climategov_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..b851e06a467c6d71daee7336dbea1e983859aad6 --- /dev/null +++ b/data_zh/goal/climategov_001-g.json @@ -0,0 +1,66 @@ +{ + "task_id": "climategov_011-g", + "domain": "NOAA_NCEI_CLIMATE_AT_A_GLANCE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "我想在得克萨斯州南部 (South Texas) 寻找几个在两段较长时期内气候接近常态或偏湿润，且在1966年3月供暖负荷依然较轻的气候分区。请将排查范围严格限定在中南部 (South Central)、上海岸 (Upper Coast)、南部 (South) 和下游河谷 (Lower Valley) 这四个分区内，并且这些分区的名称和编号顺序必须完全以官方得克萨斯气候分区 (Texas divisional) 页面片段中给出的信息为准。\n我需要最终筛选出的分区同时满足三个硬性的气候指标：首先，截至1966年2月的前10个月帕尔默Z指数距平 (Palmer Z-Index anomaly) 不得低于-0.05；其次，截至1966年12月的前24个月帕尔默Z指数距平不得低于-0.10；同时，1966年3月单月的采暖度日数 (Heating Degree Days) 实际值必须低于200°Df。找到所有符合条件的分区后，请帮我按照特定规则对它们进行排序。优先将1966年2月的10个月Z指数距平与1966年12月的24个月Z指数距平相加，并按这个加和值从大到小降序排列；如果加和值相同，就把1966年3月采暖度日数实际值更小的排在前面；若依然并列，则让得克萨斯州分区号更小的优先排列。\n最后，请将所有匹配的分区结果输出为一整行由英文逗号连接的字符串。每个独立匹配项的数据需要严格按照“<得克萨斯州分区号>|<分区名>|<1966年2月10个月Z指数距平的原样文本>|<1966年12月24个月Z指数距平的原样文本>|<1966年3月单月采暖度日数实际值的原样文本>|<保留两位小数的湿度得分>”的格式进行拼接，此处的湿度得分 (moisture score) 即为前述两次Z指数距平的加和。如果排查后发现没有任何符合条件的分区，请直接输出大写的 NONE。", + "start_url": "https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national", + "output_format": "最后，请将所有匹配的分区结果输出为一整行由英文逗号连接的字符串。每个独立匹配项的数据需要严格按照“<得克萨斯州分区号>|<分区名>|<1966年2月10个月Z指数距平的原样文本>|<1966年12月24个月Z指数距平的原样文本>|<1966年3月单月采暖度日数实际值的原样文本>|<保留两位小数的湿度得分>”的格式进行拼接，此处的湿度得分 (moisture score) 即为前述两次Z指数距平的加和。如果排查后发现没有任何符合条件的分区，请直接输出大写的 NONE。", + "oracle_answer": "7|South Central|0.72|0.35|194°Df|1.07,10|Lower Valley|0.28|0.67|106°Df|0.95,9|South|0.03|0.37|148°Df|0.40", + "metadata": { + "State-Gated Retrieval": [ + "只在 Texas divisional 页面定义的四个 South Texas 分区内筛选：South Central、Upper Coast、South、Lower Valley。", + "保留同时满足以下条件的分区：1966-02 的 10-month Palmer Z-Index anomaly 不低于 -0.05；1966-12 的 24-month anomaly 不低于 -0.10；1966-03 的 1-month Heating Degree Days Value 小于 200°Df。", + "最终按两次 Z anomaly 之和降序、再按 1966-03 HDD Value 升序、再按分区号升序排序。" + ], + "dependency_type": "Data", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the official Texas climate-division reference fixes the four South Texas division IDs and names that must be tracked across all later pages", + "the 1966-02 10-month Palmer Z-Index anomaly page and the 1966-12 24-month Palmer Z-Index anomaly page jointly generate the four-division candidate set", + "the 1966-03 1-month Heating Degree Days Value page supplies the last filter; final rows are produced only after intersecting the three divisional screens and then sorting by summed Z-anomaly score, HDD value, and division number" + ], + "freeze": { + "historical_window": "Texas climate divisions South Central, Upper Coast, South, and Lower Valley; metrics are fixed to the 1966-02 10-month Palmer Z-Index anomaly, 1966-12 24-month anomaly, and 1966-03 1-month Heating Degree Days Value pages" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在 Texas divisional 页面定义的四个 South Texas 分区内筛选：South Central、Upper Coast、South、Lower Valley。", + "保留同时满足以下条件的分区：1966-02 的 10-month Palmer Z-Index anomaly 不低于 -0.05；1966-12 的 24-month anomaly 不低于 -0.10；1966-03 的 1-month Heating Degree Days Value 小于 200°Df。", + "最终按两次 Z anomaly 之和降序、再按 1966-03 HDD Value 升序、再按分区号升序排序。" + ], + "exclusion_conditions": [ + "排除四个指定 South Texas 分区之外的 Texas divisional 结果。", + "排除把 1966-03 HDD 页面的筛选字段误读成 Anomaly 而不是 Value 的结果。", + "排除任何一个时间窗或阈值条件不满足的分区。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "texas_division_no", + "division_name", + "feb_1966_10mo_z_text", + "dec_1966_24mo_z_text", + "mar_1966_hdd_text", + "moisture_score" + ], + "texas_division_no": "canonical output uses the short Texas climate-division number; the scorer may accept an equivalent four-digit form, but the emitted oracle uses the short number", + "raw_text_fields": "the two Z-index anomaly fields and the March 1966 HDD field preserve the raw displayed text; comparison may ignore optional trailing HDD unit text such as `°Df`", + "moisture_score": "compute as February 1966 10-month Z-index anomaly plus December 1966 24-month Z-index anomaly, formatted with exactly two decimal places", + "sorting_or_selection": { + "primary": "moisture_score descending", + "secondary": "March 1966 HDD actual value ascending after numeric normalization", + "tertiary": "Texas division number ascending" + }, + "eligibility_rule": "each Texas division is counted once per requested window; if any required window value is missing, exclude the division", + "stop_condition": [ + "all candidate Texas divisions are checked under the same base period and anomaly windows", + "the unique ordered output string is resolved before emission" + ] + } + } +} diff --git a/data_zh/goal/climategov_002-g.json b/data_zh/goal/climategov_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..454325da6edcc7376bc3da8ea52483e175c4feca --- /dev/null +++ b/data_zh/goal/climategov_002-g.json @@ -0,0 +1,73 @@ +{ + "task_id": "climategov_012-g", + "domain": "NOAA_NCEI_CLIMATE_AT_A_GLANCE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我最近在研究得州 (Texas) 历史上的气候模式，想为换季期（肩季）的运营规划找一些相似的历史年份作为参考。为此，我想在 NOAA 的 Climate at a Glance 数据库里筛选出几个特定的得州气候分区。我寻找的这些区域，需要在 20 世纪早期经历过从偏干的长期水分背景回归到接近常态或偏湿一侧的转变，并且在两个不同的换季窗口里供暖负荷都偏轻。\n具体来说，最终筛选出的分区必须同时满足四个硬性的气候指标：首先，截至 1907 年 4 月的 10 个月帕尔默 Z 指数距平 (Palmer Z-Index anomaly) 不得高于 -0.30；其次，截至 1923 年 4 月的 10 个月 Z 指数距平不得低于 -0.20；同时，截至 1915 年 5 月的 2 个月采暖度日数 (Heating Degree Days) 实际值需低于 50°Df，且截至 1922 年 10 月的 5 个月采暖度日数实际值要低于 20°Df。\n锁定这些符合条件的分区后，请帮我按照特定的规则对它们进行排序。优先的排序依据是“反弹得分 (rebound score)”，即用 1923 年 4 月的 10 个月 Z 指数距平减去 1907 年 4 月的 10 个月 Z 指数距平所得到的差值，请按此差值从大到小降序排列。如果遇到得分并列的情况，就把 1922 年 10 月的 5 个月 HDD 实际值更小的分区排在前面；若依然并列，则让 Texas 分区号更小的优先排列。\n最后，请将所有匹配的分区结果输出为一整行由英文逗号连接的字符串。每个独立匹配项的数据呈现需要严格按照“|<四位分区ID>|<分区名>|<1907-04 10个月Z-Index距平原样文本>|<1923-04 10个月Z-Index距平原样文本>|<1915-05 2个月HDD实际值原样文本>|<1922-10 5个月HDD实际值原样文本>|<保留2位小数的rebound score>”的格式进行无缝拼接。如果在全量排查后发现没有任何分区符合上述的综合画像，请直接输出大写的 NONE。", + "start_url": "https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national", + "output_format": "请将所有匹配的分区结果输出为一整行由英文逗号连接的字符串。每个独立匹配项的数据呈现需要严格按照“|<四位分区ID>|<分区名>|<1907-04 10个月Z-Index距平原样文本>|<1923-04 10个月Z-Index距平原样文本>|<1915-05 2个月HDD实际值原样文本>|<1922-10 5个月HDD实际值原样文本>|<保留2位小数的rebound score>”的格式进行无缝拼接。如果在全量排查后发现没有任何分区符合上述的综合画像，请直接输出大写的 NONE。", + "oracle_answer": "10|4110|Lower Valley|-0.36|1.46|10°Df|7°Df|1.82,9|4109|South|-0.33|0.53|23°Df|16°Df|0.86\n10|4110|Lower Valley|-0.36|1.46|10|7|1.82,9|4109|South|-0.33|0.53|23|16|0.86", + "metadata": { + "State-Gated Retrieval": [ + "只保留同时满足四个历史条件的 Texas 分区：1907-04 的 10-month Palmer Z-Index anomaly 不高于 -0.30；1923-04 的 10-month anomaly 不低于 -0.20；1915-05 的 2-month HDD Value 小于 50°Df；1922-10 的 5-month HDD Value 小于 20°Df。", + "rebound score 定义为 1923-04 的 10-month anomaly 减去 1907-04 的 10-month anomaly。", + "最终按 rebound score 降序、再按 1922-10 的 5-month HDD Value 升序、再按 Texas 分区号升序排序。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Texas divisional pages yield the 1907-04 and 1923-04 10-month Palmer Z-Index anomalies plus the 1915-05 2-month and 1922-10 5-month HDD values for each division", + "the rebound score and the two shoulder-season HDD values are computed only after the same divisional candidate set survives all four historical filters", + "the final output is produced after sorting the surviving divisions by rebound score, then 1922-10 HDD value, then division number" + ], + "control_dependency": [ + "the workflow must cover the 1907, 1923, and 1915 pages as well as the 1922-10 5-month HDD page", + "both HDD pages must be read from Value rather than Anomaly", + "the final rebound ranking must be determined after the 1922-10 5-month HDD page excludes 7 South Central and 8 Upper Coast, using ReboundScore as the ordering basis" + ], + "freeze": { + "historical_window": "Texas climate divisions evaluated on the 1907-04 and 1923-04 10-month Palmer Z-Index anomaly pages, the 1915-05 2-month HDD Value page, and the 1922-10 5-month HDD Value page" + }, + "answer_type": "mixed multi-line output" + }, + "rubric": { + "inclusion_conditions": [ + "只保留同时满足四个历史条件的 Texas 分区：1907-04 的 10-month Palmer Z-Index anomaly 不高于 -0.30；1923-04 的 10-month anomaly 不低于 -0.20；1915-05 的 2-month HDD Value 小于 50°Df；1922-10 的 5-month HDD Value 小于 20°Df。", + "rebound score 定义为 1923-04 的 10-month anomaly 减去 1907-04 的 10-month anomaly。", + "最终按 rebound score 降序、再按 1922-10 的 5-month HDD Value 升序、再按 Texas 分区号升序排序。" + ], + "exclusion_conditions": [ + "排除只做完 1907、1923 和 1915 三页过滤就提前停止、没有继续读取 1922-10 / 5-month / HDD 页面的结果。", + "排除把 1915 或 1922 的 HDD 页面误读成 Anomaly 而不是 Value 的结果。", + "排除任何一个历史窗口条件不满足的分区。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "texas_division_no", + "division_id_4digit", + "division_name", + "apr_1907_10mo_z_text", + "apr_1923_10mo_z_text", + "may_1915_2mo_hdd_text", + "oct_1922_5mo_hdd_text", + "rebound_score" + ], + "texas_division_no": "emit the short Texas climate-division number in field 1 and the four-digit division ID in field 2", + "raw_text_fields": "the two Z-index anomaly fields preserve the raw displayed text; the two HDD fields preserve the raw displayed text, but comparison may ignore an optional trailing `°Df` suffix", + "rebound_score": "compute as the April 1923 10-month Z-index anomaly minus the April 1907 10-month Z-index anomaly, formatted with exactly two decimal places", + "sorting_or_selection": { + "primary": "rebound_score descending", + "secondary": "October 1922 HDD actual value ascending after numeric normalization", + "tertiary": "Texas division number ascending" + }, + "answer_set_note": "the current oracle stores two equivalent answer sets: one preserves the HDD unit suffixes and one strips them; treat the two HDD columns as equivalent after optional `°Df` removal", + "stop_condition": [ + "all candidate Texas divisions are checked under the same anomaly and HDD windows", + "the unique ordered output string is resolved before emission" + ] + } + } +} diff --git a/data_zh/goal/comptox_001-g.json b/data_zh/goal/comptox_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..914412290b7211d280b581a1faf7cd3432b2b5ce --- /dev/null +++ b/data_zh/goal/comptox_001-g.json @@ -0,0 +1,76 @@ +{ + "task_id": "comptox_010-g", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "我想把五种在欧洲彩绘产品相关记录里出现过的物质，也就是aniline、cobalt、chromium、3,3'-dichlorobenzidine 和 dibenz[a,h]anthracene 这五种物质，提取出页面明确包含‘Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe’记录的合格目标，并为其生成一份整合了历史关键词状态与最深层级用途的综合清单。第一，这个物质在以下五个带日期的历史关键词里一共命中了几项——Substances in Products - Canada (4/2014)、Indirect additives food contact (10/2018)、OEHHA Proposition 65 (3/2019)、WA Children's Safe Product Act (4/2020)、OEHHA Proposition 65 (1/2023)；命中只看有没有出现，不管前面标的数字；同时写出命中项里最早和最晚的年月。第二，给这个物质各保留一个最能反映它当前怎么被使用的类别。在剔除前述彩绘记录所属用途类别的前提下，需为每个物质分别确立‘日常消费品’（大类选取优先级为 Formulation → Article → Occupation）与‘生产原料’（大类选取优先级为 Occupation → Article → Formulation）两个维度的末端用途画像。最后，把所有物质按历史关键词命中数从高到低排列；命中数相同的，按日常消费品侧入选节点的产品数从高到低排。", + "start_url": "https://comptox.epa.gov/chemexpo/", + "output_format": "输出格式如下：|<命中数>|<最早年月>|<最晚年月>|<日常消费品侧PUC kind>|<日常消费品侧一般类别PUC ID>|<日常消费品侧入选节点PUC ID>|<日常消费品侧节点层级>|<日常消费品侧Products>|<生产原料侧PUC kind>|<生产原料侧一般类别PUC ID>|<生产原料侧入选节点PUC ID>|<生产原料侧节点层级>|<生产原料侧Products>结果之间用英文逗号分隔；若没有结果输出 NONE。", + "oracle_answer": "DTXSID8020090|5|2014-04|2023-01|Formulation|272|295|type|4|Occupation|301|356|family|27,DTXSID1031040|3|2018-10|2023-01|Formulation|77|94|type|7|Occupation|301|400|family|308,DTXSID9020409|2|2019-03|2023-01|Occupation|321|321|general|11|Occupation|321|321|general|11,DTXSID6020432|2|2019-03|2023-01|Article|313|313|general|1|Occupation|301|356|family|27,DTXSID3031022|1|2023-01|2023-01|Formulation|77|95|type|4|Occupation|301|356|family|185", + "metadata": { + "State-Gated Retrieval": [ + "只在题目指定的五个物质中筛选，并且目标物质页面必须明确包含 “Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe” 这条记录。", + "要统计五个指定 dated keywords 是否出现，并记录命中项中最早和最晚的年月。", + "随后必须分别选择一条日常消费品侧路线与一条生产原料侧路线，前者按 Formulation → Article → Occupation，后者按 Occupation → Article → Formulation 独立下钻。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "each chemical page yields the five dated historical keywords, the Europe body-paint/tattoo-ink qualifying record, and the earliest/latest dated-hit months", + "PUC drilldowns yield one consumer-side route chosen by Formulation -> Article -> Occupation and one source-side route chosen independently by Occupation -> Article -> Formulation", + "final rows are produced only after the consumer-side and source-side routes are selected and drilled separately for each chemical" + ], + "control_dependency": [ + "the source-side route must be selected independently from the consumer-side route", + "for each chemical, the second drilldown must follow the production-material priority order rather than the daily-consumer route", + "family/type/general outputs must be determined only after both route selections are made independently" + ], + "freeze": { + "historical_window": "the five named substances as objectively existing chemicals, using their ChemExpo chemical pages, PUC drilldowns, keyword-state evidence, and Europe body-paint/tattoo-ink presence as relatively stable classification signals" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在题目指定的五个物质中筛选，并且目标物质页面必须明确包含 “Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe” 这条记录。", + "要统计五个指定 dated keywords 是否出现，并记录命中项中最早和最晚的年月。", + "随后必须分别选择一条日常消费品侧路线与一条生产原料侧路线，前者按 Formulation → Article → Occupation，后者按 Occupation → Article → Formulation 独立下钻。" + ], + "exclusion_conditions": [ + "排除不含题目指定 Europe 彩绘/纹身墨水记录的物质。", + "排除把同一条日常消费品侧路线直接复用到生产原料侧的结果。", + "排除没有按指定优先顺序独立选择并下钻两条路线的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DTXSID", + "hit_count", + "earliest", + "latest", + "consumer_kind", + "consumer_general_puc_id", + "consumer_terminal_puc_id", + "consumer_level", + "consumer_products", + "material_kind", + "material_general_puc_id", + "material_terminal_puc_id", + "material_level", + "material_products" + ], + "dated_hits": "count only the exact dated keyword strings defined in the source rubric", + "date_format": "YYYY-MM", + "kind": "the kind fields use the canonical labels Article, Formulation, or Occupation", + "level": "the level fields use the canonical labels general, family, or type", + "products_source": "the Products counts come from the local chemical-detail node for the selected branch, not from an overall aggregate shown elsewhere on the site", + "sorting_or_selection": { + "primary": "hit_count descending", + "secondary": "consumer_products descending", + "tertiary": "DTXSID ascending" + } + } + } +} diff --git a/data_zh/goal/comptox_002-g.json b/data_zh/goal/comptox_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..99c5068d79c9c0f1a4b9b5a91478edca224e4819 --- /dev/null +++ b/data_zh/goal/comptox_002-g.json @@ -0,0 +1,78 @@ +{ + "task_id": "comptox_011-g", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 6, + "instruction": "我想在 ChemExpo 里看看这六个物质，当前到底是更多出现在材料接触相关的用途里，还是制造来源相关的用途里，然后从对应的方向上各选出一个最能代表它的用途分类。具体来说，范围只限于这六个物质：Di(2-Ethylhexyl) Phthalate、Melamine、Tris(2-Ethylhexyl) Phosphate、4,5-Dihydro-2-Mercaptoimidazole、Phthalic Acid、Triphenyl Phosphates Tert-Butylated。对每个物质，都需要查三组数据：针对每个物质，该画像首先需要精准量化三项基础指标：其一是汇总五类特定标签（Indirect additives food contact (10/2018)、Europe, Food contact items、Food contact items, Japan、包含 Toys and children's products 字样的词条、包含 artificial_saliva 或 artificial_sweat 字样的词条）出现情况得出的‘材料接触得分’；其二是汇总两类特定标签（drinking_water, Europe, manufacturing, plastic_additive 与 Europe, plastic_additive）出现情况得出的‘制造来源得分’；其三是统计四个带日期关键词（Indirect additives food contact (10/2018)、OEHHA Proposition 65 (3/2019)、WA Children's Safe Product Act (4/2020)、OEHHA Proposition 65 (1/2023)）的实际命中总数、并提取其中跨越的最早与最晚年月区间而生成的监管概况。在此基础上，如果材料接触那边的得分严格大于制造来源那边，就算它偏向材料接触，按 Article → Formulation → Occupation 的顺序来找最能代表这个物质的类别；否则都算偏向制造来源，按 Occupation → Article → Formulation 的顺序来找。确定了类别之后，每一层都只沿着产品数最多的下一级分类往下走，一直走到不能再细分；如果同一层有并列，就取 PUC ID 更小的。", + "start_url": "https://comptox.epa.gov/chemexpo/", + "output_format": "最后，把各物质按带日期命中数从高到低排列；命中数相同的，再按入选节点的产品数从高到低排列，输出格式如下：||||||||||||结果之间用英文逗号分隔；如果带日期命中数为 0，则 earliest 和 latest 都写 NA。", + "oracle_answer": "DTXSID5020607|5|2|4|2018-10|2023-01|contact|Article|309|493|family|1|23|58,DTXSID5020601|4|1|3|2018-10|2023-01|contact|Article|309|309|general|1|5836|1827,DTXSID6020802|4|2|1|2018-10|2018-10|contact|Article|313|313|general|15|1104|675,DTXSID8021484|3|1|1|2018-10|2018-10|contact|Occupation|321|321|general|8|28313|4200,DTXSID0021414|5|0|1|2018-10|2018-10|contact|Article|309|309|general|3|5836|1827,DTXSID20872645|0|1|0|NA|NA|source|Occupation|318|381|family|5|274|107", + "metadata": { + "State-Gated Retrieval": [ + "只看题目指定的六个物质，并先在 chemical page 上计算 contactHits、sourceHits 和 datedHits。", + "prioritySide 必须先由这些历史信号决定，然后再沿对应方向挑选一个最能代表的当前用途分类。", + "当前路线选择必须按题目给定的 kind 优先级和同层更小 PUC ID 规则继续下钻。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "each chemical page yields contactHits, sourceHits, datedHits, and the earliest/latest dated-hit months from the historical keyword set", + "after the priority side is chosen, the corresponding current PUC drilldown yields the representative kind, PUC path, product counts, and curated-chemical counts", + "final rows are produced only after the historical hit scores determine the side first and the current route is then chosen with the side-specific priority and tie-break rules" + ], + "control_dependency": [ + "historical contact/source signal scores must take priority over current maximum-Products paths", + "the priority side must be determined from contactHits, sourceHits, and datedHits rather than from current visibility alone", + "PUC path tie-breaks are valid only after the correct side has been fixed and the route has been re-drilled under that side's rules" + ], + "freeze": { + "historical_window": "the six named substances as objectively existing chemicals, using their ChemExpo chemical pages, PUC drilldowns, historical keyword families, and keyword-hit evidence as relatively stable classification signals" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只看题目指定的六个物质，并先在 chemical page 上计算 contactHits、sourceHits 和 datedHits。", + "prioritySide 必须先由这些历史信号决定，然后再沿对应方向挑选一个最能代表的当前用途分类。", + "当前路线选择必须按题目给定的 kind 优先级和同层更小 PUC ID 规则继续下钻。" + ], + "exclusion_conditions": [ + "排除忽略历史信号、直接在 chemical page 上选当前可见 Products 最大路径的结果。", + "排除未先确定 contact/source 方向就开始做 PUC 路线选择的结果。", + "排除同层 tie-break 不按更小 PUC ID 规则处理的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DTXSID", + "contactHits", + "sourceHits", + "datedHits", + "earliest", + "latest", + "prioritySide", + "PUCkind", + "generalPUCID", + "terminalPUCID", + "level", + "Products", + "PUCDocuments", + "PUCCuratedChemicals" + ], + "dated_hits": "count only the exact dated keyword strings defined in the source rubric", + "date_format": "YYYY-MM; if datedHits is 0, earliest and latest are both `NA`", + "prioritySide": "emit `contact` when contactHits > sourceHits; otherwise emit `source`", + "kind": "the PUCkind field uses the canonical labels Article, Formulation, or Occupation", + "level": "the level field uses the canonical labels general, family, or type", + "products_source": "Products comes from the selected terminal chemical-detail node", + "terminal_statistics": "PUCDocuments and PUCCuratedChemicals come from the selected terminal PUC detail page Additional Statistics block", + "sorting_or_selection": { + "primary": "datedHits descending", + "secondary": "Products descending", + "tertiary": "DTXSID ascending" + } + } + } +} diff --git a/data_zh/goal/comptox_003-g.json b/data_zh/goal/comptox_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..baa28c0205226b840009ab50bbc5c81d3a3ff5c8 --- /dev/null +++ b/data_zh/goal/comptox_003-g.json @@ -0,0 +1,67 @@ +{ + "task_id": "comptox_012-g", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我想在 ChemExpo 里先筛出一些产品较多的配方大类，然后再从每个大类里，挑出一个带 child 或 aerosol 标签、最值得优先看的具体产品。具体来说，我要找的是这样一批结果：针对每个总产品量不低于 15,000 的配方（Formulation）大类，找一个最优的具体产品类型，这个目标类型必须隶属于该大类默认展示顺序下的第一个符合以下条件的家族，其中包括家族总产品量至少为 3,000 且无默认属性（assumed attributes），同时旗下必须拥有自选属性（allowed attributes）带有‘气雾剂类（aerosol）’与‘儿童用类（child）’、且自身均无默认属性的产品类型。之后在其下所有符合条件的‘气雾剂类’和‘儿童用类’中，挑选出产品份额（该类型产品数除以家族累计产品数）最高的那一个；若遇到份额相同的情况，则依次优先选择产品数（Product Count）更高、Curated Chemicals 更多、或 PUC ID 更小的类型，直到得出唯一的最终结果。最后，保留一个最终结果：优先选择产品份额更高的具体产品类型；若两侧产品份额相同，则依次比较产品数（Product Count）、Curated Chemicals 和 PUC ID，分别保留数值更高、更多、更小的，直至得到唯一的最终类型。", + "start_url": "https://comptox.epa.gov/chemexpo/visualizations/", + "output_format": "最后，请按最终 share 从高到低输出结果，格式写成：<一般类别PUC ID>|<家族PUC ID>|<具体产品类型PUC ID>|||结果之间用英文逗号连接，且不加空格；如果没有结果，就输出 NONE。", + "oracle_answer": "48|42|62|child|2160/3531|583,137|197|210|child|6934/16904|1135", + "metadata": { + "State-Gated Retrieval": [ + "先只保留总产品量达到 15,000 及以上的 Formulation 大类。", + "在每个候选 family 中，必须同时找到一条 aerosol 侧 type 和一条 child 侧 type：family 本身 assumed attributes 为空且总产品量至少 3,000；两个 type 的 assumed attributes 也都为空。", + "最终 family 内部与双侧之间的优先选择都必须按题目规定的 share、Product Count、Curated Chemicals、PUC ID 规则比较。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Formulation summary yields the high-product candidate families whose total product count is at least 15,000", + "within each family, lower-level type pages yield the aerosol and child candidates, their assumed/allowed attributes, product counts, shares, and curated-chemical counts", + "final rows are produced only after a family survives both aerosol and child branches and the winning type is selected by the layered share/product/chemical/PUC tie-break rules" + ], + "control_dependency": [ + "both the aerosol and child branches within the same family must be fully checked before that family can be retained", + "if one side is missing, the workflow must reject the family and continue to the next sibling family rather than stop at the first partial hit", + "the final winner can be selected only after both sides have been independently optimized within the family and then compared against each other" + ], + "freeze": { + "historical_window": "ChemExpo Formulation families as objectively existing catalog families, especially large families with total product count >= 15,000, evaluated by family/type identity and product/chemical counts as relatively stable catalog descriptors" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先只保留总产品量达到 15,000 及以上的 Formulation 大类。", + "在每个候选 family 中，必须同时找到一条 aerosol 侧 type 和一条 child 侧 type：family 本身 assumed attributes 为空且总产品量至少 3,000；两个 type 的 assumed attributes 也都为空。", + "最终 family 内部与双侧之间的优先选择都必须按题目规定的 share、Product Count、Curated Chemicals、PUC ID 规则比较。" + ], + "exclusion_conditions": [ + "排除只要在任意一侧先找到可用 type 就停止、没有要求同一家族同时覆盖 aerosol 与 child 两侧的结果。", + "排除一侧缺失时没有继续回溯 sibling family 的结果。", + "排除未按题目指定的层层 tie-break 规则选出 family 内与最终优胜 type 的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "generalPUCID", + "familyPUCID", + "typePUCID", + "side", + "share", + "CuratedChemicals" + ], + "dedup_key": "(generalPUCID, familyPUCID, typePUCID, side)", + "side": "emit the lower-case branch label exactly as determined in the source workflow", + "share": "canonical output uses the raw fraction `type Products / family Cumulative Products` rather than a decimal", + "CuratedChemicals": "emit the integer count from the selected type-level node", + "sorting_or_selection": { + "primary": "share descending by numeric fraction value", + "secondary": "type-level Products descending", + "tertiary": "CuratedChemicals descending, then PUC IDs ascending as tie-breaks" + } + } + } +} diff --git a/data_zh/goal/comptox_004-g.json b/data_zh/goal/comptox_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..04c24490f0039d093d4be37d5f7be33c014a0995 --- /dev/null +++ b/data_zh/goal/comptox_004-g.json @@ -0,0 +1,84 @@ +{ + "task_id": "comptox_013-g", + "domain": "COMPTOX_CHEMEXPO", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "在 ChemExpo 中，我们需要针对 Di(2-Ethylhexyl) Phthalate、Melamine、Phthalic Acid、Tris(2-Ethylhexyl) Phosphate 和 Triphenyl Phosphates Tert-Butylated 这五个物质，核对它们的历史标签与当前实际用途是否一致。具体来说，范围只限于这五个物质：Di(2-Ethylhexyl) Phthalate、Melamine、Phthalic Acid、Tris(2-Ethylhexyl) Phosphate、Triphenyl Phosphates Tert-Butylated。对每个物质，都需要查三组数据：第一组是成品接触方面的得分。看以下五类标签有没有出现过，每类出现了就记 1 分：Indirect additives food contact (10/2018)、Europe, Food contact items、Food contact items, Japan、任何带有 Toys and children's products 字样的关键词，以及任何带有 artificial_saliva 或 artificial_sweat 字样的关键词。第二组是生产来源方面的得分。看两类标签有没有出现过，每类出现了也记 1 分：drinking_water, Europe, manufacturing, plastic_additive 和 Europe, plastic_additive。第三组是带日期关键词的命中情况。只看以下四个关键词有没有出现过：Indirect additives food contact (10/2018)、OEHHA Proposition 65 (3/2019)、WA Children's Safe Product Act (4/2020)、OEHHA Proposition 65 (1/2023)；记录命中了几个，以及命中项里最早和最晚的年月。在此基础上，如果成品接触那边的分数严格大于生产来源那边，就算它偏向成品接触，按 Article → Formulation → Occupation 的顺序为它选出一个历史线索推荐的类别；否则都算偏向生产来源，按 Occupation → Article → Formulation 的顺序来选。确定了类别之后，沿着产品数最多的下一级分类一路往下走，直到不能再细分；如果同一层有并列，就取 PUC ID 更小的。同时，还要另外找出这个物质当前的主导类别，不看历史线索，直接在所有用途分类里找产品数最多的那条线，同样一路往下走到不能再细分；同层并列也取 PUC ID 更小的。最后把这两个结果放在一起比对：如果当前主导类别是 Article 或 Formulation，而历史线索判断也指向成品接触，就记 ALIGNED；如果当前主导类别是 Occupation，而历史线索判断也指向生产来源，也记 ALIGNED；其余都记 MISALIGNED。", + "start_url": "https://comptox.epa.gov/chemexpo/", + "output_format": "输出时先把 MISALIGNED 的排在前面；同一组里再按带日期命中数从高到低排；命中数也相同的，再按当前主导类别的产品数从高到低排。格式如下：|||||||||||||||||结果之间用英文逗号分隔；如果带日期命中数为 0，则 earliest 和 latest 都写 NA。", + "oracle_answer": "DTXSID6020802|4|2|1|2018-10|2018-10|material|Article|Furniture and furnishings|Furniture and furnishings|general|15|Occupation|Raw materials|fireproof coatings|type|24|MISALIGNED,DTXSID8021484|3|1|1|2018-10|2018-10|material|Occupation|Laboratory supplies|Laboratory supplies|general|8|Occupation|Laboratory supplies|Laboratory supplies|general|8|MISALIGNED,DTXSID5020607|5|2|4|2018-10|2023-01|material|Article|Construction and building materials|flooring|family|1|Formulation|Home maintenance|paint|type|112|ALIGNED,DTXSID0021414|5|0|1|2018-10|2018-10|material|Article|Construction and building materials|Construction and building materials|general|3|Article|Construction and building materials|Construction and building materials|general|3|ALIGNED,DTXSID20872645|0|1|0|NA|NA|source|Occupation|Industrial products|hydraulic fluid|family|5|Occupation|Industrial products|hydraulic fluid|family|5|ALIGNED", + "metadata": { + "State-Gated Retrieval": [ + "只在题目指定的五个物质上工作，并先根据 keyword-set 区块计算 materialHits、sourceHits 与 datedHits。", + "历史推荐类别必须由这些历史信号独立推出；当前主导类别则需要单独从当前用途路径中求出。", + "最终只比较历史推荐类别与当前主导类别所在的大类方向是否一致，并据此标记 ALIGNED 或 MISALIGNED。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "each chemical page yields materialHits, sourceHits, datedHits, and the historical recommendation side implied by the keyword set", + "independent current PUC drilldown yields the current dominant category, path labels, and classification counts for the same chemical", + "final rows are produced only after the historical recommendation and current dominant category are computed independently and then compared at the coarse side level" + ], + "control_dependency": [ + "the historical recommendation must be determined from the keyword-set evidence rather than from the current largest category", + "historical recommendation must be computed from the keyword-set evidence before alignment is judged", + "ALIGNED / MISALIGNED status is valid only after the historical and current category directions have been derived independently and then compared" + ], + "freeze": { + "historical_window": "the five named substances as objectively existing chemicals, using their ChemExpo chemical pages, PUC drilldowns, and specified keyword-set evidence as relatively stable recommendation signals" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在题目指定的五个物质上工作，并先根据 keyword-set 区块计算 materialHits、sourceHits 与 datedHits。", + "历史推荐类别必须由这些历史信号独立推出；当前主导类别则需要单独从当前用途路径中求出。", + "最终只比较历史推荐类别与当前主导类别所在的大类方向是否一致，并据此标记 ALIGNED 或 MISALIGNED。" + ], + "exclusion_conditions": [ + "排除只看当前最大类别、直接把它当成历史推荐类别的结果。", + "排除在没有独立求出历史推荐类别的情况下默认一律 ALIGNED 的结果。", + "排除未把历史与当前两条链路分开计算、而是在同一路线里混读信号的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DTXSID", + "materialHits", + "sourceHits", + "datedHits", + "earliest", + "latest", + "historySide", + "recommendedKind", + "recommendedGeneral", + "recommendedTerminal", + "recommendedLevel", + "recommendedProducts", + "currentKind", + "currentGeneral", + "currentTerminal", + "currentLevel", + "currentProducts", + "status" + ], + "dated_hits": "count only the exact dated keyword strings defined in the source rubric", + "date_format": "YYYY-MM; if datedHits is 0, earliest and latest are both `NA`", + "historySide": "emit the lower-case historical winner `material` or `source`", + "recommended_fields": "these fields describe the historically suggested path", + "current_fields": "these fields describe the current dominant path", + "kind": "the kind fields use the canonical labels Article, Formulation, or Occupation", + "level": "the level fields use the canonical labels general, family, or type", + "status": "emit `ALIGNED` or `MISALIGNED` exactly", + "sorting_or_selection": { + "primary": "status with MISALIGNED before ALIGNED", + "secondary": "datedHits descending", + "tertiary": "currentProducts descending", + "quaternary": "DTXSID ascending" + } + } + } +} diff --git a/data_zh/goal/consumerfinance_001-g.json b/data_zh/goal/consumerfinance_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..2c0a737c9c68d17ecd9a2c0bb893670d48758897 --- /dev/null +++ b/data_zh/goal/consumerfinance_001-g.json @@ -0,0 +1,67 @@ +{ + "task_id": "consumerfinance_008-g", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "请针对美国消费者金融保护局（CFPB）在 2022-01-01 至 2024-12-31 期间立案的行政执法案件（Enforcement actions），提供一份关于存款业务（Deposits）、征信信息报送业务（Furnishing）和预付类业务（Prepaid）的核心金额提取报告。该报告的检索目标为上述每个业务类别下，按照网站默认展示顺序找到的首个满足以下全部属性的案件：同时公开提供和解令（Consent Order）与新闻稿（press release）、业务类别（Products）标签与目标类别唯一且绝对对应、且页面明文标示消费者补偿金额（consumer redress）超过 500 万美元并附带民事罚款金额（civil money penalty）。在锁定这三个目标案件后，请从各自的和解令 PDF 源文件中，分别提取消费者补偿金额与民事罚款金额在正文中首次出现的具体数值，及其对应的物理页码（PDF 首页记为 p1）。", + "start_url": "https://www.consumerfinance.gov/enforcement/actions/", + "output_format": "最终结果请严格按照业务类别的英文首字母顺序，以 |||||p||p 的格式呈现，各条目之间直接以英文逗号连接且不留空格；若某一类别未找到匹配案件，请直接输出 |NONE。", + "oracle_answer": "Deposits|Bank of America, N.A.|2023-CFPB-0006|2023-07-11|$80,400,000|p11|$60,000,000|p14,Furnishing|Hyundai Capital America|2022-CFPB-0005|2022-07-26|$13,200,000|p31|$6,000,000|p35,Prepaid|U.S. Bank National Association|2023-CFPB-0019|2023-12-19|$5,700,000|p22|$15,000,000|p26", + "metadata": { + "State-Gated Retrieval": [ + "只看 CFPB Enforcement actions 页面中 Initial filing date 落在 2022-01-01 至 2024-12-31 的 administrative enforcement actions。", + "对 Deposits、Furnishing、Prepaid 三个产品类别分别按当前默认顺序自上而下寻找第一件同时满足：页面提供 Consent Order 和 Press release；Products 与目标类别一对一对应；action detail page 明确写出 consumer redress > 5,000,000 美元且另有 civil money penalty。", + "最终从正确的 Consent Order 中提取 consumer redress 和 civil money penalty 第一次出现的金额及页码。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "enforcement-action list pages yield product-branch candidate actions in current default order", + "each action detail page and linked consent-order PDF yield product singularity, document-stack presence, redress / civil-money-penalty amounts, and first-occurrence pages", + "final rows are emitted only after identifying, for each product, the first action that survives detail-page and PDF validation" + ], + "control_dependency": [ + "list-level \"has Consent Order + Press release\" hits must be validated on the detail page for product singularity and money thresholds", + "Prepaid candidates force document-level disambiguation among Consent Order, Stipulation, and terminating-order PDFs", + "per-product first-match selection must explicitly skip rejected candidates and validate downstream PDFs before it is finalized" + ], + "freeze": { + "historical_window": "administrative enforcement actions with Initial filing date from 2022-01-01 through 2024-12-31; current default case ordering and currently linked action documents" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只看 CFPB Enforcement actions 页面中 Initial filing date 落在 2022-01-01 至 2024-12-31 的 administrative enforcement actions。", + "对 Deposits、Furnishing、Prepaid 三个产品类别分别按当前默认顺序自上而下寻找第一件同时满足：页面提供 Consent Order 和 Press release；Products 与目标类别一对一对应；action detail page 明确写出 consumer redress > 5,000,000 美元且另有 civil money penalty。", + "最终从正确的 Consent Order 中提取 consumer redress 和 civil money penalty 第一次出现的金额及页码。" + ], + "exclusion_conditions": [ + "排除 Products 不是单一目标类别、或仅在列表层看起来相关但 detail page 不成立的案件。", + "排除没有明确满足 redress > 5M 与独立 civil money penalty 条件的案件。", + "排除误用 Stipulation 或 Order Terminating the Consent Order 代替题目要求的 Consent Order。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Product", + "Respondent", + "Docket", + "FilingDate", + "RedressUSD", + "RedressPage", + "PenaltyUSD", + "PenaltyPage" + ], + "product_order": "alphabetical by Product name", + "fallback_row": "if a product has no qualifying case, emit `|NONE`", + "date_format": "FilingDate uses YYYY-MM-DD", + "money_fields": "canonical output preserves the dollar sign and commas from the oracle, but equivalent comparison may ignore `$` and commas and compare the numeric USD amount", + "page_fields": "page fields use the canonical `pN` form", + "document_scope": "extract both money amounts from the Consent Order PDF only; do not substitute a stipulation, termination order, or other companion document", + "selection_rule": "for each product, keep the first action in the default filtered order that fully satisfies every gate in the source rubric" + } + } +} diff --git a/data_zh/goal/consumerfinance_002-g.json b/data_zh/goal/consumerfinance_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..e4334b174ef2d7519f7d9fa15db27406e75404cb --- /dev/null +++ b/data_zh/goal/consumerfinance_002-g.json @@ -0,0 +1,66 @@ +{ + "task_id": "consumerfinance_009-g", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我想整理一下 CFPB Reports 里那套一年一度的家庭财务稳定性调查报告，它的最新版页面上还能直接链回 2023 和 2022 两个旧版。我关心的是：2022 版里出现过、但在后续年份年报中不再出现的那些主题，不过要排除掉那个专门用来标记\"属于同一调查系列\"的主题。对每个这样的主题，我需要以下信息：它最早在哪一年的后续年报中消失的；这些主题相关的2022 年及之前的结果中，不属于这套系列的首个报告；该报告列明的相关资源总数，其中明确指回同一调查系列的有几项，附录含字母编号且至少包含三个章节的回溯报告数量；最终入选报告的标题、发布日期及附录字母编号范围。", + "start_url": "https://www.consumerfinance.gov/data-research/research-reports/", + "output_format": "请按主题名称的字母顺序，输出一行字符串：|||||||||", + "oracle_answer": "Saving|2023|Consumer Savings App Strategies and Savings Outcomes|2022-12-07|4|2|1|Emergency Savings and Financial Security: Insights from the Making Ends Meet Survey and Consumer Credit Panel|2022-03-23|A-D,Student loans|2023|Report of the CFPB Education Loan Ombudsman|2022-10-20|0|0|0|NONE|NONE|NONE", + "metadata": { + "State-Gated Retrieval": [ + "先锁定当前最新版可直接链回 2023 和 2022 的那套 CFPB household financial well-being 年报系列。", + "以 2022 版为基准，只保留那些在 2022 出现、但在后续年度年报中不再保留的主题，并排除专门标记“属于同一调查系列”的主题。", + "对每个主题再按题目要求寻找 2022 年及以前最靠前的非本系列 pivot report，并依次统计 direct related resources、same-series 回链数、qualified report 及其 appendix span。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current CFPB Reports pages yield the 2024 -> 2023 -> 2022 annual-survey chain and the 2022 topic baseline", + "report detail pages and report-search results yield first-disappearance year, pivot report title/date, related-resource counts, and backlinks into the annual-survey series", + "final rows are produced only after separating the first jump target from later return-to-series counting" + ], + "control_dependency": [ + "binding the pivot report to same-series continuation forces an incorrect shrinkage of valid topic rows", + "title extraction must use the pivot detail page rather than search-result snippets", + "related-resource expansion must continue even when the first pivot page cannot itself continue the same-series chain" + ], + "freeze": { + "historical_window": "currently linked 2024, 2023, and 2022 CFPB household financial well-being annual reports; topic disappearance is judged over that three-year chain, and pivot-report search is restricted to 2022-and-earlier reports" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先锁定当前最新版可直接链回 2023 和 2022 的那套 CFPB household financial well-being 年报系列。", + "以 2022 版为基准，只保留那些在 2022 出现、但在后续年度年报中不再保留的主题，并排除专门标记“属于同一调查系列”的主题。", + "对每个主题再按题目要求寻找 2022 年及以前最靠前的非本系列 pivot report，并依次统计 direct related resources、same-series 回链数、qualified report 及其 appendix span。" + ], + "exclusion_conditions": [ + "排除仍在后续年度年报中保留的主题。", + "排除把“pivot report 必须还能继续回到同一系列”错误当成第 3 列硬条件的结果。", + "排除直接属于同一调查系列的搜索结果或 2022 年之后的报告。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "topic", + "first-missing-year", + "pivot-report-or-NONE", + "pivot-date-or-NONE", + "direct-related-count", + "same-series-count", + "qualified-count", + "representative-report-or-NONE", + "publication-date-or-NONE", + "appendix-span-or-NONE" + ], + "topic_order": "alphabetical by topic name", + "date_format": "pivot-date and publication-date use YYYY-MM-DD when present", + "appendix_span": "canonical span uses compact labels such as `A-D`", + "none_rule": "if qualified-count is 0, representative-report, publication-date, and appendix-span are all `NONE`" + } + } +} diff --git a/data_zh/goal/consumerfinance_003-g.json b/data_zh/goal/consumerfinance_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..5d06d59b893147d4655bd0e22a9dfa940b9bf916 --- /dev/null +++ b/data_zh/goal/consumerfinance_003-g.json @@ -0,0 +1,69 @@ +{ + "task_id": "consumerfinance_010-g", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我想把 CFPB 在 2020 年分发布的债务催收规则（ Debt Collection Rule）分别梳理清楚，包括它们各自的提案来源、延后生效的安排、最终生效日，以及实施页面上配套的 quick-reference PDF 信息。具体来说，我需要以下信息：最终规则（Final Rule）的具体发布日期;其溯源的拟议规则出处及名称、公众评议截止日期;2021 年延期生效拟议规则对本批最终规则的适用情况、公众评议截止日期、最终实际执行的生效日期;官方实施页面对应的快速参考（Quick-reference）PDF 文件名称、 正文的首个小标题（不计引言或背景性段落）。", + "start_url": "https://www.consumerfinance.gov/rules-policy/final-rules/", + "output_format": "请把两波结果按 final-rule issue date 从早到晚输出一行字符串，每一波用它的 final rule 发布月份（YYYY-MM）来标识：\n||||||||", + "oracle_answer": "2020-10|2020-10-30|2019-05-07 main|2019-09-18|YES|2021-05-19|2021-11-30|Executive summary of the October 2020 final rule|Coverage and Definitions,2020-12|2020-12-18|2019-05-07 main+2020-02-21 supplemental|2019-09-18+2020-08-04|YES|2021-05-19|2021-11-30|Executive summary of the December 2020 final rule|Validation Information Requirements and Disclosures", + "metadata": { + "State-Gated Retrieval": [ + "必须分别处理 2020 年两波同名的 Debt Collection Practices (Regulation F) final rules，而不是合并成一条。", + "对每一波都要分别确认：发布日期、对应 proposal chain 及公众意见截止日、2021 年 delayed-effective-date proposed rule 是否覆盖及其截止日、最终生效日、对应 implementation quick-reference PDF，以及该 PDF 跳过引言后的第一个小标题。", + "October wave 与 December wave 的 detail page、proposal chain 和 summary PDF 都必须各自独立核验。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "final-rules index pages and rule-development pages yield the two 2020 Regulation F final-rule waves and their proposal branches", + "each final-rule detail page, delayed-effective-date proposal page, and implementation quick-reference PDF yields the wave-specific dates, linked proposals, comment deadlines, and first summary heading", + "final rows are produced only after the October and December waves are traced separately end to end" + ], + "control_dependency": [ + "two same-title final rules force correction from name-based collapsing to issue-date branching", + "proposal-chain validation must be done per wave; otherwise the later December chain contaminates the October row", + "implementation PDFs must be matched back to the correct wave rather than accepting the latest quick-reference page" + ], + "freeze": { + "historical_window": "the 2020-10 and 2020-12 Debt Collection Rule final-rule waves, their linked 2020 proposal pages, the 2021 delayed-effective-date proposal, and the current implementation-page quick-reference PDFs" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "必须分别处理 2020 年两波同名的 Debt Collection Practices (Regulation F) final rules，而不是合并成一条。", + "对每一波都要分别确认：发布日期、对应 proposal chain 及公众意见截止日、2021 年 delayed-effective-date proposed rule 是否覆盖及其截止日、最终生效日、对应 implementation quick-reference PDF，以及该 PDF 跳过引言后的第一个小标题。", + "October wave 与 December wave 的 detail page、proposal chain 和 summary PDF 都必须各自独立核验。" + ], + "exclusion_conditions": [ + "排除把两条同名 2020 final rule 合并为一条的结果。", + "排除把 December wave 的 proposal chain 或 executive-summary heading 投射给 October wave 的结果。", + "排除未单独回到各自 final-rule detail page 和对应 PDF 核验的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "wave", + "final-rule-date", + "proposal-chain", + "proposal-comment-closes", + "delay-proposal-applied", + "delay-proposal-comments-close", + "controlling-effective-date", + "quick-reference-pdf", + "summary-heading" + ], + "wave": "wave is the final-rule issue month in YYYY-MM", + "date_format": "all standalone date fields use YYYY-MM-DD", + "proposal_chain": "canonical chain joins proposal milestones with `+`, using pieces such as `2019-05-07 main` or `2020-02-21 supplemental` in chronological order", + "proposal_comment_closes": "join multiple comment-close dates with `+` in the same order as proposal_chain", + "delay_proposal_applied": "emit `YES` when a delay proposal is part of the chain; otherwise emit `NO`", + "quick_reference_pdf": "use the displayed quick-reference PDF title, not the filename", + "summary_heading": "use the first substantive heading from the final-rule PDF", + "sorting_or_selection": "final-rule-date ascending" + } + } +} diff --git a/data_zh/goal/consumerfinance_004-g.json b/data_zh/goal/consumerfinance_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..8e501c383ab98c32dd7e83732cb3c22a0a0e6b87 --- /dev/null +++ b/data_zh/goal/consumerfinance_004-g.json @@ -0,0 +1,68 @@ +{ + "task_id": "consumerfinance_011-g", + "domain": "CFPB_REPORTS", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我想在 CFPB 的执法案件页面里，分别为 Credit Cards 和 Deposits 找到 2024 年最新、且后来已经终止的行政案件，并把终止令和原始 Consent Order 里对应的条款信息对上。具体来说，我要为 Credit Cards 和 Deposits 这两个 Products 标签各确定一件案件。候选范围只限于 Enforcement actions 里的行政执法案件，并且 Initial filing date 必须在 2024-01-01 到 2024-12-31 之间。每个产品标签下，取符合以下条件的案件中初始立案日期最晚的案件（若遇并列记录，则取案号 docket 较小者）：初始立案日期（Initial filing date）限定在 2024-01-01 至 2024-12-31 之间；案件状态变更为已过期（Expired）、已终止（Terminated）或已驳回（Dismissed）；文档清单同时包含和解令（Consent Order）、和解协议（Stipulation）、和解终止令（Order Terminating the Consent Order）与新闻稿（press release）；且业务类别（Products）标签当前检索唯一对应。对每个最终入选的案件，还要从它的 Order Terminating the Consent Order 中提取以下信息：TerminationDate：终止日期；TerminationAuthority：终止依据首次出现时的原文；TermAuthorityPage：这段内容第一次出现所在的 PDF 物理页码。另外，还要在这份终止令正文里找出第一次明确引用到的原始 Consent Order paragraph 编号；如果写成 “Paragraphs X and Y”，就只取 X。然后再回到原始 Consent Order，找到这个 paragraph 所在的小节标题。", + "start_url": "https://www.consumerfinance.gov/enforcement/actions/", + "output_format": "最后，请按产品名字母顺序输出一行字符串：||||||p||如果某个产品没有符合条件的案件，就输出：|NONE", + "oracle_answer": "Credit Cards|Apple Inc.|2024-CFPB-0012|2024-10-23|2025-09-22|12 U.S.C. § 5563(b)(3)|p1|83|ADMINISTRATIVE PROVISIONS,Deposits|Navy Federal Credit Union|2024-CFPB-0014|2024-11-07|2025-07-01|12 U.S.C. § 5563(b)(3)|p1|106|ADMINISTRATIVE PROVISIONS", + "metadata": { + "State-Gated Retrieval": [ + "只看 2024 年 Initial filing date 的 administrative enforcement actions，并分别在 Credit Cards 与 Deposits 类别中找案件。", + "案件必须状态为已失效、已终止或已撤销之一，并且页面同时提供 Consent Order、Stipulation、Order Terminating the Consent Order 和 Press release，且 Products 与目标类别一对一对应。", + "最终每个类别只保留按 Initial filing date 判定为最新的合格案件，并整理终止令与原始 Consent Order 的对应条款信息。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "enforcement-action list pages yield 2024 candidate actions by product branch", + "each action detail page and linked Consent Order / Stipulation / Order Terminating the Consent Order / Press release documents yield status, initial filing date, single-product validity, and clause references", + "final rows are selected only after per-product comparison on Initial filing date and document-stack validation" + ], + "control_dependency": [ + "\"latest\" must be determined by Initial filing date rather than termination date", + "product filters on the list page are insufficient until the action detail page confirms a single matching product", + "clause extraction in the terminating order must stay aligned with the original Consent Order rather than a superficially similar section" + ], + "freeze": { + "historical_window": "administrative enforcement actions with Initial filing date from 2024-01-01 through 2024-12-31; current action status and currently linked Consent Order / Stipulation / terminating-order / Press release documents" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只看 2024 年 Initial filing date 的 administrative enforcement actions，并分别在 Credit Cards 与 Deposits 类别中找案件。", + "案件必须状态为已失效、已终止或已撤销之一，并且页面同时提供 Consent Order、Stipulation、Order Terminating the Consent Order 和 Press release，且 Products 与目标类别一对一对应。", + "最终每个类别只保留按 Initial filing date 判定为最新的合格案件，并整理终止令与原始 Consent Order 的对应条款信息。" + ], + "exclusion_conditions": [ + "排除用 termination date 而不是 Initial filing date 来判定“最新”的结果。", + "排除文档栈不完整或 Products 不是单一目标类别的案件。", + "排除无法在 terminating order 与原始 Consent Order 之间建立题目要求条款对应关系的案件。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Product", + "Respondent", + "Docket", + "InitialFilingDate", + "TerminationDate", + "TerminationAuthority", + "TermAuthorityPage", + "ReferencedParagraph", + "ConsentSectionHeading" + ], + "product_order": "alphabetical by Product name", + "fallback_row": "if a product has no qualifying case, emit `|NONE`", + "date_format": "InitialFilingDate and TerminationDate use YYYY-MM-DD", + "termination_authority": "use the canonical statute string extracted from the termination order", + "page_fields": "TermAuthorityPage uses the canonical `pN` form", + "ReferencedParagraph": "emit the paragraph number as a plain numeric string", + "ConsentSectionHeading": "emit the uppercase heading of the consent-order section containing the referenced paragraph" + } + } +} diff --git a/data_zh/goal/consumerfinance_005-g.json b/data_zh/goal/consumerfinance_005-g.json new file mode 100644 index 0000000000000000000000000000000000000000..1255b84d8232ac22857ead4dbf8eeb87d44bac64 --- /dev/null +++ b/data_zh/goal/consumerfinance_005-g.json @@ -0,0 +1,75 @@ +{ + "task_id": "consumerfinance_012-g", + "domain": "CFPB_COMPLAINT_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我在做一份历史投诉簇的内部 outreach memo，想追踪一组比较特殊的投诉：在 CFPB Complaint Database 里，找出当前那个覆盖 credit reporting 和其他 personal consumer reports 的产品桶下、2018-01-01 到 2021-12-31 之间、标签是 Servicemember、有公开 narrative、并且文本里明确提到 medical bills 或 doctors 的投诉。请给我两条代表性投诉簇：第一条是这个 cohort 的峰值月份；第二条是这个 cohort 里最新、且投诉量仍至少达到峰值一半的月份。对每条投诉簇，请告诉我该月的总投诉量、该月投诉量最高的州及其投诉量、在这个州里该月投诉量最高的公司及其投诉量、以及这家公司在这个州和这个月里最早收到的那条投诉的编号、日期、Issue 和 Sub-issue。请按 Peak 在前、LatestHalfPeak 在后输出一行字符串：||||||||||。", + "start_url": "https://www.consumerfinance.gov/data-research/consumer-complaints/", + "output_format": "请按 Peak 在前、LatestHalfPeak 在后输出一行字符串：||||||||||。Peak 簇与 LatestHalfPeak 簇用英文逗号连接；若存在并列，月份按时间顺序判定，州按州缩写字母序升序取首位，公司按公司名称字母序升序取首位，最早投诉若同日并列则取 Complaint ID 最小者。", + "oracle_answer": "Peak|2018-02|46|CA|28|TRANSUNION INTERMEDIATE HOLDINGS, INC.|9|2806154|2018-02-07|Improper use of your report|Reporting company used your report improperly,LatestHalfPeak|2021-11|23|CA|12|EQUIFAX, INC.|3|4928768|2021-11-19|Problem with a credit reporting company's investigation into an existing problem|Their investigation did not fix an error on your report", + "metadata": { + "State-Gated Retrieval": [ + "只看当前 product bucket 下 credit reporting / other personal consumer reports 相关产品中，2018-01-01 至 2021-12-31、标签为 Servicemember、带公开 narrative 且文本明确提到 medical bills 或 doctors 的投诉。", + "第一条 cluster 必须是该 cohort 的 peak month；第二条 cluster 必须是该 cohort 中最新且投诉量仍至少达到峰值一半的月份。", + "对每个 cluster，都必须在对应的 month + state 子集中重算 TopCompany，再定位该公司在该州该月最早收到的 complaint。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current complaint-form taxonomy yields the product bucket that contains credit reporting / other personal consumer reports", + "filtered complaint records yield month counts, month-state subsets, top companies, and earliest complaint details inside each chosen subset", + "final rows are produced only after peak month and latest-half-peak month are determined, and each downstream aggregate is computed inside its narrower month-state cohort" + ], + "control_dependency": [ + "the latest month must be defined as the latest month whose count is at least ceil(PeakCount / 2)", + "overall top-company counts cannot be projected into a month-state subset without recomputation", + "earliest complaint selection is only valid after the month, state, and company filters are all frozen" + ], + "freeze": { + "historical_window": "Complaint Database records received from 2018-01-01 through 2021-12-31 under the current product-bucket mapping for the credit-reporting / other personal consumer reports family; Servicemember + public narrative + medical bills/doctors text cohort" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只看当前 product bucket 下 credit reporting / other personal consumer reports 相关产品中，2018-01-01 至 2021-12-31、标签为 Servicemember、带公开 narrative 且文本明确提到 medical bills 或 doctors 的投诉。", + "第一条 cluster 必须是该 cohort 的 peak month；第二条 cluster 必须是该 cohort 中最新且投诉量仍至少达到峰值一半的月份。", + "对每个 cluster，都必须在对应的 month + state 子集中重算 TopCompany，再定位该公司在该州该月最早收到的 complaint。" + ], + "exclusion_conditions": [ + "排除把“最新有投诉的月份”直接当成第二条 cluster 的结果。", + "排除先在全 cohort 中找 overall top company 再投射到 month-state 子集的结果。", + "排除没有先用 PeakCount 推出 half-peak threshold 的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Cluster", + "Month", + "MonthComplaints", + "TopState", + "StateComplaints", + "TopCompany", + "CompanyComplaints", + "EarliestComplaintID", + "EarliestDate", + "Issue", + "SubIssue" + ], + "cluster_order": [ + "Peak", + "LatestHalfPeak" + ], + "date_format": { + "Month": "YYYY-MM", + "EarliestDate": "YYYY-MM-DD" + }, + "TopState": "use the uppercase two-letter state abbreviation", + "TopCompany": "use the company display name as shown in the source data", + "tie_breaks": "for tied months use chronological order; for tied states use state-code alphabetical order; for tied companies use company-name alphabetical order; for the earliest complaint use EarliestDate ascending then Complaint ID ascending", + "SubIssue": "emit `NONE` when the complaint row has no sub-issue value" + } + } +} diff --git a/data_zh/goal/consumerfinance_006-g.json b/data_zh/goal/consumerfinance_006-g.json new file mode 100644 index 0000000000000000000000000000000000000000..2711d4f2f3200df30c8251a8ea7da9df729445da --- /dev/null +++ b/data_zh/goal/consumerfinance_006-g.json @@ -0,0 +1,78 @@ +{ + "task_id": "consumerfinance_013-g", + "domain": "CFPB_COMPLAINT_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我正在为一份内部的加密货币投诉“重灾区”分析报告（crypto-complaint concentration memo）收集数据，需要从 CFPB 投诉数据库中识别出两个具有特定代表性的投诉月份群体（Cluster），并提取它们的核心数据记录。\n这些数据必须源自一个特定的分析群体（Cohort）：其产品分类需对应虚拟货币“Virtual currency”在现行表单中的所属大类，且子类明确为虚拟货币“Virtual currency”；时间范围严格锁定在 2019-08-26 至 2022-08-26 之间。\n在该群体范围内，我需要锁定的两个特征月份属性如下：\n• 原始峰值月 (AllCompanies)：指该群体在未移除任何公司的情况下，月度投诉量达到绝对最高值的月份。\n• 残余峰值月 (ResidualAfterTop2)：其定义特征是，在识别出“原始峰值月”中投诉量最高的两家巨头公司，并将这两家公司在整个三年分析期内的所有记录彻底剔除后，剩余数据中重新涌现出的投诉量最高的月份。\n对于这两个特定的月份，我需要获取其详尽的属性，包括：该月总投诉量、被移除的两家巨头名称及其在原始峰值月的合计投诉贡献、该月投诉量最高的州及其规模、以及该州内被投诉最多的公司在该月、该州范围内最早的一条投诉详情（含 ID、日期、Issue 和 Sub-issue）。\n请帮我确认这两个月份的身份，并按照 AllCompanies 在前、ResidualAfterTop2 在后的顺序，分别输出一行没有任何空格的格式化字符串。每行字段序列严格固定为： ||||||||||||\n特别说明：\n• 字段请对应填写 AllCompanies 或 ResidualAfterTop2。\n• ExcludedTop2Companies 和 ExcludedTop2PeakMonthComplaints 在两行结果中均指代从“原始峰值月”中识别出的那两家巨头及其当时的合计投诉量。\n• Earliest 相关的四个字段，必须锁定为该月该州内排名第一的公司所对应的最早投诉记录。\n• 为保证答案唯一：两条记录按 AllCompanies、ResidualAfterTop2 的顺序输出；ExcludedTop2Companies 按原始峰值月投诉量从高到低排列；如任何排序指标出现并列，则按字段值字母序升序排列；若最早投诉日期并列，则取 Complaint ID 数值最小者。", + "start_url": "https://www.consumerfinance.gov/data-research/consumer-complaints/", + "output_format": "请按照 AllCompanies 在前、ResidualAfterTop2 在后的顺序，分别输出一行没有任何空格的格式化字符串。每行字段序列严格固定为：||||||||||||。", + "oracle_answer": "AllCompanies|2021-05|336|Coinbase, Inc.+BAM Management US Holdings Inc.|226|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,ResidualAfterTop2|2020-06|180|Coinbase, Inc.+BAM Management US Holdings Inc.|226|OH|28|PNC Bank N.A.|22|3687376|2020-06-07|Other transaction problem|NONE", + "metadata": { + "State-Gated Retrieval": [ + "只看当前 product bucket 下 Virtual currency 子类、接收日期在 2019-08-26 至 2022-08-26 的 Complaint Database 记录。", + "先确定 AllCompanies 原始峰值月，再识别该峰值月中投诉量最高的前两家公司。", + "这两家公司必须从整个三年 cohort 中整体移除，然后基于残余 cohort 重新计算 residual peak month 及所有 downstream 字段。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current complaint-form taxonomy yields the product bucket for Virtual currency", + "complaint records within the fixed three-year cohort yield the all-company peak month, per-month top companies, and residual-cohort recomputations after company removal", + "final rows are produced only after the top-2 companies from the original peak month are removed from the full cohort and downstream aggregates are computed on the resulting cohort" + ], + "control_dependency": [ + "peak-month top companies must be removed from the entire cohort, not only from the original peak month", + "residual peak detection must be computed from the rewritten cohort rather than by local patching of the original month", + "downstream state / company / earliest-complaint fields are valid only after the global company-removal step is locked" + ], + "freeze": { + "historical_window": "Complaint Database records received from 2019-08-26 through 2022-08-26 under the current product-bucket mapping for Virtual currency" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只看当前 product bucket 下 Virtual currency 子类、接收日期在 2019-08-26 至 2022-08-26 的 Complaint Database 记录。", + "先确定 AllCompanies 原始峰值月，再识别该峰值月中投诉量最高的前两家公司。", + "这两家公司必须从整个三年 cohort 中整体移除，然后基于残余 cohort 重新计算 residual peak month 及所有 downstream 字段。" + ], + "exclusion_conditions": [ + "排除只从原始峰值月局部删除 top-2 公司记录的结果。", + "排除没有把 top-2 company set 回写到整个 cohort 后再重算 residual peak 的结果。", + "排除基于未重算残余 cohort 的 downstream 州、公司或 earliest complaint 字段。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Cluster", + "Month", + "MonthComplaints", + "ExcludedTop2Companies", + "ExcludedTop2PeakMonthComplaints", + "TopState", + "StateComplaints", + "TopCompany", + "CompanyComplaints", + "EarliestComplaintID", + "EarliestDate", + "Issue", + "SubIssue" + ], + "cluster_order": [ + "AllCompanies", + "ResidualAfterTop2" + ], + "date_format": { + "Month": "YYYY-MM", + "EarliestDate": "YYYY-MM-DD" + }, + "ExcludedTop2Companies": "join the two excluded company names with `+` in source-peak complaint-count descending order, breaking ties alphabetically", + "TopState": "use the uppercase two-letter state abbreviation", + "TopCompany": "use the company display name as shown in the source data", + "tie_breaks": "for the earliest complaint use EarliestDate ascending then Complaint ID ascending", + "SubIssue": "emit `NONE` when the complaint row has no sub-issue value" + } + } +} diff --git a/data_zh/goal/consumerfinance_007-g.json b/data_zh/goal/consumerfinance_007-g.json new file mode 100644 index 0000000000000000000000000000000000000000..655d21351f0bab98a23f7eea4a4e70f36d7527de --- /dev/null +++ b/data_zh/goal/consumerfinance_007-g.json @@ -0,0 +1,82 @@ +{ + "task_id": "consumerfinance_014-g", + "domain": "CFPB_COMPLAINT_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "我在撰写一份内部加密货币批次的核心因素逐层分析报告（crypto-complaint sensitivity waterfall memo），需要从 CFPB 投诉数据库中提取四个处于不同过滤状态下的特征月份（Cluster）及其核心数据。\n本次分析的底层投诉数据池（Cohort）具有明确的边界：时间严格限定在 2020-01-01 至 2022-08-26 之间，且仅包含现行产品分类体系下属于“Virtual currency”子类的投诉记录。\n在这个底层数据池的基础上，我需要锁定四个代表着不同“敏感性剥离”状态的特征峰值月：\n• BaselinePeak：该初始投诉池中，整体投诉量最高的绝对峰值月。\n• AfterDominantPublicResponse：在全局数据中，彻底剔除掉“BaselinePeak 月内最主要的 Company public response”相关投诉后，剩余数据池所呈现出的新峰值月。\n• AfterDominantPublicResponseAndIssue：在上一轮的残余数据中，进一步彻底剔除掉“第二轮峰值月内最主要的 Issue”相关投诉后，所形成的第三轮峰值月。\n• AfterDominantPublicResponseIssueAndCompany：在第三轮残余数据中，最终彻底剔除掉“第三轮峰值月内被投诉最多的 Company”相关数据后，沉淀出的最终峰值月。\n针对这四个特征月份，我需要获取它们在各自过滤状态下的数据：该月总投诉量、本轮触发剔除的新增维度（NewExclusionType）及其具体取值（NewExclusionValue）、该剔除值在其“来源峰值月”中出现的频次、该月投诉量排名第一的州及其投诉量、该州内被投诉最多的公司及其投诉量，以及这家头号公司在该州、该特征月内收到的最早一条投诉的详尽信息（编号、日期、Issue 和 Sub-issue）。\n请帮我确认这四个特征月份的身份与数据，并严格按照 BaselinePeak、AfterDominantPublicResponse、AfterDominantPublicResponseAndIssue、AfterDominantPublicResponseIssueAndCompany 的特定顺序，输出四行没有任何空格的格式化字符串。每行的字段序列必须固定为：\n|||||||||||||\n若出现并列，一律按字典序升序选择；日期相同的最早投诉，再按 Complaint ID 数值升序选择。所有空值先统一为 NONE 后再排序。", + "start_url": "https://www.consumerfinance.gov/data-research/consumer-complaints/", + "output_format": "请严格按照 BaselinePeak、AfterDominantPublicResponse、AfterDominantPublicResponseAndIssue、AfterDominantPublicResponseIssueAndCompany 的特定顺序，输出四行没有任何空格的格式化字符串。每行的字段序列必须固定为：|||||||||||||。若出现并列，一律按字典序升序选择；日期相同的最早投诉，再按 Complaint ID 数值升序选择。所有空值先统一为 NONE 后再排序。", + "oracle_answer": "BaselinePeak|2021-05|336|NONE|NONE|0|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,AfterDominantPublicResponse|2022-07|31|Company public response|NONE|321|CA|6|BANK OF AMERICA, NATIONAL ASSOCIATION|4|5735227|2022-07-05|Other transaction problem|NONE,AfterDominantPublicResponseAndIssue|2021-10|13|Issue|Fraud or scam|26|TX|2|BANK OF AMERICA, NATIONAL ASSOCIATION|1|4821611|2021-10-18|Other transaction problem|NONE,AfterDominantPublicResponseIssueAndCompany|2021-06|8|Company|Foris DAX, Inc.|5|NC|3|TRUIST FINANCIAL CORPORATION|2|4462160|2021-06-15|Money was not available when promised|NONE", + "metadata": { + "State-Gated Retrieval": [ + "只看当前 product bucket 下 Virtual currency 子类、接收日期在 2020-01-01 至 2022-08-26 的 Complaint Database 记录。", + "按题目要求依次确定 BaselinePeak、AfterDominantPublicResponse、AfterDominantIssue、AfterDominantCompany 四个阶段的峰值月。", + "每一轮识别出的 dominant Company public response、dominant Issue、dominant Company，都必须回写到对应上游 residual cohort 中整体删除后，再重跑下一轮统计。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current complaint-form taxonomy yields the product bucket for Virtual currency", + "complaint records yield the baseline peak plus the dominant Company public response, dominant Issue, and dominant Company at successive residual-peak states", + "final rows are produced only after each dominant value is applied to the full upstream residual cohort and then used to determine the next peak" + ], + "control_dependency": [ + "dominant values found in a peak month cannot be deleted only inside that month; each must be propagated to the full upstream cohort", + "each new residual peak depends on the prior round's global rewrite, so local month-by-month deletion gives the wrong chain", + "downstream counts and exemplar complaints are valid only after the full three-stage waterfall is executed" + ], + "freeze": { + "historical_window": "Complaint Database records received from 2020-01-01 through 2022-08-26 under the current product-bucket mapping for Virtual currency" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只看当前 product bucket 下 Virtual currency 子类、接收日期在 2020-01-01 至 2022-08-26 的 Complaint Database 记录。", + "按题目要求依次确定 BaselinePeak、AfterDominantPublicResponse、AfterDominantIssue、AfterDominantCompany 四个阶段的峰值月。", + "每一轮识别出的 dominant Company public response、dominant Issue、dominant Company，都必须回写到对应上游 residual cohort 中整体删除后，再重跑下一轮统计。" + ], + "exclusion_conditions": [ + "排除只在当前峰值月局部删记录、没有回写到整个上游 cohort 的结果。", + "排除没有在每一轮 residual cohort 上重新寻找下一峰值月的结果。", + "排除基于未整体重跑 downstream 统计得到的中间或最终字段。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "Cluster", + "Month", + "MonthComplaints", + "NewExclusionType", + "NewExclusionValue", + "NewExclusionCountInSourcePeak", + "TopState", + "StateComplaints", + "TopCompany", + "CompanyComplaints", + "EarliestComplaintID", + "EarliestDate", + "Issue", + "SubIssue" + ], + "cluster_order": [ + "BaselinePeak", + "AfterDominantPublicResponse", + "AfterDominantPublicResponseAndIssue", + "AfterDominantPublicResponseIssueAndCompany" + ], + "date_format": { + "Month": "YYYY-MM", + "EarliestDate": "YYYY-MM-DD" + }, + "NewExclusionType": "emit the canonical exclusion-type label from the source workflow; when no new exclusion is applied, emit `NONE`", + "NewExclusionValue": "emit the canonical excluded value; when no value exists, emit `NONE`", + "TopState": "use the uppercase two-letter state abbreviation", + "TopCompany": "use the company display name as shown in the source data", + "tie_breaks": "normalize empty values to `NONE` before sorting; for other ties use lexicographic order ascending, and for the earliest complaint use EarliestDate ascending then Complaint ID ascending", + "SubIssue": "emit `NONE` when the complaint row has no sub-issue value" + } + } +} diff --git a/data_zh/goal/europemc_001-g.json b/data_zh/goal/europemc_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..14366bf0011ae7161bba748d179bdbc8795eb210 --- /dev/null +++ b/data_zh/goal/europemc_001-g.json @@ -0,0 +1,67 @@ +{ + "task_id": "europemc_001-g", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 21, + "instruction": "我想把这篇 2020 年 COVID‑19 死亡风险预测论文里几套预测方案实际用到的入院变量统一整理成一行，方便看清哪些变量彼此重叠，哪些只出现在对照方案里。\n具体来说，我要找的那篇论文是这样的：2020 年发表的、全文可以免费看到的综述，标题同时包含 prognosis model、mortality risk、COVID‑19，正文讨论的是 Wuhan 的住院患者。\n我要保留的变量包括两部分：一部分是同时进入 Random Forest 和 XGBoost 变量重要性排序的入院变量；另一部分是没有同时进入这两份排序，但出现在作者拿来对照的 CURB‑65 或 NEWS 里的额外入院变量。\n请把每个变量写成下面这个格式：
变量~RF位次或0~XGB位次或0~F~C~N~X\n其中：\n\t•\tRF 表示这个变量在 Random Forest 排序里的名次，没有就写 0；\n\t•\tXGB 表示这个变量在本文用于排序的 XGBoost 排序里的名次，没有就写 0；\n\t•\tF / C / N / X 依次表示这个变量是否进入了作者最后的逻辑回归模型、是否属于 CURB‑65、是否属于 NEWS、以及是否属于文中用来做对照的那套 XGBoost 模型。\n最后，请把所有变量按变量名的字母序排列，并用 | 连接成一行；如果找不到这篇论文，就输出 NONE。", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "请把每个变量写成下面这个格式：
变量~RF位次或0~XGB位次或0~F~C~N~X\n其中：\n\t•\tRF 表示这个变量在 Random Forest 排序里的名次，没有就写 0；\n\t•\tXGB 表示这个变量在本文用于排序的 XGBoost 排序里的名次，没有就写 0；\n\t•\tF / C / N / X 依次表示这个变量是否进入了作者最后的逻辑回归模型、是否属于 CURB‑65、是否属于 NEWS、以及是否属于文中用来做对照的那套 XGBoost 模型。\n最后，请把所有变量按变量名的字母序排列，并用 | 连接成一行；如果找不到这篇论文，就输出 NONE。", + "oracle_answer": "Age~4~2~1~1~0~0|Alanine aminotransferase~17~11~0~0~0~0|Aspartate transaminase~6~4~0~0~0~0|Blood urea nitrogen~5~7~0~1~0~0|Confusion~0~0~0~1~1~0|CRP~2~6~1~0~0~1|Creatinine~9~13~0~0~0~0|Diastolic pressure~16~17~0~1~0~0|Heart rate~15~14~0~0~1~0|LDH~1~1~1~0~0~1|Lymphocyte count~3~5~0~0~0~1|Monocytes~12~16~0~0~0~0|Neutrophil~7~3~0~0~0~0|Normal platelet~10~9~0~0~0~0|Oxygen inhalation~0~0~0~0~1~0|Respiratory rate~11~10~0~1~1~0|SPO2~0~0~0~0~1~0|Systolic pressure~13~12~0~1~1~0|Temperature~18~18~0~0~1~0|Total bilirubin~14~15~0~0~0~0|White blood cell~8~8~0~0~0~0", + "metadata": { + "State-Gated Retrieval": [ + "先找到那篇 2020 年、全文可免费获取、标题同时包含 prognosis model、mortality risk、COVID-19，且正文讨论 Wuhan 住院患者的目标论文。", + "只保留两类变量：同时进入 Random Forest 与 XGBoost 排序的入院变量；或虽未同时进入这两份排序，但属于 CURB-65 或 NEWS 额外变量的对照项。", + "每个变量都要按题目要求标注 RF rank、XGB rank、以及是否属于最终逻辑回归、CURB-65、NEWS、对照 XGBoost，并按变量名字母序输出。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Europe PMC search results and the target open-access article yield the candidate Wuhan COVID mortality-risk review", + "article tables and discussion sections yield RF/XGBoost rankings, final logistic-regression inclusion, and comparator-variable memberships for CURB-65 / NEWS / external XGBoost", + "final rows are produced only after overlapping variables and comparator-only variables are merged into one normalized variable table" + ], + "control_dependency": [ + "comparator-only variables must be captured from the discussion definitions rather than from Table 2 + Table 3 alone", + "comparator membership must be read from the article's explicit scheme definitions rather than inferred from common clinical usage", + "variable normalization must wait until RF/XGBoost overlap and comparator-only additions are both complete" + ], + "freeze": { + "historical_window": "the 2020 open-access COVID-19 mortality-risk review about Wuhan inpatients; variable inclusion and comparator definitions are taken from the article's current full-text tables and discussion" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先找到那篇 2020 年、全文可免费获取、标题同时包含 prognosis model、mortality risk、COVID-19，且正文讨论 Wuhan 住院患者的目标论文。", + "只保留两类变量：同时进入 Random Forest 与 XGBoost 排序的入院变量；或虽未同时进入这两份排序，但属于 CURB-65 或 NEWS 额外变量的对照项。", + "每个变量都要按题目要求标注 RF rank、XGB rank、以及是否属于最终逻辑回归、CURB-65、NEWS、对照 XGBoost，并按变量名字母序输出。" + ], + "exclusion_conditions": [ + "排除没有同时进入 RF 和 XGB、且也不属于 CURB-65 / NEWS 额外变量的入院变量。", + "排除停在 Table 2 + Table 3、不继续到 discussion 读取 comparator 定义的结果。", + "排除凭常识推断 comparator 变量、而不是按论文显式定义核验的结果。" + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "variable", + "RF_rank_or_0", + "XGB_rank_or_0", + "F", + "C", + "N", + "X" + ], + "variable": "use the variable wording normalized in the article tables; keep `Systolic pressure` and `Diastolic pressure` as separate variables", + "rank_fields": "RF_rank_or_0 and XGB_rank_or_0 are positive integer ranks when present, otherwise 0", + "boolean_fields": "F, C, N, and X are emitted as 1 or 0 only", + "sorting_or_selection": "variable name alphabetical ascending", + "stop_condition": [ + "the shared variable set from Table 2 and Table 3 is fully resolved", + "the comparator definitions for CURB-65, NEWS, and the comparison XGBoost model are fixed before the final line is emitted" + ] + } + } +} diff --git a/data_zh/goal/europemc_002-g.json b/data_zh/goal/europemc_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..1a4e60b6f263b755d2555355c1baea67f7197276 --- /dev/null +++ b/data_zh/goal/europemc_002-g.json @@ -0,0 +1,62 @@ +{ + "task_id": "europemc_002-g", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 6, + "instruction": "我想按 ClinicalTrials.gov 编号追踪 2021 年阿尔茨海默病药物研发综述里处于 Phase 1 的研究，看看它们在 2022 和 2023 年同系列综述中是否还能连续找到。\n具体来说，范围只限于 2021 年那篇《Alzheimer's disease drug development pipeline》和 2022、2023 年同系列的全文可以免费获取的综述。我要找的是这样一批研究：它们在 2021 年综述里属于 Phase 1，并且到了 2022 年和 2023 年这两篇同系列综述中，仍然都能用同一个 ClinicalTrials.gov 编号继续找到；这里不能只靠药物名称，因为显示名称可能会变。\n请把所有满足条件的研究整理成一行，格式写成：
NCT号
~2021药名~
2022阶段
~2022药名~
2023阶段~2023药名
按 NCT 号升序排列，并用 | 连接；如果找不到这组三篇论文，就输出 NONE。", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "请把所有满足条件的研究整理成一行，格式写成：
NCT号
~2021药名~
2022阶段
~2022药名~
2023阶段~2023药名
按 NCT 号升序排列，并用 | 连接；如果找不到这组三篇论文，就输出 NONE。", + "oracle_answer": "NCT03277573~Salsalate~P1~Salsalate~P1~Salsalate|NCT03634007~AAVrh.10hAPOE2~P1~LX1001~P2~LX1001|NCT03748303~Allopregnanolone (Allo)~P1~Allopregnanolone~P1~Allopregnanolone|NCT04149860~Lu AF87908~P1~Lu AF87908~P1~Lu AF87908|NCT04451408~LY3372993~P1~LY3372993~P1~LY3372993|NCT04500847~Emtricitabine~P1~Emtricitabine~P1~Emtricitabine", + "metadata": { + "State-Gated Retrieval": [ + "只以 2021 年 Alzheimer's disease drug development pipeline 文章中 Phase 1 的研究作为基线。", + "2022 年和 2023 年是否继续保留，必须按同一个 ClinicalTrials.gov NCT 编号精确匹配，而不是只看药物名。", + "最终只保留在 2022 和 2023 两年里都还能按同一 NCT 找到的研究，并按 NCT 升序输出。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2021, 2022, and 2023 pipeline reviews yield the 2021 Phase 1 baseline cohort and the later-year lookup tables", + "article tables yield exact ClinicalTrials.gov NCT IDs, yearly phase labels, and yearly drug names for the same study", + "final rows are produced only after 2021 baseline studies are re-identified in both later reviews by exact NCT matching" + ], + "control_dependency": [ + "continuation must be matched by exact NCT rather than by drug name, because drug names drift across years", + "2022 and 2023 lookups must use the fixed 2021 Phase 1 NCT set as the starting cohort rather than later-year table membership alone", + "yearly phase/name fields are only valid after the same NCT is confirmed across all three reviews" + ], + "freeze": { + "historical_window": "the 2021, 2022, and 2023 open-access Alzheimer's disease drug development pipeline reviews; the baseline is the 2021 Phase 1 cohort and continuation is matched by exact ClinicalTrials.gov NCT" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只以 2021 年 Alzheimer's disease drug development pipeline 文章中 Phase 1 的研究作为基线。", + "2022 年和 2023 年是否继续保留，必须按同一个 ClinicalTrials.gov NCT 编号精确匹配，而不是只看药物名。", + "最终只保留在 2022 和 2023 两年里都还能按同一 NCT 找到的研究，并按 NCT 升序输出。" + ], + "exclusion_conditions": [ + "排除只凭药物名称延续、没有按同一 ClinicalTrials.gov 编号精确匹配的结果。", + "排除只在 2022 或只在 2023 中找到、未同时连续保留的研究。", + "排除不属于 2021 基线 Phase 1 集合的研究。" + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "NCT", + "agent_2021", + "phase_2022", + "agent_2022", + "phase_2023", + "agent_2023" + ], + "NCT": "use the exact ClinicalTrials.gov identifier as the cross-year identity key", + "phase_fields": "normalize phases to P1, P2, or P3; if the same NCT appears multiple times in a year, keep the highest phase for that year", + "agent_fields": "keep the agent text as shown in each year-specific table", + "sorting_or_selection": "NCT ascending" + } + } +} diff --git a/data_zh/goal/europemc_003-g.json b/data_zh/goal/europemc_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..22b897cca4af1c4584f6b1a5cef063ed550773d9 --- /dev/null +++ b/data_zh/goal/europemc_003-g.json @@ -0,0 +1,63 @@ +{ + "task_id": "europemc_003-g", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "我想看看 2023 年《Antibodies to Watch》里被预测会在 2022–2023 提交首次上市申请的那批候选分子，在 2024 年同系列文章里哪些真的已经获批或进入了首次监管审评。\n具体来说，范围只限于 Europe PMC 中 2023 和 2024 两篇同系列的《Antibodies to Watch》开放获取的全文。我要保留的是这样一批分子：它们在 2023 年那篇文章里被列为**\"预计会在 2022–2023 提交首次上市申请\"**，并且到了 2024 年那篇文章里，已经获批，或已进入首次监管审评。\n请把每个符合条件的分子写成：
INN~2023类别~2023预测标签~2024状态~2024适应证~2024地区\n其中：\n\t•\t2023类别 用 NC/CA 表示 非癌症 / 癌症；\n\t•\t2024状态 用 A/R 表示 首次获批 / 首次监管审评中。\n最后请按 INN 字母序排列，并用 | 连接成一行输出；如果找不到这两篇论文，就输出 NONE。", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "请把每个符合条件的分子写成：
INN~2023类别~2023预测标签~2024状态~2024适应证~2024地区\n其中：\n\t•\t2023类别 用 NC/CA 表示 非癌症 / 癌症；\n\t•\t2024状态 用 A/R 表示 首次获批 / 首次监管审评中。\n最后请按 INN 字母序排列，并用 | 连接成一行输出；如果找不到这两篇论文，就输出 NONE。", + "oracle_answer": "Cosibelimab~CA~MAA,Q2 2023~R~Squamous cell carcinoma~US|Elranatamab~CA~2023~A~Multiple myeloma~US,EU,Switzerland,Brazil|Garadacimab~NC~BLA,2023~R~Hereditary angioedema~EU|Odronextamab~CA~BLA,H2 2022~R~Diffuse large B-cell lymphoma~US,EU|Pozelimab~NC~BLA,H2 2022~A~CHAPLE disease~US|Suciraslimab~NC~NDA,2023~R~Rheumatoid arthritis~China|Talquetamab~CA~2023–25~A~Multiple myeloma~US,EU,UK,Switzerland|Zolbetuximab~CA~BLA,2023~R~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China", + "metadata": { + "State-Gated Retrieval": [ + "先在 2023 年 Antibodies to Watch 中找出所有被预测会在 2022-2023 提交首次上市申请的候选分子。", + "再在 2024 年同系列文章里逐一核对这些分子，只保留已经首次获批，或已进入首次监管审评的候选。", + "2024 状态必须区分 A=首次获批 与 R=首次监管审评中，并补充 2024 适应证和地区。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2023 Antibodies to Watch article yields the forecast baseline of candidates expected to file in 2022-2023", + "the 2024 article tables yield first-approval outcomes, first-regulatory-review outcomes, indications, and regions for the same INNs", + "final rows are produced only after Table 1 approvals and Table 2 first-review candidates are merged back onto the 2023 forecast cohort" + ], + "control_dependency": [ + "both 2024 Table 1 and Table 2 must be read so that first-review-but-not-yet-approved candidates are retained", + "2024 status coding must distinguish approval from first regulatory review instead of collapsing both into a single positive match", + "region and indication fields are valid only after the 2023 forecast cohort is reconciled against both 2024 tables" + ], + "freeze": { + "historical_window": "the 2023 and 2024 open-access Antibodies to Watch articles; baseline candidates come from the 2023 forecast set and 2024 outcomes come from current Table 1 plus Table 2" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先在 2023 年 Antibodies to Watch 中找出所有被预测会在 2022-2023 提交首次上市申请的候选分子。", + "再在 2024 年同系列文章里逐一核对这些分子，只保留已经首次获批，或已进入首次监管审评的候选。", + "2024 状态必须区分 A=首次获批 与 R=首次监管审评中，并补充 2024 适应证和地区。" + ], + "exclusion_conditions": [ + "排除只在 2024 Table 1 中查 approvals、不继续到 Table 2 补 first regulatory review 候选的结果。", + "排除不在 2023 forecast baseline 中的分子。", + "排除 2024 年既未首次获批、也未进入首次监管审评的候选。" + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "INN", + "category_2023", + "prediction_label_2023", + "status_2024", + "indication_2024", + "region_2024" + ], + "category_2023": "emit `NC` or `CA` exactly", + "prediction_label_2023": "keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H2 2022`", + "status_2024": "emit `A` for first approval and `R` for first regulatory review", + "region_2024": "preserve the raw region string but remove spaces after commas, for example `US,EU`", + "sorting_or_selection": "INN alphabetical ascending" + } + } +} diff --git a/data_zh/goal/europemc_004-g.json b/data_zh/goal/europemc_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..df66653c194c96c44e7f00c1b6dae8fb01b88b07 --- /dev/null +++ b/data_zh/goal/europemc_004-g.json @@ -0,0 +1,67 @@ +{ + "task_id": "europemc_004-g", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 9, + "instruction": "我正在评估抗体年度 watchlist 预测的准确性，需要基于 Europe PMC 数据库，找出一批进度明显滞后的候选抗体（INN），并提取出它们这三年来的状态变化。\n这批目标抗体的特殊之处在于，它们的动态连续被 2022、2023 和 2024 年的三篇《Antibodies to Watch》系列开放获取（Open Access）全文所记录。具体来说，它们在 2022 年的文章里原本已经被列入了“预计即将提交审评”的名单，但由于进度延期，到了 2023 年的文章中，它们依然作为候选者留在了当年的 watchlist 里。筛选时以候选抗体实体为单位，而不是仅按名称字符串精确匹配；若 2022 年文章使用药物代码、项目名或其他可识别名称，且 2023 或 2024 年文章明确给出其与某 INN 的对应关系，则应视为同一候选实体，并在最终结果中统一使用可确认的 INN 输出。\n对于这些连续延期的候选抗体，我需要确认它们在 2024 年那篇文章里的最终状态：是终于获得了首次批准（First approved）、正处于首次审评阶段（In first regulatory review）、继续留在后续的 watchlist 中，还是已经从 2024 年的主文名单里彻底消失了。\n请协助我锁定这批抗体，并将提取到的各维度参数严格按 INN 的字母顺序，用 | 拼接成一行字符串输出（若在数据库中未能找齐这三篇目标文章，请直接输出 NONE）。每一个抗体的内部字段拼接顺序必须固定为：INN~2022类别~2022阶段~2023预测标签~2024状态~2024阶段或NA~2024适应证或NA~2024地区或NA。输出中分隔符两侧不得添加额外空格，但字段内部的原文空格应保留；2022类别统一使用 CA/NC，阶段统一使用 P2/P3，2024状态统一使用 A/R/F/D，分别表示 First approved、In first regulatory review、后续 watchlist、2024 主文名单消失。", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "将提取到的各维度参数严格按 INN 的字母顺序，用 | 拼接成一行字符串输出（若在数据库中未能找齐这三篇目标文章，请直接输出 NONE）。每一个抗体的内部字段拼接顺序必须固定为：INN~2022类别~2022阶段~2023预测标签~2024状态~2024阶段或NA~2024适应证或NA~2024地区或NA。输出中分隔符两侧不得添加额外空格，但字段内部的原文空格应保留；2022类别统一使用 CA/NC，阶段统一使用 P2/P3，2024状态统一使用 A/R/F/D，分别表示 First approved、In first regulatory review、后续 watchlist、2024 主文名单消失。", + "oracle_answer": "Apamistamab-I-131~CA~P3~BLA,H1 2023~F~P3~Ablation of bone marrow prior to transplantation in AML patients~NA|Bentracimab~NC~P3~BLA,Q4 2022~F~P3~Reversal of the antiplatelet effects of ticagrelor~NA|Cosibelimab~CA~P3~MAA,Q2 2023~R~NA~Squamous cell carcinoma~US|Erfonrilimab~CA~P3~NDA~F~P3~Pancreatic ductal adenocarcinoma~NA|Odronextamab~CA~P2~BLA,H2 2022~R~NA~Diffuse large B-cell lymphoma~US,EU|Talquetamab~CA~P2~2023-25~A~NA~Multiple myeloma~US,EU,UK,Switzerland|Tiragolumab~CA~P3~2023~F~P3~NSCLC~NA|Zanidatamab~CA~P2~2023~D~NA~NA~NA|Zolbetuximab~CA~P3~BLA,2023~R~NA~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China", + "metadata": { + "State-Gated Retrieval": [ + "先以 2022 年 Antibodies to Watch 中“预计即将提交审评”的候选为基线，但只保留在 2023 年同系列中仍然作为 watchlist 候选保留的分子。", + "对这批连续延期候选，再到 2024 年文章中确定其最终状态：首次获批、首次审评中，或在 Tables 1-4 中完全缺席。", + "名称比对时必须处理 Apamistamab 的命名漂移；2024 完全缺席必须显式编码为 D。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2022, 2023, and 2024 Antibodies to Watch articles yield the 2022 soon-to-file baseline, 2023 carry-over membership, and 2024 status tables", + "article tables and full-text naming context yield name normalizations, 2024 table presence/absence, and final status labels for each carried-over INN", + "final rows are produced only after 2022 candidates are filtered by 2023 carry-over status and then resolved against 2024 Tables 1-4 plus explicit absence" + ], + "control_dependency": [ + "2022 candidates must first be filtered by 2023 carry-over status before they are matched against the 2024 tables", + "Apamistamab naming drift forces explicit normalization before 2024 lookup", + "complete 2024 absence must be emitted as D rather than treated as a lookup failure" + ], + "freeze": { + "historical_window": "the 2022, 2023, and 2024 open-access Antibodies to Watch articles; the 2022 baseline is filtered by 2023 carry-over status and then checked against 2024 Tables 1-4, with explicit absence retained as a status" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先以 2022 年 Antibodies to Watch 中“预计即将提交审评”的候选为基线，但只保留在 2023 年同系列中仍然作为 watchlist 候选保留的分子。", + "对这批连续延期候选，再到 2024 年文章中确定其最终状态：首次获批、首次审评中，或在 Tables 1-4 中完全缺席。", + "名称比对时必须处理 Apamistamab 的命名漂移；2024 完全缺席必须显式编码为 D。" + ], + "exclusion_conditions": [ + "排除直接拿 2022 基线去 2024 做字面匹配、未经过 2023 carry-over 过滤的结果。", + "排除未处理 Apamistamab 命名漂移的匹配结果。", + "排除把 2024 完全缺席当成查找失败，而不是一个需要输出的状态。" + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "INN", + "category_2022", + "phase_2022", + "prediction_label_2023", + "status_2024", + "phase_or_NA_2024", + "indication_or_NA_2024", + "region_or_NA_2024" + ], + "category_2022": "emit `NC` or `CA` exactly", + "phase_2022": "normalize stage labels such as `Phase 3` to `P3` and `Pivotal Phase 2` to `P2`", + "prediction_label_2023": "keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H1 2023`", + "status_2024": "emit one of `A`, `R`, `F`, or `D` exactly", + "conditional_fields_2024": "if status is A or R, phase_or_NA_2024 must be `NA` and region_or_NA_2024 must carry the raw region string; if status is F, region_or_NA_2024 is `NA` and phase_or_NA_2024 carries the normalized phase; if status is D, all three trailing 2024 fields are `NA`", + "naming_exception": "preserve the fixed source exception around the Apamistamab-I-131 naming variant instead of over-normalizing the INN", + "sorting_or_selection": "INN alphabetical ascending" + } + } +} diff --git a/data_zh/goal/europemc_005-g.json b/data_zh/goal/europemc_005-g.json new file mode 100644 index 0000000000000000000000000000000000000000..cf1c18402168ff0bfdb7dd407be72a65a646ab1a --- /dev/null +++ b/data_zh/goal/europemc_005-g.json @@ -0,0 +1,69 @@ +{ + "task_id": "europemc_005-g", + "domain": "EUROPEPMC_PMC", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 20, + "instruction": "我正在整理一份关于 COVID‑19 住院患者病情走向预测指标的跨平台梳理。这项任务的核心依据是一篇 2024 年发表的 WHO 全球个体患者数据验证论文，以及它所关联的 3 篇原始模型论文。在这篇 2024 年的验证论文中，共有 4 个预后模型最终真正在低中收入国家的数据里完成了外部验证。我们需要查清这 4 个模型在实际评估中分别用到了哪些不同的入院变量。\n对于梳理出来的每一个入院变量，都需要查清它在实际应用中的各项特征：首先是它在 WHO 平台基线表里的匹配难度，即是可以直接实质同名匹配，还是必须经过固定映射才能对上；其次是它的来源背景，即它是否归属于验证中表现最强的模型、校准度最接近理想值的模型，或者是否来自明确使用了动态数据的原始模型。\n为保证口径一致，模型缩写、性能归属、动态数据属性和变量冲突均以目标文献中可复核的模型描述、汇总性能结果、方法说明和字段定义为准；若存在变量命名或映射差异，以能保持跨模型解释一致性的保守对应关系进行标记。\n如果能在数据库里找齐这 1 篇验证论文和 3 篇原始模型论文，你能否将提取到的所有变量信息整理好，并严格按照变量名字母顺序用 | 拼接成一行没有任何空格的字符串输出给我（如果找不到这 4 篇文章请直接输出 NONE）？\n排版要求： 每个变量的内部信息请固定写成 变量~类别~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict的格式。其中，布尔状态请用 1 表示是、0 表示否；WHO 基线表的匹配情况请用 E 表示直接/实质同名可取，M 表示需要固定映射。", + "start_url": "https://europepmc.org/advancesearch", + "output_format": "如果能在数据库里找齐这 1 篇验证论文和 3 篇原始模型论文，请将提取到的所有变量信息整理好，并严格按照变量名字母顺序用 | 拼接成一行没有任何空格的字符串输出；如果找不到这 4 篇文章请直接输出 NONE。每个变量的内部信息请固定写成 变量~类别~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict的格式。其中，布尔状态请用 1 表示是、0 表示否；WHO 基线表的匹配情况请用 E 表示直接/实质同名可取，M 表示需要固定映射。", + "oracle_answer": "Age~DEM~1~1~1~1~Age~E~1~1~1~0|Cancer~COM~0~0~1~0~Cancer~E~1~0~0~0|Chronic kidney disease~COM~0~0~0~1~CKD~M~0~0~0~1|Chronic lung disease~COM~0~0~1~0~Pulmonary disease~M~1~0~0~0|Chronic renal disease~COM~0~0~1~0~CKD~M~1~0~0~1|Coronary heart disease~COM~0~1~0~0~CHD~M~0~0~0~1|Cough~SYM~0~0~1~0~Cough~E~1~0~0~0|Diabetes mellitus~COM~0~0~1~0~Diabetes~M~1~0~0~0|Diarrhea~SYM~0~0~1~0~Diarrhea~E~1~0~0~0|Dyspnea~SYM~0~0~1~0~Dyspnea~E~1~0~0~0|Fever~VIT~0~0~0~1~Body temperature~M~0~0~0~0|Heart disease~COM~0~0~1~0~CHD~M~1~0~0~1|Hypertension~COM~0~1~1~0~Hypertension~E~1~0~0~0|Immunocompromised status~COM~0~0~1~0~Immunosuppression~M~1~0~0~0|O2 saturation~VIT~1~0~0~0~Oxygen saturation~M~0~1~1~0|Respiratory rate~VIT~1~0~0~1~Respiratory rate~E~0~1~1~0|Sex~DEM~0~0~1~0~Men~M~1~0~0~0|Smoking~DEM~1~0~0~0~Smoking~E~0~1~1~1|Smoking status~DEM~0~0~0~1~Smoking~M~0~0~0~1|Systolic blood pressure~VIT~0~0~0~1~Systolic blood pressure~E~0~0~0~0", + "metadata": { + "State-Gated Retrieval": [ + "先在 2024 WHO 全球个体患者数据验证论文中锁定最终在 LMIC 数据中成功完成外部验证的 4 个预后模型，并追溯到对应的 3 篇原始模型论文。", + "对每个 predictor，要保留 WHO Table 1 的原始 wording，并标注它在 WHO 基线表中的匹配方式 E/M，以及是否来自 TopAUC、BestCal、Dyn 模型。", + "遇到 WHO 侧概念合并的 predictor 时，必须回溯 Wang / Zhou 等原始论文拆分后再重算相关字段。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the 2024 WHO global validation paper yields the four externally validated models and the WHO-side predictor wording/mapping baseline", + "the three original model papers yield model-specific predictor wordings, dynamic-data flags, and conflicts hidden by WHO-side conceptual merging", + "final rows are produced only after WHO predictors are kept separate, traced back to the original papers, and then re-annotated for mapping and model provenance" + ], + "control_dependency": [ + "conceptually merged WHO predictors must be split back out when the original Wang/Zhou papers expose distinct variables", + "Table 2 mapping decisions are not valid until Table 1 wording and original-paper predictor sets are reconciled", + "TopAUC / BestCal / Dyn flags must be determined after the predictor split is applied correctly" + ], + "freeze": { + "historical_window": "the 2024 WHO global IPD validation paper and the three linked original COVID prognosis-model papers, using their current open-access full texts and tables" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先在 2024 WHO 全球个体患者数据验证论文中锁定最终在 LMIC 数据中成功完成外部验证的 4 个预后模型，并追溯到对应的 3 篇原始模型论文。", + "对每个 predictor，要保留 WHO Table 1 的原始 wording，并标注它在 WHO 基线表中的匹配方式 E/M，以及是否来自 TopAUC、BestCal、Dyn 模型。", + "遇到 WHO 侧概念合并的 predictor 时，必须回溯 Wang / Zhou 等原始论文拆分后再重算相关字段。" + ], + "exclusion_conditions": [ + "排除在 WHO Table 1 之后就把概念相近 predictor 直接合并、未回溯原始论文拆分的结果。", + "排除只凭 WHO Table 2 做宽松映射、未结合原始论文 wording 的结果。", + "排除在 predictor 拆分修正前就固定 TopAUC / BestCal / Dyn 标注的结果。" + ], + "normalization": { + "field_separator": "~", + "record_separator": "|", + "schema": [ + "variable", + "category", + "B", + "W", + "Zh", + "Zo", + "WHOfield", + "WHOx", + "TopAUC", + "BestCal", + "Dyn", + "Conflict" + ], + "variable_set": "the candidate variable set comes only from the WHO validation Table 1 and remains at the original 20 predictors", + "conflict_groups": "do not pre-merge the three source conflict groups `Smoking`/`Smoking status`, `Chronic renal disease`/`Chronic kidney disease`, and `Coronary heart disease`/`Heart disease` before applying the conflict flag", + "boolean_fields": "B, W, Zh, Zo, TopAUC, BestCal, Dyn, and Conflict are emitted as 1 or 0 only", + "WHOx": "emit `E` for exact or substantively same-name WHO matches, `M` for the fixed mapped match, and `NA` when no WHO field matches", + "sorting_or_selection": "variable name alphabetical ascending" + } + } +} diff --git a/data_zh/goal/genome_001-g.json b/data_zh/goal/genome_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..cf282aeef15d27d5cca3f743101bd1746ab3deb1 --- /dev/null +++ b/data_zh/goal/genome_001-g.json @@ -0,0 +1,64 @@ +{ + "task_id": "genome_001-g", + "domain": "KEGG_BRITE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "我想从 KEGG 中筛选出用于溃疡性结肠炎、截至 2025 年 6 月底已在日本获批，且带有明确细胞色素 P450（CYP）代谢或抑制提示的免疫抑制剂。对每个符合条件的药物，请保留其日本治疗分类代码、ATC 码、对应的靶点支系和日本首次批准日期。请按日本首次批准日期从早到晚输出一行字符串，格式为 ||||；多个条目之间用英文逗号分隔；如无符合条件的结果，输出 NONE。", + "start_url": "https://www.genome.jp/kegg/brite.html", + "output_format": "请按日本首次批准日期从早到晚输出一行字符串，格式为 ||||；多个条目之间用英文逗号分隔；如无符合条件的结果，输出 NONE。", + "oracle_answer": "D09783|3999|L04AF01|JAK1/JAK2/JAK3/TYK2|2013/3/25,D11048|3999|L04AF03|JAK1|2020/1/23,D10931|2399|L04AE05|S1PR1/S1PR4/S1PR5|2025/6/24", + "metadata": { + "State-Gated Retrieval": [ + "以 KEGG 中用于溃疡性结肠炎的免疫抑制剂为范围，只保留截至 2025-06-30 已在日本获批、且带有明确 CYP 相关代谢信息或 CYP 抑制提示的条目。", + "候选药物必须在纠正后的 UC drug list 中重新核验日本治疗分类、ATC、靶点支系、CYP 证据和日本首次批准日期。", + "最终按日本首次获批日期从早到晚输出。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "KEGG disease H01466 and linked drug entries yield the ulcerative-colitis immunosuppressant candidate set", + "each candidate drug entry yields Japanese class, ATC, target branch, CYP metabolism/inhibition evidence, and Japan approval date", + "final rows are produced only after the full UC candidate set is determined and every candidate is checked against CYP evidence and PMDA timing" + ], + "control_dependency": [ + "the candidate set must include Japanese class 3999 UC drugs when the disease page exposes them rather than being limited to 2399 alone", + "target / CYP / PMDA validation must be applied across the full candidate set rather than only the old 2399 subset", + "entries without explicit CYP evidence may be dropped only after the full candidate set has been established" + ], + "freeze": { + "historical_window": "KEGG ulcerative-colitis drug entries as objectively existing drug entities, using target, CYP, Japan-class, and related entry metadata as relatively stable annotations" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "以 KEGG 中用于溃疡性结肠炎的免疫抑制剂为范围，只保留截至 2025-06-30 已在日本获批、且带有明确 CYP 相关代谢信息或 CYP 抑制提示的条目。", + "候选药物必须在纠正后的 UC drug list 中重新核验日本治疗分类、ATC、靶点支系、CYP 证据和日本首次批准日期。", + "最终按日本首次获批日期从早到晚输出。" + ], + "exclusion_conditions": [ + "排除把上游范围错误锁在 2399 消化器分支、未回退到完整 UC drug list 的结果。", + "排除没有明确 CYP 相关代谢信息或 CYP 抑制提示的条目。", + "排除日本获批日期晚于 2025-06-30 或不属于 KEGG UC 免疫抑制剂范围的条目。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "DRUG_ID", + "JP_class", + "ATC", + "Target_branch", + "JP_date" + ], + "dedup_key": "DRUG_ID", + "JP_date": "use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value", + "Target_branch": "emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`", + "sorting_or_selection": { + "primary": "JP_date ascending", + "secondary": "DRUG_ID ascending" + } + } + } +} diff --git a/data_zh/goal/genome_002-g.json b/data_zh/goal/genome_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..9bbff4fc70085ce2893e86937b25bf023b78e57d --- /dev/null +++ b/data_zh/goal/genome_002-g.json @@ -0,0 +1,65 @@ +{ + "task_id": "genome_002-g", + "domain": "KEGG_GENOME", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我想在 KEGG 提供的宿主—共生体示例中，找出其细菌共生体 KEGG GENOME 条目截至 2005 年底前已收录、且细菌共生体基因组包含明确命名的额外复制子的动物内共生案例。该案例还需满足：这些复制子名称能够在宿主—共生体联合通路图中，直接对应到氨基酸生物合成模块。请列出该案例中所有满足条件的通路—模块组合，并按 ||||| 的格式输出一行字符串；按 pathway 编号升序排列，条目之间用英文逗号分隔；如无符合条件的结果，输出 NONE。如涉及物种标识，请使用 KEGG organism code。", + "start_url": "https://www.genome.jp/kegg/genome/", + "output_format": "请按 ||||| 的格式输出一行字符串；按 pathway 编号升序排列，条目之间用英文逗号分隔；如无符合条件的结果，输出 NONE。如涉及物种标识，请使用 KEGG organism code。", + "oracle_answer": "api+buc|buc|00290|M00432|pLeu|2000,api+buc|buc|00400|M00023|pTrp|2000", + "metadata": { + "State-Gated Retrieval": [ + "只保留宿主—共生体示例中，细菌共生体 KEGG GENOME Created 年份不晚于 2005 年底、且其基因组带有已命名额外复制子的案例。", + "这些复制子的名称必须能在宿主—共生体联合 pathway 页面上直接对应到氨基酸合成模块。", + "最终输出 surviving 案例中所有符合条件的 pathway-module-replicon 记录，并按 pathway 编号升序排列。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "KEGG host-symbiont examples and symbiont genome pages yield the pre-2006 candidate pairs and named extra replicons", + "joint pathway maps, module pages, and genome annotations yield the pathway-module-replicon links attributable to the symbiont side", + "final rows are produced only after the surviving host-symbiont pair is validated against both replicon existence and module support on the joint pathway page" + ], + "control_dependency": [ + "only branches satisfying the named-plasmid requirement may be retained, so the bmy+wbm branch must be excluded when the wbm genome page fails that requirement", + "module retrieval must use the api+buc pathway state and the 00400 view, because that view is the one that actually exposes M00023", + "module support is valid only after symbiont-side evidence for both M00023 and M00432 is validated in the selected pathway state" + ], + "freeze": { + "historical_window": "KEGG host-symbiont examples as objectively existing biological entities, using joint pathway, module, and genome replicon annotations as relatively stable structural information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只保留宿主—共生体示例中，细菌共生体 KEGG GENOME Created 年份不晚于 2005 年底、且其基因组带有已命名额外复制子的案例。", + "这些复制子的名称必须能在宿主—共生体联合 pathway 页面上直接对应到氨基酸合成模块。", + "最终输出 surviving 案例中所有符合条件的 pathway-module-replicon 记录，并按 pathway 编号升序排列。" + ], + "exclusion_conditions": [ + "排除像 bmy+wbm 这样共生体 genome 页并没有满足命名 plasmid 要求的案例。", + "排除只按 pathway 名称沿 00380 等页面追查、没有回到联合 pathway 面核验 module 证据的结果。", + "排除复制子名称与模块关系不能在联合 pathway 图上直接成立的记录。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema": [ + "group", + "symbiont", + "pathway", + "module", + "replicon", + "created_year" + ], + "group": "use the canonical host-symbiont group label from the source workflow, such as `api+buc`", + "symbiont": "use the bare lowercase KEGG organism code", + "pathway": "emit the numeric KEGG pathway ID without a `map` prefix", + "module": "normalize the KEGG module identifier to the `Mxxxxx` form", + "replicon": "preserve the named extra replicon exactly as displayed in the source, such as `pLeu` or `pTrp`", + "created_year": "emit the four-digit created year", + "sorting_or_selection": "pathway numeric ascending" + } + } +} diff --git a/data_zh/goal/genome_003-g.json b/data_zh/goal/genome_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..9347f84d35e68961bf6b62a0629000e2a05aef55 --- /dev/null +++ b/data_zh/goal/genome_003-g.json @@ -0,0 +1,64 @@ +{ + "task_id": "genome_004-g", + "domain": "KEGG_BRITE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "我在整理一张日本斑块状银屑病系统用药获批顺序表。请仅纳入截至 2024 年底前已在日本获批、用于斑块状银屑病系统治疗且靶向 IL‑17/IL‑23 信号轴的活性成分；外用药以及其他作用轴的系统用药均不纳入。请按日本首次批准日期从早到晚输出多行表；如同日获批，按 DRUG_ID 升序。每行格式为 ||||。", + "start_url": "https://www.kegg.jp/brite/br08301", + "output_format": "请按日本首次批准日期从早到晚输出多行表；如同日获批，按 DRUG_ID 升序。每行格式为 ||||。", + "oracle_answer": "D09967|Secukinumab|L04AC10|IL17A|2014/12/26\nD10061|Brodalumab|L04AC12|IL17RA|2016/7/4\nD10071|Ixekizumab|L04AC13|IL17A|2016/7/4\nD10438|Guselkumab|L04AC16|IL23A|2018/3/23\nD11052|Risankizumab|L04AC18|IL23A|2019/3/26\nD10400|Tildrakizumab|L04AC17|IL23A|2020/6/29\nD11550|Bimekizumab|L04AC21|IL17A/IL17F|2022/1/20\nD11817|Deucravacitinib|L04AF07|TYK2|2022/9/26", + "metadata": { + "State-Gated Retrieval": [ + "只保留截至 2024-12-31 前已在日本获批、用于斑块状银屑病的系统用药中，真正作用于 IL-17/IL-23 信号轴的活性成分。", + "候选集合必须覆盖 ligand side、receptor side 和 TYK2 kinase side，而不是只看 interleukin ligand 一侧。", + "最终条目按日本首次批准日期升序排列；如同日则按 DRUG_ID 升序。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "KEGG disease/drug entry points yield the Japan-approved systemic plaque-psoriasis drug cohort through 2024-12-31", + "each drug entry yields target branch, ATC, systemic-use validity, and Japan approval date for IL-17/IL-23-axis candidates", + "final rows are produced only after ligand-side, receptor-side, and kinase-side candidates are jointly reconciled and re-sorted by Japan approval date" + ], + "control_dependency": [ + "entry-point coverage must include receptor-side IL17RA and kinase-side TYK2 mechanisms when downstream drug pages expose them, rather than staying ligand-only", + "Ustekinumab must be removed only when target interpretation shows IL12 + IL23A rather than the IL-17/IL-23-axis criterion required here", + "systemic-use, Japanese 3999, and PMDA-date filtering must be applied after each candidate-space expansion rather than attached to the earlier ligand-only state" + ], + "freeze": { + "historical_window": "KEGG plaque-psoriasis systemic-drug entries as objectively existing drug entities, using target-branch and related drug-entry metadata as relatively stable annotations" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只保留截至 2024-12-31 前已在日本获批、用于斑块状银屑病的系统用药中，真正作用于 IL-17/IL-23 信号轴的活性成分。", + "候选集合必须覆盖 ligand side、receptor side 和 TYK2 kinase side，而不是只看 interleukin ligand 一侧。", + "最终条目按日本首次批准日期升序排列；如同日则按 DRUG_ID 升序。" + ], + "exclusion_conditions": [ + "排除外用药、非系统用药或不在指定历史冻结窗口内的条目。", + "排除 Ustekinumab 这类实际暴露为 IL12 + IL23A、但不满足本题 IL-17/IL-23 轴口径的条目。", + "排除因为只看 ligand side 而漏掉 Brodalumab 或 Deucravacitinib 的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "DRUG_ID", + "Name", + "ATC", + "Target_branch", + "PMDA_date" + ], + "PMDA_date": "use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value", + "Target_branch": "emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`", + "sorting_or_selection": { + "primary": "PMDA_date ascending", + "secondary": "DRUG_ID ascending" + } + } + } +} diff --git a/data_zh/goal/genome_004-g.json b/data_zh/goal/genome_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..0f745f86cb1dffb881da38833e85b64f8335bd92 --- /dev/null +++ b/data_zh/goal/genome_004-g.json @@ -0,0 +1,78 @@ +{ + "task_id": "genome_004-g", + "domain": "KEGG_GENOME", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我正在为灵长类进化课程准备讲义，想把这个维生素 C 代谢例外模式整理成一张两行对照表。请输出两行表，列为 rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year。第一行为 EXCEPTION_CLADE，第二行为 RETAINED_SISTER_CLADE；示例物种请使用 KEGG organism code。", + "start_url": "https://www.genome.jp/kegg/kegg2.html", + "output_format": "请输出两行对照表，列为 rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year。", + "oracle_answer": "1|EXCEPTION_CLADE|Primates|Haplorrhini|map00053|map00040|M00014|M00129|LOST|csyr|2022\n2|RETAINED_SISTER_CLADE|Primates|Strepsirrhini|map00053|map00040|M00014|M00129|RETAINED|oga|2022", + "metadata": { + "State-Gated Retrieval": [ + "只在截至 2022 年底已建立的灵长类基因组条目中筛选：保留上游糖醛酸模块 M00014、但缺失动物型维生素 C 合成模块 M00129 的异常下一级类群。", + "该异常类群必须能在同一上一级分裂下找到可对照的姐妹分支，且该姐妹分支仍保留 M00129。", + "最终输出要把异常分支和保留姐妹分支并排整理成两行对照表，并给出路径、模块与示例物种字段。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "KEGG primate clade pages and genome entries yield candidate subclades and example species established through the cutoff year", + "pathway and module views yield M00014 and M00129 presence/absence evidence for the exception clade and its sister branch", + "final rows are produced only after the exception clade and retained sister are jointly validated under the same parent split and paired with example organisms" + ], + "control_dependency": [ + "the exception clade remains provisional until both the sister-branch contrast and the example-species checks succeed", + "the comparison pathway must make both retained M00014 and missing M00129 visible in the same view", + "the two output rows are emitted together only after the exception clade and retained sister branch are fixed under the same parent split" + ], + "freeze": { + "historical_window": "the objectively existing primate genome entries established on or before 2022, using current KEGG clade, pathway, and module pages as relatively stable reference information for comparing retained M00014 against lost M00129" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在截至 2022 年底已建立的灵长类基因组条目中筛选：上游糖醛酸模块 M00014 仍保留、但动物型维生素 C 合成模块 M00129 缺失的异常下一级类群。", + "该异常类群必须存在可对照的姐妹分支，且该姐妹分支仍保留 M00129。", + "最终输出必须把异常分支和保留姐妹分支并排整理成两行对照表，并给出路径、模块与示例物种字段。" + ], + "exclusion_conditions": [ + "排除停在 Simiiformes、没有继续检查更外层边界而漏掉 Haplorrhini 的结果。", + "排除使用不能同时展示 M00014 与 M00129 差异的 pathway 视图。", + "排除没有完成姐妹分支保留对照验证的候选类群。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "clade_role", + "parent_clade", + "clade", + "anomaly_pathway", + "contrast_pathway", + "retained_upstream_module", + "vitamin_c_synthesis_module", + "vitamin_c_module_status", + "example_org", + "cutoff_year" + ], + "rank": "emit 1 for EXCEPTION_CLADE and 2 for RETAINED_SISTER_CLADE", + "clade_role": [ + "EXCEPTION_CLADE", + "RETAINED_SISTER_CLADE" + ], + "pathway_normalization": "emit KEGG pathway ids with the map prefix", + "module_normalization": "emit KEGG module ids with the leading M", + "vitamin_c_module_status": [ + "LOST", + "RETAINED" + ], + "organism_code": "use bare KEGG organism codes in lowercase, not species names", + "cutoff_year": "use a four-digit year; this task is frozen at 2022", + "sorting_or_selection": "emit rows in the fixed order EXCEPTION_CLADE then RETAINED_SISTER_CLADE" + } + } +} diff --git a/data_zh/goal/nvd_001-g.json b/data_zh/goal/nvd_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..ba5d162595c5cd1c48ae0119c7aee7d901ffa5a2 --- /dev/null +++ b/data_zh/goal/nvd_001-g.json @@ -0,0 +1,66 @@ +{ + "task_id": "nvd_001-g", + "domain": "NVD", + "autonomy_type": "ordered table", + "instruction": "我想确认 Apache Tomcat 9.0.0 正式版发布前的哪些 milestone 版本，既同时受到四个指定 CVE 影响，又在 NVD 历史记录中留下了 CPE 名称写法变更记录。这里的 CPE 名称写法变更，指的是同一 milestone 版本在旧记录中使用 mN 形式表示，而在当前记录中改为 milestoneN 形式表示。检索范围仅限 Apache Tomcat 9.0.0 的 milestone 版本；这些版本必须同时出现在 CVE-2016-5018、CVE-2016-6794、CVE-2016-6796 和 CVE-2016-6797 的 NVD 当前受影响产品配置中。请排除仅由其他 Tomcat 9.0.0 预发布相关漏洞带入的 milestone 版本，也排除 Tomcat 6、Tomcat 7、Tomcat 8、Tomcat 8.5 以及所有非 Tomcat 产品。请输出多行有序表，列为 milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd，并按 milestone 编号的数值升序排列。", + "start_url": "https://nvd.nist.gov/vuln/search#/nvd/home?resultType=records", + "output_format": "请输出多行有序表，列为 milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd，并按 milestone 编号的数值升序排列。", + "oracle_output_cardinality": 3, + "oracle_answer": "CVE:2018-7543|1.2.32|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2018-17207|1.2.42|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2020-11738|1.3.28|lite+pro|ModifiedAnalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02", + "metadata": { + "State-Gated Retrieval": [ + "只保留当前产品线属于 awesomemotive:duplicator、且在 deprecated 旧厂商链中能回溯到 snapcreek:duplicator 的 Duplicator 相关 CVE。", + "每个候选 CVE 都必须在 Change History 中同时满足：Initial Analysis 还不是 lite/lite+pro；后续在 2021-10-18 的 NIST 分析事件里第一次改到 lite 或 lite+pro；并在 2026-02-02 发生 snapcreek -> awesomemotive 的 vendor remap。", + "最终输出只保留满足上述三重条件的 CVE 行。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "NVD product/CPE search pages yield the current awesomemotive:duplicator family and the deprecated snapcreek:duplicator lineage", + "each target CVE detail page and Change History yield the Initial Analysis state, the first lite/lite+pro analysis event, and the 2026-02-02 vendor-remap event", + "final rows are produced only after candidate CVEs are intersected on both snapcreek -> awesomemotive migration and later introduction of lite/lite+pro in NIST analysis history" + ], + "control_dependency": [ + "the search must include the deprecated snapcreek lineage rather than only the current product state", + "vendor migration alone is insufficient until detail-level history confirms that lite/lite+pro was introduced after Initial Analysis", + "candidate CVEs must be filtered against the full change-history chronology, excluding any whose Initial Analysis already contained lite" + ], + "freeze": { + "historical_window": "Duplicator CVEs published from 2018-01-01 through 2024-12-31, evaluated against NVD analysis history up to the 2026-02-02 snapcreek -> awesomemotive vendor-remap events" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只保留当前产品线属于 awesomemotive:duplicator、且在 deprecated 旧厂商链中能回溯到 snapcreek:duplicator 的 Duplicator 相关 CVE。", + "每个候选 CVE 都必须在 Change History 中同时满足：Initial Analysis 还不是 lite/lite+pro；后续在 2021-10-18 的 NIST 分析事件里第一次改到 lite 或 lite+pro；并在 2026-02-02 发生 snapcreek -> awesomemotive 的 vendor remap。", + "最终输出只保留满足上述三重条件的 CVE 行。" + ], + "exclusion_conditions": [ + "排除只看 current description 或 current product state、没有回退到 deprecated snapcreek 链和 Change History 的结果。", + "排除 Initial Analysis 就已经是 lite/lite+pro 的 CVE。", + "排除没有 2026-02-02 vendor remap、或不属于 Duplicator 产品线的记录。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ",", + "schema_note": "the current source docx rubric, evidence, and oracle answer use a Duplicator CVE rowset, even though the instruction/output_format text still describes a Tomcat milestone task; normalization therefore follows the checked oracle row schema rather than the stale milestone wording", + "schema": [ + "CVE", + "lite_upper_version", + "lite_vs_lite+pro", + "analysis_event@date", + "snapcreek_to_awesomemotive@date" + ], + "CVE": "emit the identifier in the canonical `CVE:YYYY-NNNN` form used by the oracle", + "lite_vs_lite+pro": "emit `lite` or `lite+pro` exactly", + "analysis_event@date": "emit `Reanalysis@YYYY-MM-DD` or `ModifiedAnalysis@YYYY-MM-DD` exactly as supported by the source record", + "snapcreek_to_awesomemotive@date": "emit the ownership-transfer event as `snapcreek->awesomemotive@YYYY-MM-DD`", + "sorting_or_selection": { + "primary": "NVD published date ascending", + "secondary": "CVE ascending" + } + } + } +} diff --git a/data_zh/goal/nvd_002-g.json b/data_zh/goal/nvd_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..4ee5cb46e4b99f0ad62870bbddf43bcdc3c97ed5 --- /dev/null +++ b/data_zh/goal/nvd_002-g.json @@ -0,0 +1,62 @@ +{ + "task_id": "nvd_002-g", + "instruction": "我们在整理一份 Oracle 收购 MySQL 后留下的 MySQL 5.1 旧资产例外清单，想确认哪些名称前缀仍写作 mysql:mysql 的旧 CPE 2.3 条目，在 NVD 对四个 InnoDB 拒绝服务漏洞的历史记录中，都被 NIST 明确改写为对应的 oracle:mysql 条目。请从 CVE-2010-3676、CVE-2010-3677、CVE-2010-3678 和 CVE-2010-3680 这四个漏洞入手，逐一查看相关 CPE 在 NVD 中的变更记录，找出那些在四个漏洞里都发生了“前缀从 mysql:mysql 改为 oracle:mysql”这一变更的 MySQL 5.1 条目；筛选时只保留这类从旧前缀迁移到新前缀的记录，排除 MySQL 5.0 分支，以及仅在 mysql:mysql 旧前缀内部做版本别名归一化的条目。最后，请输出多行有序表，列为 version_update | legacy_cpe | current_cpe | remap_time_nvd，按版本号数值升序排列；同一版本下，update 为空的记录排在非空 update 之前。", + "domain": "NVD", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 44, + "start_url": "https://nvd.nist.gov/products/cpe/search", + "output_format": "请输出多行有序表，列为 version_update | legacy_cpe | current_cpe | remap_time_nvd，按版本号数值升序排列；同一版本下，不带 update 的条目排在带 update 的条目前。", + "oracle_answer": "version_update|legacy_cpe|current_cpe|remap_time_nvd\n5.1.1|cpe:2.3:a:mysql:mysql:5.1.1:::::::*|cpe:2.3:a:oracle:mysql:5.1.1:::::::*|2019-12-17 15:04:33\n5.1.2|cpe:2.3:a:mysql:mysql:5.1.2:::::::*|cpe:2.3:a:oracle:mysql:5.1.2:::::::*|2019-12-17 15:04:39\n5.1.3|cpe:2.3:a:mysql:mysql:5.1.3:::::::*|cpe:2.3:a:oracle:mysql:5.1.3:::::::*|2019-12-17 15:04:46\n5.1.4|cpe:2.3:a:mysql:mysql:5.1.4:::::::*|cpe:2.3:a:oracle:mysql:5.1.4:::::::*|2019-12-17 15:04:53\n5.1.10|cpe:2.3:a:mysql:mysql:5.1.10:::::::*|cpe:2.3:a:oracle:mysql:5.1.10:::::::*|2019-12-17 15:05:30\n5.1.11|cpe:2.3:a:mysql:mysql:5.1.11:::::::*|cpe:2.3:a:oracle:mysql:5.1.11:::::::*|2019-12-17 15:05:37\n5.1.12|cpe:2.3:a:mysql:mysql:5.1.12:::::::*|cpe:2.3:a:oracle:mysql:5.1.12:::::::*|2019-12-17 15:05:45\n5.1.13|cpe:2.3:a:mysql:mysql:5.1.13:::::::*|cpe:2.3:a:oracle:mysql:5.1.13:::::::*|2019-12-17 15:05:52\n5.1.14|cpe:2.3:a:mysql:mysql:5.1.14:::::::*|cpe:2.3:a:oracle:mysql:5.1.14:::::::*|2019-12-17 15:05:59\n5.1.15|cpe:2.3:a:mysql:mysql:5.1.15:::::::*|cpe:2.3:a:oracle:mysql:5.1.15:::::::*|2019-12-17 15:06:07\n5.1.16|cpe:2.3:a:mysql:mysql:5.1.16:::::::*|cpe:2.3:a:oracle:mysql:5.1.16:::::::*|2019-12-17 15:06:14\n5.1.17|cpe:2.3:a:mysql:mysql:5.1.17:::::::*|cpe:2.3:a:oracle:mysql:5.1.17:::::::*|2019-12-17 15:06:21\n5.1.18|cpe:2.3:a:mysql:mysql:5.1.18:::::::*|cpe:2.3:a:oracle:mysql:5.1.18:::::::*|2019-12-17 15:06:27\n5.1.19|cpe:2.3:a:mysql:mysql:5.1.19:::::::*|cpe:2.3:a:oracle:mysql:5.1.19:::::::*|2019-12-17 15:06:34\n5.1.20|cpe:2.3:a:mysql:mysql:5.1.20:::::::*|cpe:2.3:a:oracle:mysql:5.1.20:::::::*|2019-12-17 15:06:42\n5.1.21|cpe:2.3:a:mysql:mysql:5.1.21:::::::*|cpe:2.3:a:oracle:mysql:5.1.21:::::::*|2019-12-17 15:06:50\n5.1.22|cpe:2.3:a:mysql:mysql:5.1.22:::::::*|cpe:2.3:a:oracle:mysql:5.1.22:::::::*|2019-12-17 15:06:56\n5.1.23:a|cpe:2.3:a:mysql:mysql:5.1.23:a::::::|cpe:2.3:a:oracle:mysql:5.1.23:a::::::|2019-12-17 15:23:28\n5.1.24|cpe:2.3:a:mysql:mysql:5.1.24:::::::*|cpe:2.3:a:oracle:mysql:5.1.24:::::::*|2019-12-17 15:07:03\n5.1.25|cpe:2.3:a:mysql:mysql:5.1.25:::::::*|cpe:2.3:a:oracle:mysql:5.1.25:::::::*|2019-12-17 15:07:10\n5.1.26|cpe:2.3:a:mysql:mysql:5.1.26:::::::*|cpe:2.3:a:oracle:mysql:5.1.26:::::::*|2019-12-17 15:07:17\n5.1.27|cpe:2.3:a:mysql:mysql:5.1.27:::::::*|cpe:2.3:a:oracle:mysql:5.1.27:::::::*|2019-12-17 15:07:24\n5.1.28|cpe:2.3:a:mysql:mysql:5.1.28:::::::*|cpe:2.3:a:oracle:mysql:5.1.28:::::::*|2019-12-17 15:07:31\n5.1.29|cpe:2.3:a:mysql:mysql:5.1.29:::::::*|cpe:2.3:a:oracle:mysql:5.1.29:::::::*|2019-12-17 15:07:38\n5.1.30|cpe:2.3:a:mysql:mysql:5.1.30:::::::*|cpe:2.3:a:oracle:mysql:5.1.30:::::::*|2019-12-17 15:07:46\n5.1.31:sp1|cpe:2.3:a:mysql:mysql:5.1.31:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.31:sp1::::::|2019-12-17 15:23:35\n5.1.33|cpe:2.3:a:mysql:mysql:5.1.33:::::::*|cpe:2.3:a:oracle:mysql:5.1.33:::::::*|2019-12-17 15:07:55\n5.1.34:sp1|cpe:2.3:a:mysql:mysql:5.1.34:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.34:sp1::::::|2019-12-17 15:23:42\n5.1.35|cpe:2.3:a:mysql:mysql:5.1.35:::::::*|cpe:2.3:a:oracle:mysql:5.1.35:::::::*|2019-12-17 15:08:03\n5.1.36|cpe:2.3:a:mysql:mysql:5.1.36:::::::*|cpe:2.3:a:oracle:mysql:5.1.36:::::::*|2019-12-17 15:08:10\n5.1.37:sp1|cpe:2.3:a:mysql:mysql:5.1.37:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.37:sp1::::::|2019-12-17 15:23:49\n5.1.38|cpe:2.3:a:mysql:mysql:5.1.38:::::::*|cpe:2.3:a:oracle:mysql:5.1.38:::::::*|2019-12-17 15:08:17\n5.1.39|cpe:2.3:a:mysql:mysql:5.1.39:::::::*|cpe:2.3:a:oracle:mysql:5.1.39:::::::*|2019-12-17 10:22:31\n5.1.40|cpe:2.3:a:mysql:mysql:5.1.40:::::::*|cpe:2.3:a:oracle:mysql:5.1.40:::::::*|2019-12-17 10:22:46\n5.1.40:sp1|cpe:2.3:a:mysql:mysql:5.1.40:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.40:sp1::::::|2019-12-17 10:22:39\n5.1.41|cpe:2.3:a:mysql:mysql:5.1.41:::::::*|cpe:2.3:a:oracle:mysql:5.1.41:::::::*|2019-12-17 10:22:52\n5.1.42|cpe:2.3:a:mysql:mysql:5.1.42:::::::*|cpe:2.3:a:oracle:mysql:5.1.42:::::::*|2019-12-17 10:22:59\n5.1.43|cpe:2.3:a:mysql:mysql:5.1.43:::::::*|cpe:2.3:a:oracle:mysql:5.1.43:::::::*|2019-12-17 10:23:06\n5.1.43:sp1|cpe:2.3:a:mysql:mysql:5.1.43:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.43:sp1::::::|2019-12-17 10:23:11\n5.1.44|cpe:2.3:a:mysql:mysql:5.1.44:::::::*|cpe:2.3:a:oracle:mysql:5.1.44:::::::*|2019-12-17 10:23:17\n5.1.45|cpe:2.3:a:mysql:mysql:5.1.45:::::::*|cpe:2.3:a:oracle:mysql:5.1.45:::::::*|2019-12-17 10:23:24\n5.1.46|cpe:2.3:a:mysql:mysql:5.1.46:::::::*|cpe:2.3:a:oracle:mysql:5.1.46:::::::*|2019-12-17 10:23:38\n5.1.46:sp1|cpe:2.3:a:mysql:mysql:5.1.46:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.46:sp1::::::|2019-12-17 10:23:31\n5.1.47|cpe:2.3:a:mysql:mysql:5.1.47:::::::*|cpe:2.3:a:oracle:mysql:5.1.47:::::::*|2019-12-17 10:23:45", + "metadata": { + "State-Gated Retrieval": [ + "只保留 MySQL 5.1 分支中，在 CVE-2010-3676、3677、3678、3680 四个漏洞的 NVD Change History 中都能明确看到 mysql:mysql -> oracle:mysql vendor migration 的 CPE 2.3 条目。", + "每个结果都必须给出 version_update、legacy_cpe、current_cpe 和 remap_time_nvd。", + "同一版本下，不带 update 的条目排在带 update 的条目前，并按版本号数值升序输出。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current and deprecated MySQL 5.1 CPE search results yield candidate legacy/current CPE strings", + "the four target CVE pages and their Change History entries yield vendor-migration evidence, exact version_update strings, and remap timestamps", + "final rows are produced only after taking the common mysql:mysql 5.1 -> oracle:mysql 5.1 migrations across all four CVEs and removing alias-only or 5.0 entries" + ], + "control_dependency": [ + "legacy vendor mapping must be determined from Analysis Description plus Change History rather than from the current description/current CPE view", + "include-deprecated results cannot be accepted wholesale because alias-only remaps must be filtered out", + "5.1-branch membership and sort order must be determined after the vendor-migration filter removes 5.0 and non-migration rows" + ], + "freeze": { + "historical_window": "the MySQL 5.1 branches visible in CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680, restricted to explicit mysql:mysql -> oracle:mysql vendor-migration events" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只保留 MySQL 5.1 分支中，在 CVE-2010-3676、3677、3678、3680 四个漏洞的 NVD Change History 中都能明确看到 mysql:mysql -> oracle:mysql vendor migration 的 CPE 2.3 条目。", + "每个结果都必须给出 version_update、legacy_cpe、current_cpe 和 remap_time_nvd。", + "同一版本下，不带 update 的条目排在带 update 的条目前，并按版本号数值升序输出。" + ], + "exclusion_conditions": [ + "排除 MySQL 5.0 分支条目。", + "排除仍属于旧厂商 mysql:mysql、只是内部版本别名归一化、并未发生 vendor migration 的条目。", + "排除只从 current Oracle MySQL 5.1 CPE state 读取、没有利用 legacy mapping 与 Change History 的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row `version_update|legacy_cpe|current_cpe|remap_time_nvd`", + "schema": [ + "version_update", + "legacy_cpe", + "current_cpe", + "remap_time_nvd" + ], + "version_update": "sort by numeric MySQL version ascending; within the same base version, the empty update comes before any non-empty update suffix", + "legacy_cpe": "preserve the exact legacy CPE 2.3 string", + "current_cpe": "preserve the exact current CPE 2.3 string", + "remap_time_nvd": "emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form", + "dedup_key": "(legacy_cpe, current_cpe)" + } + } +} diff --git a/data_zh/goal/nvd_003-g.json b/data_zh/goal/nvd_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..04f8cf3fc107b7afaaf3065f15fffaeb9532013c --- /dev/null +++ b/data_zh/goal/nvd_003-g.json @@ -0,0 +1,114 @@ +{ + "task_id": "nvd_004-g", + "domain": "NVD", + "autonomy_type": "ordered table", + "instruction": "我想确认 Apache Tomcat 9.0.0 正式版发布前的哪些 milestone（里程碑）版本，同时出现在 CVE-2016-5018、CVE-2016-6794、CVE-2016-6796 和 CVE-2016-6797 这四个漏洞的 NVD 当前受影响产品配置中，并且在 NVD 历史记录里可以看到同一版本的 CPE 产品标识从旧的 mN 形式迁移为现行的 milestoneN 形式。这一步用于清理仍采用 Apache Tomcat 9.0.0.Mx 旧写法的 SBOM 规则。这里的 mN 形式，是指用 m1、m2 等方式表示 milestone 版本；milestoneN 形式则是 NVD 当前使用的对应写法。请仅保留 Apache Tomcat 9.0.0 的这类 milestone 版本，排除两类条目：一类是并未同时满足上述四个漏洞条件、只是因为其他 Tomcat 9.0.0 预发布版本相关漏洞而出现在记录中的 milestone 版本；另一类是 Tomcat 6、Tomcat 7、Tomcat 8、Tomcat 8.5 以及所有非 Tomcat 产品。请输出多行有序表，列为 milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd，并按 milestone 编号的数值升序排列。", + "start_url": "https://nvd.nist.gov/products/cpe/search", + "output_format": "请输出多行有序表，列为 milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd，并按 milestone 编号的数值升序排列。", + "oracle_output_cardinality": 9, + "oracle_answer": "milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd\nM1|cpe:2.3:a:apache:tomcat:9.0.0:m1:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone1:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM2|cpe:2.3:a:apache:tomcat:9.0.0:m2:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone2:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM3|cpe:2.3:a:apache:tomcat:9.0.0:m3:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone3:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM4|cpe:2.3:a:apache:tomcat:9.0.0:m4:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone4:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM5|cpe:2.3:a:apache:tomcat:9.0.0:m5:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone5:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM6|cpe:2.3:a:apache:tomcat:9.0.0:m6:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone6:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM7|cpe:2.3:a:apache:tomcat:9.0.0:m7:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone7:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM8|cpe:2.3:a:apache:tomcat:9.0.0:m8:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone8:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM9|cpe:2.3:a:apache:tomcat:9.0.0:m9:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone9:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18", + "metadata": { + "State-Gated Retrieval": [ + "只保留 Apache Tomcat 9.0.0 milestone 版本中，同时出现在 CVE-2016-5018、6794、6796、6797 四个目标 CVE 当前受影响产品范围里的版本。", + "并且这些版本必须能在 NVD Change History 中看到 mN -> milestoneN 的 CPE Deprecation Remap。", + "最终按 milestone 编号数值升序输出，且 required_cves 必须对应这四个指定 CVE。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current milestoneN CPE search/detail pages yield the Tomcat milestone family and the legacy mN mapping anchors", + "the four target CVE pages and Change History entries yield the exact mN -> milestoneN deprecation remaps and the required-CVE intersection", + "final rows are produced only after taking the remaps common to all four target CVEs and sorting by numeric milestone" + ], + "control_dependency": [ + "the candidate milestone set must be determined from the four-target-CVE intersection rather than from all prerelease Tomcat CVEs", + "later remapped milestones such as M10+ must be excluded by applying the specified four-CVE boundary", + "only explicit NVD CPE Deprecation Remap events from mN to milestoneN count, so generic Tomcat prerelease visibility cannot be accepted as evidence" + ], + "freeze": { + "historical_window": "the Tomcat 9.0.0 prerelease milestones jointly covered by CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797, with remap evidence fixed to the 2023-12-08 11:41:18 NVD deprecation events" + }, + "answer_type": "multi-row ordered table" + }, + "all_involved_urls": { + "fixed_entry_and_docs": [ + "https://nvd.nist.gov/products/cpe/search", + "https://nvd.nist.gov/vuln/vulnerability-detail-pages" + ], + "cpe_search_result_pages": [ + "https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL", + "https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED", + "https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20m&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED", + "https://nvd.nist.gov/products/cpe/search/results?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED" + ], + "representative_cpe_detail_pages": [ + "https://nvd.nist.gov/products/cpe/detail/615922?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED", + "https://nvd.nist.gov/products/cpe/detail/615947?keyword=cpe%3A2.3%3Aa%3Aapache&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED" + ], + "row_level_cpe_api_urls_m1_to_m9": [ + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone2%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone3%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone4%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone5%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone6%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone7%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone8%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A", + "https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone9%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A" + ], + "target_cve_detail_pages": [ + "https://nvd.nist.gov/vuln/detail/CVE-2016-5018", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6794", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6796", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6797" + ], + "negative_control_cve_detail_pages": [ + "https://nvd.nist.gov/vuln/detail/CVE-2016-6816", + "https://nvd.nist.gov/vuln/detail/CVE-2016-6817", + "https://nvd.nist.gov/vuln/detail/CVE-2019-0221" + ], + "cve_change_history_api": [ + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-5018&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6794&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6796&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6797&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6816&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6817&eventName=CPE%20Deprecation%20Remap", + "https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2019-0221&eventName=CPE%20Deprecation%20Remap" + ], + "representative_change_record_pages": [ + "https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=04%2F18%2F2022T13%3A57%3A03.500-0400", + "https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=08%2F24%2F2017T09%3A11%3A40.690-0400" + ] + }, + "rubric": { + "inclusion_conditions": [ + "只保留 Apache Tomcat 9.0.0 milestone 版本中，同时出现在 CVE-2016-5018、6794、6796、6797 四个目标 CVE 当前受影响产品范围里的版本。", + "并且这些版本必须能在 NVD Change History 中看到 mN -> milestoneN 的 CPE Deprecation Remap。", + "最终按 milestone 编号数值升序输出，且 required_cves 必须对应这四个指定 CVE。" + ], + "exclusion_conditions": [ + "排除只因为其他 Tomcat 9.0.0 预发布漏洞才被带入的 milestone，例如 M10/M11 及更晚 milestone。", + "排除 Tomcat 6、7、8、8.5 或任何非 Tomcat 产品。", + "排除没有明确 NVD remap 证据、只是 current milestone 页面可见的记录。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row `milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd`", + "schema": [ + "milestone", + "legacy_cpe", + "current_cpe", + "required_cves", + "remap_time_nvd" + ], + "milestone": "emit the canonical milestone label `M1` through `M9` and sort by the numeric suffix ascending", + "legacy_cpe": "preserve the exact legacy CPE 2.3 string containing the short milestone token such as `m1`", + "current_cpe": "preserve the exact current CPE 2.3 string containing the full milestone token such as `milestone1`", + "required_cves": "emit the fixed literal `CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797`", + "remap_time_nvd": "emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form" + } + } +} diff --git a/data_zh/goal/reptile_001-g.json b/data_zh/goal/reptile_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..5b24e1c9a9cdf4168eacd5d270eb15f038b58675 --- /dev/null +++ b/data_zh/goal/reptile_001-g.json @@ -0,0 +1,61 @@ +{ + "task_id": "reptile_001-g", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "我正在为 George A. Boulenger 1890 年《The Fauna of British India, Including Ceylon and Burma》中记载的印度蛇类早期馆藏标本整理名称对照。请在 Reptile Database 中整理出同时满足以下条件的条目：相较于书中所用名称，现已归入其他属；当前物种页面仍保留 BMNH 模式标本信息；模式产地（type locality）仍可对应 India。对每个符合条件的条目，请同时给出其当前物种页面所列历史名称中，年代最近且尚未采用现行属名的双名学名，并判断以该完整旧名作为名称检索时，结果是否唯一对应该条目。请按现行接受名字母序汇总输出，格式为 |||；多个条目之间用英文分号连接；如无符合条件的条目，输出 NONE。", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "请按现行接受名字母序汇总输出，格式为 |||；多个条目之间用英文分号连接；如无符合条件的条目，输出 NONE。", + "oracle_answer": "Argyrophis oatesii|Typhlops oatesii|UNIQUE|SYNTYPES;Dendrelaphis grandoculis|Ahaetulla grandoculis|UNIQUE|LECTOTYPE;Fowlea sanctijohannis|Xenochrophis sanctijohannis|UNIQUE|HOLOTYPE;Gerrhopilus beddomii|Typhlops beddomii|UNIQUE|SYNTYPES;Hebius khasiensis|Amphiesma khasiense|UNIQUE|LECTOTYPE;Hebius parallelus|Amphiesma parallelum|AMBIG|LECTOTYPE;Indotyphlops jerdoni|Typhlops jerdoni|UNIQUE|SYNTYPES;Myriopholis blanfordii|Leptotyphlops blanfordi|AMBIG|SYNTYPES", + "metadata": { + "State-Gated Retrieval": [ + "候选必须来自 Boulenger 1890《Fauna of British India》中的印度蛇类历史馆藏条目。", + "当前 Reptile Database 物种页必须同时满足：现已改归其他属；页面仍保留 BMNH 的模式标本信息；type locality 仍可对应 India。", + "在每个合格页面中，要选出时间上最接近现在、但尚未改用当前属名的旧双名学名，并用这个旧名做 exact 回查，再标记 UNIQUE 或 AMBIG。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Boulenger 1890 historical sample and current accepted-species pages yield candidates that changed genus while retaining BMNH type data and India-compatible type locality", + "each accepted page yields the nearest pre-current-genus old label, the BMNH type status, and the historical/type-locality evidence anchoring the entity", + "final rows are produced only after the old-label exact back-search is evaluated for uniqueness without losing the original entity anchor" + ], + "control_dependency": [ + "when an exact old-label back-search now hits multiple species, the original anchored entity must be kept and the uniqueness label must be set to AMBIG", + "once a candidate has passed the historical-cluster, genus-shift, BMNH, and India-locality gates, later old-label ambiguity can only rewrite the uniqueness field, not the entity itself", + "candidate anchoring must be preserved across the two-stage workflow so that old-label search noise does not redirect the accepted-species row" + ], + "freeze": { + "historical_window": "the objectively existing reptile taxa in the George A. Boulenger 1890 British India sample, using Reptile Database accepted pages, synonym labels, BMNH type data, and type-locality text as nearly objective and highly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "候选必须来自 Boulenger 1890《Fauna of British India》中的印度蛇类历史馆藏条目。", + "当前 Reptile Database 物种页必须同时满足：现已改归其他属；页面仍保留 BMNH 的模式标本信息；type locality 仍可对应 India。", + "在每个合格页面中，要选出时间上最接近现在、但尚未改用当前属名的旧双名学名，并用这个旧名做 exact 回查，再标记 UNIQUE 或 AMBIG。" + ], + "exclusion_conditions": [ + "排除当前接受名未发生换属、或页面不再保留 BMNH 模式标本信息的条目。", + "排除 type locality 不能对应 India 的条目。", + "排除把 exact 旧名回查非唯一的候选直接丢弃；这类候选应保留原实体并标记为 AMBIG。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "accepted name", + "old label", + "UNIQUE/AMBIG", + "BMNH status" + ], + "accepted_name": "emit the current accepted binomial exactly as shown in the reconciled source", + "old_label": "preserve the historical label exactly as used on the legacy branch", + "UNIQUE/AMBIG": "emit `UNIQUE` or `AMBIG` in uppercase", + "BMNH_status": "normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or SYNTYPES", + "sorting_or_selection": "accepted name alphabetical ascending" + } + } +} diff --git a/data_zh/goal/reptile_002-g.json b/data_zh/goal/reptile_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..32af7a7bd5a0f7a0db8d5ed64832c09c07a04786 --- /dev/null +++ b/data_zh/goal/reptile_002-g.json @@ -0,0 +1,63 @@ +{ + "task_id": "reptile_002-g", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "我正在为东南亚 Lygosoma 早期馆藏标本整理旧标签与现行接受名之间的名称对照。请在当前的 Lygosoma 名录中找出所有同时满足以下条件的现行物种：其物种页面同物异名（Synonym）栏中列有 Smith（1935/1937）使用的 Riopa 组合名，且这一旧名称在现行分类下可对应不止一个现行物种。对每个符合条件的物种，请给出其页面中最先列出的模式标本编号、模式标本类别（type status），以及该页模式产地（type locality）最终对应的地区。请按当前接受名字母序输出，格式为 ||||；多个条目之间用英文分号连接；如无符合条件的条目，输出 NONE。", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "请按当前接受名字母序输出，格式为 ||||；多个条目之间用英文分号连接；如无符合条件的条目，输出 NONE。", + "oracle_answer": "Lygosoma bampfyldei|Riopa bampfyldei|BMNH 1946.8.10.84|SYNTYPES|East Malaysia;Lygosoma peninsulare|Riopa bampfyldei|LSUHC 13857|HOLOTYPE|Peninsular Malaysia;Lygosoma schneideri|Riopa bampfyldei|NMBA 4743|HOLOTYPE|Indonesia", + "metadata": { + "State-Gated Retrieval": [ + "只保留能从 Smith 1937 的旧名链追溯到当前 Lygosoma 记录，并且可在当前页面读取 type accession、type status 与 locality 的 accepted 物种。", + "对每条 accepted 记录，都要输出该 accepted name、对应旧标签、type accession、type status 和 locality。", + "若同一个精确旧名同时挂在多个 accepted 物种上，必须把它们作为不同链条分别保留。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Smith 1937 old-name chain yields the three current Lygosoma accepted pages connected to Riopa bampfyldei / Lygosoma bampfyldei", + "each accepted page yields its own type accession, type status, and type locality needed to separate the homonymous old-name paths", + "final rows are produced only after the one-to-many old-name split is rebuilt and the three paths are re-anchored to their own type evidence" + ], + "control_dependency": [ + "same-specific-epithet matching cannot establish a one-to-one mapping when the same Smith 1937 old name appears on multiple accepted pages", + "once literal old-name reuse is exposed, the workflow must keep the original parallel three-chain state rather than collapsing to a one-to-one mapping", + "type accession and locality evidence must be read separately for each chain rather than patched onto the first stopping page" + ], + "freeze": { + "historical_window": "the objectively existing taxa linked to the Smith 1937 old-name cluster around Riopa bampfyldei, using Reptile Database accepted pages together with type accessions, statuses, and localities as nearly objective and highly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只保留能从 Smith 1937 的旧名链追溯到当前 Lygosoma 记录，并且可在当前页面读取 type accession、type status 与 locality 的 accepted 物种。", + "对每条 accepted 记录，都要输出该 accepted name、对应旧标签、type accession、type status 和 locality。", + "若同一个精确旧名同时挂在多个 accepted 物种上，必须把它们作为不同链条分别保留。" + ], + "exclusion_conditions": [ + "排除凭“旧名与现行种加词相同”就直接认定还是同一物种的结果。", + "排除发现同一精确旧名同时出现在多个 accepted 页后，仍只保留第一条链的结果。", + "排除没有回到各 accepted 页重新核验 type accession 与 locality 的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "accepted", + "Smith-era Riopa label", + "first type code", + "type status", + "region" + ], + "accepted": "emit the current accepted binomial exactly as shown in the reconciled source", + "Smith-era_Riopa_label": "preserve the Smith-era Riopa label exactly as used on the legacy branch", + "first_type_code": "emit the first accession code that follows the selected type-status statement", + "type_status": "normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES", + "region": "emit the modern geographic region label from the source reconciliation, such as East Malaysia or Peninsular Malaysia", + "sorting_or_selection": "accepted name alphabetical ascending" + } + } +} diff --git a/data_zh/goal/reptile_003-g.json b/data_zh/goal/reptile_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..9a15de77560e8c11869edecea3daa1bac78c294e --- /dev/null +++ b/data_zh/goal/reptile_003-g.json @@ -0,0 +1,66 @@ +{ + "task_id": "reptile_003-g", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 10, + "instruction": "我正在为一批 1980 年前后仍以 Mabuya 或 Mabuia 名称编入馆藏、现需归并至 Eutropis 现行名录的旧馆藏卡片整理名称对照。请在当前 Eutropis 名录中找出所有符合以下条件的条目：其物种页面中最先列出的 1980 年旧标签，属名写作 Mabuya 或 Mabuia；且在当前名录中按名称检索该旧标签时，不能唯一对应单一 Eutropis 条目，而是可同时对应多个现行 Eutropis 条目。对每个符合条件的条目，请给出当前接受名、这一 1980 旧标签、该旧标签在页面中的限定说明（qualifier），以及当前页面最先列出的模式标本类别（type status）和编号。请按旧标签字母序、同一旧标签下按当前接受名字母序输出，格式为 |<1980 label>|||；多个条目之间用英文分号连接；如无符合条件的条目，输出 NONE。", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "请按旧标签字母序、同一旧标签下按当前接受名字母序输出，格式为 |<1980 label>|||；多个条目之间用英文分号连接；如无符合条件的条目，输出 NONE。", + "oracle_answer": "Eutropis indeprensa|Mabuya indeprensa|NONE|HOLOTYPE|CAS 85664;Eutropis sahulinghangganan|Mabuya indeprensa|PART-MISID|HOLOTYPE|PNM 9867;Eutropis multifasciata|Mabuya multifasciata|NONE|NEOTYPE|MZB 11912;Eutropis multicarinata|Mabuya multicarinata|NONE|HOLOTYPE|BMNH 1946.8.15.13-15;Eutropis borealis|Mabuya multicarinata borealis|NONE|HOLOTYPE|CAS 15447;Eutropis islamaliit|Mabuya multicarinata borealis|PART-MISID|HOLOTYPE|PNM 9847;Eutropis caraga|Mabuya multicarinata multicarinata|PART-MISID|HOLOTYPE|PNM 9845;Eutropis palauensis|Mabuya multicarinata multicarinata|PART-BYIMPL|HOLOTYPE|CAS 248251;Eutropis dattaroyi|Mabuya rudis|PART|HOLOTYPE|ZSI 25118;Eutropis rudis|Mabuya rudis|NONE|LECTOTYPE|BMNH 1946.8.15.26", + "metadata": { + "State-Gated Retrieval": [ + "只保留当前 Eutropis 记录中，能够在 synonym 区块里自上而下找到第一条以 Mabuya 或 Mabuia 开头、且年份为 1980 的旧标签的 accepted 物种。", + "再用这条 1980 旧标签按默认名字匹配回查，并输出 accepted name、old label、回查判定、type status 与 type specimen。", + "若后续回查暴露出新的候选链，也必须回退并把它纳入最终结果。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "current Eutropis detail pages yield the first 1980-tagged Mabuya/Mabuia synonym label for each accepted species", + "exact back-search on that 1980 old label yields the present accepted page, type status, and type specimen needed for the output row", + "final rows are produced only after the 1980-specific old-label anchor is rebuilt and the accepted-species candidate pool is expanded when back-search evidence reveals omitted chains" + ], + "control_dependency": [ + "the workflow must identify the first Mabuya/Mabuia label carrying the 1980 year rather than stopping at the first old label on the page", + "when old-label back-search reveals missing chains such as Eutropis dattaroyi, the candidate pool must be expanded to include them rather than patched in place", + "accepted-page synonym parsing and back-search interpretation must stay coupled so that 1980 labels are not replaced by older but irrelevant names" + ], + "freeze": { + "historical_window": "the objectively existing Eutropis taxa represented in Reptile Database pages, using page-level synonym labels, especially the first Mabuya/Mabuia-form label tagged with the 1980 citation year, as nearly objective and highly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只保留当前 Eutropis 记录中，能够在 synonym 区块里自上而下找到第一条以 Mabuya 或 Mabuia 开头、且年份为 1980 的旧标签的 accepted 物种。", + "再用这条 1980 旧标签按默认名字匹配回查，并输出 accepted name、old label、回查判定、type status 与 type specimen。", + "若后续回查暴露出新的候选链，也必须回退并把它纳入最终结果。" + ], + "exclusion_conditions": [ + "排除把“最先出现的旧名”误当成“最先出现的 1980 旧标签”的结果。", + "排除只抓 Spanish? no", + "排除在后续证据暴露出遗漏链条时，没有回退重建候选池的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "accepted", + "1980 label", + "qualifier", + "type status", + "first type code" + ], + "accepted": "emit the current accepted binomial exactly as shown in the reconciled source", + "1980_label": "preserve the 1980-era label exactly as used on the legacy branch", + "qualifier": "normalize to one of `NONE`, `PART`, `PART-MISID`, or `PART-BYIMPL`", + "type_status": "normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES", + "first_type_code": "emit the first accession code that follows the selected type-status statement", + "sorting_or_selection": { + "primary": "1980 label alphabetical ascending", + "secondary": "accepted name alphabetical ascending" + } + } + } +} diff --git a/data_zh/goal/reptile_004-g.json b/data_zh/goal/reptile_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..a3528ae5dfb05fcd05607fdaa6534e41e3b8ed1a --- /dev/null +++ b/data_zh/goal/reptile_004-g.json @@ -0,0 +1,65 @@ +{ + "task_id": "reptile_004-g", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 6, + "instruction": "我正在整理一批旧半趾虎馆藏卡片，这些卡片沿用的是 Hemidactylus brookii 物种页面注释中列出的历史标签。请找出所有符合以下条件的旧标签：现已不应归并至 Hemidactylus brookii，且数据库已明确给出最终归并去向。对每个符合条件的旧标签，请给出其最终应归入的现行物种；如归并过程中需要先经过一个中间历史名称，请列出该名称，否则写 DIRECT；并同时给出该旧标签自身对应的模式标本类别、模式标本编号，以及其模式产地（type locality）所在国家。请按旧标签字母序输出，格式为 |||||；多个条目之间用英文分号连接；如无符合条件的条目，输出 NONE。", + "start_url": "https://reptile-database.reptarium.cz/advanced_search", + "output_format": "请按旧标签字母序输出，格式为 |||||；多个条目之间用英文分号连接；如无符合条件的条目，输出 NONE。", + "oracle_answer": "Hemidactylus brooki leightoni|Hemidactylus angulatus|DIRECT|HOLOTYPE|BMNH 1946.8.25.65|Colombia;Hemidactylus brookii haitianus|Hemidactylus angulatus|DIRECT|LECTOTYPE|ZMH R22378|Haiti;Hemidactylus brookii parvimaculatus|Hemidactylus parvimaculatus|DIRECT|HOLOTYPE|NMSL No. RG. 15|Sri Lanka;Hemidactylus brookii subtriedroides|Hemidactylus murrayi|Hemidactylus tenkatei|LECTOTYPE|BMNH [subtriedroides] [tenkatei]|Myanmar;Hemidactylus gleadowi|Hemidactylus gleadowi|DIRECT|NEOTYPE|BMNH 1884.7.25.8|Pakistan;Hemidactylus tenkatei|Hemidactylus murrayi|DIRECT|LECTOTYPE|RMNH 4353|Indonesia", + "metadata": { + "State-Gated Retrieval": [ + "每条结果都必须从题目指定的旧标签链条出发，最终在当前 accepted 页中核定 accepted name、bridge 状态、type status、type accession 和 locality。", + "对 subtriedroides 分支，必须继续沿 tenkatei 再追到 murrayi，输出最终 accepted 为 Hemidactylus murrayi，并保留 bridge=Hemidactylus tenkatei。", + "对 haitianus、leightoni 等分支，必须读取各自 locality / type 行，而不是借用错误页面的页首信息。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the old-label chains from Hemidactylus angulatus and related names yield accepted pages, bridge names, and the type/locality lines for each path", + "comment, Types, and type-comment blocks yield the later evidence that tenkatei is further sunk into H. murrayi", + "final rows are produced only after each old-label path is re-anchored to its own locality/type line and the subtriedroides -> tenkatei -> murrayi bridge chain is completed" + ], + "control_dependency": [ + "type data must be taken from the locality/type line belonging to the actual old-label branch rather than from the page-top block of the wrong accepted page", + "stopping at the intermediate tenkatei bridge is insufficient; the workflow must continue to the later murrayi evidence and rewrite both tenkatei and subtriedroides final accepted names", + "bridge labels remain useful, but final accepted names and type lines must be determined from the deeper synonym chain" + ], + "freeze": { + "historical_window": "the objectively existing taxa in the Hemidactylus angulatus / brookii / murrayi complex, using Reptile Database locality, type, comment, and type-comment blocks as nearly objective and highly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "每条结果都必须从题目指定的旧标签链条出发，最终在当前 accepted 页中核定 accepted name、bridge 状态、type status、type accession 和 locality。", + "对 subtriedroides 分支，必须继续沿 tenkatei 再追到 murrayi，输出最终 accepted 为 Hemidactylus murrayi，并保留 bridge=Hemidactylus tenkatei。", + "对 haitianus、leightoni 等分支，必须读取各自 locality / type 行，而不是借用错误页面的页首信息。" + ], + "exclusion_conditions": [ + "排除读取了错误页内层级、把 H. angulatus 页首的 Holotype / locality 套到其他分支的结果。", + "排除在 subtriedroides -> tenkatei 链上提前停止、未继续读取 murrayi 后续证据的结果。", + "排除未把 locality / type 行与具体旧标签分支逐一对齐的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": ";", + "schema": [ + "legacy label", + "accepted", + "bridge", + "type status", + "type code", + "country" + ], + "legacy_label": "preserve the legacy label exactly as used on the source branch", + "accepted": "emit the current accepted binomial exactly as shown in the reconciled source", + "bridge": "emit `DIRECT` when no intermediate legacy bridge name is needed; otherwise emit the intermediate legacy name that links the branches", + "type_status": "normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or NEOTYPE", + "type_code": "take the type accession from the legacy-label branch rather than a generic page-level type line", + "country": "emit the modern English country name from the reconciled source branch", + "sorting_or_selection": "legacy label alphabetical ascending" + } + } +} diff --git a/data_zh/goal/reptile_005-g.json b/data_zh/goal/reptile_005-g.json new file mode 100644 index 0000000000000000000000000000000000000000..3e4b3cc0cd0d4e2f87242056dc1e189497f5a02e --- /dev/null +++ b/data_zh/goal/reptile_005-g.json @@ -0,0 +1,68 @@ +{ + "task_id": "reptile_005-g", + "domain": "REPTILE_DATABASE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我想把当前 Naja 名录里这条斯里兰卡旧馆藏名的归并信息整理成一张两行对照表。请输出两行表，列为 rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note。第一行为 ACCEPTED_NAME，第二行为 CONTESTED_NAME。", + "start_url": "https://reptile-database.reptarium.cz/advanced_search?genus=Naja&submit=Search", + "output_format": "请输出两行对照表，列为 rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note。", + "oracle_answer": "1|ACCEPTED_NAME|Naja naja|SUBJECTIVE_JUNIOR_SYNONYM_OF_NAJA_NAJA|VALID_LECTOTYPE|ZMB 2796|restricted type locality: Sri Lanka\n2|CONTESTED_NAME|Naja polyocellata|SHI et al. 2022+SILVA et al. 2023|HOLOTYPE|BMNH 1946.1.18.50|invalid lectotype claim: NRM (= NHR) Lin-90", + "metadata": { + "State-Gated Retrieval": [ + "必须在当前 Naja 名录中锁定来自 Sri Lanka 的 contested-name 分支：该名称近年曾被重新当作独立有效名使用，但数据库当前又明确并入 accepted name。", + "同一 accepted 页中还必须同时读取 recent-use evidence、final synonym status、lectotype 更正信息、restricted type locality，以及 contested name 自身的 holotype 信息。", + "最终输出必须把 ACCEPTED_NAME 与 CONTESTED_NAME 两侧信息整理成两行对照表。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the current Naja species list and the Naja naja page yield the Sri Lanka contested-name branch, recent-use citations, and the accepted-name context", + "comment, Types, and type-comment blocks yield the final synonym treatment plus the valid and invalid lectotype assignments and the contested-name holotype", + "final rows are produced only after the accepted-name and contested-name sides are reconciled on the same accepted page" + ], + "control_dependency": [ + "recent-use evidence for Naja polyocellata must be interpreted together with the current page-level final synonym treatment", + "lectotype status must be fixed from the combined Types and type-comment evidence rather than from a single provisional assignment", + "the accepted-name and contested-name rows are emitted together only after final status, type locality, and specimen roles are fixed" + ], + "freeze": { + "historical_window": "the objectively existing taxa in the Sri Lanka Naja branch, using current Reptile Database comment, Types, and type-comment blocks as nearly objective and highly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "必须在当前 Naja 名录中锁定来自 Sri Lanka 的 contested name 记录，该名称近年曾被文献重新作为独立有效名使用，但数据库当前又明确说明其仍应并入 accepted name。", + "同一 accepted 页中还必须同时能读取 recent-use evidence、final synonym status、lectotype 更正信息、restricted type locality，以及 contested name 自身的 holotype 信息。", + "最终输出必须把 ACCEPTED_NAME 与 CONTESTED_NAME 两侧信息整理成两行对照表。" + ], + "exclusion_conditions": [ + "排除把近年恢复使用的 contested name 直接当作当前 accepted name 的结果。", + "排除只读到 Wallach 2014 的 lectotype 指定、没有继续读取 comment 与 type comment 修正的结果。", + "排除未同时输出 restricted type locality 与 contested-name holotype 的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "name_role", + "name", + "status_or_evidence", + "specimen_role", + "specimen_code", + "supporting_note" + ], + "rank": "emit 1 for ACCEPTED_NAME and 2 for CONTESTED_NAME", + "name_role": [ + "ACCEPTED_NAME", + "CONTESTED_NAME" + ], + "name_fields": "use the current binomial spellings exactly", + "specimen_code_normalization": "preserve museum abbreviations, spaces, parentheses, and specimen punctuation exactly as the page shows", + "sorting_or_selection": "emit rows in the fixed order ACCEPTED_NAME then CONTESTED_NAME" + } + } +} diff --git a/data_zh/goal/wateroffice_001-g.json b/data_zh/goal/wateroffice_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..91a7eadb0dce8d8fbf5d170a5837e81926d27e6f --- /dev/null +++ b/data_zh/goal/wateroffice_001-g.json @@ -0,0 +1,67 @@ +{ + "task_id": "wateroffice_001-g", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我在整理圣约翰河春季汛期的历史日流量对比资料，想沿 Saint John River 主河道找出当前实时站网中最后一个仍可同时比较 1973 年和 2018 年 3–4 月日流量的站点，以及它下游方向遇到的第一个不再满足该条件的主河道站点。目标窗口满足完整日流量条件时记为 PASS；若只有水位记录则记为 LEVEL_ONLY；若有日流量但目标月份缺失或不完整则记为 FLOW_GAP。请输出两行 breakpoint table，列为 rank|station_number|breakpoint_role|target_window_status|final_verdict。第一行为 LAST_USABLE，第二行为 FIRST_DOWNSTREAM_FAIL。", + "start_url": "https://wateroffice.ec.gc.ca/search/real_time_e.html", + "output_format": "请输出两行 breakpoint table，列为 rank|station_number|breakpoint_role|target_window_status|final_verdict。", + "oracle_answer": "1|01AF002|LAST_USABLE|PASS|KEEP\n2|01AK003|FIRST_DOWNSTREAM_FAIL|LEVEL_ONLY|REJECT", + "metadata": { + "State-Gated Retrieval": [ + "只在当前实时站网中的 Saint John River 主河道候选站里判断最后一个仍可用于目标历史窗口比较的站点。", + "历史 availability 页面必须区分 Flow Data Availability 与 Daily Water Level Data Availability，并核对 1973/2018 年 3–4 月完整性。", + "最终要在同一验证规则下同时给出 LAST_USABLE 与 FIRST_DOWNSTREAM_FAIL 两个断点行。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the current live mainstem candidate list yields the Saint John River candidate chain whose downstream breakpoints must be checked", + "per-station historical availability pages yield Flow Data Availability, Daily Water Level Data Availability, and target-month completeness for 1973 and 2018", + "the final breakpoint rows are produced only after deep availability checks identify the last usable station and the first downstream failure under the same rule" + ], + "control_dependency": [ + "the breakpoint pair must be determined from historical availability that distinguishes flow from level-only evidence", + "target-year/month completeness must be checked on the availability page rather than inferred from the live-station list", + "the second row is emitted only after the first downstream failing mainstem station is fixed under the same deep rule" + ], + "freeze": { + "historical_window": "mainstem candidate stations evaluated within the fixed historical March/April daily-availability windows for 1973 and 2018, using station ordering and completeness signals as nearly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在当前实时站网中的 Saint John River 主河道候选站里判断最后一个仍可用于目标历史窗口比较的站点。", + "历史 availability 页面必须区分 Flow Data Availability 与 Daily Water Level Data Availability，并核对 1973/2018 年 3–4 月完整性。", + "最终要在同一验证规则下同时给出 LAST_USABLE 与 FIRST_DOWNSTREAM_FAIL 两个断点行。" + ], + "exclusion_conditions": [ + "排除只看当前实时主河道候选集、按参考索引直接确定断点的浅层结果。", + "排除把 level-only 证据误当成满足 Flow 的结果。", + "排除没有逐站下钻 availability 页核验目标月份完整性的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "breakpoint_role", + "target_window_status", + "final_verdict" + ], + "rank": "emit `1` for LAST_USABLE and `2` for FIRST_DOWNSTREAM_FAIL", + "station_number": "preserve the station number exactly", + "breakpoint_role": "emit `LAST_USABLE` and `FIRST_DOWNSTREAM_FAIL` exactly", + "target_window_status": "emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly", + "final_verdict": "emit `KEEP` for the usable breakpoint row and `REJECT` for the downstream failing breakpoint row", + "stop_condition": [ + "the last usable mainstem station is fixed under the deep availability rule", + "the first downstream failing mainstem station is fixed under the same rule before the two-row output is emitted" + ] + } + } +} diff --git a/data_zh/goal/wateroffice_002-g.json b/data_zh/goal/wateroffice_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..37b02f6bbc6016a6e3ecf1d9e74b3bc056b9a669 --- /dev/null +++ b/data_zh/goal/wateroffice_002-g.json @@ -0,0 +1,66 @@ +{ + "task_id": "wateroffice_002-g", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 4, + "instruction": "我整理 Bulkley River 从 Houston 到 Hazelton 河段的历史日流量，想确认这一河段的 Bulkley River 主河道候选站中，哪些站在 1948 年和 1950 年 4–7 月真正具备完整日流量记录。若目标窗口满足完整日流量条件，则记为 PASS；若只有水位记录则记为 LEVEL_ONLY；若有日流量但 4–7 月中任一目标月份不是完整月份则记为 FLOW_GAP。请按从下游到上游的顺序输出一张表，列为 rank|station_number|target_window_status|final_verdict。", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "请按从下游到上游的顺序输出一张表，列为 rank|station_number|target_window_status|final_verdict。", + "oracle_answer": "1|08EE004|PASS|KEEP\n2|08EE001|LEVEL_ONLY|REJECT\n3|08EE005|FLOW_GAP|REJECT\n4|08EE003|FLOW_GAP|REJECT", + "metadata": { + "State-Gated Retrieval": [ + "先在 Historical Results 列表层找出表面上看起来覆盖 1948/1950 且带 Flow 标签的主河道候选站。", + "真正合格的站点必须在 availability 页面上同时满足：目标年份位于 Flow 区，且 April-July 全部为 C。", + "最终必须按同一候选集逐站给出 target_window_status 和 final_verdict，并按从下游到上游输出。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Historical Results list yields four downstream-to-upstream mainstem candidates whose result rows span the target years and include Flow labels", + "each candidate availability page yields whether the target years are in the Flow table and whether April-July is complete", + "the final ordered rows are produced only after all four candidates are classified under the stricter Flow-table-and-Apr-Jul-C rule" + ], + "control_dependency": [ + "list-level year spans and coarse Flow tags must be confirmed by explicit target-month checks on the availability page", + "Hazelton, Smithers, and Houston candidate statuses must be fixed before the downstream-most KEEP row can be confirmed", + "row order and KEEP/REJECT labels must be emitted only after the stricter availability rule is applied to all four stations" + ], + "freeze": { + "historical_window": "the target mainstem stations tested within the fixed historical daily Flow-availability windows for 1948 and 1950, with April-July complete-C coverage used as nearly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先在 Historical Results 列表层找出表面上看起来覆盖 1948/1950 且带 Flow 标签的主河道候选站。", + "真正合格的站点必须在 availability 页面上同时满足：目标年份位于 Flow 区，且 April-July 全部为 C。", + "最终必须按同一候选集逐站给出 target_window_status 和 final_verdict，并按从下游到上游输出。" + ], + "exclusion_conditions": [ + "排除只依据列表层“年份跨度 + 粗 Flow 标签”就认定可用的站点。", + "排除把 LEVEL_ONLY 或 FLOW_GAP 站点标成 KEEP 的结果。", + "排除没有把更强的 availability 规则重新施加到所有浅层候选的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "target_window_status", + "final_verdict" + ], + "rank": "emit 1 through 4 in downstream-to-upstream order within the validated candidate set", + "station_number": "preserve the station number exactly", + "target_window_status": "emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly", + "final_verdict": "emit `KEEP` or `REJECT` exactly", + "sorting_or_selection": "downstream to upstream within the validated Bulkley River mainstem candidate set", + "stop_condition": [ + "all four shallow candidates are classified under the stricter availability rule", + "the ordered table is emitted only after the downstream-to-upstream sequence is fixed" + ] + } + } +} diff --git a/data_zh/goal/wateroffice_003-g.json b/data_zh/goal/wateroffice_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..dbc6d4ab6ebbf31ec5b4703ac0ff3e1afe48c019 --- /dev/null +++ b/data_zh/goal/wateroffice_003-g.json @@ -0,0 +1,62 @@ +{ + "task_id": "wateroffice_003-g", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 5, + "instruction": "我在整理 Thompson River 从 Chase 到 Spences Bridge 河段的历史融雪期日流量资料，想确认 Thompson River 从 Chase 到 Spences Bridge 河段的主河道站点中，哪些在 1958 年和 1971 年 5—7 月都实际具备日流量记录。请对这一河段内在站点列表中显示覆盖 1958 年和 1971 年、且带有流量信息的主河道站点，按从 Chase 下游到 Spences Bridge 的河道顺序逐站核实。输出表格列为 rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict。若某站在目标年份仅有水位记录而无日流量记录，记为 LEVEL_ONLY；若日流量记录缺失，或 5—7 月中任一目标月份记录不完整，记为 FLOW_GAP；仅当两个年份均满足条件时，final_verdict 才记为 KEEP，否则记为 REJECT。", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "输出表格列为 rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict。", + "oracle_answer": "1|08LE031|SOUTH THOMPSON RIVER AT CHASE|PASS|PASS|KEEP\n2|08LE069|SOUTH THOMPSON RIVER AT MONTE CREEK|FLOW_GAP|LEVEL_ONLY|REJECT\n3|08LF023|THOMPSON RIVER AT KAMLOOPS|LEVEL_ONLY|LEVEL_ONLY|REJECT\n4|08LF033|THOMPSON RIVER NEAR SAVONA|FLOW_GAP|FLOW_GAP|REJECT\n5|08LF051|THOMPSON RIVER NEAR SPENCES BRIDGE|PASS|PASS|KEEP", + "metadata": { + "State-Gated Retrieval": [ + "题目涉及的 5 个候选站都必须在 availability 页核验目标年份是否位于 Flow 表中，且 May-July 是否全部为 C。", + "每个站最终都要输出对两个目标年份的 PASS / LEVEL_ONLY / FLOW_GAP 等判定，并据此标记 KEEP 或 REJECT。", + "结果顺序必须保持题目要求的河道路径排序。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the river-path ordering yields five South Thompson / Thompson mainstem candidates", + "each station's availability page yields whether 1958 and 1971 are present in the Flow table and whether May-July is complete", + "final rows are produced only after every candidate is classified under the stricter target-year and target-month Flow rule" + ], + "control_dependency": [ + "overall year coverage on the results list must be confirmed by the availability page inside the Flow table", + "Monte Creek, Savona, and Kamloops must be rejected by LEVEL_ONLY / FLOW_GAP evidence before the KEEP rows are final", + "candidate ordering remains fixed, but status labels must be rewritten after the deeper availability rule is applied to all five stations" + ], + "freeze": { + "historical_window": "the ordered South Thompson / Thompson mainstem candidates tested within the fixed historical Flow-availability windows for 1958 and 1971, with May-July complete-C coverage used as nearly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "题目涉及的 5 个候选站都必须在 availability 页核验目标年份是否位于 Flow 表中，且 May-July 是否全部为 C。", + "每个站最终都要输出对两个目标年份的 PASS / LEVEL_ONLY / FLOW_GAP 等判定，并据此标记 KEEP 或 REJECT。", + "结果顺序必须保持题目要求的河道路径排序。" + ], + "exclusion_conditions": [ + "排除把列表层整体年份覆盖当成足够证据的浅层结果。", + "排除没有区分 Flow 表内目标年、月份完整性与 Level-only 证据的结果。", + "排除未对全部 5 个候选统一应用同一深层规则的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "station_name", + "1958_MayJul", + "1971_MayJul", + "final_verdict" + ], + "rank": "use the fixed Chase-to-Spences-Bridge mainstem order from the reference index, not the transient search-result order", + "year_window_fields": "the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP", + "final_verdict": "emit `KEEP` or `REJECT` exactly" + } + } +} diff --git a/data_zh/goal/wateroffice_004-g.json b/data_zh/goal/wateroffice_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..be2f8a13b0136d98f281b43bb15a041a7cd8e7ff --- /dev/null +++ b/data_zh/goal/wateroffice_004-g.json @@ -0,0 +1,62 @@ +{ + "task_id": "wateroffice_004-g", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 13, + "instruction": "我在整理 Columbia River 主河道从 Fairmont Hot Springs 到 International Boundary 河段的历史日流量资料，想逐站核对 Wateroffice 中哪些测站在 1955 年和 1956 年的 5–10 月具备完整日流量记录。候选范围限于 Columbia River 主河道上、站点记录整体时间范围跨越 1955 年和 1956 年的河道测站。请按从上游到下游的河道顺序逐站核实，输出表格列为 rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict。若目标年份仅有水位记录而无日流量记录，记为 LEVEL_ONLY；若该年 5–10 月日流量均完整，记为 PASS。’若日流量记录不存在，或 5—10 月中任一目标月份记录不完整，记为 FLOW_GAP；仅当 1955 年和 1956 年两个年份均满足完整日流量条件时，final_verdict 才记为 KEEP，否则记为 REJECT。", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "输出表格列为 rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict。", + "oracle_answer": "1|08NA045|COLUMBIA RIVER NEAR FAIRMONT HOT SPRINGS|PASS|PASS|KEEP\n2|08NA004|COLUMBIA RIVER AT ATHALMER|LEVEL_ONLY|LEVEL_ONLY|REJECT\n3|08NA052|COLUMBIA RIVER NEAR EDGEWATER|PASS|FLOW_GAP|REJECT\n4|08NA002|COLUMBIA RIVER AT NICHOLSON|PASS|PASS|KEEP\n5|08NB005|COLUMBIA RIVER AT DONALD|PASS|PASS|KEEP\n6|08NB006|COLUMBIA RIVER AT SURPRISE RAPIDS|PASS|PASS|KEEP\n7|08ND007|COLUMBIA RIVER ABOVE NAGLE CREEK|PASS|PASS|KEEP\n8|08ND011|COLUMBIA RIVER ABOVE STEAMBOAT RAPIDS|FLOW_GAP|PASS|REJECT\n9|08ND006|COLUMBIA RIVER AT TWELVE MILE FERRY|PASS|PASS|KEEP\n10|08NE002|COLUMBIA RIVER AT CASTLEGAR|LEVEL_ONLY|LEVEL_ONLY|REJECT\n11|08NE049|COLUMBIA RIVER AT BIRCHBANK|PASS|PASS|KEEP\n12|08NE003|COLUMBIA RIVER AT TRAIL|LEVEL_ONLY|LEVEL_ONLY|REJECT\n13|08NE058|COLUMBIA RIVER AT INTERNATIONAL BOUNDARY|PASS|PASS|KEEP", + "metadata": { + "State-Gated Retrieval": [ + "所有候选 Columbia River 站点都必须下钻 availability 页，确认目标年份位于 Flow 表中且 May-October 全为 C。", + "每个站都要给出 1955、1956 两年的 KEEP / REJECT 依据，并区分 LEVEL_ONLY、FLOW_GAP 与整体年份跨度陷阱。", + "最终表格要保持题目规定的顺序与字段。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Columbia River candidate ordering yields fourteen stations spanning the target years", + "each availability page yields whether 1955 and 1956 are present in the Flow table and whether May-October is complete", + "final rows are produced only after every station is classified under the stricter Flow-table-and-May-Oct-C rule" + ], + "control_dependency": [ + "list-level year spans must be confirmed by the availability page inside the Flow table", + "LEVEL_ONLY and FLOW_GAP evidence must be applied to each station before the KEEP/REJECT table is finalized", + "candidate counts and rejection reasons must be determined after the stricter availability rule replaces the shallow year-span heuristic" + ], + "freeze": { + "historical_window": "the ordered Columbia River candidates tested within the fixed historical Flow-availability windows for 1955 and 1956, with May-October complete-C coverage used as nearly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "所有候选 Columbia River 站点都必须下钻 availability 页，确认目标年份位于 Flow 表中且 May-October 全为 C。", + "每个站都要给出 1955、1956 两年的 KEEP / REJECT 依据，并区分 LEVEL_ONLY、FLOW_GAP 与整体年份跨度陷阱。", + "最终表格要保持题目规定的顺序与字段。" + ], + "exclusion_conditions": [ + "排除只凭“整体年份跨过 1955/1956”就保留候选站的浅层结果。", + "排除未逐站区分 Flow 可用、Level-only 和月份不完整的结果。", + "排除没有统一把深层 availability 规则施加到所有 14 个候选站的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "station_name", + "1955_MayOct", + "1956_MayOct", + "final_verdict" + ], + "rank": "use the fixed upstream-to-downstream Columbia mainstem order from the reference index, not the transient search-result order", + "year_window_fields": "the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP", + "final_verdict": "emit `KEEP` or `REJECT` exactly" + } + } +} diff --git a/data_zh/goal/wateroffice_005-g.json b/data_zh/goal/wateroffice_005-g.json new file mode 100644 index 0000000000000000000000000000000000000000..c4ba4d1f8c5f2a250c3ba071d4195493caee2eb0 --- /dev/null +++ b/data_zh/goal/wateroffice_005-g.json @@ -0,0 +1,74 @@ +{ + "task_id": "wateroffice_005-g", + "domain": "WATER_OFFICE", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "我在整理 Peace River 从 Dunvegan Bridge 到 Fifth Meridian 河段的历史日流量资料，想把这条主河道上的最终可复用站、它下游方向遇到的第一个失效站，以及浅层初筛会误判出的 provisional 末端站整理成一张三行诊断表。若目标窗口满足完整日流量条件，则记为 PASS；若目标年份只有水位记录，则记为 LEVEL_ONLY；若有日流量记录但 5–9 月中任一目标月份不完整，则记为 FLOW_GAP；若目标年份既无日流量也无水位记录，则记为 NO_TARGET_RECORD。请输出三行表，列为 rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count。", + "start_url": "https://wateroffice.ec.gc.ca/search/historical_e.html", + "output_format": "请输出三行诊断表，列为 rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count。", + "oracle_answer": "1|07HA001|FINAL_STATION|PASS|5|2\n2|07HD001|FIRST_BREAK_AFTER_FINAL|FLOW_GAP|5|2\n3|07KA002|PROVISIONAL_STATION|FLOW_GAP|5|2", + "metadata": { + "State-Gated Retrieval": [ + "只在位于 Dunvegan Bridge 与 Fifth Meridian 之间的 Peace River 主河道测站中筛选。", + "真正可用的站点必须在 availability 页满足：1966 与 1967 两年都位于 Flow 表中，且 May-September 每个月都是完整月份。", + "最终输出必须同时给出 FINAL_STATION、FIRST_BREAK_AFTER_FINAL 与 PROVISIONAL_STATION 三行，并在每行重复填写 provisional_count 与 final_count。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Peace River mainstem chain between Dunvegan Bridge and Fifth Meridian yields the shallow candidate set and the downstream breakpoint positions that need revalidation", + "each availability page yields whether 1966 and 1967 are present in the Flow or Level tables and whether May-September is complete", + "final rows are produced only after the final station, the first downstream failure, and the provisional downstream winner are all fixed under the same deep availability rule" + ], + "control_dependency": [ + "station-level target-year Flow evidence must be validated by explicit May-September completeness checks on the availability page", + "the final downstream reusable station and the first downstream failure must be determined under the same deep rule rather than from the shallow candidate screen", + "the provisional downstream winner stays in the output only as a diagnostic row after its FLOW_GAP status is confirmed on the availability page" + ], + "freeze": { + "historical_window": "the Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian, evaluated within the fixed historical 1966 and 1967 Flow-availability windows, with May-September complete-C coverage used as nearly stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在位于 Dunvegan Bridge 与 Fifth Meridian 之间的 Peace River 主河道测站中筛选。", + "真正可用的站点必须在 availability 页满足：1966 与 1967 两年都位于 Flow 表中，且 May-September 每个月都是完整月份。", + "最终输出必须同时给出 FINAL_STATION、FIRST_BREAK_AFTER_FINAL 与 PROVISIONAL_STATION 三行，并在每行重复填写 provisional_count 与 final_count。" + ], + "exclusion_conditions": [ + "排除只凭“目标年份有 Flow 记录”就认定站点可用的浅层判断。", + "排除未逐站检查 May-September 全部完整性的结果。", + "排除把 07KA002 这类 availability 深层证据显示为 FLOW_GAP 的站点标成 FINAL_STATION 的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "station_number", + "diagnosis_role", + "target_window_status", + "provisional_count", + "final_count" + ], + "rank": "emit the fixed order 1, 2, 3 for FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION", + "station_number": "use uppercase WSC station codes exactly as the Reference Index and availability pages show", + "diagnosis_role": [ + "FINAL_STATION", + "FIRST_BREAK_AFTER_FINAL", + "PROVISIONAL_STATION" + ], + "target_window_status": [ + "PASS", + "LEVEL_ONLY", + "FLOW_GAP", + "NO_TARGET_RECORD" + ], + "count_fields": "repeat the global provisional_count and final_count in every row as plain integers", + "sorting_or_selection": "emit rows in the fixed diagnostic order FINAL_STATION, FIRST_BREAK_AFTER_FINAL, PROVISIONAL_STATION" + } + } + } diff --git a/data_zh/goal/waterquality_001-g.json b/data_zh/goal/waterquality_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..c8e358a1a99ba58ed77811a29a8471beb305552b --- /dev/null +++ b/data_zh/goal/waterquality_001-g.json @@ -0,0 +1,68 @@ +{ + "task_id": "waterquality_001-g", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我正在整理里约格兰德中游既往监测资料，希望确定两处适合作为主河道污水影响哨点的监测位置。请在位于 RIO GRANDE AT EMBUDO, NM 下游、且确属 Rio Grande 主河道的监测位置中，确定两处符合条件的站点：上游站点应位于 Town of Bernalillo 污水处理厂排放口下游；下游站点应位于 Town of Bernalillo 污水处理厂排放口和 Rio Rancho No. 2 污水处理厂排放口两者下游。两处站点均须同时满足以下条件：站点本身不是排口、设施、井、运河或排水渠；站点类型标注为 River/Stream；Microbiological、Nutrient、Organics, Other 和 Physical 四类记录均完整覆盖 2015—2020 年；其中 Microbiological 和 Physical 的记录起始年份均早于 2010 年。若相应区段内有多个主河道站点符合条件，则各取沿主河道位置最靠上的一处。请按从上游到下游的顺序输出一行，格式为 <主河道站点ID>||，两段之间用英文逗号分隔。", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "请按从上游到下游的顺序输出一行，格式为 <主河道站点ID>||，两段之间用英文逗号分隔。", + "oracle_answer": "SANDIAWQ_WQX-RG003|2004|2004,SANDIAWQ_WQX-RG008|2004|2004", + "metadata": { + "State-Gated Retrieval": [ + "只从 RIO GRANDE AT EMBUDO, NM 下游的 Rio Grande 主河道监测站中找两处目标站点，并要求都已越过题目指定排放口位置。", + "站点 detail page 必须明确为 River/Stream，且 Microbiological、Nutrient、Organics, Other、Physical 四类记录完整覆盖 2015-2020，同时 Microbiological 与 Physical 的起始年都早于 2010。", + "最终两处站点按上游到下游顺序输出。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "provider/list views yield the Rio Grande mainstem candidates downstream of the Bernalillo and Rio Rancho No. 2 discharge points", + "detail pages yield flow position, object layer, characteristic-group period-of-record coverage for 2015-2020, and the Microbiological/Physical baseline years", + "final rows are produced only after the corrected downstream sentry stations are fixed and ordered from upstream to downstream" + ], + "control_dependency": [ + "provider-list stream tags are only provisional and must be corrected by detail-page mainstem and object-layer validation", + "target-window presence is insufficient until full 2015-2020 coverage is confirmed on the detail page for all four groups", + "once RG002/RG007 fail the deeper checks, the workflow must keep the discharge-point downstream root state and continue to RG003/RG008" + ], + "freeze": { + "historical_window": "Rio Grande mainstem stations downstream of the Town of Bernalillo and Rio Rancho No. 2 WWTP outfalls, validated against 2015-2020 coverage for Microbiological, Nutrient, Organics, Other, and Physical", + "current_metadata_snapshot": "2026-05-04" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只从 RIO GRANDE AT EMBUDO, NM 下游的 Rio Grande 主河道监测站中找两处目标站点，并要求都已越过题目指定排放口位置。", + "站点 detail page 必须明确为 River/Stream，且 Microbiological、Nutrient、Organics, Other、Physical 四类记录完整覆盖 2015-2020，同时 Microbiological 与 Physical 的起始年都早于 2010。", + "最终两处站点按上游到下游顺序输出。" + ], + "exclusion_conditions": [ + "排除 provider list 上浅层的 (Stream) 标签或目标窗口附近有记录、但 detail page 不能满足 flow position、object layer 或完整 period-of-record 条件的站点。", + "排除排放口、设施、井、运河或排水渠类位置。", + "排除 RG002、RG007 这类不是相应排口下游合格哨点的候选。" + ], + "normalization": { + "record_separator": ",", + "field_separator": "|", + "schema_per_record": [ + "MonitoringLocationIdentifier", + "Microbiological_start_year", + "Physical_start_year" + ], + "ordering": "emit exactly two records from upstream to downstream", + "station_id": "use uppercase MonitoringLocationIdentifier", + "year_fields": "emit four-digit years as plain integers", + "selection": { + "record_1": "the first qualifying mainstem station below the Bernalillo outfall", + "record_2": "the first qualifying mainstem station below both the Bernalillo and Rio Rancho No. 2 outfalls" + }, + "stop_condition": [ + "the Bernalillo branch stops only after its first qualifying mainstem station is fixed", + "the Rio Rancho No. 2 branch stops only after its first qualifying mainstem station is fixed", + "the two segments are emitted as one comma-joined line in upstream-to-downstream order" + ] + } + } +} diff --git a/data_zh/goal/waterquality_002-g.json b/data_zh/goal/waterquality_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..81d609a095d9650e565297dddbcee1c77234e15d --- /dev/null +++ b/data_zh/goal/waterquality_002-g.json @@ -0,0 +1,68 @@ +{ + "task_id": "waterquality_002-g", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 2, + "instruction": "我在梳理里奥格兰德河下游 2001–2010 年的变化趋势，想从位于 RIO GRANDE BELOW ANZALDUAS 下游且仍属于 HUC 13090002 的监测站点中，为 Hidalgo County 和 Cameron County 各选出一个代表站点。站点须同时满足以下条件：位于 RIO GRANDE BELOW ANZALDUAS 下游，且仍属于 HUC 13090002；站点详情页中的监测位置类型标注为 River/Stream；Microbiological、Nutrient、Organics, Other 和 Physical 四类记录均覆盖 2001—2010 年。若同一县有多个站点符合条件，则以“四类记录首次同时具备”的年份更早者为准。请按 Hidalgo、Cameron 的顺序输出一行，格式为 :|<四类同时具备的最早年份>||||，两段之间用英文逗号分隔。", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "请按 Hidalgo、Cameron 的顺序输出一行，格式为 :|<四类同时具备的最早年份>||||，两段之间用英文逗号分隔。", + "oracle_answer": "Hidalgo:TCEQMAIN-15808|1998|1998|1998|1998|1998,Cameron:TCEQMAIN-13177|1995|1981|1981|1995|1981", + "metadata": { + "State-Gated Retrieval": [ + "只在 RIO GRANDE BELOW ANZALDUAS 下游且仍属于 HUC 13090002 的监测站点中，为 Hidalgo County 与 Cameron County 各选一个代表站。", + "候选 detail page 必须为 River/Stream，且 Microbiological、Nutrient、Organics, Other、Physical 四类记录都覆盖 2001-2010。", + "若同县有多个合格站，则取四类记录首次同时齐备年份更早的站点。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the downstream root station and county split yield Hidalgo and Cameron candidate mainstem stations within HUC 13090002", + "detail pages yield River/Stream validity, the four characteristic-group start years, and the earliest year when all four groups are simultaneously present for 2001-2010 coverage", + "final rows are produced only after county-specific candidate chains are rerun under the preserved downstream root state and then ranked by common-start year" + ], + "control_dependency": [ + "the Hidalgo branch must preserve the “below TCEQMAIN-13664” downstream root state rather than flowing back to the anchor itself", + "a multi-select characteristic-group hit is only provisional until all four groups are fanned in to one MonitoringLocationIdentifier and tidal/intake conflicts are excluded on the detail page", + "county winners are valid only after late-start and non-river candidates are removed and the common-start-year tie-break is recomputed" + ], + "freeze": { + "historical_window": "stations below RIO GRANDE BELOW ANZALDUAS within HUC 13090002, split by Hidalgo and Cameron County, with Microbiological, Nutrient, Organics, Other, and Physical coverage over 2001-2010", + "current_metadata_snapshot": "2026-05-04" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在 RIO GRANDE BELOW ANZALDUAS 下游且仍属于 HUC 13090002 的监测站点中，为 Hidalgo County 与 Cameron County 各选一个代表站。", + "候选 detail page 必须为 River/Stream，且 Microbiological、Nutrient、Organics, Other、Physical 四类记录都覆盖 2001-2010。", + "若同县有多个合格站，则取四类记录首次同时齐备年份更早的站点。" + ], + "exclusion_conditions": [ + "排除在 Hidalgo 分支丢失 downstream 根状态、把起始站自身回流进候选集的结果。", + "排除把四个 Characteristic Group 一次多选就当成同时满足，而没有按站点 ID 扇入核验的结果。", + "排除 tidal、intake、late-start 等 detail page 明确冲突的站点。" + ], + "normalization": { + "record_separator": ",", + "field_separator": "|", + "schema_per_record": [ + "County:MonitoringLocationIdentifier", + "common_start_year", + "Microbiological_start_year", + "Nutrient_start_year", + "Organics_Other_start_year", + "Physical_start_year" + ], + "ordering": "emit exactly two records, with Hidalgo first and Cameron second", + "county_prefix": "use the county label in title case, followed by : and the uppercase MonitoringLocationIdentifier", + "year_fields": "emit four-digit years as plain integers", + "common_start_year": "the earliest year in which all four required groups are simultaneously present for the chosen county station", + "stop_condition": [ + "each county branch is rerun until one River/Stream station survives all four group checks", + "the county winner is fixed only after late-start and non-river candidates are excluded at detail depth", + "the two county segments are emitted on one line in the fixed Hidalgo-then-Cameron order" + ] + } + } +} diff --git a/data_zh/goal/waterquality_003-g.json b/data_zh/goal/waterquality_003-g.json new file mode 100644 index 0000000000000000000000000000000000000000..2a395f2be4331461ce72c402b56871203e5b40ea --- /dev/null +++ b/data_zh/goal/waterquality_003-g.json @@ -0,0 +1,66 @@ +{ + "task_id": "waterquality_003-g", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "我在整理 Brazos River 自 Brazos Rv at Waco, TX 向下游延伸的主干河段 2012–2018 年水质对照资料，想在 Brazos Rv at Waco, TX 下游的 Brazos River 主干河段中，为包含 Waco 在内的三个指定 HUC（12060202、12070101、12070104）各确定一处可用于 2012—2018 年长期对照的 TCEQ 监测站。候选监测位置需同时满足以下条件：位于对应 HUC 内；站点详情页中的监测位置类型标注为 River/Stream；站名仍对应 Brazos River 主干，而非支流或其他命名水体；Inorganics, Major, Non-metals、Microbiological、Nutrient、Organics, Other 和 Physical 五类记录均覆盖 2012—2018 年，具体指站点起始年不晚于 2012、结束年不早于 2018。请将三个结果按从上游到下游的顺序列出，每行格式为 ||<五类同时具备的最早年份>|||||。", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "请将三个结果按从上游到下游的顺序列出，每行格式为 ||<五类同时具备的最早年份>|||||。", + "oracle_answer": "12060202|TCEQMAIN-12037|2000|1991|2000|1991|1999|1991\n12070101|TCEQMAIN-12030|2006|1972|1972|1972|2006|1972\n12070104|TCEQMAIN-11848|1975|1974|1975|1974|1975|1974", + "metadata": { + "State-Gated Retrieval": [ + "必须保持 Waco 锚点以下的下游根状态，并在题目指定的 3 个 HUC 内寻找 Brazos 主干监测站。", + "每个候选站都要在 5 个特征组上完成分支检索与扇入，再在详情页核验 2012-2018 全时间窗覆盖与主干语义。", + "每个 HUC 只保留共同起始年最早的合格站，并输出题目要求的起始年字段。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the Waco downstream root state and three target HUC branches yield the Brazos mainstem candidate stations", + "detail pages yield true downstream position, mainstem-vs-tributary semantics, and five-group period-of-record coverage across 2012-2018", + "final rows are produced only after the three HUC branches are executed, merged by station, and ranked by the earliest year when all five groups are jointly available" + ], + "control_dependency": [ + "the workflow must preserve the downstream root state below Waco rather than reintroducing upstream stations like TCEQMAIN-12044", + "name-based waterbody matches must be validated on the detail page by excluding tributaries such as LITTLE BRAZOS RIVER and confirming full-window coverage", + "station ranking must be determined after false positives from partial-window records are removed" + ], + "freeze": { + "historical_window": "Brazos River mainstem stations downstream of the Waco anchor evaluated within the fixed historical 2012-2018 window, using the HUC 12060202 / 12070101 / 12070104 split and five characteristic groups as largely stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "必须保持 Waco 锚点以下的下游根状态，并在题目指定的 3 个 HUC 内寻找 Brazos 主干监测站。", + "每个候选站都要在 5 个特征组上完成分支检索与扇入，再在详情页核验 2012-2018 全时间窗覆盖与主干语义。", + "每个 HUC 只保留共同起始年最早的合格站，并输出题目要求的起始年字段。" + ], + "exclusion_conditions": [ + "排除丢失 Waco 以下下游根状态、把上游站带回候选集的结果。", + "排除把 LITTLE BRAZOS RIVER 等支流误当成 Brazos 主干的结果。", + "排除只因为查询窗口附近有数据、却未覆盖整个 2012-2018 窗口的站点。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "HUC", + "MonitoringLocationIdentifier", + "common_start_year", + "Inorganics_start", + "Microbiological_start", + "Nutrient_start", + "Organics_Other_start", + "Physical_start" + ], + "HUC": "preserve the HUC exactly as emitted in the source result", + "MonitoringLocationIdentifier": "preserve the monitoring-location identifier exactly, for example `TCEQMAIN-12037`", + "common_start_year": "emit the maximum of the five per-group start years", + "selection_rule": "only keep mainstem river/stream sites whose five required groups all cover the target 2012-2018 window", + "sorting_or_selection": "upstream to downstream along the mainstem" + } + } +} diff --git a/data_zh/goal/waterquality_004-g.json b/data_zh/goal/waterquality_004-g.json new file mode 100644 index 0000000000000000000000000000000000000000..bbf5e521240e423482174847d37ecd098fbdf00c --- /dev/null +++ b/data_zh/goal/waterquality_004-g.json @@ -0,0 +1,67 @@ +{ + "task_id": "waterquality_004-g", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "我在核对 Trinity River 主河道上以 FM 85 附近河段为上游端、以 Interstate 10 附近河段为下游端的 1993–2001 年有毒污染物相关水质监测资料，想沿河为上游、中游和下游三段各选一处 TCEQ 长期对照站。\n候选监测位置需同时满足以下条件：站点记录中的监测位置类型标注为 River/Stream；站名对应 Trinity River 主干，而非支流、其他命名水体或分汊河道；Inorganics, Major, Non-metals、Microbiological、Nutrient、Organics, Other、Organics, PCBs 和 Physical 六类记录均覆盖 1993—2001 年，具体指起始年不晚于 1993 且结束年不早于 2001。请按沿河从上游到下游的顺序列出三行，每行格式为 ||<六类同时具备的最早年份>||||||。", + "start_url": "https://www.waterqualitydata.us/", + "output_format": "请按沿河从上游到下游的顺序列出三行，每行格式为 ||<六类同时具备的最早年份>||||||。", + "oracle_answer": "12030105|TCEQMAIN-10924|1983|1982|1983|1982|1983|1983|1982\n12030202|TCEQMAIN-10897|1993|1969|1972|1972|1993|1974|1969\n12030203|TCEQMAIN-10892|1976|1969|1971|1972|1974|1976|1969", + "metadata": { + "State-Gated Retrieval": [ + "只在 Trinity River 主干语义成立的候选站中筛选，并要求 6 个特征组都覆盖 1993-2001。", + "必须把六个组别拆开检索并按站点 ID 扇入，再在详情页核验完整时间窗覆盖与传统毒性污染物相关组别的完整性。", + "最终每个目标分区只保留满足全部组别要求且共同起始年最优的站。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "Trinity River mainstem candidate stations are generated from the target HUC branches and six characteristic-group searches", + "detail pages yield River/Stream validity, 1993-2001 full-window coverage, and the group-specific start years needed for ranking", + "final rows are produced only after six-group fan-in and detail-page validation remove partial-group and non-mainstem false positives" + ], + "control_dependency": [ + "each of the six characteristic groups must be evaluated separately and intersected by station ID before a multi-select hit can be retained", + "station names and River/Stream tags are insufficient until the detail page confirms Trinity mainstem semantics and 1993-2001 full-window coverage", + "candidate rejection and final ranking must be determined after applying the PCBs / Organics, Other gap checks" + ], + "freeze": { + "historical_window": "Trinity River mainstem stations validated within the fixed historical 1993-2001 window, using six characteristic groups and ranking by earliest joint availability plus group start years as largely stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在 Trinity River 主干语义成立的候选站中筛选，并要求 6 个特征组都覆盖 1993-2001。", + "必须把六个组别拆开检索并按站点 ID 扇入，再在详情页核验完整时间窗覆盖与传统毒性污染物相关组别的完整性。", + "最终每个目标分区只保留满足全部组别要求且共同起始年最优的站。" + ], + "exclusion_conditions": [ + "排除把特征组多选误当成同时满足的浅层结果。", + "排除只看站名和 River/Stream，不核验 1993-2001 全窗口覆盖的结果。", + "排除忽略 PCBs 或 Organics, Other 缺失的站点。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "HUC", + "MonitoringLocationIdentifier", + "common_start_year", + "Inorganics_start", + "Microbiological_start", + "Nutrient_start", + "Organics_Other_start", + "Organics_PCBs_start", + "Physical_start" + ], + "HUC": "preserve the HUC exactly as emitted in the source result", + "MonitoringLocationIdentifier": "preserve the monitoring-location identifier exactly, for example `TCEQMAIN-10924`", + "common_start_year": "emit the maximum of the six per-group start years", + "selection_rule": "only keep mainstem river/stream sites whose six required groups all cover the target window", + "sorting_or_selection": "upstream to downstream along the mainstem" + } + } +} diff --git a/data_zh/goal/waterquality_005-g.json b/data_zh/goal/waterquality_005-g.json new file mode 100644 index 0000000000000000000000000000000000000000..a0a2dbaedfa3877d595f942801287220b49ae72e --- /dev/null +++ b/data_zh/goal/waterquality_005-g.json @@ -0,0 +1,68 @@ +{ + "task_id": "waterquality_005-g", + "domain": "WATER_QUALITY_PORTAL", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 9, + "instruction": "我在整理 Neches River 下游 1978–1984 年的综合水质资料，想把离 NECHES RIVER AT CR 4915 最近、且仍代表 Neches River 内陆主河道的那个合格 TCEQ 对照站的九类 Characteristic Group 起始年份整理成表。请输出一张 9 行表，列为 rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year，行顺序固定为题目指定的九类 Characteristic Group 顺序。", + "start_url": "https://www.waterqualitydata.us/provider/STORET/TCEQMAIN/TCEQMAIN-10598/", + "output_format": "请输出一张 9 行表，列为 rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year。", + "oracle_answer": "1|TCEQMAIN-10580|12020003|Hardin County|Biological, Algae, Phytoplankton|1972|1977\n2|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Major, Non-metals|1971|1977\n3|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Minor, Metals|1974|1977\n4|TCEQMAIN-10580|12020003|Hardin County|Microbiological|1972|1977\n5|TCEQMAIN-10580|12020003|Hardin County|Nutrient|1972|1977\n6|TCEQMAIN-10580|12020003|Hardin County|Organics, Other|1974|1977\n7|TCEQMAIN-10580|12020003|Hardin County|Organics, PCBs|1974|1977\n8|TCEQMAIN-10580|12020003|Hardin County|Organics, Pesticide|1977|1977\n9|TCEQMAIN-10580|12020003|Hardin County|Physical|1971|1977", + "metadata": { + "State-Gated Retrieval": [ + "只在 NECHES RIVER AT CR 4915 下游、且仍能代表 Neches River 内陆主河道的 TCEQ 监测站中筛选。", + "候选站必须在 9 个 Characteristic Group 上都覆盖 1978-1984，并在 detail page 中继续满足 River/Stream、非湖库、非 Sabine-Neches 出口边界河段条件。", + "最终输出必须围绕唯一获胜站点，按固定的九类 Characteristic Group 顺序逐行列出 group_start_year 与 common_start_year。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "the downstream root state from NECHES RIVER AT CR 4915 yields candidate inland mainstem stations across successive downstream HUCs", + "detail pages yield River/Stream validity, inland-vs-boundary semantics, and nine-group period-of-record coverage across 1978-1984", + "final rows are produced only after one winning station survives the inland-mainstem and nine-group fan-in checks and its nine group start years are emitted in the required order" + ], + "control_dependency": [ + "the nearest downstream mainstem station remains provisional until all nine characteristic groups are split, rerun, and intersected by station ID", + "the downstream search must continue to the next mainstem HUC when the first branch fails the nine-group coverage gate", + "location semantics remain valid only after detail-page exclusion of lake/reservoir and Sabine-Neches boundary stations" + ], + "freeze": { + "historical_window": "Neches River inland mainstem stations downstream of NECHES RIVER AT CR 4915, validated within the fixed 1978-1984 window against nine characteristic groups as largely stable reference information" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只在 NECHES RIVER AT CR 4915 下游、且仍能代表 Neches River 内陆主河道的 TCEQ 监测站中筛选。", + "候选站必须在 9 个 Characteristic Group 上都覆盖 1978-1984，并在 detail page 中继续满足 River/Stream、非湖库、非 Sabine-Neches 出口边界河段条件。", + "最终输出必须围绕唯一获胜站点，按固定的九类 Characteristic Group 顺序逐行列出 group_start_year 与 common_start_year。" + ], + "exclusion_conditions": [ + "排除只凭“最近下游主干站”语义就保留 TCEQMAIN-10591 的浅层结果。", + "排除没有把 9 个 Characteristic Group 拆开检索并按站点 ID 扇入核验的结果。", + "排除位于湖库水体或 Sabine-Neches 出口边界河段的站点。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "omit the header row; emit data rows only", + "schema": [ + "rank", + "MonitoringLocationIdentifier", + "HUC", + "County", + "characteristic_group", + "group_start_year", + "common_start_year" + ], + "rank": "emit 1 through 9 in the fixed characteristic-group order required by the task", + "MonitoringLocationIdentifier": "use uppercase MonitoringLocationIdentifier", + "HUC": "emit the HUC as an 8-digit string with no separators", + "County": "use the county name exactly as shown on the detail page", + "characteristic_group": "preserve the group label exactly as listed in the task", + "year_fields": "emit four-digit years as plain integers", + "common_start_year": "repeat the earliest year in which all nine required groups are simultaneously present for the chosen station", + "sorting_or_selection": "emit rows in the fixed nine-group order stated in the task" + } + } +} diff --git a/data_zh/goal/wonder_001-g.json b/data_zh/goal/wonder_001-g.json new file mode 100644 index 0000000000000000000000000000000000000000..565f6edaf31eae74bf048b79bbf0da38327993a9 --- /dev/null +++ b/data_zh/goal/wonder_001-g.json @@ -0,0 +1,64 @@ +{ + "task_id": "wonder_003-g", + "domain": "CDC_WONDER", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 8, + "instruction": "我想为一页回顾 2020 年美国居家分娩变化的公共卫生简报，找出当年全体产妇居家分娩比例较 2019 年同月上升至少 25% 的月份，并同时给出这些月份在非西班牙裔黑人产妇和西班牙裔产妇中的 2020 年比例及相对变化。请按日历月份顺序输出多行管道分隔表，表头固定为 month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel；所有数值直接写数字，不加百分号。", + "start_url": "https://wonder.cdc.gov/natality-expanded-current.html", + "output_format": "请按日历月份顺序输出多行管道分隔表，表头固定为 month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel；所有数值直接写数字，不加百分号。", + "oracle_answer": "month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel\nMay|1.03|1.49|45|0.74|54|0.55|57\nJune|1.04|1.31|26|0.66|20|0.48|30\nJuly|1.03|1.30|26|0.68|42|0.48|30\nAugust|1.02|1.29|26|0.69|50|0.48|26\nSeptember|1.01|1.31|30|0.73|43|0.54|54\nOctober|1.00|1.28|28|0.75|50|0.47|27\nNovember|0.99|1.30|31|0.73|43|0.55|67\nDecember|0.92|1.28|39|0.80|63|0.53|61", + "metadata": { + "State-Gated Retrieval": [ + "先按日历月份比较 2019 年与 2020 年全体产妇的居家分娩比例，只保留 2020 年较 2019 年同月上升至少 25% 的月份。", + "居家分娩分子必须使用完整 home 类别而不是单独 Home intended。", + "对这些月份，再补充 2020 年 Black non-Hispanic 与 Hispanic 产妇的居家分娩比例及相对 2019 年同月的变化。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "monthly natality queries yield the 2019 vs 2020 all-mother home-birth rates and the candidate month set", + "follow-up race/ethnicity queries yield 2020 Black non-Hispanic and Hispanic home-birth rates plus their same-month changes versus 2019", + "final rows are produced only after qualifying months are determined from rate growth and the resulting month set is reused for both subgroup backfill chains" + ], + "control_dependency": [ + "month selection must be based on relative rate increase rather than counts alone", + "the home-birth numerator must use Residence or an equivalent full-home measure rather than Home intended alone before downstream subgroup queries run", + "subgroup columns must be generated from the resulting month set rather than appended to earlier rows" + ], + "freeze": { + "historical_window": "2019 and 2020 U.S. natality monthly home-birth rates for all mothers, Black non-Hispanic mothers, and Hispanic mothers" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "先按日历月份比较 2019 年与 2020 年全体产妇的居家分娩比例，只保留 2020 年较 2019 年同月上升至少 25% 的月份。", + "居家分娩分子必须使用完整 home 类别而不是单独 Home intended。", + "对这些月份，再补充 2020 年 Black non-Hispanic 与 Hispanic 产妇的居家分娩比例及相对 2019 年同月的变化。" + ], + "exclusion_conditions": [ + "排除把“比例上升至少 25%”误读为“人数上升至少 25%”的月份行集。", + "排除只用 Home intended 单类而不是完整 home numerator 的结果。", + "排除在错误月份集上补 subgroup 列的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row `month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel`", + "schema": [ + "month", + "all_2019", + "all_2020", + "all_rel", + "black_2020", + "black_rel", + "hispanic_2020", + "hispanic_rel" + ], + "month": "use the English month name and keep calendar order", + "numeric_fields": "all numeric outputs are plain numbers without a percent sign", + "relative_change_fields": "all_rel, black_rel, and hispanic_rel are emitted as integer percentages without the `%` character" + } + } +} diff --git a/data_zh/goal/wonder_002-g.json b/data_zh/goal/wonder_002-g.json new file mode 100644 index 0000000000000000000000000000000000000000..a1f9c21983576bacae9b0f80dbcb7c97ef258b31 --- /dev/null +++ b/data_zh/goal/wonder_002-g.json @@ -0,0 +1,64 @@ +{ + "task_id": "wonder_004-g", + "domain": "CDC_WONDER", + "autonomy_type": "ordered table", + "oracle_output_cardinality": 3, + "instruction": "我想在 2021 年美国按母亲种族和西班牙裔来源划分的人群中，找出所有在统计报告中单独列示、婴儿死亡率高于全美总体水平，且能够明确确定首位死因的群体。对每个符合条件的群体，请列出全年婴儿死亡率、出生后不满 28 天的新生儿期死亡率、出生后 28 天及以上的后新生儿期死亡率、该群体的首位死因、该死因率，以及这一死因在全体婴儿死因中的排名。请按全年婴儿死亡率从高到低输出多行管道分隔表，格式为 group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank。", + "start_url": "https://wonder.cdc.gov/lbd-current-expanded.html", + "output_format": "请按全年婴儿死亡率从高到低输出多行管道分隔表，格式为 group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank。", + "oracle_answer": "group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank\nBlack non-Hispanic|10.55|6.35|4.19|Short gestation and low birth weight|196.4|2\nAmerican Indian or Alaska Native non-Hispanic|7.46|3.83|3.67|Congenital malformations|134.0|1\nPuerto Rican Hispanic|6.05|3.93|2.13|Short gestation and low birth weight|108.9|2", + "metadata": { + "State-Gated Retrieval": [ + "只保留在 2021 年美国婴儿死亡统计中单独列示、全年 infant mortality rate 高于全美总体水平、且首位死因能够明确识别的群体。", + "对每个合格群体，都要给出 infant rate、neonatal rate、postneonatal rate、top cause、cause rate 以及该死因在全体婴儿死因中的排名。", + "首位死因必须按群体自己的 leading-cause 查询确定，并结合 notes / reliability 标记核验可用性。" + ], + "dependency_type": "Data + Control", + "intra_chain": true, + "inter_chain": true, + "data_dependency": [ + "infant-mortality queries yield group-level overall, neonatal, and postneonatal rates for reportable mother race/Hispanic-origin groups", + "leading-cause queries and reliability notes yield each eligible group's top cause, cause-specific rate, and U.S. rank", + "final rows are produced only after the eligible-group set is rebuilt using both overall-rate and cause-specific-identifiability criteria" + ], + "control_dependency": [ + "groups above the U.S. overall rate cannot be accepted until cause-specific reliability checks are run, which removes NHOPI", + "leading cause must be queried at the group level rather than inherited from an all-infants cause table", + "the cause-rate multiplier must be defined as per 100,000 live births before downstream ranking/output" + ], + "freeze": { + "historical_window": "2021 U.S. infant mortality by mother race and Hispanic origin, including the group-level leading-cause tables and reliability notes" + }, + "answer_type": "multi-row ordered table" + }, + "rubric": { + "inclusion_conditions": [ + "只保留在 2021 年美国婴儿死亡统计中单独列示、全年 infant mortality rate 高于全美总体水平、且首位死因能够明确识别的群体。", + "对每个合格群体，都要给出 infant rate、neonatal rate、postneonatal rate、top cause、cause rate 以及该死因在全体婴儿死因中的排名。", + "首位死因必须按群体自己的 leading-cause 查询确定，并结合 notes / reliability 标记核验可用性。" + ], + "exclusion_conditions": [ + "排除虽然全年死亡率高于全美总体、但因 cause-specific reliability 问题不能明确给出首位死因的群体。", + "排除只从全体婴儿死因表继承 top cause、没有做群体级 leading-cause 查询的结果。", + "排除 cause_rate 使用错误 rate multiplier、未按每 100,000 live births 口径读取的结果。" + ], + "normalization": { + "field_separator": "|", + "record_separator": "\n", + "header_row": "required literal first row `group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank`", + "schema": [ + "group", + "infant_rate", + "neonatal_rate", + "postneonatal_rate", + "top_cause", + "cause_rate", + "us_rank" + ], + "sorting_or_selection": "infant_rate descending", + "rate_fields": "infant_rate, neonatal_rate, and postneonatal_rate are per 1,000 live births; cause_rate is per 100,000 live births, but all four are emitted as plain numbers without unit text", + "top_cause": "emit the short cause label used in the oracle, not an expanded prose description", + "us_rank": "emit the integer rank of that same cause in the overall infant leading-cause list" + } + } +} diff --git a/goal.jsonl b/goal.jsonl new file mode 100644 index 0000000000000000000000000000000000000000..f16d9205ec56b665fc26f56f97071ea03661e937 --- /dev/null +++ b/goal.jsonl @@ -0,0 +1,50 @@ +{"task_id":"arxiv_001-g","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"I am organizing the research trajectory of dataset distillation and dataset condensation on arXiv from 2019 to 2021, aiming to identify machine learning papers that discuss using a small set of synthetic training data to replace large-scale training sets. From the 2019–2021 arXiv records, retain only entries whose primary category is Machine Learning; if a paper is only cross-listed into Machine Learning by another primary category, do not include it. Additionally, these papers must have a revision within the next calendar year after the initial submission, and the current record must still clearly indicate a subsequent publication venue. Output a table sorted by v1 submitted in ascending order, with columns: arXiv ID, term family, cue location, v1 submitted, first next-year version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying entries exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Output a table sorted by v1 submitted in ascending order, with columns: arXiv ID, term family, cue location, v1 submitted, first next-year version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying entries exist, output NONE.","oracle_answer":"arXiv ID|term family|cue location|v1 submitted|first next-year version|date of that version|primary category|publication-trail source|current publication clue\n1910.02551|Distillation|Title|2019-10-06|v3|2020-05-05|cs.LG|Related DOI|10.1109/IJCNN52387.2021.9533769\n2011.00050|Distillation|Abstract-only|2020-10-30|v2|2021-03-02|cs.LG|Comments|Accepted to ICLR 2021\n2107.13034|Distillation|Title|2021-07-27|v3|2022-01-17|cs.LG|Comments|NeurIPS 2021\n2110.04181|Condensation|Title|2021-10-08|v2|2022-04-21|cs.LG|Journal reference|Proceedings of the IEEE/CVF Winter Conference on Applications of Computer Vision 2023 (WACV)","metadata":{"State-Gated Retrieval":["Only include arXiv records where v1 submitted falls between 2019-01-01 and 2021-12-31.","The title or abstract must explicitly use terms from the dataset distillation or dataset condensation family, and the semantics must refer to replacing large-scale training sets with a small set of synthetic training data.","The current primary category must be cs.LG; if a paper is only cross-listed into Machine Learning by another primary category, do not include it.","The paper must have a revision within the next calendar year after the initial submission, and the current record must still clearly indicate a subsequent publication venue."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Root searches yield candidate arXiv IDs","Each candidate abstract page yields primary category, v1 date, first next-year version, cue location, and publication-trail source","Answer rows are produced only after deduplication and detail-page validation"],"control_dependency":["Records must be filtered by original submission year, with per-record validation that a version in the next calendar year exists","Cross-listed-only hits must be excluded, and the current primary category must be validated on abstract pages","Searches must cover both Title and Abstract because valid distillation hits can appear only in the abstract","Topic matches without a current publication trail still fail until the Comments, Journal reference, or Related DOI field is checked on the abstract page"],"freeze":{"historical_window":"v1 year in {2019, 2020, 2021}"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only include arXiv records where v1 submitted falls between 2019-01-01 and 2021-12-31.","The title or abstract must explicitly use terms from the dataset distillation or dataset condensation family, and the semantics must refer to replacing large-scale training sets with a small set of synthetic training data.","The current primary category must be cs.LG; if a paper is only cross-listed into Machine Learning by another primary category, do not include it.","The paper must have a revision within the next calendar year after the initial submission, and the current record must still clearly indicate a subsequent publication venue."],"exclusion_conditions":["Exclude records whose current primary category is not cs.LG and that are only cross-listed to cs.LG.","Exclude records where the title or abstract contains distillation/condensation terms but does not correspond to the dataset distillation or dataset condensation research line.","Exclude records that have no version revision in the next calendar year, or whose current record contains no clearly visible publication clue."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"required literal first row shown in the oracle","schema":["arXiv ID","term family","cue location","v1 submitted","first next-year version","date of that version","primary category","publication-trail source","current publication clue"],"dedup_key":"bare arXiv ID without version suffix","date_format":"YYYY-MM-DD","term_family_extraction":{"allowed_families":["Distillation","Condensation"],"tie_break":"if both families appear, prefer the title hit; if both appear only in the abstract, keep the first abstract occurrence"},"cue_location":{"Title":"qualifying cue appears only in the title","Abstract-only":"qualifying cue appears only in the abstract","Title + Abstract":"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name"},"publication_trail_source":["Comments","Journal reference","Related DOI"],"current_publication_clue":"keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue","sorting_or_selection":{"primary":"v1 submitted ascending","secondary":"arXiv ID ascending"},"stop_condition":["all four corrected result pages are exhausted","all unique candidate IDs are opened to abstract-page depth","for every surviving candidate, the abstract page, current browse context, and publication-trail fields are checked before emitting the final ordered table"]}}} +{"task_id":"arxiv_002-g","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":10,"instruction":"I am compiling a reading list of 2022 research on reasoning prompting for large language models. From arXiv papers whose first version (v1) was submitted in 2022, I want to select those whose title or abstract explicitly focuses on chain-of-thought or self-consistency reasoning and whose primary category is Computation and Language. Candidate papers must also have a version update in 2023, and the current arXiv record's Comments field must directly indicate a subsequent publication venue. Output a table sorted by the date of each paper's earliest 2023 version in ascending order, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2023 version, date of that version, primary category, publication clue. If no qualifying papers exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Output a table sorted by the date of each paper's earliest 2023 version in ascending order, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2023 version, date of that version, primary category, publication clue. If no qualifying papers exist, output NONE.","oracle_answer":"arXiv ID|cue family|cue location|v1 submitted|first 2023 version|date of that version|primary category|publication clue\n2210.01240|Chain-of-thought|Title + Abstract|2022-10-03|v2|2023-01-25|cs.CL|Published as a conference paper at ICLR 2023\n2205.11916|Chain-of-thought|Abstract-only|2022-05-24|v4|2023-01-29|cs.CL|Accepted to NeurIPS2022\n2203.11171|Self-consistency; Chain-of-thought|Title + Abstract|2022-03-21|v4|2023-03-07|cs.CL|Published at ICLR 2023; camera ready version at ICLR 2023\n2210.03629|Chain-of-thought|Abstract-only|2022-10-06|v3|2023-03-10|cs.CL|v3 is the ICLR camera ready version\n2210.03350|Chain-of-thought|Abstract-only|2022-10-07|v2|2023-05-23|cs.CL|To appear at Findings of EMNLP 2023\n2212.10001|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-01|cs.CL|ACL-23 Camera Ready\n2212.08061|Chain-of-thought|Abstract-only|2022-12-15|v2|2023-06-04|cs.CL|ACL 2023 Main Conference\n2212.10071|Chain-of-thought|Abstract-only|2022-12-20|v2|2023-06-13|cs.CL|ACL 2023 camera-ready\n2212.10509|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-23|cs.CL|ACL'23 Camera Ready\n2211.12588|Chain-of-thought; Self-consistency|Abstract-only|2022-11-22|v4|2023-10-23|cs.CL|Published at TMLR 2023","metadata":{"State-Gated Retrieval":["Only retain arXiv papers whose v1 was submitted in 2022.","The title or abstract must explicitly contain cues related to chain-of-thought or self-consistency.","The current primary category must be cs.CL; do not include records that are only cross-listed from other primary categories.","The paper must have a version update in 2023, and the current Comments field must clearly indicate a subsequent publication venue."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["root searches yield candidate arXiv IDs","each candidate abstract page yields primary category, v1 date, first 2023 version, comments/publication clue","answer rows are produced only after deduplication and detail-page validation"],"control_dependency":["searches must cover both Title and Abstract fields because valid rows can appear only in the abstract","cross-listed hits whose primary category is not cs.CL must be excluded, and the primary category must be validated on the abstract page","topic-matched hits must be validated against a current Comments publication clue before they can be accepted","2023 candidates must be identified by original submission year and full version-history checks, rather than by latest-date proxies"],"freeze":{"historical_window":"v1 submitted in 2022; version-history event in 2023"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only retain arXiv papers whose v1 was submitted in 2022.","The title or abstract must explicitly contain cues related to chain-of-thought or self-consistency.","The current primary category must be cs.CL; do not include records that are only cross-listed from other primary categories.","The paper must have a version update in 2023, and the current Comments field must clearly indicate a subsequent publication venue."],"exclusion_conditions":["Exclude records whose current primary category is not cs.CL, even if they appear in relevant search results.","Exclude records that contain only vague abbreviations or weak related hints, but whose title and abstract lack clear CoT/self-consistency semantics.","Exclude records that have no 2023 version update, or whose current record lacks a direct publication clue."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"required literal first row shown in the oracle","schema":["arXiv ID","cue family","cue location","v1 submitted","first 2023 version","date of that version","primary category","publication clue"],"dedup_key":"bare arXiv ID without version suffix","date_format":"YYYY-MM-DD","cue_family":["Chain-of-thought","Self-consistency"],"cue_location":{"Title":"qualifying cue appears only in the title","Abstract-only":"qualifying cue appears only in the abstract","Title + Abstract":"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name"},"publication_clue":{"source":"Comments field only","extraction":"keep the shortest phrase that still preserves the current publication-status clue"},"sorting_or_selection":{"primary":"date of the earliest 2023 version ascending","secondary":"arXiv ID ascending"},"stop_condition":["all corrected result pages are exhausted","all unique candidate IDs are opened to abstract-page depth","for every surviving candidate, the current browse context, Comments field, and full Submission history are checked before emitting the final ordered table"]}}} +{"task_id":"arxiv_003-g","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"I am compiling a reading list of early vision Transformer papers. From arXiv papers whose first version (v1) was submitted in Q4 2020, I want to select those whose title or abstract explicitly uses vision- or image-related Transformer terminology and whose primary category is Computer Vision and Pattern Recognition. Additionally, eligible papers must have had at least one updated version in 2021, and their current arXiv record must still directly indicate a subsequent publication venue. Output a table sorted in ascending order by the date of each paper's earliest 2021 version, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying papers exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Output a table sorted in ascending order by the date of each paper's earliest 2021 version, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying papers exist, output NONE.","oracle_answer":"arXiv ID|cue family|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication-trail source|current publication clue\n2101.01097|Vision Transformer|Abstract-only|2020-12-30|v2|2021-01-08|cs.CV|Journal reference|IEEE Int. Conf. on Image Processing (ICIP) 2021\n2012.12556|Visual Transformer; Vision Transformer|Title + Abstract|2020-12-23|v2|2021-01-15|cs.CV|Comments; Related DOI|Accepted by TPAMI 2022; 10.1109/TPAMI.2022.3152247\n2012.00364|Image Processing Transformer|Title + Abstract|2020-12-01|v3|2021-05-28|cs.CV|Comments|CVPR 2021\n2011.08019|Vision Transformer|Title + Abstract|2020-11-16|v2|2021-06-02|cs.CV|Comments|Accepted for Publication in IJCB2021\n2010.11929|Vision Transformer|Abstract-only|2020-10-22|v2|2021-06-03|cs.CV|Comments|ICLR camera-ready version","metadata":{"State-Gated Retrieval":["Only include arXiv papers whose v1 submission date falls in Q4 2020.","The title or abstract must explicitly contain vision- or image-related Transformer terminology.","The current primary category must be cs.CV.","The paper must have had an updated version in 2021, and the current record must still directly indicate a subsequent publication venue."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["root searches yield candidate arXiv IDs","candidate abstract pages yield v1 submitted date, first 2021 version, primary category, cue location, and publication-trail source","answer rows depend on deduplication plus detail-page validation"],"control_dependency":["searches must cover both Title and Abstract because valid positives can appear only in the abstract","candidate eligibility must be determined by the original-submission date window rather than by arXiv-ID or announcement intuition","candidate filtering must use full Submission-history validation rather than most-recent-submission filtering","searches must use the broader semantic cue state rather than a ViT-only entry point, because ViT-only hits can be false positives","publication-trail false positives still require Comments / Journal reference / Related DOI validation before final inclusion"],"freeze":{"historical_window":"v1 submitted from 2020-10-01 through 2020-12-31; version-history event in 2021"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only include arXiv papers whose v1 submission date falls in Q4 2020.","The title or abstract must explicitly contain vision- or image-related Transformer terminology.","The current primary category must be cs.CV.","The paper must have had an updated version in 2021, and the current record must still directly indicate a subsequent publication venue."],"exclusion_conditions":["Exclude records whose current primary category is not cs.CV and are only cross-listed.","Exclude records that contain only weak cues such as Transformer/ViT but lack explicit vision- or image-related terminology in the title and abstract.","Exclude records that had no version update in 2021 or whose current record contains no direct publication clue."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"required literal first row shown in the oracle","schema":["arXiv ID","cue family","cue location","v1 submitted","first 2021 version","date of that version","primary category","publication-trail source","current publication clue"],"dedup_key":"bare arXiv ID without version suffix","date_format":"YYYY-MM-DD","cue_family_extraction":"record every qualifying family actually present and join multiple families with `; ` in the emitted field","cue_location":{"Title":"qualifying cue appears only in the title","Abstract-only":"qualifying cue appears only in the abstract","Title + Abstract":"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name"},"publication_trail_source":["Comments","Journal reference","Related DOI"],"current_publication_clue":"keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue","sorting_or_selection":{"primary":"date of the earliest 2021 version ascending","secondary":"arXiv ID ascending"},"stop_condition":["all corrected result pages are exhausted","all unique candidate IDs are opened to abstract-page depth","for every surviving candidate, the abstract page, current browse context, Comments field, Journal reference, Related DOI, and full Submission history are checked before emitting the final ordered table"]}}} +{"task_id":"arxiv_004-g","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"From arXiv papers whose first version was submitted in the first half of 2020, select those whose primary category is Machine Learning and whose title or abstract clearly focuses on certified robustness defenses. The research subject of each candidate paper must explicitly involve at least one of the following cues: randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor/poisoning, or partition aggregation. Additionally, these papers must have a version update in 2021, and the current arXiv record must still show a formal publication or acceptance destination. Output a table sorted in ascending order by the date of each paper's earliest 2021 version, with columns: arXiv ID, defense family, threat/topic cue, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Output a table sorted in ascending order by the date of each paper's earliest 2021 version, with columns: arXiv ID, defense family, threat/topic cue, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.","oracle_answer":"arXiv ID|defense family|threat/topic cue|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication clue\n2002.10733|De-randomized smoothing; Randomized smoothing|patch attacks|Title + Abstract|2020-02-25|v3|2021-01-08|cs.LG|NeurIPS 2020\n2006.04062|Smoothed classifiers; Randomized smoothing|certified L2 robustness|Title + Abstract|2020-06-07|v4|2021-01-08|cs.LG|NeurIPS 2020\n2003.08904|RAB; Randomized smoothing|backdoor attacks|Title + Abstract|2020-03-19|v4|2021-02-26|cs.LG|IEEE Symposium on Security and Privacy 2023\n2006.14768|Deep Partition Aggregation|general poisoning attacks; label-flipping poisoning attacks|Title + Abstract|2020-06-26|v2|2021-03-18|cs.LG|ICLR 2021\n2002.12398|Transformation-specific smoothing; Randomized smoothing|semantic transformations|Title + Abstract|2020-02-27|v4|2021-09-17|cs.LG|2021 ACM SIGSAC Conference on Computer and Communications Security (CCS '21)","metadata":{"State-Gated Retrieval":["Only include arXiv papers with v1 submitted between 2020-01-01 and 2020-06-30.","The title or abstract must clearly focus on randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor or poisoning attacks, or partition aggregation.","The current primary category must be cs.LG.","Must have a version update in 2021, and the current record must show a formal publication or acceptance destination."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["root searches yield candidate arXiv IDs","candidate abstract pages yield v1 date, primary category, full Submission history, cue location, and current publication clue","final rows depend on deduplication plus detail-page validation"],"control_dependency":["candidate filtering must use the original-submission window together with full 2021 version-history validation, because valid rows can have later newest versions","cross-listed hits whose primary category is not the target category must be excluded, with category validation on detail pages","searches must cover the broader certified-defense family, including partition-aggregation and backdoor/poisoning variants, rather than smoothing-only entries","topic+venue hits must be confirmed by detail-history validation that a 2021 version actually exists"],"freeze":{"historical_window":"v1 submitted from 2020-01-01 through 2020-06-30; version-history event in 2021"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only include arXiv papers with v1 submitted between 2020-01-01 and 2020-06-30.","The title or abstract must clearly focus on randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor or poisoning attacks, or partition aggregation.","The current primary category must be cs.LG.","Must have a version update in 2021, and the current record must show a formal publication or acceptance destination."],"exclusion_conditions":["Exclude records whose current primary category is not cs.LG, even if semantically related.","Exclude records that are only broadly related to robustness, defense, or backdoor/poisoning but do not meet the required certified-defense semantics.","Exclude records without a 2021 version update or without a current publication clue."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"required literal first row shown in the oracle","schema":["arXiv ID","defense family","threat/topic cue","cue location","v1 submitted","first 2021 version","date of that version","primary category","publication clue"],"dedup_key":"bare arXiv ID without version suffix","date_format":"YYYY-MM-DD","defense_family_extraction":"record every qualifying defense family actually present and join multiple families with `; ` in the emitted field","threat_topic_cue":"keep the shortest qualifying threat or topic cue that justifies inclusion","cue_location":{"Title":"qualifying cue appears only in the title","Abstract-only":"qualifying cue appears only in the abstract","Title + Abstract":"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name"},"publication_clue":"keep the shortest phrase that still preserves venue or publication-status information","sorting_or_selection":{"primary":"date of the earliest 2021 version ascending","secondary":"arXiv ID ascending"},"stop_condition":["all corrected result pages are exhausted","all unique candidate IDs are opened to abstract-page depth","for every surviving candidate, the abstract page, current browse context, Comments field, and full Submission history are checked before emitting the final ordered table"]}}} +{"task_id":"census_001-g","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":20,"instruction":"Using the 2014–2018 American Community Survey 5-year estimates, identify North Carolina counties that simultaneously exhibit insufficient internet access, a high share of seniors living alone, limited transportation options, and low income. Candidate counties must meet all of the following conditions: at least 4,000 households with no internet access; a share of households with no internet access higher than the statewide share; a share of households with a householder aged 65 or older living alone higher than the statewide share; a share of households with no vehicle higher than the statewide share; and a median household income lower than the statewide median. All statewide comparisons must use the North Carolina statewide estimate from the same data release. List all qualifying counties in a single line ordered alphabetically by county name. Each county should be formatted as County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome, with counties separated by commas. Percentage fields should retain three decimal places without a percent sign.","start_url":"https://www.census.gov/data.html","output_format":"List all qualifying counties in a single line ordered alphabetically by county name. Each county should be formatted as County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome, with counties separated by commas. Percentage fields should retain three decimal places without a percent sign.","oracle_answer":"Beaufort County|5988|30.986|16.083|7.664|43688,Bladen County|4194|30.026|13.681|10.417|32378,Cleveland County|11599|31.449|12.469|7.825|40393,Columbus County|7371|33.045|15.148|7.958|36398,Duplin County|7574|34.773|14.370|7.424|38850,Edgecombe County|7454|34.879|13.720|11.225|35516,Halifax County|7575|35.873|14.657|11.565|34251,Lenoir County|4923|21.292|15.614|11.699|38387,Nash County|8617|23.467|13.597|7.917|48362,Richmond County|5193|28.001|13.706|9.269|36091,Robeson County|19814|43.103|11.312|9.854|33679,Rockingham County|9938|26.714|14.166|7.164|42490,Rutherford County|7583|28.783|16.033|6.335|40347,Sampson County|8216|34.907|14.088|7.686|39068,Scotland County|4971|37.909|13.910|11.470|35617,Surry County|7595|26.203|13.762|6.779|41068,Vance County|5131|30.444|12.347|11.600|37282,Wayne County|9709|20.163|11.742|8.456|42192,Wilkes County|7046|24.849|14.773|5.992|40829,Wilson County|7652|23.817|13.322|9.540|42850","metadata":{"State-Gated Retrieval":["Use only the 2014-2018 American Community Survey 5-year estimates for North Carolina counties, and use the North Carolina statewide value from the same release as the comparison baseline.","Retain only counties with at least 4,000 households with no internet access, and where the share of households with no internet access, the share of households with a householder aged 65 or older living alone, and the share of households with no vehicle are all higher than the statewide shares, while the median household income is lower than the statewide median.","Output the final results in alphabetical order by county name, retaining the six required fields."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the 2014-2018 ACS 5-year product and North Carolina county geography yield the full county candidate set plus the statewide baseline row","the relevant ACS tables yield no-internet households, senior-living-alone share, no-vehicle share, and median household income for each county and the state baseline","final rows are produced only after the 5-year product/geography setup is fixed consistently and the full county filtering chain is executed from B28002 through the downstream filters"],"control_dependency":["the 2018 ACS 5-year Detailed Tables product must be used instead of the 2018 ACS 1-year product","county coverage must be established under one consistent product-and-geography setup rather than by piecemeal fixes within the current table","all downstream county comparisons must use the same 5-year statewide baseline and the same all-counties geography"],"freeze":{"historical_window":"2014-2018 American Community Survey 5-year estimates for North Carolina counties, using the North Carolina statewide row from the same release as the comparison baseline"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Use only the 2014-2018 American Community Survey 5-year estimates for North Carolina counties, and use the North Carolina statewide value from the same release as the comparison baseline.","Retain only counties with at least 4,000 households with no internet access, and where the share of households with no internet access, the share of households with a householder aged 65 or older living alone, and the share of households with no vehicle are all higher than the statewide shares, while the median household income is lower than the statewide median.","Output the final results in alphabetical order by county name, retaining the six required fields."],"exclusion_conditions":["Exclude results that incorrectly use the 2018 ACS 1-Year Estimates Detailed Tables or any data other than the 2014-2018 5-year release.","Exclude results that do not use the North Carolina statewide row from the same release as the comparison baseline.","Exclude any county that does not satisfy every threshold or statewide comparison condition."],"normalization":{"field_separator":"|","record_separator":",","schema":["County","NoInternetHH","NoInternetRatePct","SeniorLivingAloneSharePct","NoVehicleRatePct","MedianIncome"],"county":"use the county display name including the word `County` and excluding a trailing state suffix","dedup_key":"county FIPS / GEOID","percentage_fields":"all percentage fields are plain numbers with exactly three decimal places and no percent sign","numeric_fields":"household counts and median income are emitted as plain integers without commas","sorting_or_selection":"county name alphabetical ascending","stop_condition":["the North Carolina statewide threshold is fixed once from the designated table","all 100 North Carolina counties are covered under the same table/product settings","every surviving county is validated against all four required tables before emission"]}}} +{"task_id":"census_002-g","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"Using the 2015–2019 American Community Survey 5-year estimates, identify New Mexico counties that simultaneously exhibit large renter populations, notable language barriers, limited internet access, transportation disadvantages, low income, and rental stress. These counties are intended to assess which areas were unsuitable for replacing in-person tenant legal aid with online self-service before the pandemic. Candidate counties must meet all of the following conditions: at least 2,500 renter-occupied households; at least 500 limited-English-speaking households; a share of limited-English-speaking households higher than the statewide share; a share of households with no internet access higher than the statewide share; a share of households with no vehicle higher than the statewide share; a median household income lower than the statewide median; and rental stress higher than the statewide level. Rental stress higher than the statewide level must be demonstrated by at least one of the following: a share of renter households with a rent-to-income ratio of 35% or higher that exceeds the statewide share, or a share of renter households with more than one occupant per room that exceeds the statewide share. All comparisons of “higher than statewide” or “lower than statewide” use the New Mexico statewide value from the same data release. Output a single line with all qualifying counties sorted alphabetically by county name. Each county is written as County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath, where StressPath must be RENT, CROWD, or BOTH. Separate multiple counties with commas. Percentage fields retain three decimal places with no percent sign.","start_url":"https://data.census.gov/advanced","output_format":"Output a single line with all qualifying counties sorted alphabetically by county name. Each county is written as County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath, where StressPath must be RENT, CROWD, or BOTH. Separate multiple counties with commas. Percentage fields retain three decimal places with no percent sign.","oracle_answer":"Doña Ana County|28729|7883|10.127|22.612|6.079|44.172|6.391|40973|BOTH,Luna County|3482|1109|12.455|34.030|8.165|42.700|1.407|29360|RENT,McKinley County|6090|1610|7.688|50.587|10.978|27.568|16.256|33834|CROWD,San Miguel County|3443|1200|10.337|38.470|7.684|47.376|2.440|30946|RENT,Taos County|2854|652|5.387|28.844|5.726|48.823|4.555|38329|RENT","metadata":{"State-Gated Retrieval":["Use only New Mexico county data from the 2015–2019 American Community Survey 5-year estimates, and use the New Mexico statewide value from the same release as the comparison baseline.","Candidate counties must have at least 2,500 renter households, at least 500 limited-English-speaking households, and LEP share, no-internet share, and no-vehicle share all higher than the statewide values, while median household income is lower than the statewide value.","LEPHH must be computed by summing all four limited-English language groups in C16002. Retain only counties where at least one of Severe Rent Burden or Crowded Renter exceeds the statewide value, and write StressPath according to the rule."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the 2015-2019 ACS 5-year county geography yields New Mexico county candidates and the statewide baseline row","C16002 and the downstream housing/income tables yield LEPHH, LEP share, no-internet share, no-vehicle share, severe rent burden, crowded-renter share, and median income for counties and the state baseline","final rows are produced only after the LEPHH numerator is computed from all four limited-English language groups and the downstream stress-path filters are applied"],"control_dependency":["the LEPHH numerator must be computed from all four limited-English language groups in C16002 rather than from Spanish-only counts","county eligibility and StressPath labels must be determined from the LEPHH measure and statewide LEP baseline defined under that full four-group calculation","the RENT / CROWD / BOTH classification must be determined by evaluating the same county set against both downstream housing-stress branches"],"freeze":{"historical_window":"2015-2019 American Community Survey 5-year estimates for New Mexico counties, using the New Mexico statewide row from the same release as the comparison baseline"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Use only New Mexico county data from the 2015–2019 American Community Survey 5-year estimates, and use the New Mexico statewide value from the same release as the comparison baseline.","Candidate counties must have at least 2,500 renter households, at least 500 limited-English-speaking households, and LEP share, no-internet share, and no-vehicle share all higher than the statewide values, while median household income is lower than the statewide value.","LEPHH must be computed by summing all four limited-English language groups in C16002. Retain only counties where at least one of Severe Rent Burden or Crowded Renter exceeds the statewide value, and write StressPath according to the rule."],"exclusion_conditions":["Exclude results that treat Spanish-only limited-English households as the entire LEPHH count.","Exclude results that do not use the statewide baseline from the same release or do not recompute LEPHH/LEPSharePct/LEPShare_state.","Exclude counties that do not satisfy the final stress-path condition of RENT, CROWD, or BOTH."],"normalization":{"field_separator":"|","record_separator":",","schema":["County","RenterHH","LEPHH","LEPSharePct","NoInternetPct","NoVehiclePct","SevereRentBurdenPct","CrowdedRenterPct","MedianIncome","StressPath"],"county":"use the county display name including the word `County` and excluding a trailing state suffix","dedup_key":"county FIPS / GEOID","LEPHH":"sum the four designated limited-English-proficient renter-household cells before emitting the integer total","percentage_fields":"all percentage fields are plain numbers with exactly three decimal places and no percent sign","numeric_fields":"household counts and median income are emitted as plain integers without commas","StressPath":{"allowed_values":["RENT","CROWD","BOTH"],"rule":"emit BOTH only when both the severe-rent-burden and crowded-renter signals survive; otherwise emit the single surviving label"},"sorting_or_selection":"county name alphabetical ascending","stop_condition":["all candidate counties are validated under the same geography and product settings","the renter scope and LEP aggregation are checked before the final line is emitted"]}}} +{"task_id":"census_003-g","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"Using the 2013–2017 American Community Survey 5-year estimates for California counties, identify counties where, for school meal material updates and annual parent information updates, relying solely on an English-only online portal is insufficient and paper materials with offline assistance must still be retained. Candidate counties must meet all of the following conditions: population aged 5–17 at least 75,000; among the population aged 5–17, the number of people who speak English \"not well\" or \"not at all\" is at least 2,000 and its share is higher than the statewide share; share of households without internet access higher than the statewide share; median household income lower than the statewide share; and at least two of three support-need signals higher than the statewide share. The three support-need signals are: share of households with no vehicle; share of minors living in households that received SSI, cash public assistance, or Food Stamps/SNAP in the past 12 months; and share of renter-occupied households with more than one occupant per room. All comparisons of \"higher than statewide\" or \"lower than statewide\" use the California statewide value from the same data release. Output all qualifying counties in a single line sorted alphabetically by county name. Each county is written as County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath, where SupportPath uses only the three labels BENEFITS, CROWD, and MOBILITY joined by + in that fixed order. Multiple counties are separated by commas.","start_url":"https://data.census.gov/advanced","output_format":"Output all qualifying counties in a single line sorted alphabetically by county name. Each county is written as County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath, where SupportPath uses only the three labels BENEFITS, CROWD, and MOBILITY joined by + in that fixed order. Multiple counties are separated by commas.","oracle_answer":"Fresno County|200205|5127|2.561|20.588|8.686|46.388|13.967|48730|BENEFITS+CROWD+MOBILITY,Kern County|185802|4130|2.223|21.739|7.058|37.285|14.394|50826|BENEFITS+CROWD,Los Angeles County|1641669|37540|2.287|16.338|9.204|27.238|16.741|61015|BENEFITS+CROWD+MOBILITY,Tulare County|104542|2703|2.586|25.738|6.274|49.347|14.535|44871|BENEFITS+CROWD","metadata":{"State-Gated Retrieval":["Use only California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline.","Retain only counties with a population aged 5–17 of at least 75,000, a SchoolAgeLEP count of at least 2,000 with its share higher than the statewide share, a no-internet share higher than the statewide share, and a median household income lower than the statewide share.","SchoolAgeLEP must be the sum of the eight not-well/not-at-all cells across the four major language groups in B16004. The final county must also have at least two of the three offline support signals (Mobility, Benefits, Crowd) higher than the statewide share."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the 2013-2017 ACS 5-year county geography yields California county candidates and the statewide baseline row","B16004 and the downstream access/income/support tables yield SchoolAgeLEP, no-internet share, no-vehicle share, child-benefit share, crowded-renter share, and median income for counties and the statewide baseline","final rows are produced only after the SchoolAgeLEP numerator is computed from all eight 1980-target language cells and the downstream support-path branches are applied"],"control_dependency":["the SchoolAgeLEP numerator must be computed from the full eight-cell language set in B16004 rather than from only two Spanish LEP cells","county eligibility and SupportPath labels must be determined from the LEP numerator and candidate set defined under that full eight-cell calculation","the BENEFITS / CROWD / MOBILITY path labels must be determined by applying all three downstream support branches to the same county set"],"freeze":{"historical_window":"2013-2017 American Community Survey 5-year estimates for California counties, using the California statewide row from the same release as the comparison baseline"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Use only California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline.","Retain only counties with a population aged 5–17 of at least 75,000, a SchoolAgeLEP count of at least 2,000 with its share higher than the statewide share, a no-internet share higher than the statewide share, and a median household income lower than the statewide share.","SchoolAgeLEP must be the sum of the eight not-well/not-at-all cells across the four major language groups in B16004. The final county must also have at least two of the three offline support signals (Mobility, Benefits, Crowd) higher than the statewide share."],"exclusion_conditions":["Exclude results that use only the two Spanish LEP rows without merging all eight target cells.","Exclude results that do not rerun the B28011, B19013, B08201, B09010, and B25014 branches.","Exclude counties whose final SupportPath does not have at least two signals higher than the statewide share."],"normalization":{"field_separator":"|","record_separator":",","schema":["County","SchoolAgePop","SchoolAgeLEP","LEPSharePct","NoInternetPct","NoVehiclePct","ChildBenefitSharePct","CrowdedRenterPct","MedianIncome","SupportPath"],"county":"use the county display name including the word `County` and excluding a trailing state suffix","dedup_key":"county FIPS / GEOID","SchoolAgeLEP":"sum the eight designated school-age LEP cells before emitting the integer total","percentage_fields":"all percentage fields are plain numbers with exactly three decimal places and no percent sign","numeric_fields":"population counts and median income are emitted as plain integers without commas","SupportPath":"use only BENEFITS, CROWD, and MOBILITY, and when multiple labels apply join them with `+` in the fixed order BENEFITS+CROWD+MOBILITY","sorting_or_selection":"county name alphabetical ascending","stop_condition":["all candidate counties are validated under the same geography and product settings","the school-age LEP aggregation and all three support-signal gates are checked before the final line is emitted"]}}} +{"task_id":"census_004-g","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":7,"instruction":"Using the 2012–2016 American Community Survey 5-year estimates, identify Pennsylvania counties with high elderly evacuation support needs that should conduct in-person outreach before winter storms. A candidate county must meet all of the following conditions: a population aged 65 and older of at least 15,000; a population aged 65 and older with ambulatory difficulty of at least 4,000, with its share of the 65+ population higher than the statewide share; a median household income below the statewide median; and at least two of four evacuation-support barriers above the statewide level. The four barriers are: share of households with a householder aged 65+ living alone, share of households with no vehicle, share of renter-occupied households with no vehicle, and mobile homes as a share of all housing units. All comparisons to the statewide level use the Pennsylvania statewide values from the same data release. Output all qualifying counties as a single line, sorted alphabetically by county name. Each county is formatted as County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath, with counties separated by commas. For BarrierPath, use only ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE, joined by + in that fixed order.","start_url":"https://www.census.gov/data.html","output_format":"Output all qualifying counties as a single line, sorted alphabetically by county name. Each county is formatted as County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath, with counties separated by commas. For BarrierPath, use only ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE, joined by + in that fixed order.","oracle_answer":"Blair County|23013|5576|24.230|14.917|9.440|24.316|6.388|44033|ALONE+MOBILE_HOME, Cambria County|27058|6308|23.313|15.243|10.309|26.627|4.070|42917|ALONE+MOBILE_HOME+RENTER_NO_VEHICLE, Fayette County|25186|5886|23.370|14.961|9.302|22.290|10.489|40511|ALONE+MOBILE_HOME, Lycoming County|19486|4311|22.124|12.164|9.257|23.312|6.726|48731|ALONE+MOBILE_HOME, Mercer County|21537|4799|22.283|14.090|9.572|24.413|7.912|45831|ALONE+MOBILE_HOME, Philadelphia County|188185|56935|30.255|11.553|30.954|44.924|0.250|39770|NO_VEHICLE+RENTER_NO_VEHICLE, Schuylkill County|26613|6465|24.293|14.357|9.676|23.652|4.080|46573|ALONE+MOBILE_HOME","metadata":{"State-Gated Retrieval":["Use only Pennsylvania county data from the 2012–2016 American Community Survey 5-year estimates, and use the Pennsylvania statewide values from the same release as the comparison baseline.","Retain only counties with a 65+ population of at least 15,000, a 65+ ambulatory-difficulty population of at least 4,000 with a share above the statewide share, and a median household income below the statewide median.","The 65+ ambulatory-difficulty numerator must combine the four target cells from B18105 for ages 65–74 and 75+, male and female. The final county must also have at least two of the four barriers (Alone, No Vehicle, Renter No Vehicle, Mobile Home) above the statewide level."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["ACS tables B01001 and B18105 yield county senior-population totals and the full 65+ ambulatory-difficulty numerator","statewide comparison tables yield Pennsylvania baselines plus county barrier metrics for living alone, no vehicle, renter no vehicle, mobile home, and median income","final rows are produced only after the county candidate set is defined from the full ambulatory-difficulty numerator and the downstream six-table filters are applied"],"control_dependency":["the ambulatory-difficulty numerator must include the full 65+ population across 65–74 and 75+ and male and female cells rather than only the 75+ cells","downstream county eligibility and barrier labels must be determined from the county candidate set defined under that full ambulatory numerator","the at-least-two-barriers test must compare every county metric against the same Pennsylvania statewide baselines from the same ACS release"],"freeze":{"historical_window":"2012–2016 American Community Survey 5-year estimates for Pennsylvania counties, with Pennsylvania statewide baselines taken from the same release"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Use only Pennsylvania county data from the 2012–2016 American Community Survey 5-year estimates, and use the Pennsylvania statewide values from the same release as the comparison baseline.","Retain only counties with a 65+ population of at least 15,000, a 65+ ambulatory-difficulty population of at least 4,000 with a share above the statewide share, and a median household income below the statewide median.","The 65+ ambulatory-difficulty numerator must combine the four target cells from B18105 for ages 65–74 and 75+, male and female. The final county must also have at least two of the four barriers (Alone, No Vehicle, Renter No Vehicle, Mobile Home) above the statewide level."],"exclusion_conditions":["Exclude results that take only the 75-and-over ambulatory-difficulty cells and mistakenly treat them as the full 65+ count.","Exclude results that do not use the Pennsylvania statewide baselines from the same release.","Exclude counties whose final BarrierPath does not satisfy at least two barriers above the statewide level."],"normalization":{"field_separator":"|","record_separator":",","schema":["County","SeniorPop","AmbulatoryDifficulty65Plus","AmbDiffPct","SeniorLivingAloneSharePct","NoVehiclePct","RenterNoVehiclePct","MobileHomePct","MedianIncome","BarrierPath"],"county":"use the county display name including the word `County` and excluding a trailing state suffix","dedup_key":"county FIPS / GEOID","percentage_fields":"all percentage fields are plain numbers with exactly three decimal places and no percent sign","numeric_fields":"population counts and median income are emitted as plain integers without commas","BarrierPath":"use only ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE, and when multiple labels apply join them with `+` in the fixed order ALONE+MOBILE_HOME+NO_VEHICLE+RENTER_NO_VEHICLE","sorting_or_selection":"county name alphabetical ascending","stop_condition":["all candidate counties are validated under the same geography and product settings","the senior ambulatory-difficulty gate and all barrier-signal gates are checked before the final line is emitted"]}}} +{"task_id":"climategov_011-g","domain":"NOAA_NCEI_CLIMATE_AT_A_GLANCE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"Identify South Texas climate divisions that were near-normal or wetter over two longer periods and still had light heating demand in March 1966. Restrict the search strictly to the four divisions South Central, Upper Coast, South, and Lower Valley, using the exact names and numbering order from the official Texas climate-division page fragment.\n\nRetain only divisions that meet all three hard climate criteria: (1) the 10-month Palmer Z-Index anomaly ending February 1966 must be at least -0.05; (2) the 24-month Palmer Z-Index anomaly ending December 1966 must be at least -0.10; and (3) the actual March 1966 monthly Heating Degree Days value must be below 200°Df.\n\nSort qualifying divisions as follows: primary key is the sum of the February 1966 10-month Z-index anomaly and the December 1966 24-month Z-index anomaly, in descending order; secondary key is the March 1966 HDD actual value, in ascending order; tertiary key is the Texas division number, in ascending order.\n\nFinally, output all matching divisions as a single comma-separated string. Each entry must follow the format \"|||||\", where the moisture score is the sum of the two Z-index anomalies. If no division qualifies, output NONE in uppercase.","start_url":"https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national","output_format":"Output all matching divisions as a single comma-separated string. Each entry must follow the format \"|||||\", where the moisture score is the sum of the two Z-index anomalies. If no division qualifies, output NONE in uppercase.","oracle_answer":"7|South Central|0.72|0.35|194°Df|1.07,10|Lower Valley|0.28|0.67|106°Df|0.95,9|South|0.03|0.37|148°Df|0.40","metadata":{"State-Gated Retrieval":["Filter only within the four South Texas divisions defined on the Texas divisional page: South Central, Upper Coast, South, and Lower Valley.","Retain divisions that simultaneously satisfy: 1966-02 10-month Palmer Z-Index anomaly >= -0.05; 1966-12 24-month anomaly >= -0.10; 1966-03 1-month Heating Degree Days Value < 200°Df.","Sort by sum of the two Z anomalies descending, then by 1966-03 HDD Value ascending, then by division number ascending."],"dependency_type":"Data","intra_chain":true,"inter_chain":true,"data_dependency":["The official Texas climate-division reference fixes the four South Texas division IDs and names that must be tracked across all later pages.","The 1966-02 10-month Palmer Z-Index anomaly page and the 1966-12 24-month Palmer Z-Index anomaly page jointly identify the four target South Texas divisions.","The 1966-03 1-month Heating Degree Days Value page supplies the last filter; final rows are produced only after intersecting the three divisional screens and then sorting by summed Z-anomaly score, HDD value, and division number."],"freeze":{"historical_window":"Texas climate divisions South Central, Upper Coast, South, and Lower Valley; metrics are fixed to the 1966-02 10-month Palmer Z-Index anomaly, 1966-12 24-month anomaly, and 1966-03 1-month Heating Degree Days Value pages."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Filter only within the four South Texas divisions defined on the Texas divisional page: South Central, Upper Coast, South, and Lower Valley.","Retain divisions that simultaneously satisfy: 1966-02 10-month Palmer Z-Index anomaly >= -0.05; 1966-12 24-month anomaly >= -0.10; 1966-03 1-month Heating Degree Days Value < 200°Df.","Sort by sum of the two Z anomalies descending, then by 1966-03 HDD Value ascending, then by division number ascending."],"exclusion_conditions":["Exclude any Texas divisional results outside the four specified South Texas divisions.","Exclude results that misread the 1966-03 HDD page filter field as Anomaly instead of Value.","Exclude any division that fails any time window or threshold condition."],"normalization":{"field_separator":"|","record_separator":",","schema":["texas_division_no","division_name","feb_1966_10mo_z_text","dec_1966_24mo_z_text","mar_1966_hdd_text","moisture_score"],"texas_division_no":"Canonical output uses the short Texas climate-division number; the scorer may accept an equivalent four-digit form, but the emitted oracle uses the short number.","raw_text_fields":"The two Z-index anomaly fields and the March 1966 HDD field preserve the raw displayed text; comparison may ignore optional trailing HDD unit text such as `°Df`.","moisture_score":"Compute as February 1966 10-month Z-index anomaly plus December 1966 24-month Z-index anomaly, formatted with exactly two decimal places.","sorting_or_selection":{"primary":"moisture_score descending","secondary":"March 1966 HDD actual value ascending after numeric normalization","tertiary":"Texas division number ascending"},"eligibility_rule":"Each Texas division is counted once per requested window; if any required window value is missing, exclude the division.","stop_condition":["All candidate Texas divisions are checked under the same base period and anomaly windows.","The unique ordered output string is resolved before emission."]}}} +{"task_id":"climategov_012-g","domain":"NOAA_NCEI_CLIMATE_AT_A_GLANCE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am researching historical climate patterns in Texas and want to find similar historical years as references for shoulder-season operational planning. To do this, I need to identify specific Texas climate divisions in NOAA's Climate at a Glance database. The divisions I am looking for must have experienced a shift from a dry long-term moisture background back toward near-normal or wetter conditions in the early 20th century, and must have had light heating loads in two different shoulder-season windows.\n\nSpecifically, the selected divisions must satisfy all four of the following hard climate criteria: first, the 10-month Palmer Z-Index anomaly ending April 1907 must be no higher than -0.30; second, the 10-month Z-Index anomaly ending April 1923 must be no lower than -0.20; third, the 2-month Heating Degree Days (HDD) actual value ending May 1915 must be below 50°Df; and fourth, the 5-month HDD actual value ending October 1922 must be below 20°Df.\n\nAfter identifying the qualifying divisions, sort them according to the following rules. The primary sort key is the \"rebound score\", defined as the April 1923 10-month Z-Index anomaly minus the April 1907 10-month Z-Index anomaly, sorted in descending order. In case of a tie, place the division with the smaller October 1922 5-month HDD actual value first. If still tied, place the division with the smaller Texas division number first.\n\nFinally, output all matching divisions as a single comma-separated string. Each matching item must be formatted exactly as: \"|<4-digit division ID>||||||\". If after checking all divisions none meet the combined criteria, output NONE in uppercase.","start_url":"https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national","output_format":"Output all matching divisions as a single comma-separated string. Each matching item must be formatted exactly as: \"|<4-digit division ID>||||||\". If after checking all divisions none meet the combined criteria, output NONE in uppercase.","oracle_answer":"10|4110|Lower Valley|-0.36|1.46|10°Df|7°Df|1.82,9|4109|South|-0.33|0.53|23°Df|16°Df|0.86\n10|4110|Lower Valley|-0.36|1.46|10|7|1.82,9|4109|South|-0.33|0.53|23|16|0.86","metadata":{"State-Gated Retrieval":["Retain only Texas divisions that satisfy all four historical conditions: the 10-month Palmer Z-Index anomaly for April 1907 must be no higher than -0.30; the 10-month anomaly for April 1923 must be no lower than -0.20; the 2-month HDD Value for May 1915 must be less than 50°Df; and the 5-month HDD Value for October 1922 must be less than 20°Df.","The rebound score is defined as the April 1923 10-month anomaly minus the April 1907 10-month anomaly.","Sort first by rebound score descending, then by the October 1922 5-month HDD Value ascending, then by Texas division number ascending."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Texas divisional pages yield the 1907-04 and 1923-04 10-month Palmer Z-Index anomalies plus the 1915-05 2-month and 1922-10 5-month HDD values for each division.","The rebound score and the two shoulder-season HDD values are computed only after the same set of candidate divisions survives all four historical filters.","The final output is produced after sorting the surviving divisions by rebound score, then 1922-10 HDD value, then division number."],"control_dependency":["The workflow must cover the 1907, 1923, and 1915 pages as well as the 1922-10 5-month HDD page.","Both HDD pages must be read from Value rather than Anomaly.","The final rebound ranking must be determined after the 1922-10 5-month HDD page excludes 7 South Central and 8 Upper Coast, using ReboundScore as the ordering basis."],"freeze":{"historical_window":"Texas climate divisions evaluated on the 1907-04 and 1923-04 10-month Palmer Z-Index anomaly pages, the 1915-05 2-month HDD Value page, and the 1922-10 5-month HDD Value page."},"answer_type":"mixed multi-line output"},"rubric":{"inclusion_conditions":["Retain only Texas divisions that satisfy all four historical conditions: the 10-month Palmer Z-Index anomaly for April 1907 must be no higher than -0.30; the 10-month anomaly for April 1923 must be no lower than -0.20; the 2-month HDD Value for May 1915 must be less than 50°Df; and the 5-month HDD Value for October 1922 must be less than 20°Df.","The rebound score is defined as the April 1923 10-month anomaly minus the April 1907 10-month anomaly.","Sort first by rebound score descending, then by the October 1922 5-month HDD Value ascending, then by Texas division number ascending."],"exclusion_conditions":["Exclude results that stop after filtering only the 1907, 1923, and 1915 pages without also reading the 1922-10 5-month HDD page.","Exclude results that mistakenly read the 1915 or 1922 HDD page as Anomaly instead of Value.","Exclude any division that does not satisfy any one of the historical window conditions."],"normalization":{"field_separator":"|","record_separator":",","schema":["texas_division_no","division_id_4digit","division_name","apr_1907_10mo_z_text","apr_1923_10mo_z_text","may_1915_2mo_hdd_text","oct_1922_5mo_hdd_text","rebound_score"],"texas_division_no":"Emit the short Texas climate-division number in field 1 and the four-digit division ID in field 2.","raw_text_fields":"The two Z-index anomaly fields preserve the raw displayed text; the two HDD fields preserve the raw displayed text, but comparison may ignore an optional trailing °Df suffix.","rebound_score":"Compute as the April 1923 10-month Z-index anomaly minus the April 1907 10-month Z-index anomaly, formatted with exactly two decimal places.","sorting_or_selection":{"primary":"rebound_score descending","secondary":"October 1922 HDD actual value ascending after numeric normalization","tertiary":"Texas division number ascending"},"answer_set_note":"The current oracle stores two equivalent answer sets: one preserves the HDD unit suffixes and one strips them; treat the two HDD columns as equivalent after optional °Df removal.","stop_condition":["All candidate Texas divisions are checked under the same anomaly and HDD windows.","The unique ordered output string is resolved before emission."]}}} +{"task_id":"comptox_010-g","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"Among the following five substances found in records related to painted products in Europe—aniline, cobalt, chromium, 3,3'-dichlorobenzidine, and dibenz[a,h]anthracene—select those whose pages explicitly contain the record 'Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe'. For each qualifying substance, produce a consolidated list that integrates historical keyword status and the deepest-level use categories. First, for each substance, count how many of the following five dated historical keywords are present (presence only, ignoring any leading numbers): Substances in Products - Canada (4/2014), Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children's Safe Product Act (4/2020), OEHHA Proposition 65 (1/2023). Also record the earliest and latest year-month among the hits. Second, for each substance, retain one category that best reflects its current use. After excluding the use category to which the above-mentioned painted-products record belongs, establish for each substance a terminal-use profile along two dimensions: 'daily consumer goods' (with the broad-category selection priority Formulation → Article → Occupation) and 'production materials' (with the broad-category selection priority Occupation → Article → Formulation). Finally, sort all substances by historical keyword hit count in descending order; for ties, sort by the number of products at the selected consumer-side node in descending order.","start_url":"https://comptox.epa.gov/chemexpo/","output_format":"Output format: |||||||||||||. Results separated by commas; if no qualifying items exist, output NONE.","oracle_answer":"DTXSID8020090|5|2014-04|2023-01|Formulation|272|295|type|4|Occupation|301|356|family|27,DTXSID1031040|3|2018-10|2023-01|Formulation|77|94|type|7|Occupation|301|400|family|308,DTXSID9020409|2|2019-03|2023-01|Occupation|321|321|general|11|Occupation|321|321|general|11,DTXSID6020432|2|2019-03|2023-01|Article|313|313|general|1|Occupation|301|356|family|27,DTXSID3031022|1|2023-01|2023-01|Formulation|77|95|type|4|Occupation|301|356|family|185","metadata":{"State-Gated Retrieval":["Screen only the five specified substances, and the target substance page must explicitly contain the record 'Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe'.","Count whether each of the five specified dated keywords appears, and record the earliest and latest year-month among the hits.","Then independently select one consumer-side route and one production-material-side route, the former following Formulation → Article → Occupation and the latter following Occupation → Article → Formulation, and refine each route separately to its deepest level."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["each chemical page yields the five dated historical keywords, the Europe body-paint/tattoo-ink qualifying record, and the earliest/latest dated-hit months","PUC category paths yield one consumer-side route chosen by Formulation -> Article -> Occupation and one source-side route chosen independently by Occupation -> Article -> Formulation","final rows are produced only after the consumer-side and source-side routes are selected and refined separately for each chemical"],"control_dependency":["the source-side route must be selected independently from the consumer-side route","for each chemical, the second route refinement must follow the production-material priority order rather than the daily-consumer route","family/type/general outputs must be determined only after both route selections are made independently"],"freeze":{"historical_window":"the five named substances as objectively existing chemicals, using their ChemExpo chemical pages, PUC category paths, keyword-state evidence, and Europe body-paint/tattoo-ink presence as relatively stable classification signals"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Screen only the five specified substances, and the target substance page must explicitly contain the record 'Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe'.","Count whether each of the five specified dated keywords appears, and record the earliest and latest year-month among the hits.","Then independently select one consumer-side route and one production-material-side route, the former following Formulation → Article → Occupation and the latter following Occupation → Article → Formulation, and refine each route separately to its deepest level."],"exclusion_conditions":["Exclude substances that do not contain the specified Europe painted-products/tattoo-ink record.","Exclude results that directly reuse the same consumer-side route for the production-material side.","Exclude results that do not independently select and refine both routes according to the specified priority orders."],"normalization":{"field_separator":"|","record_separator":",","schema":["DTXSID","hit_count","earliest","latest","consumer_kind","consumer_general_puc_id","consumer_terminal_puc_id","consumer_level","consumer_products","material_kind","material_general_puc_id","material_terminal_puc_id","material_level","material_products"],"dated_hits":"count only the exact dated keyword strings defined in the source rubric","date_format":"YYYY-MM","kind":"the kind fields use the canonical labels Article, Formulation, or Occupation","level":"the level fields use the canonical labels general, family, or type","products_source":"the Products counts come from the local chemical-detail node for the selected branch, not from an overall aggregate shown elsewhere on the site","sorting_or_selection":{"primary":"hit_count descending","secondary":"consumer_products descending","tertiary":"DTXSID ascending"}}}} +{"task_id":"comptox_011-g","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":6,"instruction":"In ChemExpo, for each of the six substances, determine whether it appears more often in material-contact uses or manufacturing-source uses, then select the most representative use category from the corresponding direction. Specifically, the scope is limited to these six substances: Di(2-Ethylhexyl) Phthalate, Melamine, Tris(2-Ethylhexyl) Phosphate, 4,5-Dihydro-2-Mercaptoimidazole, Phthalic Acid, and Triphenyl Phosphates Tert-Butylated. For each substance, three sets of data must be checked: first, a 'material-contact score' obtained by summing the occurrences of five specific labels (Indirect additives food contact (10/2018), Europe, Food contact items, Food contact items, Japan, entries containing 'Toys and children's products', and entries containing 'artificial_saliva' or 'artificial_sweat'); second, a 'manufacturing-source score' obtained by summing the occurrences of two specific labels (drinking_water, Europe, manufacturing, plastic_additive and Europe, plastic_additive); third, a regulatory profile generated by counting the total hits of four date-keyword labels (Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children's Safe Product Act (4/2020), OEHHA Proposition 65 (1/2023)) and extracting the earliest and latest month-year range spanned. Based on this, if the material-contact score is strictly greater than the manufacturing-source score, the substance is considered to favor material contact, and the most representative category is selected in the order Article → Formulation → Occupation; otherwise, it is considered to favor manufacturing source, and the selection order is Occupation → Article → Formulation. After determining the category, at each level, follow only the subcategory with the highest product count, continuing until no further subdivision is possible; if there is a tie at the same level, select the one with the smaller PUC ID.","start_url":"https://comptox.epa.gov/chemexpo/","output_format":"Finally, sort the substances by datedHits in descending order; for ties, sort by Products of the selected node in descending order. Output format: ||||||||||||. Results are separated by commas; if datedHits is 0, write NA for both earliest and latest.","oracle_answer":"DTXSID5020607|5|2|4|2018-10|2023-01|contact|Article|309|493|family|1|23|58,DTXSID5020601|4|1|3|2018-10|2023-01|contact|Article|309|309|general|1|5836|1827,DTXSID6020802|4|2|1|2018-10|2018-10|contact|Article|313|313|general|15|1104|675,DTXSID8021484|3|1|1|2018-10|2018-10|contact|Occupation|321|321|general|8|28313|4200,DTXSID0021414|5|0|1|2018-10|2018-10|contact|Article|309|309|general|3|5836|1827,DTXSID20872645|0|1|0|NA|NA|source|Occupation|318|381|family|5|274|107","metadata":{"State-Gated Retrieval":["Only consider the six specified substances, and first compute contactHits, sourceHits, and datedHits on the chemical page.","prioritySide must be determined by these historical signals first, then select the most representative current use category along the corresponding direction.","The current route selection must continue drilling down according to the given kind priority and the same-level smaller PUC ID rule."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["each chemical page yields contactHits, sourceHits, datedHits, and the earliest/latest dated-hit months from the historical keyword set","after the priority side is chosen, the corresponding current PUC category path yields the representative kind, PUC path, product counts, and curated-chemical counts","final rows are produced only after the historical hit scores determine the side first and the current route is then chosen with the side-specific priority and tie-break rules"],"control_dependency":["historical contact/source signal scores must take priority over current maximum-Products paths","the priority side must be determined from contactHits, sourceHits, and datedHits rather than from current visibility alone","PUC path tie-breaks are valid only after the correct side has been fixed and the route has been traced under that side's rules"],"freeze":{"historical_window":"the six named substances as objectively existing chemicals, using their ChemExpo chemical pages, PUC category paths, historical keyword families, and keyword-hit evidence as relatively stable classification signals"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only consider the six specified substances, and first compute contactHits, sourceHits, and datedHits on the chemical page.","prioritySide must be determined by these historical signals first, then select the most representative current use category along the corresponding direction.","The current route selection must continue drilling down according to the given kind priority and the same-level smaller PUC ID rule."],"exclusion_conditions":["Exclude results that ignore historical signals and directly select the path with the maximum currently visible Products on the chemical page.","Exclude results that start PUC route selection without first determining the contact/source direction.","Exclude results where same-level tie-breaks do not follow the smaller PUC ID rule."],"normalization":{"field_separator":"|","record_separator":",","schema":["DTXSID","contactHits","sourceHits","datedHits","earliest","latest","prioritySide","PUCkind","generalPUCID","terminalPUCID","level","Products","PUCDocuments","PUCCuratedChemicals"],"dated_hits":"count only the exact dated keyword strings defined in the source rubric","date_format":"YYYY-MM; if datedHits is 0, earliest and latest are both `NA`","prioritySide":"emit `contact` when contactHits > sourceHits; otherwise emit `source`","kind":"the PUCkind field uses the canonical labels Article, Formulation, or Occupation","level":"the level field uses the canonical labels general, family, or type","products_source":"Products comes from the selected terminal chemical-detail node","terminal_statistics":"PUCDocuments and PUCCuratedChemicals come from the selected terminal PUC detail page Additional Statistics block","sorting_or_selection":{"primary":"datedHits descending","secondary":"Products descending","tertiary":"DTXSID ascending"}}}} +{"task_id":"comptox_012-g","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I want to first screen for Formulation categories with many products in ChemExpo, and then from each category pick one specific product type that carries a child or aerosol label and is most worth prioritizing. Specifically, I am looking for a set of results: for each Formulation category with a total product count of at least 15,000, find one optimal specific product type. This target type must belong to the first family under that category's default display order that meets the following conditions: the family has a total product count of at least 3,000 and no assumed attributes, and it must have product types whose allowed attributes include 'aerosol' and 'child', with those types themselves having no assumed attributes. Then, among all qualifying 'aerosol' and 'child' types under that family, select the one with the highest product share (type product count divided by family cumulative product count). In case of a tie in share, prioritize in order: higher Product Count, more Curated Chemicals, or smaller PUC ID, until a single winner is determined. Finally, retain one final result: prefer the specific product type with the higher product share; if shares are equal, compare Product Count, Curated Chemicals, and PUC ID in that order, retaining the type with the higher count, more chemicals, or smaller ID, until a single final type is obtained.","start_url":"https://comptox.epa.gov/chemexpo/visualizations/","output_format":"Finally, output results sorted by final share descending, in the format: |||||. Join results with commas and no spaces. If no qualifying results exist, output NONE.","oracle_answer":"48|42|62|child|2160/3531|583,137|197|210|child|6934/16904|1135","metadata":{"State-Gated Retrieval":["First, retain only Formulation categories with a total product count of at least 15,000.","In each candidate family, both an aerosol-side type and a child-side type must be found: the family itself must have no assumed attributes and a total product count of at least 3,000; both types must also have no assumed attributes.","All selections within a family and between the two sides must follow the specified tie-break rules: share, Product Count, Curated Chemicals, PUC ID."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["The Formulation summary yields the high-product candidate families whose total product count is at least 15,000.","Within each family, lower-level type pages yield the aerosol and child candidates, their assumed/allowed attributes, product counts, shares, and curated-chemical counts.","Final rows are produced only after a family survives both aerosol and child branches and the winning type is selected by the layered share/product/chemical/PUC tie-break rules."],"control_dependency":["Both the aerosol and child branches within the same family must be fully checked before that family can be retained.","If one side is missing, the workflow must reject the family and continue to the next sibling family rather than stop at the first partial hit.","The final winner can be selected only after both sides have been independently optimized within the family and then compared against each other."],"freeze":{"historical_window":"ChemExpo Formulation families as objectively existing catalog families, especially large families with total product count >= 15,000, evaluated by family/type identity and product/chemical counts as relatively stable catalog descriptors."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["First, retain only Formulation categories with a total product count of at least 15,000.","In each candidate family, both an aerosol-side type and a child-side type must be found: the family itself must have no assumed attributes and a total product count of at least 3,000; both types must also have no assumed attributes.","All selections within a family and between the two sides must follow the specified tie-break rules: share, Product Count, Curated Chemicals, PUC ID."],"exclusion_conditions":["Exclude results that stop as soon as a usable type is found on either side, without requiring the same family to cover both aerosol and child sides.","Exclude results that stop as soon as one side is missing instead of continuing to check sibling families at the same level.","Exclude results that do not follow the specified layered tie-break rules to select the winning type within the family and as the final winner."],"normalization":{"field_separator":"|","record_separator":",","schema":["generalPUCID","familyPUCID","typePUCID","side","share","CuratedChemicals"],"dedup_key":"(generalPUCID, familyPUCID, typePUCID, side)","side":"emit the lower-case branch label exactly as determined in the source workflow","share":"canonical output uses the raw fraction `type Products / family Cumulative Products` rather than a decimal","CuratedChemicals":"emit the integer count from the selected type-level node","sorting_or_selection":{"primary":"share descending by numeric fraction value","secondary":"type-level Products descending","tertiary":"CuratedChemicals descending, then PUC IDs ascending as tie-breaks"}}}} +{"task_id":"comptox_013-g","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"In ChemExpo, for the five substances Di(2-Ethylhexyl) Phthalate, Melamine, Phthalic Acid, Tris(2-Ethylhexyl) Phosphate, and Triphenyl Phosphates Tert-Butylated, check whether their historical labels are consistent with their current uses. The scope is limited to these five substances. For each substance, examine three groups of data. First, the material-contact score: check whether each of the following five label types appears, scoring 1 point per type: Indirect additives food contact (10/2018), Europe, Food contact items, Food contact items, Japan, any keyword containing Toys and children's products, and any keyword containing artificial_saliva or artificial_sweat. Second, the production-source score: check whether each of the following two label types appears, scoring 1 point per type: drinking_water, Europe, manufacturing, plastic_additive and Europe, plastic_additive. Third, dated-keyword hits: check only whether each of the following four keywords appears: Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children's Safe Product Act (4/2020), OEHHA Proposition 65 (1/2023); record the number of hits and the earliest and latest year-month among the hits. Then, if the material-contact score is strictly greater than the production-source score, treat it as leaning toward material contact and select a historically recommended category following the order Article → Formulation → Occupation; otherwise treat it as leaning toward production source and select following the order Occupation → Article → Formulation. After determining the category, follow the subcategory with the most products downward until no further subdivision is possible; if there is a tie at the same level, take the one with the smaller PUC ID. Separately, also find the current dominant category for this substance, ignoring historical clues, directly finding the path with the most products among all use categories, again following downward until no further subdivision is possible, breaking ties by smaller PUC ID. Finally, compare the two results: if the current dominant category is Article or Formulation and the historical clue also points to material contact, record ALIGNED; if the current dominant category is Occupation and the historical clue also points to production source, record ALIGNED; otherwise record MISALIGNED.","start_url":"https://comptox.epa.gov/chemexpo/","output_format":"Output MISALIGNED records first; within the same group, sort by dated hits descending; if hits are equal, sort by current dominant category product count descending. Format: |||||||||||||||||. Separate records with commas. If dated hits is 0, write NA for both earliest and latest.","oracle_answer":"DTXSID6020802|4|2|1|2018-10|2018-10|material|Article|Furniture and furnishings|Furniture and furnishings|general|15|Occupation|Raw materials|fireproof coatings|type|24|MISALIGNED,DTXSID8021484|3|1|1|2018-10|2018-10|material|Occupation|Laboratory supplies|Laboratory supplies|general|8|Occupation|Laboratory supplies|Laboratory supplies|general|8|MISALIGNED,DTXSID5020607|5|2|4|2018-10|2023-01|material|Article|Construction and building materials|flooring|family|1|Formulation|Home maintenance|paint|type|112|ALIGNED,DTXSID0021414|5|0|1|2018-10|2018-10|material|Article|Construction and building materials|Construction and building materials|general|3|Article|Construction and building materials|Construction and building materials|general|3|ALIGNED,DTXSID20872645|0|1|0|NA|NA|source|Occupation|Industrial products|hydraulic fluid|family|5|Occupation|Industrial products|hydraulic fluid|family|5|ALIGNED","metadata":{"State-Gated Retrieval":["Work only on the five specified substances, and first compute materialHits, sourceHits, and datedHits from the keyword-set blocks.","The historically recommended category must be derived independently from these historical signals; the current dominant category must be derived separately from the current use path.","Finally, compare only whether the broad direction of the historically recommended category and the current dominant category match, and mark ALIGNED or MISALIGNED accordingly."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["each chemical page yields materialHits, sourceHits, datedHits, and the historical recommendation side implied by the keyword set","an independent current PUC category path yields the current dominant category, path labels, and classification counts for the same chemical","final rows are produced only after the historical recommendation and current dominant category are computed independently and then compared at the coarse side level"],"control_dependency":["the historical recommendation must be determined from the keyword-set evidence rather than from the current largest category","historical recommendation must be computed from the keyword-set evidence before alignment is judged","ALIGNED / MISALIGNED status is valid only after the historical and current category directions have been derived independently and then compared"],"freeze":{"historical_window":"the five named substances as objectively existing chemicals, using their ChemExpo chemical pages, PUC category paths, and specified keyword-set evidence as relatively stable recommendation signals"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Work only on the five specified substances, and first compute materialHits, sourceHits, and datedHits from the keyword-set blocks.","The historically recommended category must be derived independently from these historical signals; the current dominant category must be derived separately from the current use path.","Finally, compare only whether the broad direction of the historically recommended category and the current dominant category match, and mark ALIGNED or MISALIGNED accordingly."],"exclusion_conditions":["Exclude results that only look at the current largest category and directly treat it as the historically recommended category.","Exclude results that default to ALIGNED for all cases without independently deriving the historically recommended category.","Exclude results that do not compute the historical and current paths separately but mix signals in the same route."],"normalization":{"field_separator":"|","record_separator":",","schema":["DTXSID","materialHits","sourceHits","datedHits","earliest","latest","historySide","recommendedKind","recommendedGeneral","recommendedTerminal","recommendedLevel","recommendedProducts","currentKind","currentGeneral","currentTerminal","currentLevel","currentProducts","status"],"dated_hits":"count only the exact dated keyword strings defined in the source rubric","date_format":"YYYY-MM; if datedHits is 0, earliest and latest are both `NA`","historySide":"emit the lower-case historical winner `material` or `source`","recommended_fields":"these fields describe the historically suggested path","current_fields":"these fields describe the current dominant path","kind":"the kind fields use the canonical labels Article, Formulation, or Occupation","level":"the level fields use the canonical labels general, family, or type","status":"emit `ALIGNED` or `MISALIGNED` exactly","sorting_or_selection":{"primary":"status with MISALIGNED before ALIGNED","secondary":"datedHits descending","tertiary":"currentProducts descending","quaternary":"DTXSID ascending"}}}} +{"task_id":"consumerfinance_008-g","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"For CFPB administrative enforcement actions filed between 2022-01-01 and 2024-12-31, produce a core-amount extraction report covering three product categories: Deposits, Furnishing, and Prepaid. For each category, identify the first action in the website’s default display order that satisfies all of the following: the action detail page provides both a Consent Order and a press release; the Products label corresponds exclusively and exactly to the target category; and the page explicitly states a consumer redress amount exceeding $5,000,000 along with a separate civil money penalty. After locating these three target actions, extract from each action’s Consent Order PDF the first occurrence of the consumer redress amount and the civil money penalty amount in the body text, along with their physical page numbers (PDF page 1 is p1).","start_url":"https://www.consumerfinance.gov/enforcement/actions/","output_format":"Output the results strictly in alphabetical order of the product category’s English name, using the format |||||p||p. Join entries with commas and no spaces. If no qualifying case is found for a category, output |NONE.","oracle_answer":"Deposits|Bank of America, N.A.|2023-CFPB-0006|2023-07-11|$80,400,000|p11|$60,000,000|p14,Furnishing|Hyundai Capital America|2022-CFPB-0005|2022-07-26|$13,200,000|p31|$6,000,000|p35,Prepaid|U.S. Bank National Association|2023-CFPB-0019|2023-12-19|$5,700,000|p22|$15,000,000|p26","metadata":{"State-Gated Retrieval":["Consider only administrative enforcement actions on the CFPB Enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.","For each of the three product categories (Deposits, Furnishing, Prepaid), search top-down in the current default order for the first action that simultaneously satisfies: the page provides a Consent Order and a Press release; the Products label corresponds one-to-one with the target category; and the action detail page explicitly states consumer redress > $5,000,000 and also includes a civil money penalty.","Finally, extract from the correct Consent Order the first-occurrence amounts and page numbers for consumer redress and civil money penalty."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Enforcement-action list pages yield product-branch candidate actions in current default order.","Each action detail page and linked consent-order PDF yield product singularity, document-stack presence, redress and civil-money-penalty amounts, and first-occurrence pages.","Final rows are emitted only after identifying, for each product, the first action that survives detail-page and PDF validation."],"control_dependency":["List-level “has Consent Order + Press release” hits must be validated on the detail page for product singularity and money thresholds.","Prepaid candidates force document-level disambiguation among Consent Order, Stipulation, and terminating-order PDFs.","Per-product first-match selection must explicitly skip rejected candidates and validate downstream PDFs before it is finalized."],"freeze":{"historical_window":"Administrative enforcement actions with Initial filing date from 2022-01-01 through 2024-12-31; current default case ordering and currently linked action documents."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Consider only administrative enforcement actions on the CFPB Enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.","For each of the three product categories (Deposits, Furnishing, Prepaid), search top-down in the current default order for the first action that simultaneously satisfies: the page provides a Consent Order and a Press release; the Products label corresponds one-to-one with the target category; and the action detail page explicitly states consumer redress > $5,000,000 and also includes a civil money penalty.","Finally, extract from the correct Consent Order the first-occurrence amounts and page numbers for consumer redress and civil money penalty."],"exclusion_conditions":["Exclude cases where Products is not a single target category, or where the case appears relevant only at the list level but fails validation on the detail page.","Exclude cases that do not clearly satisfy redress > $5M and a separate civil money penalty.","Exclude cases that mistakenly use a Stipulation or Order Terminating the Consent Order in place of the required Consent Order."],"normalization":{"field_separator":"|","record_separator":",","schema":["Product","Respondent","Docket","FilingDate","RedressUSD","RedressPage","PenaltyUSD","PenaltyPage"],"product_order":"alphabetical by Product name","fallback_row":"if a product has no qualifying case, emit `|NONE`","date_format":"FilingDate uses YYYY-MM-DD","money_fields":"canonical output preserves the dollar sign and commas from the oracle, but equivalent comparison may ignore `$` and commas and compare the numeric USD amount","page_fields":"page fields use the canonical `pN` form","document_scope":"extract both money amounts from the Consent Order PDF only; do not substitute a stipulation, termination order, or other companion document","selection_rule":"for each product, keep the first action in the default filtered order that fully satisfies every gate in the source rubric"}}} +{"task_id":"consumerfinance_009-g","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I want to organize the annual household financial stability survey reports in CFPB Reports, whose latest version page links directly to the 2023 and 2022 editions. I am interested in topics that appeared in the 2022 edition but no longer appear in subsequent annual reports, excluding the topic specifically used to mark \"belongs to the same survey series.\" For each such topic, I need the following information: the earliest subsequent year in which it disappeared; the first report not belonging to this series among the results related to these topics from 2022 and earlier; the total number of related resources listed in that report, how many of them link back to the same survey series, how many of those linked reports have appendices with letter labels and at least three sections; and the title, publication date, and appendix letter range of the final selected report.","start_url":"https://www.consumerfinance.gov/data-research/research-reports/","output_format":"Output a single line per topic, sorted alphabetically by topic name: |||||||||","oracle_answer":"Saving|2023|Consumer Savings App Strategies and Savings Outcomes|2022-12-07|4|2|1|Emergency Savings and Financial Security: Insights from the Making Ends Meet Survey and Consumer Credit Panel|2022-03-23|A-D,Student loans|2023|Report of the CFPB Education Loan Ombudsman|2022-10-20|0|0|0|NONE|NONE|NONE","metadata":{"State-Gated Retrieval":["First, identify the CFPB household financial well-being annual report series whose latest version links directly to the 2023 and 2022 editions.","Using the 2022 edition as the baseline, retain only topics that appear in 2022 but are no longer retained in subsequent annual reports, and exclude the topic specifically marked as \"belongs to the same survey series.\"","For each topic, find the earliest non-series pivot report from 2022 or earlier, then count its directly listed related resources, how many link back to the same survey series, how many qualify under the appendix rule, and the appendix span of the final qualifying report."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["current CFPB Reports pages yield the 2024 -> 2023 -> 2022 annual-survey chain and the 2022 topic baseline","report detail pages and report-search results yield first-disappearance year, pivot report title/date, related-resource counts, and links back to the annual-survey series","final rows are produced only after separating the first jump target from later return-to-series counting"],"control_dependency":["requiring the pivot report itself to link back to the same survey series incorrectly rules out valid topic rows","title extraction must use the pivot detail page rather than search-result snippets","related-resource expansion must continue even when the pivot report itself does not link back to the same survey series"],"freeze":{"historical_window":"currently linked 2024, 2023, and 2022 CFPB household financial well-being annual reports; topic disappearance is judged over that three-year chain, and pivot-report search is restricted to 2022-and-earlier reports"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["First, identify the CFPB household financial well-being annual report series whose latest version links directly to the 2023 and 2022 editions.","Using the 2022 edition as the baseline, retain only topics that appear in 2022 but are no longer retained in subsequent annual reports, and exclude the topic specifically marked as \"belongs to the same survey series.\"","For each topic, find the earliest non-series pivot report from 2022 or earlier, then count its directly listed related resources, how many link back to the same survey series, how many qualify under the appendix rule, and the appendix span of the final qualifying report."],"exclusion_conditions":["Exclude topics that are still retained in subsequent annual reports.","Exclude results that incorrectly treat \"the pivot report itself must link back to the same survey series\" as a hard condition for column 3.","Exclude search results that directly belong to the same survey series or reports after 2022."],"normalization":{"field_separator":"|","record_separator":",","schema":["topic","first-missing-year","pivot-report-or-NONE","pivot-date-or-NONE","direct-related-count","same-series-count","qualified-count","representative-report-or-NONE","publication-date-or-NONE","appendix-span-or-NONE"],"topic_order":"alphabetical by topic name","date_format":"pivot-date and publication-date use YYYY-MM-DD when present","appendix_span":"canonical span uses compact labels such as `A-D`","none_rule":"if qualified-count is 0, representative-report, publication-date, and appendix-span are all `NONE`"}}} +{"task_id":"consumerfinance_010-g","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I want to clearly organize the two waves of the Debt Collection Rule issued by the CFPB in 2020, including their respective proposal sources, delayed-effective-date arrangements, final effective dates, and the accompanying quick-reference PDF information on the implementation page. Specifically, I need the following: the exact issue date of each Final Rule; the originating proposed rule source and name, and the public comment deadline; whether the 2021 delayed-effective-date proposed rule applies to this batch of final rules, its public comment deadline, and the actual effective date that ultimately took effect; the quick-reference PDF file name on the official implementation page, and the first subheading in the body (excluding introductory or background paragraphs).","start_url":"https://www.consumerfinance.gov/rules-policy/final-rules/","output_format":"Output the two waves as a single-line string sorted by final-rule issue date from earliest to latest, identifying each wave by its final rule issue month (YYYY-MM):\n||||||||","oracle_answer":"2020-10|2020-10-30|2019-05-07 main|2019-09-18|YES|2021-05-19|2021-11-30|Executive summary of the October 2020 final rule|Coverage and Definitions,2020-12|2020-12-18|2019-05-07 main+2020-02-21 supplemental|2019-09-18+2020-08-04|YES|2021-05-19|2021-11-30|Executive summary of the December 2020 final rule|Validation Information Requirements and Disclosures","metadata":{"State-Gated Retrieval":["The two 2020 Debt Collection Practices (Regulation F) final rules that share the same name must be processed separately, not merged into one.","For each wave, independently confirm: the issue date, the corresponding proposal chain and public comment deadlines, whether the 2021 delayed-effective-date proposed rule covers it and its comment deadline, the final effective date, the corresponding implementation quick-reference PDF, and the first subheading in that PDF after skipping the introduction.","The detail page, proposal chain, and summary PDF for the October wave and the December wave must each be verified independently."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["final-rules index pages and rule-development pages yield the two 2020 Regulation F final-rule waves and their proposal branches","each final-rule detail page, delayed-effective-date proposal page, and implementation quick-reference PDF yields the wave-specific dates, linked proposals, comment deadlines, and first summary heading","final rows are produced only after the October and December waves are traced separately end to end"],"control_dependency":["two same-title final rules force correction from name-based collapsing to issue-date branching","proposal-chain validation must be done per wave; otherwise the later December chain contaminates the October row","implementation PDFs must be matched back to the correct wave rather than accepting the latest quick-reference page"],"freeze":{"historical_window":"the 2020-10 and 2020-12 Debt Collection Rule final-rule waves, their linked 2020 proposal pages, the 2021 delayed-effective-date proposal, and the current implementation-page quick-reference PDFs"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["The two 2020 Debt Collection Practices (Regulation F) final rules that share the same name must be processed separately, not merged into one.","For each wave, independently confirm: the issue date, the corresponding proposal chain and public comment deadlines, whether the 2021 delayed-effective-date proposed rule covers it and its comment deadline, the final effective date, the corresponding implementation quick-reference PDF, and the first subheading in that PDF after skipping the introduction.","The detail page, proposal chain, and summary PDF for the October wave and the December wave must each be verified independently."],"exclusion_conditions":["Exclude results that merge the two identically named 2020 final rules into one.","Exclude results that project the December wave's proposal chain or executive-summary heading onto the October wave.","Exclude results that are not independently verified against each wave's own final-rule detail page and corresponding PDF."],"normalization":{"field_separator":"|","record_separator":",","schema":["wave","final-rule-date","proposal-chain","proposal-comment-closes","delay-proposal-applied","delay-proposal-comments-close","controlling-effective-date","quick-reference-pdf","summary-heading"],"wave":"wave is the final-rule issue month in YYYY-MM","date_format":"all standalone date fields use YYYY-MM-DD","proposal_chain":"canonical chain joins proposal milestones with `+`, using pieces such as `2019-05-07 main` or `2020-02-21 supplemental` in chronological order","proposal_comment_closes":"join multiple comment-close dates with `+` in the same order as proposal_chain","delay_proposal_applied":"emit `YES` when a delay proposal is part of the chain; otherwise emit `NO`","quick_reference_pdf":"use the displayed quick-reference PDF title, not the filename","summary_heading":"use the first substantive heading from the final-rule PDF","sorting_or_selection":"final-rule-date ascending"}}} +{"task_id":"consumerfinance_011-g","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"On the CFPB enforcement actions page, find the most recent 2024 administrative enforcement action that has since been terminated, separately for Credit Cards and Deposits, and align the termination order with the corresponding clause information in the original Consent Order. Specifically, identify one action for each of the two Products labels: Credit Cards and Deposits. The candidate pool is limited to administrative enforcement actions under Enforcement actions with an Initial filing date between 2024-01-01 and 2024-12-31. For each product label, select the action with the latest Initial filing date among those meeting all of the following conditions (if tied, pick the one with the smaller docket number): Initial filing date between 2024-01-01 and 2024-12-31; case status changed to Expired, Terminated, or Dismissed; the document set includes a Consent Order, a Stipulation, an Order Terminating the Consent Order, and a press release; and the Products label currently maps uniquely to the target product. For each selected action, extract the following from its Order Terminating the Consent Order: TerminationDate (the termination date); TerminationAuthority (the exact text of the termination authority at its first occurrence); TermAuthorityPage (the PDF physical page number where this text first appears). Additionally, find the first explicit reference to a paragraph number of the original Consent Order within the termination order text; if it reads \"Paragraphs X and Y\", take only X. Then go back to the original Consent Order and find the section heading that contains that paragraph.","start_url":"https://www.consumerfinance.gov/enforcement/actions/","output_format":"Finally, output a single-line string in alphabetical order by product name: ||||||p||. If a product has no qualifying case, output: |NONE","oracle_answer":"Credit Cards|Apple Inc.|2024-CFPB-0012|2024-10-23|2025-09-22|12 U.S.C. § 5563(b)(3)|p1|83|ADMINISTRATIVE PROVISIONS,Deposits|Navy Federal Credit Union|2024-CFPB-0014|2024-11-07|2025-07-01|12 U.S.C. § 5563(b)(3)|p1|106|ADMINISTRATIVE PROVISIONS","metadata":{"State-Gated Retrieval":["Consider only administrative enforcement actions with an Initial filing date in 2024, and search for cases separately under Credit Cards and Deposits.","The case must have a status of Expired, Terminated, or Dismissed, and the page must simultaneously provide a Consent Order, Stipulation, Order Terminating the Consent Order, and Press release, with the Products label mapping one-to-one to the target category.","For each category, retain only the most recent qualifying case determined by Initial filing date, and compile the corresponding clause information from the termination order and the original Consent Order."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Enforcement-action list pages yield 2024 candidate actions by product branch.","Each action detail page and linked Consent Order, Stipulation, Order Terminating the Consent Order, and Press release documents yield status, initial filing date, single-product validity, and clause references.","Final rows are selected only after per-product comparison on Initial filing date and document-stack validation."],"control_dependency":["\"Latest\" must be determined by Initial filing date rather than termination date.","Product filters on the list page are insufficient until the action detail page confirms a single matching product.","Clause extraction in the terminating order must stay aligned with the original Consent Order rather than a superficially similar section."],"freeze":{"historical_window":"Administrative enforcement actions with Initial filing date from 2024-01-01 through 2024-12-31; current action status and currently linked Consent Order, Stipulation, terminating-order, and Press release documents."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Consider only administrative enforcement actions with an Initial filing date in 2024, and search for cases separately under Credit Cards and Deposits.","The case must have a status of Expired, Terminated, or Dismissed, and the page must simultaneously provide a Consent Order, Stipulation, Order Terminating the Consent Order, and Press release, with the Products label mapping one-to-one to the target category.","For each category, retain only the most recent qualifying case determined by Initial filing date, and compile the corresponding clause information from the termination order and the original Consent Order."],"exclusion_conditions":["Exclude results that use termination date instead of Initial filing date to determine \"latest\".","Exclude cases with an incomplete document stack or where Products does not map to a single target category.","Exclude cases where the required clause correspondence between the terminating order and the original Consent Order cannot be established."],"normalization":{"field_separator":"|","record_separator":",","schema":["Product","Respondent","Docket","InitialFilingDate","TerminationDate","TerminationAuthority","TermAuthorityPage","ReferencedParagraph","ConsentSectionHeading"],"product_order":"Alphabetical by Product name","fallback_row":"If a product has no qualifying case, emit `|NONE`","date_format":"InitialFilingDate and TerminationDate use YYYY-MM-DD","termination_authority":"Use the canonical statute string extracted from the termination order","page_fields":"TermAuthorityPage uses the canonical `pN` form","ReferencedParagraph":"Emit the paragraph number as a plain numeric string","ConsentSectionHeading":"Emit the uppercase heading of the consent-order section containing the referenced paragraph"}}} +{"task_id":"consumerfinance_012-g","domain":"CFPB_COMPLAINT_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am preparing an internal outreach memo on historical complaint clusters and want to track a specific set of complaints: in the CFPB Complaint Database, identify complaints under the current product bucket covering credit reporting and other personal consumer reports, received between 2018-01-01 and 2021-12-31, tagged as Servicemember, with a public narrative, and whose text explicitly mentions medical bills or doctors. Please provide two representative complaint clusters: the first is the peak month of this cohort; the second is the latest month in this cohort whose complaint count is still at least half of the peak count. For each cluster, report the total complaint count for that month, the state with the highest complaint count in that month and its count, the company with the highest complaint count in that state and month and its count, and the earliest complaint received by that company in that state and month, including its ID, date, Issue, and Sub-issue. Output a single line with Peak first and LatestHalfPeak second, using the format: ||||||||||.","start_url":"https://www.consumerfinance.gov/data-research/consumer-complaints/","output_format":"Output a single line with Peak first and LatestHalfPeak second, using the format: ||||||||||. Join the Peak and LatestHalfPeak clusters with a comma. For ties: months are ordered chronologically; states are ordered by state abbreviation alphabetically ascending, taking the first; companies are ordered by company name alphabetically ascending, taking the first; for the earliest complaint, if multiple complaints share the same date, take the one with the smallest Complaint ID.","oracle_answer":"Peak|2018-02|46|CA|28|TRANSUNION INTERMEDIATE HOLDINGS, INC.|9|2806154|2018-02-07|Improper use of your report|Reporting company used your report improperly,LatestHalfPeak|2021-11|23|CA|12|EQUIFAX, INC.|3|4928768|2021-11-19|Problem with a credit reporting company's investigation into an existing problem|Their investigation did not fix an error on your report","metadata":{"State-Gated Retrieval":["Only consider complaints under the current product bucket for credit reporting / other personal consumer reports, received from 2018-01-01 to 2021-12-31, tagged as Servicemember, with a public narrative, and whose text explicitly mentions medical bills or doctors.","The first cluster must be the peak month of this cohort; the second cluster must be the latest month in this cohort whose complaint count is at least half of the peak count.","For each cluster, recompute the top company within the corresponding month-state subset, then locate the earliest complaint received by that company in that state and month."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["current complaint-form taxonomy yields the product bucket that contains credit reporting / other personal consumer reports","filtered complaint records yield month counts, month-state subsets, top companies, and earliest complaint details inside each chosen subset","final rows are produced only after peak month and latest-half-peak month are determined, and each downstream aggregate is computed inside its narrower month-state cohort"],"control_dependency":["the latest month must be defined as the latest month whose count is at least ceil(PeakCount / 2)","overall top-company counts cannot be projected into a month-state subset without recomputation","earliest complaint selection is only valid after the month, state, and company filters are all frozen"],"freeze":{"historical_window":"Complaint Database records received from 2018-01-01 through 2021-12-31 under the current product-bucket mapping for the credit-reporting / other personal consumer reports family; Servicemember + public narrative + medical bills/doctors text cohort"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only consider complaints under the current product bucket for credit reporting / other personal consumer reports, received from 2018-01-01 to 2021-12-31, tagged as Servicemember, with a public narrative, and whose text explicitly mentions medical bills or doctors.","The first cluster must be the peak month of this cohort; the second cluster must be the latest month in this cohort whose complaint count is at least half of the peak count.","For each cluster, recompute the top company within the corresponding month-state subset, then locate the earliest complaint received by that company in that state and month."],"exclusion_conditions":["Exclude results that directly treat the latest month with any complaints as the second cluster.","Exclude results that first find an overall top company in the full cohort and then project it onto a month-state subset.","Exclude results that do not first derive the half-peak threshold from PeakCount."],"normalization":{"field_separator":"|","record_separator":",","schema":["Cluster","Month","MonthComplaints","TopState","StateComplaints","TopCompany","CompanyComplaints","EarliestComplaintID","EarliestDate","Issue","SubIssue"],"cluster_order":["Peak","LatestHalfPeak"],"date_format":{"Month":"YYYY-MM","EarliestDate":"YYYY-MM-DD"},"TopState":"use the uppercase two-letter state abbreviation","TopCompany":"use the company display name as shown in the source data","tie_breaks":"for tied months use chronological order; for tied states use state-code alphabetical order; for tied companies use company-name alphabetical order; for the earliest complaint use EarliestDate ascending then Complaint ID ascending","SubIssue":"emit `NONE` when the complaint row has no sub-issue value"}}} +{"task_id":"consumerfinance_013-g","domain":"CFPB_COMPLAINT_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am collecting data for an internal crypto-complaint concentration memo and need to identify two representative complaint-month clusters from the CFPB complaint database and extract their core data records.\nThe data must come from a specific cohort: the product category must correspond to the current form’s bucket for Virtual currency, with the sub-product explicitly set to Virtual currency; the time window is strictly 2019-08-26 through 2022-08-26.\nWithin this cohort, the two characteristic months to identify are:\n• Original peak month (AllCompanies): the month with the absolute highest complaint volume in the cohort without removing any company.\n• Residual peak month (ResidualAfterTop2): after identifying the two companies with the highest complaint volume in the original peak month and completely removing all records of those two companies from the entire three-year analysis period, the month with the highest complaint volume that emerges from the remaining data.\nFor these two specific months, I need detailed attributes: total complaints for that month, the names of the two removed companies and their combined complaint contribution in the original peak month, the state with the highest complaint volume in that month and its volume, and the earliest complaint detail (including ID, date, Issue, and Sub-issue) for the most complained-about company within that state and month.\nPlease confirm the identity of these two months and output one formatted string per month with no spaces, in the order AllCompanies first, ResidualAfterTop2 second. The field sequence per row is strictly: ||||||||||||\nSpecial notes:\n• The field must be filled with AllCompanies or ResidualAfterTop2 accordingly.\n• ExcludedTop2Companies and ExcludedTop2PeakMonthComplaints in both rows refer to the two companies identified from the original peak month and their combined complaint volume at that time.\n• The four Earliest-related fields must correspond to the earliest complaint record for the top company in that state and month.\n• To ensure a unique answer: output the two records in the order AllCompanies, ResidualAfterTop2; list ExcludedTop2Companies in descending order of their complaint volume in the original peak month, breaking ties alphabetically by field value; if the earliest complaint date is tied, take the one with the smallest Complaint ID.","start_url":"https://www.consumerfinance.gov/data-research/consumer-complaints/","output_format":"Output one formatted string per row with no spaces, in the order AllCompanies first, ResidualAfterTop2 second. The field sequence per row is strictly: ||||||||||||.","oracle_answer":"AllCompanies|2021-05|336|Coinbase, Inc.+BAM Management US Holdings Inc.|226|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,ResidualAfterTop2|2020-06|180|Coinbase, Inc.+BAM Management US Holdings Inc.|226|OH|28|PNC Bank N.A.|22|3687376|2020-06-07|Other transaction problem|NONE","metadata":{"State-Gated Retrieval":["Only consider Complaint Database records under the current product bucket for Virtual currency, with sub-product Virtual currency, and received between 2019-08-26 and 2022-08-26.","First determine the AllCompanies original peak month, then identify the top two companies by complaint volume in that peak month.","These two companies must be completely removed from the entire three-year cohort, then recompute the residual peak month and all downstream fields based on the remaining cohort."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["current complaint-form taxonomy yields the product bucket for Virtual currency","complaint records within the fixed three-year cohort yield the all-company peak month, per-month top companies, and residual-cohort recomputations after company removal","final rows are produced only after the top-2 companies from the original peak month are removed from the full cohort and downstream aggregates are computed on the resulting cohort"],"control_dependency":["peak-month top companies must be removed from the entire cohort, not only from the original peak month","residual peak detection must be computed from the rewritten cohort rather than by local patching of the original month","downstream state / company / earliest-complaint fields are valid only after the global company-removal step is locked"],"freeze":{"historical_window":"Complaint Database records received from 2019-08-26 through 2022-08-26 under the current product-bucket mapping for Virtual currency"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only consider Complaint Database records under the current product bucket for Virtual currency, with sub-product Virtual currency, and received between 2019-08-26 and 2022-08-26.","First determine the AllCompanies original peak month, then identify the top two companies by complaint volume in that peak month.","These two companies must be completely removed from the entire three-year cohort, then recompute the residual peak month and all downstream fields based on the remaining cohort."],"exclusion_conditions":["Exclude results that only locally delete the top-2 company records from the original peak month.","Exclude results that do not reapply the top-2 company set to the entire cohort before recomputing the residual peak.","Exclude downstream state, company, or earliest-complaint fields based on a cohort that has not been recomputed after removal."],"normalization":{"field_separator":"|","record_separator":",","schema":["Cluster","Month","MonthComplaints","ExcludedTop2Companies","ExcludedTop2PeakMonthComplaints","TopState","StateComplaints","TopCompany","CompanyComplaints","EarliestComplaintID","EarliestDate","Issue","SubIssue"],"cluster_order":["AllCompanies","ResidualAfterTop2"],"date_format":{"Month":"YYYY-MM","EarliestDate":"YYYY-MM-DD"},"ExcludedTop2Companies":"join the two excluded company names with `+` in source-peak complaint-count descending order, breaking ties alphabetically","TopState":"use the uppercase two-letter state abbreviation","TopCompany":"use the company display name as shown in the source data","tie_breaks":"for the earliest complaint use EarliestDate ascending then Complaint ID ascending","SubIssue":"emit `NONE` when the complaint row has no sub-issue value"}}} +{"task_id":"consumerfinance_014-g","domain":"CFPB_COMPLAINT_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"I am writing an internal crypto-complaint sensitivity waterfall memo and need to extract four characteristic months (Clusters) at different filtering stages from the CFPB complaint database, along with their core data.\n\nThe underlying complaint cohort has clear boundaries: time is strictly limited to between 2020-01-01 and 2022-08-26, and it includes only complaint records classified under the \"Virtual currency\" subcategory within the current product taxonomy.\n\nBased on this underlying cohort, I need to identify four characteristic peak months representing different successive exclusion stages:\n• BaselinePeak: The absolute peak month with the highest total complaint volume in the initial complaint pool.\n• AfterDominantPublicResponse: After globally removing all complaints related to the dominant Company public response from the BaselinePeak month, the new peak month in the remaining data pool.\n• AfterDominantPublicResponseAndIssue: After further globally removing all complaints related to the dominant Issue from the second-round peak month, the third-round peak month formed from the remaining data.\n• AfterDominantPublicResponseIssueAndCompany: After finally globally removing all complaints related to the most complained-about Company from the third-round peak month, the final peak month that emerges from the remaining data.\n\nFor these four characteristic months, I need their data under each respective filtering state: total complaints for that month, the new exclusion dimension triggered in this round (NewExclusionType) and its specific value (NewExclusionValue), the frequency of that excluded value in its \"source peak month\", the state with the highest complaint volume in that month and its complaint count, the most complained-about company within that state and its complaint count, and the detailed information (ID, date, Issue, and Sub-issue) of the earliest complaint received by that top company in that state and characteristic month.\n\nPlease confirm the identity and data for these four characteristic months, and output four formatted strings with no spaces, strictly in the specific order: BaselinePeak, AfterDominantPublicResponse, AfterDominantPublicResponseAndIssue, AfterDominantPublicResponseIssueAndCompany. The field sequence for each row must be fixed as:\n|||||||||||||\n\nFor ties, always select in ascending lexicographic order; for the earliest complaint with the same date, select by ascending Complaint ID numerically. Normalize all empty values to NONE before sorting.","start_url":"https://www.consumerfinance.gov/data-research/consumer-complaints/","output_format":"Output four formatted strings with no spaces, strictly in the specific order: BaselinePeak, AfterDominantPublicResponse, AfterDominantPublicResponseAndIssue, AfterDominantPublicResponseIssueAndCompany. The field sequence for each row must be fixed as: |||||||||||||. For ties, always select in ascending lexicographic order; for the earliest complaint with the same date, select by ascending Complaint ID numerically. Normalize all empty values to NONE before sorting.","oracle_answer":"BaselinePeak|2021-05|336|NONE|NONE|0|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,AfterDominantPublicResponse|2022-07|31|Company public response|NONE|321|CA|6|BANK OF AMERICA, NATIONAL ASSOCIATION|4|5735227|2022-07-05|Other transaction problem|NONE,AfterDominantPublicResponseAndIssue|2021-10|13|Issue|Fraud or scam|26|TX|2|BANK OF AMERICA, NATIONAL ASSOCIATION|1|4821611|2021-10-18|Other transaction problem|NONE,AfterDominantPublicResponseIssueAndCompany|2021-06|8|Company|Foris DAX, Inc.|5|NC|3|TRUIST FINANCIAL CORPORATION|2|4462160|2021-06-15|Money was not available when promised|NONE","metadata":{"State-Gated Retrieval":["Only consider Complaint Database records under the Virtual currency subcategory within the current product bucket, with a received date between 2020-01-01 and 2022-08-26.","Sequentially determine the peak months for the four stages: BaselinePeak, AfterDominantPublicResponse, AfterDominantIssue, and AfterDominantCompany, as required by the task.","Each identified dominant Company public response, dominant Issue, and dominant Company must be written back to the corresponding upstream residual cohort, globally removed, and then the next round of statistics must be recalculated."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["current complaint-form taxonomy yields the product bucket for Virtual currency","complaint records yield the baseline peak plus the dominant Company public response, dominant Issue, and dominant Company at successive residual-peak states","final rows are produced only after each dominant value is applied to the full upstream residual cohort and then used to determine the next peak"],"control_dependency":["dominant values found in a peak month cannot be deleted only inside that month; each must be propagated to the full upstream cohort","each new residual peak depends on the prior round's global rewrite, so local month-by-month deletion gives the wrong chain","downstream counts and exemplar complaints are valid only after the full three-stage waterfall is executed"],"freeze":{"historical_window":"Complaint Database records received from 2020-01-01 through 2022-08-26 under the current product-bucket mapping for Virtual currency"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only consider Complaint Database records under the Virtual currency subcategory within the current product bucket, with a received date between 2020-01-01 and 2022-08-26.","Sequentially determine the peak months for the four stages: BaselinePeak, AfterDominantPublicResponse, AfterDominantIssue, and AfterDominantCompany, as required by the task.","Each identified dominant Company public response, dominant Issue, and dominant Company must be written back to the corresponding upstream residual cohort, globally removed, and then the next round of statistics must be recalculated."],"exclusion_conditions":["Exclude results that only delete records locally within the current peak month without writing back to the entire upstream cohort.","Exclude results that do not re-find the next peak month on each round's residual cohort.","Exclude intermediate or final fields based on downstream statistics that were not recalculated globally."],"normalization":{"field_separator":"|","record_separator":",","schema":["Cluster","Month","MonthComplaints","NewExclusionType","NewExclusionValue","NewExclusionCountInSourcePeak","TopState","StateComplaints","TopCompany","CompanyComplaints","EarliestComplaintID","EarliestDate","Issue","SubIssue"],"cluster_order":["BaselinePeak","AfterDominantPublicResponse","AfterDominantPublicResponseAndIssue","AfterDominantPublicResponseIssueAndCompany"],"date_format":{"Month":"YYYY-MM","EarliestDate":"YYYY-MM-DD"},"NewExclusionType":"emit the canonical exclusion-type label from the source workflow; when no new exclusion is applied, emit `NONE`","NewExclusionValue":"emit the canonical excluded value; when no value exists, emit `NONE`","TopState":"use the uppercase two-letter state abbreviation","TopCompany":"use the company display name as shown in the source data","tie_breaks":"normalize empty values to `NONE` before sorting; for other ties use lexicographic order ascending, and for the earliest complaint use EarliestDate ascending then Complaint ID ascending","SubIssue":"emit `NONE` when the complaint row has no sub-issue value"}}} +{"task_id":"europemc_001-g","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":21,"instruction":"I want to consolidate into a single line the admission variables actually used by several prediction schemes in this 2020 COVID-19 mortality risk prediction paper, so that it is easy to see which variables overlap across schemes and which appear only in the comparator schemes.\nSpecifically, the target paper is a 2020 open-access review whose title contains all three terms \"prognosis model\", \"mortality risk\", and \"COVID-19\", and whose main text discusses Wuhan inpatients.\nThe variables to retain fall into two categories: (1) admission variables that appear in both the Random Forest and XGBoost variable importance rankings; (2) admission variables that do not appear in both rankings but are additional variables present in the CURB-65 or NEWS schemes used by the authors as comparators.\nFormat each variable as follows:\nvariable~RF_rank_or_0~XGB_rank_or_0~F~C~N~X\nwhere:\n\t•\tRF is the variable's rank in the Random Forest ranking, or 0 if absent;\n\t•\tXGB is the variable's rank in the XGBoost ranking used in the paper, or 0 if absent;\n\t•\tF, C, N, X indicate, respectively, whether the variable entered the authors' final logistic regression model, belongs to CURB-65, belongs to NEWS, and belongs to the XGBoost model used as a comparator in the paper.\nFinally, sort all variables alphabetically by variable name, join them with | into a single line; if the target paper cannot be found, output NONE.","start_url":"https://europepmc.org/advancesearch","output_format":"Format each variable as follows:\nvariable~RF_rank_or_0~XGB_rank_or_0~F~C~N~X\nwhere:\n\t•\tRF is the variable's rank in the Random Forest ranking, or 0 if absent;\n\t•\tXGB is the variable's rank in the XGBoost ranking used in the paper, or 0 if absent;\n\t•\tF, C, N, X indicate, respectively, whether the variable entered the authors' final logistic regression model, belongs to CURB-65, belongs to NEWS, and belongs to the XGBoost model used as a comparator in the paper.\nFinally, sort all variables alphabetically by variable name, join them with | into a single line; if the target paper cannot be found, output NONE.","oracle_answer":"Age~4~2~1~1~0~0|Alanine aminotransferase~17~11~0~0~0~0|Aspartate transaminase~6~4~0~0~0~0|Blood urea nitrogen~5~7~0~1~0~0|Confusion~0~0~0~1~1~0|CRP~2~6~1~0~0~1|Creatinine~9~13~0~0~0~0|Diastolic pressure~16~17~0~1~0~0|Heart rate~15~14~0~0~1~0|LDH~1~1~1~0~0~1|Lymphocyte count~3~5~0~0~0~1|Monocytes~12~16~0~0~0~0|Neutrophil~7~3~0~0~0~0|Normal platelet~10~9~0~0~0~0|Oxygen inhalation~0~0~0~0~1~0|Respiratory rate~11~10~0~1~1~0|SPO2~0~0~0~0~1~0|Systolic pressure~13~12~0~1~1~0|Temperature~18~18~0~0~1~0|Total bilirubin~14~15~0~0~0~0|White blood cell~8~8~0~0~0~0","metadata":{"State-Gated Retrieval":["First locate the target paper: a 2020 open-access review whose title contains all three terms \"prognosis model\", \"mortality risk\", and \"COVID-19\", and whose main text discusses Wuhan inpatients.","Retain only two categories of variables: admission variables that appear in both the Random Forest and XGBoost rankings; or admission variables that, although not appearing in both rankings, belong to the CURB-65 or NEWS comparator schemes.","For each variable, annotate the RF rank, XGB rank, and whether it belongs to the final logistic regression, CURB-65, NEWS, and the comparator XGBoost model as required, then output sorted alphabetically by variable name."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Europe PMC search results and the target open-access article yield the candidate Wuhan COVID mortality-risk review","article tables and discussion sections yield RF/XGBoost rankings, final logistic-regression inclusion, and comparator-variable memberships for CURB-65 / NEWS / external XGBoost","final rows are produced only after overlapping variables and comparator-only variables are merged into one normalized variable table"],"control_dependency":["comparator-only variables must be captured from the discussion definitions rather than from Table 2 + Table 3 alone","comparator membership must be read from the article's explicit scheme definitions rather than inferred from common clinical usage","variable normalization must wait until RF/XGBoost overlap and comparator-only additions are both complete"],"freeze":{"historical_window":"the 2020 open-access COVID-19 mortality-risk review about Wuhan inpatients; variable inclusion and comparator definitions are taken from the article's current full-text tables and discussion"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["First locate the target paper: a 2020 open-access review whose title contains all three terms \"prognosis model\", \"mortality risk\", and \"COVID-19\", and whose main text discusses Wuhan inpatients.","Retain only two categories of variables: admission variables that appear in both the Random Forest and XGBoost rankings; or admission variables that, although not appearing in both rankings, belong to the CURB-65 or NEWS comparator schemes.","For each variable, annotate the RF rank, XGB rank, and whether it belongs to the final logistic regression, CURB-65, NEWS, and the comparator XGBoost model as required, then output sorted alphabetically by variable name."],"exclusion_conditions":["Exclude admission variables that appear in neither both RF and XGB rankings nor the CURB-65 / NEWS additional variables.","Exclude results that stop at Table 2 + Table 3 without proceeding to the discussion to read the comparator definitions.","Exclude results that infer comparator variables from common knowledge rather than verifying against the paper's explicit definitions."],"normalization":{"field_separator":"~","record_separator":"|","schema":["variable","RF_rank_or_0","XGB_rank_or_0","F","C","N","X"],"variable":"use the variable wording normalized in the article tables; keep `Systolic pressure` and `Diastolic pressure` as separate variables","rank_fields":"RF_rank_or_0 and XGB_rank_or_0 are positive integer ranks when present, otherwise 0","boolean_fields":"F, C, N, and X are emitted as 1 or 0 only","sorting_or_selection":"variable name alphabetical ascending","stop_condition":["the shared variable set from Table 2 and Table 3 is fully resolved","the comparator definitions for CURB-65, NEWS, and the comparison XGBoost model are fixed before the final line is emitted"]}}} +{"task_id":"europemc_002-g","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":6,"instruction":"Track Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline review by ClinicalTrials.gov identifier, and check whether they persist in the 2022 and 2023 open-access reviews of the same series. Only include studies that were Phase 1 in the 2021 review and can still be found under the same ClinicalTrials.gov identifier in both the 2022 and 2023 reviews. Do not rely on drug names alone, as they may change. Output all qualifying studies as a single line in the format: NCT~2021 drug~2022 phase~2022 drug~2023 phase~2023 drug, sorted by NCT ascending and joined by |. If the three papers cannot be found, output NONE.","start_url":"https://europepmc.org/advancesearch","output_format":"Output all qualifying studies as a single line in the format: NCT~2021 drug~2022 phase~2022 drug~2023 phase~2023 drug, sorted by NCT ascending and joined by |. If no qualifying studies exist, output NONE.","oracle_answer":"NCT03277573~Salsalate~P1~Salsalate~P1~Salsalate|NCT03634007~AAVrh.10hAPOE2~P1~LX1001~P2~LX1001|NCT03748303~Allopregnanolone (Allo)~P1~Allopregnanolone~P1~Allopregnanolone|NCT04149860~Lu AF87908~P1~Lu AF87908~P1~Lu AF87908|NCT04451408~LY3372993~P1~LY3372993~P1~LY3372993|NCT04500847~Emtricitabine~P1~Emtricitabine~P1~Emtricitabine","metadata":{"State-Gated Retrieval":["Only use Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline article as the baseline.","Whether a study is retained in 2022 and 2023 must be determined by exact matching on the same ClinicalTrials.gov NCT identifier, not by drug name alone.","Only retain studies that can be found under the same NCT in both 2022 and 2023, and output them sorted by NCT ascending."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the 2021, 2022, and 2023 pipeline reviews yield the 2021 Phase 1 baseline cohort and the later-year lookup tables","article tables yield exact ClinicalTrials.gov NCT IDs, yearly phase labels, and yearly drug names for the same study","final rows are produced only after 2021 baseline studies are re-identified in both later reviews by exact NCT matching"],"control_dependency":["continuation must be matched by exact NCT rather than by drug name, because drug names drift across years","2022 and 2023 lookups must use the fixed 2021 Phase 1 NCT set as the starting cohort rather than later-year table membership alone","yearly phase/name fields are only valid after the same NCT is confirmed across all three reviews"],"freeze":{"historical_window":"the 2021, 2022, and 2023 open-access Alzheimer's disease drug development pipeline reviews; the baseline is the 2021 Phase 1 cohort and continuation is matched by exact ClinicalTrials.gov NCT"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only use Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline article as the baseline.","Whether a study is retained in 2022 and 2023 must be determined by exact matching on the same ClinicalTrials.gov NCT identifier, not by drug name alone.","Only retain studies that can be found under the same NCT in both 2022 and 2023, and output them sorted by NCT ascending."],"exclusion_conditions":["Exclude results that are continued only by drug name without exact matching on the same ClinicalTrials.gov identifier.","Exclude studies found only in 2022 or only in 2023, not continuously retained in both years.","Exclude studies not in the 2021 baseline Phase 1 set."],"normalization":{"field_separator":"~","record_separator":"|","schema":["NCT","agent_2021","phase_2022","agent_2022","phase_2023","agent_2023"],"NCT":"use the exact ClinicalTrials.gov identifier as the cross-year identity key","phase_fields":"normalize phases to P1, P2, or P3; if the same NCT appears multiple times in a year, keep the highest phase for that year","agent_fields":"keep the agent text as shown in each year-specific table","sorting_or_selection":"NCT ascending"}}} +{"task_id":"europemc_003-g","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"Identify the candidate molecules predicted in the 2023 \"Antibodies to Watch\" article to file their first marketing applications in 2022–2023, and determine which of them have actually received first approval or entered first regulatory review in the 2024 installment of the same series.\nSpecifically, the scope is limited to the open-access full texts of the 2023 and 2024 \"Antibodies to Watch\" articles in Europe PMC. Retain only those molecules that were listed in the 2023 article as **\"predicted to file first marketing applications in 2022–2023\"** and that, by the 2024 article, have either been approved or have entered first regulatory review.\nFor each qualifying molecule, output a record in the format:\nINN~2023_category~2023_prediction_label~2024_status~2024_indication~2024_region\nwhere:\n\t•\t2023_category is NC (non-cancer) or CA (cancer);\n\t•\t2024_status is A (first approval) or R (first regulatory review).\nFinally, sort records alphabetically by INN, join them with | into a single line, and output that line. If neither article can be found, output NONE.","start_url":"https://europepmc.org/advancesearch","output_format":"For each qualifying molecule, output: INN~2023_category~2023_prediction_label~2024_status~2024_indication~2024_region\nwhere:\n\t•\t2023_category is NC (non-cancer) or CA (cancer);\n\t•\t2024_status is A (first approval) or R (first regulatory review).\nSort records alphabetically by INN, join them with | into a single line, and output that line. If neither article can be found, output NONE.","oracle_answer":"Cosibelimab~CA~MAA,Q2 2023~R~Squamous cell carcinoma~US|Elranatamab~CA~2023~A~Multiple myeloma~US,EU,Switzerland,Brazil|Garadacimab~NC~BLA,2023~R~Hereditary angioedema~EU|Odronextamab~CA~BLA,H2 2022~R~Diffuse large B-cell lymphoma~US,EU|Pozelimab~NC~BLA,H2 2022~A~CHAPLE disease~US|Suciraslimab~NC~NDA,2023~R~Rheumatoid arthritis~China|Talquetamab~CA~2023–25~A~Multiple myeloma~US,EU,UK,Switzerland|Zolbetuximab~CA~BLA,2023~R~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China","metadata":{"State-Gated Retrieval":["First, in the 2023 Antibodies to Watch article, identify all candidate molecules predicted to file first marketing applications in 2022–2023.","Then, in the 2024 article of the same series, check each of these molecules and retain only those that have received first approval or entered first regulatory review.","The 2024 status must distinguish A = first approval from R = first regulatory review, and the 2024 indication and region must be included."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the 2023 Antibodies to Watch article yields the forecast baseline of candidates expected to file in 2022-2023","the 2024 article tables yield first-approval outcomes, first-regulatory-review outcomes, indications, and regions for the same INNs","final rows are produced only after Table 1 approvals and Table 2 first-review candidates are merged back onto the 2023 forecast cohort"],"control_dependency":["both 2024 Table 1 and Table 2 must be read so that first-review-but-not-yet-approved candidates are retained","2024 status coding must distinguish approval from first regulatory review instead of collapsing both into a single positive match","region and indication fields are valid only after the 2023 forecast cohort is reconciled against both 2024 tables"],"freeze":{"historical_window":"the 2023 and 2024 open-access Antibodies to Watch articles; baseline candidates come from the 2023 forecast set and 2024 outcomes come from current Table 1 plus Table 2"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["First, in the 2023 Antibodies to Watch article, identify all candidate molecules predicted to file first marketing applications in 2022–2023.","Then, in the 2024 article of the same series, check each of these molecules and retain only those that have received first approval or entered first regulatory review.","The 2024 status must distinguish A = first approval from R = first regulatory review, and the 2024 indication and region must be included."],"exclusion_conditions":["Exclude results that only check approvals in 2024 Table 1 without also consulting Table 2 for first-regulatory-review candidates.","Exclude molecules not in the 2023 forecast baseline.","Exclude candidates that in 2024 have neither received first approval nor entered first regulatory review."],"normalization":{"field_separator":"~","record_separator":"|","schema":["INN","category_2023","prediction_label_2023","status_2024","indication_2024","region_2024"],"category_2023":"emit `NC` or `CA` exactly","prediction_label_2023":"keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H2 2022`","status_2024":"emit `A` for first approval and `R` for first regulatory review","region_2024":"preserve the raw region string but remove spaces after commas, for example `US,EU`","sorting_or_selection":"INN alphabetical ascending"}}} +{"task_id":"europemc_004-g","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":9,"instruction":"I am evaluating the accuracy of annual antibody watchlist predictions. Based on the Europe PMC database, I need to identify a set of candidate antibodies (INNs) whose progress has clearly lagged behind, and extract their status changes over the three-year period.\nThese target antibodies are special because their dynamics are continuously recorded across three open-access full-text articles in the Antibodies to Watch series from 2022, 2023, and 2024. Specifically, they were originally listed as \"expected to be submitted for review soon\" in the 2022 article, but due to delays, they remained as candidates on the watchlist in the 2023 article. Screening should be done at the antibody-candidate level, not by exact name string matching. If the 2022 article uses a drug code, project name, or other identifiable name, and the 2023 or 2024 article explicitly provides its correspondence to a specific INN, it should be treated as the same candidate entity, and the confirmed INN should be used in the final output.\nFor these continuously delayed candidate antibodies, I need to determine their final status in the 2024 article: whether they finally received first approval, are in first regulatory review, remain on a subsequent watchlist, or have completely disappeared from the main 2024 article list.\nPlease help me identify this set of antibodies and output the extracted parameters as a single-line string joined by |, strictly sorted alphabetically by INN. If the three target articles cannot all be found in the database, output NONE. The internal field order for each antibody must be fixed as: INN~2022 category~2022 phase~2023 prediction label~2024 status~2024 phase or NA~2024 indication or NA~2024 region or NA. No extra spaces should be added around the delimiters in the output, but original spaces within fields should be preserved. Use CA/NC uniformly for 2022 category, P2/P3 for phase, and A/R/F/D for 2024 status, representing First approved, In first regulatory review, subsequent watchlist, and disappeared from the 2024 main article list, respectively.","start_url":"https://europepmc.org/advancesearch","output_format":"Output the extracted parameters as a single-line string joined by |, strictly sorted alphabetically by INN. If the three target articles cannot all be found in the database, output NONE. The internal field order for each antibody must be fixed as: INN~2022 category~2022 phase~2023 prediction label~2024 status~2024 phase or NA~2024 indication or NA~2024 region or NA. No extra spaces should be added around the delimiters in the output, but original spaces within fields should be preserved. Use CA/NC uniformly for 2022 category, P2/P3 for phase, and A/R/F/D for 2024 status, representing First approved, In first regulatory review, subsequent watchlist, and disappeared from the 2024 main article list, respectively.","oracle_answer":"Apamistamab-I-131~CA~P3~BLA,H1 2023~F~P3~Ablation of bone marrow prior to transplantation in AML patients~NA|Bentracimab~NC~P3~BLA,Q4 2022~F~P3~Reversal of the antiplatelet effects of ticagrelor~NA|Cosibelimab~CA~P3~MAA,Q2 2023~R~NA~Squamous cell carcinoma~US|Erfonrilimab~CA~P3~NDA~F~P3~Pancreatic ductal adenocarcinoma~NA|Odronextamab~CA~P2~BLA,H2 2022~R~NA~Diffuse large B-cell lymphoma~US,EU|Talquetamab~CA~P2~2023-25~A~NA~Multiple myeloma~US,EU,UK,Switzerland|Tiragolumab~CA~P3~2023~F~P3~NSCLC~NA|Zanidatamab~CA~P2~2023~D~NA~NA~NA|Zolbetuximab~CA~P3~BLA,2023~R~NA~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China","metadata":{"State-Gated Retrieval":["Start with the 2022 Antibodies to Watch candidates listed as \"expected to be submitted for review soon\" as the baseline, but retain only those molecules that still remain as watchlist candidates in the 2023 same-series article.","For these continuously delayed candidates, then determine their final status in the 2024 article: first approved, in first regulatory review, or completely absent from Tables 1-4.","Name comparison must handle the Apamistamab naming drift; complete absence in 2024 must be explicitly encoded as D."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the 2022, 2023, and 2024 Antibodies to Watch articles yield the 2022 soon-to-file baseline, 2023 carry-over membership, and 2024 status tables","article tables and full-text naming context yield name normalizations, 2024 table presence/absence, and final status labels for each carried-over INN","final rows are produced only after 2022 candidates are filtered by 2023 carry-over status and then resolved against 2024 Tables 1-4 plus explicit absence"],"control_dependency":["2022 candidates must first be filtered by 2023 carry-over status before they are matched against the 2024 tables","Apamistamab naming drift forces explicit normalization before 2024 lookup","complete 2024 absence must be emitted as D rather than treated as a lookup failure"],"freeze":{"historical_window":"the 2022, 2023, and 2024 open-access Antibodies to Watch articles; the 2022 baseline is filtered by 2023 carry-over status and then checked against 2024 Tables 1-4, with explicit absence retained as a status"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Start with the 2022 Antibodies to Watch candidates listed as \"expected to be submitted for review soon\" as the baseline, but retain only those molecules that still remain as watchlist candidates in the 2023 same-series article.","For these continuously delayed candidates, then determine their final status in the 2024 article: first approved, in first regulatory review, or completely absent from Tables 1-4.","Name comparison must handle the Apamistamab naming drift; complete absence in 2024 must be explicitly encoded as D."],"exclusion_conditions":["Exclude results that directly match the 2022 baseline against 2024 by literal string matching without first applying the 2023 carry-over filter.","Exclude matching results that do not handle the Apamistamab naming drift.","Exclude cases where complete absence in 2024 is treated as a lookup failure rather than a status that must be output."],"normalization":{"field_separator":"~","record_separator":"|","schema":["INN","category_2022","phase_2022","prediction_label_2023","status_2024","phase_or_NA_2024","indication_or_NA_2024","region_or_NA_2024"],"category_2022":"emit `NC` or `CA` exactly","phase_2022":"normalize stage labels such as `Phase 3` to `P3` and `Pivotal Phase 2` to `P2`","prediction_label_2023":"keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H1 2023`","status_2024":"emit one of `A`, `R`, `F`, or `D` exactly","conditional_fields_2024":"if status is A or R, phase_or_NA_2024 must be `NA` and region_or_NA_2024 must carry the raw region string; if status is F, region_or_NA_2024 is `NA` and phase_or_NA_2024 carries the normalized phase; if status is D, all three trailing 2024 fields are `NA`","naming_exception":"preserve the fixed source exception around the Apamistamab-I-131 naming variant instead of over-normalizing the INN","sorting_or_selection":"INN alphabetical ascending"}}} +{"task_id":"europemc_005-g","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":20,"instruction":"I am compiling a cross-platform summary of predictors for COVID-19 inpatient outcome trajectories. This task centers on a 2024 WHO global individual patient data validation paper and its three linked original model papers. In this 2024 validation paper, four prognostic models ultimately completed external validation in low- and middle-income country data. We need to identify which distinct admission variables each of these four models used in their actual evaluations.\nFor each admission variable identified, we need to determine its characteristics in actual use: first, its matching difficulty in the WHO platform baseline table, i.e., whether it can be matched directly under the same or a substantively equivalent name or must go through a fixed mapping; second, its source background, i.e., whether it belongs to the model with the strongest performance in validation, the model with calibration closest to ideal, or an original model that explicitly used dynamic data.\nTo ensure consistency, model abbreviations, performance attributions, dynamic-data attributes, and variable conflicts shall be based on verifiable model descriptions, summary performance results, method explanations, and field definitions in the target literature; any variable naming or mapping differences shall be marked with a conservative correspondence that maintains cross-model interpretability.\nIf all four articles (the one validation paper and the three original model papers) can be found in the database, please organize all extracted variable information and output it as a single string with no spaces, joining records by | in strict alphabetical order of variable names (if the four articles cannot be found, output NONE).\nFormat requirement: each variable's internal information must be written in the fixed format variable~category~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict. Boolean states use 1 for yes and 0 for no; WHO baseline table matching uses E for a direct or substantively equivalent-name match and M for fixed mapping required.","start_url":"https://europepmc.org/advancesearch","output_format":"If all four articles (the one validation paper and the three original model papers) can be found in the database, organize all extracted variable information and output it as a single string with no spaces, joining records by | in strict alphabetical order of variable names; if the four articles cannot be found, output NONE. Each variable's internal information must be written in the fixed format variable~category~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict. Boolean states use 1 for yes and 0 for no; WHO baseline table matching uses E for a direct or substantively equivalent-name match and M for fixed mapping required.","oracle_answer":"Age~DEM~1~1~1~1~Age~E~1~1~1~0|Cancer~COM~0~0~1~0~Cancer~E~1~0~0~0|Chronic kidney disease~COM~0~0~0~1~CKD~M~0~0~0~1|Chronic lung disease~COM~0~0~1~0~Pulmonary disease~M~1~0~0~0|Chronic renal disease~COM~0~0~1~0~CKD~M~1~0~0~1|Coronary heart disease~COM~0~1~0~0~CHD~M~0~0~0~1|Cough~SYM~0~0~1~0~Cough~E~1~0~0~0|Diabetes mellitus~COM~0~0~1~0~Diabetes~M~1~0~0~0|Diarrhea~SYM~0~0~1~0~Diarrhea~E~1~0~0~0|Dyspnea~SYM~0~0~1~0~Dyspnea~E~1~0~0~0|Fever~VIT~0~0~0~1~Body temperature~M~0~0~0~0|Heart disease~COM~0~0~1~0~CHD~M~1~0~0~1|Hypertension~COM~0~1~1~0~Hypertension~E~1~0~0~0|Immunocompromised status~COM~0~0~1~0~Immunosuppression~M~1~0~0~0|O2 saturation~VIT~1~0~0~0~Oxygen saturation~M~0~1~1~0|Respiratory rate~VIT~1~0~0~1~Respiratory rate~E~0~1~1~0|Sex~DEM~0~0~1~0~Men~M~1~0~0~0|Smoking~DEM~1~0~0~0~Smoking~E~0~1~1~1|Smoking status~DEM~0~0~0~1~Smoking~M~0~0~0~1|Systolic blood pressure~VIT~0~0~0~1~Systolic blood pressure~E~0~0~0~0","metadata":{"State-Gated Retrieval":["First, in the 2024 WHO global individual patient data validation paper, identify the four prognostic models that successfully completed external validation in LMIC data, and trace back to the three corresponding original model papers.","For each predictor, retain the original wording from WHO Table 1, and annotate its matching method in the WHO baseline table as E or M, and whether it comes from the TopAUC, BestCal, or Dyn model.","When encountering a predictor that is conceptually merged on the WHO side, trace back to the original Wang/Zhou papers to split it apart before recalculating the relevant fields."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the 2024 WHO global validation paper yields the four externally validated models and the WHO-side predictor wording/mapping baseline","the three original model papers yield model-specific predictor wordings, dynamic-data flags, and conflicts hidden by WHO-side conceptual merging","final rows are produced only after WHO predictors are kept separate, traced back to the original papers, and then re-annotated for mapping and model provenance"],"control_dependency":["conceptually merged WHO predictors must be split back out when the original Wang/Zhou papers expose distinct variables","Table 2 mapping decisions are not valid until Table 1 wording and original-paper predictor sets are reconciled","TopAUC / BestCal / Dyn flags must be determined after the predictor split is applied correctly"],"freeze":{"historical_window":"the 2024 WHO global IPD validation paper and the three linked original COVID prognosis-model papers, using their current open-access full texts and tables"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["First, in the 2024 WHO global individual patient data validation paper, identify the four prognostic models that successfully completed external validation in LMIC data, and trace back to the three corresponding original model papers.","For each predictor, retain the original wording from WHO Table 1, and annotate its matching method in the WHO baseline table as E or M, and whether it comes from the TopAUC, BestCal, or Dyn model.","When encountering a predictor that is conceptually merged on the WHO side, trace back to the original Wang/Zhou papers to split it apart before recalculating the relevant fields."],"exclusion_conditions":["Exclude results that directly merge conceptually similar predictors after WHO Table 1 without tracing back to the original papers for splitting.","Exclude results that rely solely on WHO Table 2 for loose mapping without incorporating the original paper wording.","Exclude results that fix TopAUC / BestCal / Dyn annotations before the predictor split correction is applied."],"normalization":{"field_separator":"~","record_separator":"|","schema":["variable","category","B","W","Zh","Zo","WHOfield","WHOx","TopAUC","BestCal","Dyn","Conflict"],"variable_set":"the candidate variable set comes only from the WHO validation Table 1 and remains at the original 20 predictors","conflict_groups":"do not pre-merge the three source conflict groups `Smoking`/`Smoking status`, `Chronic renal disease`/`Chronic kidney disease`, and `Coronary heart disease`/`Heart disease` before applying the conflict flag","boolean_fields":"B, W, Zh, Zo, TopAUC, BestCal, Dyn, and Conflict are emitted as 1 or 0 only","WHOx":"emit `E` for exact WHO matches or direct matches under a substantively equivalent name, `M` for the fixed mapped match, and `NA` when no WHO field matches","sorting_or_selection":"variable name alphabetical ascending"}}} +{"task_id":"genome_001-g","domain":"KEGG_BRITE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"From KEGG, identify immunosuppressants used for ulcerative colitis that have been approved in Japan by the end of June 2025 and carry clear cytochrome P450 (CYP) metabolism or inhibition evidence. For each qualifying drug, retain its Japanese therapeutic classification code, ATC code, corresponding target branch, and Japan first approval date. Output a single-line string sorted by Japan first approval date from earliest to latest, formatted as ||||; separate multiple entries with commas; if no qualifying items exist, output NONE.","start_url":"https://www.genome.jp/kegg/brite.html","output_format":"Output a single-line string sorted by Japan first approval date from earliest to latest, formatted as ||||; separate multiple entries with commas; if no qualifying items exist, output NONE.","oracle_answer":"D09783|3999|L04AF01|JAK1/JAK2/JAK3/TYK2|2013/3/25,D11048|3999|L04AF03|JAK1|2020/1/23,D10931|2399|L04AE05|S1PR1/S1PR4/S1PR5|2025/6/24","metadata":{"State-Gated Retrieval":["Within the scope of KEGG immunosuppressants for ulcerative colitis, retain only those approved in Japan by 2025-06-30 and carrying clear CYP-related metabolism information or CYP inhibition evidence.","Each candidate drug must be re-verified against the corrected UC drug list for Japanese therapeutic classification, ATC, target branch, CYP evidence, and Japan first approval date.","Finally, output sorted by Japan first approval date from earliest to latest."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["KEGG disease H01466 and linked drug entries yield the ulcerative-colitis immunosuppressant candidate set","each candidate drug entry yields Japanese class, ATC, target branch, CYP metabolism/inhibition evidence, and Japan approval date","final rows are produced only after the full UC candidate set is determined and every candidate is checked against CYP evidence and PMDA timing"],"control_dependency":["the candidate set must include Japanese class 3999 UC drugs when the disease page exposes them rather than being limited to 2399 alone","target / CYP / PMDA validation must be applied across the full candidate set rather than only the old 2399 subset","entries without explicit CYP evidence may be dropped only after the full candidate set has been established"],"freeze":{"historical_window":"KEGG ulcerative-colitis drug entries as objectively existing drug entities, using target, CYP, Japan-class, and related entry metadata as relatively stable annotations"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Within the scope of KEGG immunosuppressants for ulcerative colitis, retain only those approved in Japan by 2025-06-30 and carrying clear CYP-related metabolism information or CYP inhibition evidence.","Each candidate drug must be re-verified against the corrected UC drug list for Japanese therapeutic classification, ATC, target branch, CYP evidence, and Japan first approval date.","Finally, output sorted by Japan first approval date from earliest to latest."],"exclusion_conditions":["Exclude results that incorrectly lock the upstream scope to the 2399 digestive branch without falling back to the full UC drug list.","Exclude entries without clear CYP-related metabolism information or CYP inhibition evidence.","Exclude entries with a Japan approval date after 2025-06-30 or that are not within the KEGG UC immunosuppressant scope."],"normalization":{"field_separator":"|","record_separator":",","schema":["DRUG_ID","JP_class","ATC","Target_branch","JP_date"],"dedup_key":"DRUG_ID","JP_date":"use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value","Target_branch":"emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`","sorting_or_selection":{"primary":"JP_date ascending","secondary":"DRUG_ID ascending"}}}} +{"task_id":"genome_002-g","domain":"KEGG_GENOME","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"From the KEGG host–symbiont examples, identify animal endosymbiosis cases whose bacterial symbiont KEGG GENOME entry was already recorded by the end of 2005 and whose bacterial symbiont genome contains a clearly named extra replicon. Additionally, the names of these replicons must directly correspond to amino acid biosynthesis modules on the host–symbiont joint pathway map. For the surviving case(s), list all qualifying pathway–module–replicon combinations. Output a single-line string in the format |||||, sorted by pathway ID in ascending order, with entries separated by commas. If no qualifying items exist, output NONE. Use KEGG organism codes for species identifiers.","start_url":"https://www.genome.jp/kegg/genome/","output_format":"Output a single-line string in the format |||||, sorted by pathway ID in ascending order, with entries separated by commas. If no qualifying items exist, output NONE. Use KEGG organism codes for species identifiers.","oracle_answer":"api+buc|buc|00290|M00432|pLeu|2000,api+buc|buc|00400|M00023|pTrp|2000","metadata":{"State-Gated Retrieval":["Retain only host–symbiont examples where the bacterial symbiont KEGG GENOME Created year is no later than 2005 and the genome carries a named extra replicon.","The names of these replicons must directly correspond to amino acid biosynthesis modules on the host–symbiont joint pathway page.","Finally, output all qualifying pathway–module–replicon records from the surviving case(s), sorted by pathway ID in ascending order."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["KEGG host–symbiont examples and symbiont genome pages yield the pre-2006 candidate pairs and named extra replicons","Joint pathway maps, module pages, and genome annotations yield the pathway–module–replicon links attributable to the symbiont side","Final rows are produced only after the surviving host–symbiont pair is validated against both replicon existence and module support on the joint pathway page"],"control_dependency":["Only branches satisfying the named-plasmid requirement may be retained, so the bmy+wbm branch must be excluded when the wbm genome page fails that requirement","Module retrieval must use the api+buc pathway state and the 00400 view, because that view is the one that actually exposes M00023","Module support is valid only after symbiont-side evidence for both M00023 and M00432 is validated in the selected pathway state"],"freeze":{"historical_window":"KEGG host–symbiont examples as objectively existing biological entities, using joint pathway, module, and genome replicon annotations as relatively stable structural information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Retain only host–symbiont examples where the bacterial symbiont KEGG GENOME Created year is no later than 2005 and the genome carries a named extra replicon.","The names of these replicons must directly correspond to amino acid biosynthesis modules on the host–symbiont joint pathway page.","Finally, output all qualifying pathway–module–replicon records from the surviving case(s), sorted by pathway ID in ascending order."],"exclusion_conditions":["Exclude cases like bmy+wbm where the symbiont genome page does not satisfy the named-plasmid requirement.","Exclude results that only follow pathway names along pages such as 00380 without returning to the joint pathway page to verify module evidence.","Exclude records where the replicon–module relationship cannot be directly established on the joint pathway map."],"normalization":{"field_separator":"|","record_separator":",","schema":["group","symbiont","pathway","module","replicon","created_year"],"group":"Use the canonical host–symbiont group label from the source workflow, such as `api+buc`","symbiont":"Use the bare lowercase KEGG organism code","pathway":"Emit the numeric KEGG pathway ID without a `map` prefix","module":"Normalize the KEGG module identifier to the `Mxxxxx` form","replicon":"Preserve the named extra replicon exactly as displayed in the source, such as `pLeu` or `pTrp`","created_year":"Emit the four-digit created year","sorting_or_selection":"Pathway numeric ascending"}}} +{"task_id":"genome_004-g","domain":"KEGG_BRITE","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"I am compiling an ordered table of systemic drugs approved for plaque psoriasis in Japan. Include only active ingredients that were approved in Japan by the end of 2024, are used for systemic treatment of plaque psoriasis, and target the IL-17/IL-23 signaling axis. Exclude topical drugs and systemic drugs acting through other axes. Output multiple rows sorted by Japan first approval date from earliest to latest; for drugs approved on the same day, sort by DRUG_ID ascending. Each row format: ||||.","start_url":"https://www.kegg.jp/brite/br08301","output_format":"Output multiple rows sorted by Japan first approval date from earliest to latest; for drugs approved on the same day, sort by DRUG_ID ascending. Each row format: ||||.","oracle_answer":"D09967|Secukinumab|L04AC10|IL17A|2014/12/26\nD10061|Brodalumab|L04AC12|IL17RA|2016/7/4\nD10071|Ixekizumab|L04AC13|IL17A|2016/7/4\nD10438|Guselkumab|L04AC16|IL23A|2018/3/23\nD11052|Risankizumab|L04AC18|IL23A|2019/3/26\nD10400|Tildrakizumab|L04AC17|IL23A|2020/6/29\nD11550|Bimekizumab|L04AC21|IL17A/IL17F|2022/1/20\nD11817|Deucravacitinib|L04AF07|TYK2|2022/9/26","metadata":{"State-Gated Retrieval":["Retain only active ingredients that were approved in Japan by 2024-12-31, are used for systemic treatment of plaque psoriasis, and genuinely act on the IL-17/IL-23 signaling axis.","The candidate set must cover the ligand side, receptor side, and TYK2 kinase side, not only the interleukin ligand side.","Final entries sorted by Japan first approval date ascending; for the same date, sort by DRUG_ID ascending."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["KEGG disease/drug entry points yield the Japan-approved systemic plaque-psoriasis drug cohort through 2024-12-31","each drug entry yields target branch, ATC, systemic-use validity, and Japan approval date for IL-17/IL-23-axis candidates","final rows are produced only after ligand-side, receptor-side, and kinase-side candidates are jointly reconciled and re-sorted by Japan approval date"],"control_dependency":["entry-point coverage must include receptor-side IL17RA and kinase-side TYK2 mechanisms when downstream drug pages expose them, rather than staying ligand-only","Ustekinumab must be removed only when target interpretation shows IL12 + IL23A rather than the IL-17/IL-23-axis criterion required here","systemic-use, Japanese 3999, and PMDA-date filtering must be applied after each expansion of the candidate set rather than attached to the earlier ligand-only state"],"freeze":{"historical_window":"KEGG plaque-psoriasis systemic-drug entries as objectively existing drug entities, using target-branch and related drug-entry metadata as relatively stable annotations"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Retain only active ingredients that were approved in Japan by 2024-12-31, are used for systemic treatment of plaque psoriasis, and genuinely act on the IL-17/IL-23 signaling axis.","The candidate set must cover the ligand side, receptor side, and TYK2 kinase side, not only the interleukin ligand side.","Final entries sorted by Japan first approval date ascending; for the same date, sort by DRUG_ID ascending."],"exclusion_conditions":["Exclude topical drugs, non-systemic drugs, or entries outside the specified historical freeze window.","Exclude Ustekinumab, whose actual target is IL12 + IL23A, because it does not meet the IL-17/IL-23 axis criterion required here.","Exclude results that miss Brodalumab or Deucravacitinib due to considering only the ligand side."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["DRUG_ID","Name","ATC","Target_branch","PMDA_date"],"PMDA_date":"use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value","Target_branch":"emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`","sorting_or_selection":{"primary":"PMDA_date ascending","secondary":"DRUG_ID ascending"}}}} +{"task_id":"genome_004-g","domain":"KEGG_GENOME","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am preparing a handout for a primate evolution course and want a two-row comparison table for this vitamin C metabolism exception pattern. Output two rows with columns rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year. The first row should be EXCEPTION_CLADE and the second row RETAINED_SISTER_CLADE. Use KEGG organism codes for the example species.","start_url":"https://www.genome.jp/kegg/kegg2.html","output_format":"Output a two-row comparison table with columns rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year.","oracle_answer":"1|EXCEPTION_CLADE|Primates|Haplorrhini|map00053|map00040|M00014|M00129|LOST|csyr|2022\n2|RETAINED_SISTER_CLADE|Primates|Strepsirrhini|map00053|map00040|M00014|M00129|RETAINED|oga|2022","metadata":{"State-Gated Retrieval":["Search only among primate genome entries established by the end of 2022, and isolate the anomalous lower-level clade that retains the upstream glucuronate module M00014 but lacks the animal-type vitamin C biosynthesis module M00129.","That anomalous clade must be paired with a sister branch under the same higher-level split, and the sister branch must still retain M00129.","The final output must place the anomalous branch and the retained sister branch into a two-row comparison table, including the required pathway, module, and example-species fields."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the KEGG primate clade pages and genome entries yield candidate subclades and example species established through the cutoff year","the pathway and module views yield M00014 and M00129 presence/absence evidence for the exception clade and its sister branch","final rows are produced only after the exception clade and retained sister branch are jointly validated under the same parent split and paired with example organisms"],"control_dependency":["the exception clade remains provisional until both the sister-branch contrast and the example-species checks succeed","the comparison view must make retained M00014 and missing M00129 visible together","the two output rows are emitted together only after the exception clade and retained sister branch are fixed under the same parent split"],"freeze":{"historical_window":"the objectively existing primate genome entries established on or before 2022, using current KEGG clade, pathway, and module pages as relatively stable reference information for comparing retained M00014 against lost M00129"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Search only among primate genome entries established by the end of 2022, and isolate the anomalous lower-level clade that retains the upstream glucuronate module M00014 but lacks the animal-type vitamin C biosynthesis module M00129.","That anomalous clade must have a contrastable sister branch, and that sister branch must still retain M00129.","The final output must place the anomalous branch and the retained sister branch into a two-row comparison table, including the required pathway, module, and example-species fields."],"exclusion_conditions":["Exclude results that stop at Simiiformes without checking the broader boundary and therefore miss Haplorrhini.","Exclude pathway views that do not make the M00014 versus M00129 contrast visible together.","Exclude candidate clades that have not been validated against a retained sister branch."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","clade_role","parent_clade","clade","anomaly_pathway","contrast_pathway","retained_upstream_module","vitamin_c_synthesis_module","vitamin_c_module_status","example_org","cutoff_year"],"rank":"emit 1 for EXCEPTION_CLADE and 2 for RETAINED_SISTER_CLADE","clade_role":["EXCEPTION_CLADE","RETAINED_SISTER_CLADE"],"pathway_normalization":"emit KEGG pathway ids with the map prefix","module_normalization":"emit KEGG module ids with the leading M","vitamin_c_module_status":["LOST","RETAINED"],"organism_code":"use bare KEGG organism codes in lowercase, not species names","cutoff_year":"use a four-digit year; this task is frozen at 2022","sorting_or_selection":"emit rows in the fixed order EXCEPTION_CLADE then RETAINED_SISTER_CLADE"}}} +{"task_id":"nvd_001-g","domain":"NVD","autonomy_type":"ordered table","instruction":"Identify which milestone versions of Apache Tomcat 9.0.0, released before the final GA release, are both affected by all four specified CVEs and have a CPE name notation change in NVD history. A CPE name notation change means the same milestone version was recorded as mN in older records but changed to milestoneN in current records. The search scope is limited to Apache Tomcat 9.0.0 milestone versions; these versions must appear in the current NVD affected product configurations for CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797. Exclude milestone versions brought in only by other Tomcat 9.0.0 pre-release related vulnerabilities, and also exclude Tomcat 6, Tomcat 7, Tomcat 8, Tomcat 8.5, and all non-Tomcat products. Output a multi-row ordered table with columns: milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd, sorted by milestone number in ascending order.","start_url":"https://nvd.nist.gov/vuln/search#/nvd/home?resultType=records","output_format":"Output a multi-row ordered table with columns: milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd, sorted by milestone number in ascending order.","oracle_output_cardinality":3,"oracle_answer":"CVE:2018-7543|1.2.32|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2018-17207|1.2.42|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2020-11738|1.3.28|lite+pro|ModifiedAnalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02","metadata":{"State-Gated Retrieval":["Retain only Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator and whose deprecated vendor chain traces back to snapcreek:duplicator.","Each candidate CVE must satisfy all of the following in its Change History: the Initial Analysis was not yet lite/lite+pro; the first change to lite or lite+pro occurred in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurred on 2026-02-02.","The final output retains only CVE rows that meet all three conditions above."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["NVD product/CPE search pages yield the current awesomemotive:duplicator family and the deprecated snapcreek:duplicator lineage","each target CVE detail page and Change History yield the Initial Analysis state, the first lite/lite+pro analysis event, and the 2026-02-02 vendor-remap event","final rows are produced only after candidate CVEs are intersected on both snapcreek -> awesomemotive migration and later introduction of lite/lite+pro in NIST analysis history"],"control_dependency":["the search must include the deprecated snapcreek lineage rather than only the current product state","vendor migration alone is insufficient until detail-level history confirms that lite/lite+pro was introduced after Initial Analysis","candidate CVEs must be filtered against the full change-history chronology, excluding any whose Initial Analysis already contained lite"],"freeze":{"historical_window":"Duplicator CVEs published from 2018-01-01 through 2024-12-31, evaluated against NVD analysis history up to the 2026-02-02 snapcreek -> awesomemotive vendor-remap events"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Retain only Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator and whose deprecated vendor chain traces back to snapcreek:duplicator.","Each candidate CVE must satisfy all of the following in its Change History: the Initial Analysis was not yet lite/lite+pro; the first change to lite or lite+pro occurred in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurred on 2026-02-02.","The final output retains only CVE rows that meet all three conditions above."],"exclusion_conditions":["Exclude results that rely only on the current description or current product state without tracing back to the deprecated snapcreek chain and Change History.","Exclude CVEs whose Initial Analysis was already lite/lite+pro.","Exclude records without a 2026-02-02 vendor remap or that do not belong to the Duplicator product line."],"normalization":{"field_separator":"|","record_separator":",","schema_note":"the current source docx rubric, evidence, and oracle answer use a Duplicator CVE rowset, even though the instruction/output_format text still describes a Tomcat milestone task; normalization therefore follows the checked oracle row schema rather than the stale milestone wording","schema":["CVE","lite_upper_version","lite_vs_lite+pro","analysis_event@date","snapcreek_to_awesomemotive@date"],"CVE":"emit the identifier in the canonical `CVE:YYYY-NNNN` form used by the oracle","lite_vs_lite+pro":"emit `lite` or `lite+pro` exactly","analysis_event@date":"emit `Reanalysis@YYYY-MM-DD` or `ModifiedAnalysis@YYYY-MM-DD` exactly as supported by the source record","snapcreek_to_awesomemotive@date":"emit the ownership-transfer event as `snapcreek->awesomemotive@YYYY-MM-DD`","sorting_or_selection":{"primary":"NVD published date ascending","secondary":"CVE ascending"}}}} +{"task_id":"nvd_002-g","instruction":"We are compiling an exception list of legacy MySQL 5.1 assets left after Oracle's acquisition of MySQL. We need to identify which old CPE 2.3 entries whose name prefix still reads mysql:mysql were explicitly remapped by NIST to the corresponding oracle:mysql entries in the NVD history records for four InnoDB denial-of-service vulnerabilities. Start with CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680. For each vulnerability, examine the relevant CPE change records in NVD and find MySQL 5.1 entries where the prefix changed from mysql:mysql to oracle:mysql in all four vulnerabilities. During screening, retain only records that underwent this legacy-to-current prefix migration; exclude MySQL 5.0 branch entries and entries that only performed version alias normalization within the old mysql:mysql prefix. Finally, output a multi-row ordered table with columns version_update | legacy_cpe | current_cpe | remap_time_nvd, sorted by numeric version in ascending order; within the same version, records with an empty update field come before those with a non-empty update.","domain":"NVD","autonomy_type":"ordered table","oracle_output_cardinality":44,"start_url":"https://nvd.nist.gov/products/cpe/search","output_format":"Output a multi-row ordered table with columns version_update | legacy_cpe | current_cpe | remap_time_nvd, sorted by numeric version in ascending order; within the same version, entries without an update come before entries with an update.","oracle_answer":"version_update|legacy_cpe|current_cpe|remap_time_nvd\n5.1.1|cpe:2.3:a:mysql:mysql:5.1.1:::::::*|cpe:2.3:a:oracle:mysql:5.1.1:::::::*|2019-12-17 15:04:33\n5.1.2|cpe:2.3:a:mysql:mysql:5.1.2:::::::*|cpe:2.3:a:oracle:mysql:5.1.2:::::::*|2019-12-17 15:04:39\n5.1.3|cpe:2.3:a:mysql:mysql:5.1.3:::::::*|cpe:2.3:a:oracle:mysql:5.1.3:::::::*|2019-12-17 15:04:46\n5.1.4|cpe:2.3:a:mysql:mysql:5.1.4:::::::*|cpe:2.3:a:oracle:mysql:5.1.4:::::::*|2019-12-17 15:04:53\n5.1.10|cpe:2.3:a:mysql:mysql:5.1.10:::::::*|cpe:2.3:a:oracle:mysql:5.1.10:::::::*|2019-12-17 15:05:30\n5.1.11|cpe:2.3:a:mysql:mysql:5.1.11:::::::*|cpe:2.3:a:oracle:mysql:5.1.11:::::::*|2019-12-17 15:05:37\n5.1.12|cpe:2.3:a:mysql:mysql:5.1.12:::::::*|cpe:2.3:a:oracle:mysql:5.1.12:::::::*|2019-12-17 15:05:45\n5.1.13|cpe:2.3:a:mysql:mysql:5.1.13:::::::*|cpe:2.3:a:oracle:mysql:5.1.13:::::::*|2019-12-17 15:05:52\n5.1.14|cpe:2.3:a:mysql:mysql:5.1.14:::::::*|cpe:2.3:a:oracle:mysql:5.1.14:::::::*|2019-12-17 15:05:59\n5.1.15|cpe:2.3:a:mysql:mysql:5.1.15:::::::*|cpe:2.3:a:oracle:mysql:5.1.15:::::::*|2019-12-17 15:06:07\n5.1.16|cpe:2.3:a:mysql:mysql:5.1.16:::::::*|cpe:2.3:a:oracle:mysql:5.1.16:::::::*|2019-12-17 15:06:14\n5.1.17|cpe:2.3:a:mysql:mysql:5.1.17:::::::*|cpe:2.3:a:oracle:mysql:5.1.17:::::::*|2019-12-17 15:06:21\n5.1.18|cpe:2.3:a:mysql:mysql:5.1.18:::::::*|cpe:2.3:a:oracle:mysql:5.1.18:::::::*|2019-12-17 15:06:27\n5.1.19|cpe:2.3:a:mysql:mysql:5.1.19:::::::*|cpe:2.3:a:oracle:mysql:5.1.19:::::::*|2019-12-17 15:06:34\n5.1.20|cpe:2.3:a:mysql:mysql:5.1.20:::::::*|cpe:2.3:a:oracle:mysql:5.1.20:::::::*|2019-12-17 15:06:42\n5.1.21|cpe:2.3:a:mysql:mysql:5.1.21:::::::*|cpe:2.3:a:oracle:mysql:5.1.21:::::::*|2019-12-17 15:06:50\n5.1.22|cpe:2.3:a:mysql:mysql:5.1.22:::::::*|cpe:2.3:a:oracle:mysql:5.1.22:::::::*|2019-12-17 15:06:56\n5.1.23:a|cpe:2.3:a:mysql:mysql:5.1.23:a::::::|cpe:2.3:a:oracle:mysql:5.1.23:a::::::|2019-12-17 15:23:28\n5.1.24|cpe:2.3:a:mysql:mysql:5.1.24:::::::*|cpe:2.3:a:oracle:mysql:5.1.24:::::::*|2019-12-17 15:07:03\n5.1.25|cpe:2.3:a:mysql:mysql:5.1.25:::::::*|cpe:2.3:a:oracle:mysql:5.1.25:::::::*|2019-12-17 15:07:10\n5.1.26|cpe:2.3:a:mysql:mysql:5.1.26:::::::*|cpe:2.3:a:oracle:mysql:5.1.26:::::::*|2019-12-17 15:07:17\n5.1.27|cpe:2.3:a:mysql:mysql:5.1.27:::::::*|cpe:2.3:a:oracle:mysql:5.1.27:::::::*|2019-12-17 15:07:24\n5.1.28|cpe:2.3:a:mysql:mysql:5.1.28:::::::*|cpe:2.3:a:oracle:mysql:5.1.28:::::::*|2019-12-17 15:07:31\n5.1.29|cpe:2.3:a:mysql:mysql:5.1.29:::::::*|cpe:2.3:a:oracle:mysql:5.1.29:::::::*|2019-12-17 15:07:38\n5.1.30|cpe:2.3:a:mysql:mysql:5.1.30:::::::*|cpe:2.3:a:oracle:mysql:5.1.30:::::::*|2019-12-17 15:07:46\n5.1.31:sp1|cpe:2.3:a:mysql:mysql:5.1.31:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.31:sp1::::::|2019-12-17 15:23:35\n5.1.33|cpe:2.3:a:mysql:mysql:5.1.33:::::::*|cpe:2.3:a:oracle:mysql:5.1.33:::::::*|2019-12-17 15:07:55\n5.1.34:sp1|cpe:2.3:a:mysql:mysql:5.1.34:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.34:sp1::::::|2019-12-17 15:23:42\n5.1.35|cpe:2.3:a:mysql:mysql:5.1.35:::::::*|cpe:2.3:a:oracle:mysql:5.1.35:::::::*|2019-12-17 15:08:03\n5.1.36|cpe:2.3:a:mysql:mysql:5.1.36:::::::*|cpe:2.3:a:oracle:mysql:5.1.36:::::::*|2019-12-17 15:08:10\n5.1.37:sp1|cpe:2.3:a:mysql:mysql:5.1.37:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.37:sp1::::::|2019-12-17 15:23:49\n5.1.38|cpe:2.3:a:mysql:mysql:5.1.38:::::::*|cpe:2.3:a:oracle:mysql:5.1.38:::::::*|2019-12-17 15:08:17\n5.1.39|cpe:2.3:a:mysql:mysql:5.1.39:::::::*|cpe:2.3:a:oracle:mysql:5.1.39:::::::*|2019-12-17 10:22:31\n5.1.40|cpe:2.3:a:mysql:mysql:5.1.40:::::::*|cpe:2.3:a:oracle:mysql:5.1.40:::::::*|2019-12-17 10:22:46\n5.1.40:sp1|cpe:2.3:a:mysql:mysql:5.1.40:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.40:sp1::::::|2019-12-17 10:22:39\n5.1.41|cpe:2.3:a:mysql:mysql:5.1.41:::::::*|cpe:2.3:a:oracle:mysql:5.1.41:::::::*|2019-12-17 10:22:52\n5.1.42|cpe:2.3:a:mysql:mysql:5.1.42:::::::*|cpe:2.3:a:oracle:mysql:5.1.42:::::::*|2019-12-17 10:22:59\n5.1.43|cpe:2.3:a:mysql:mysql:5.1.43:::::::*|cpe:2.3:a:oracle:mysql:5.1.43:::::::*|2019-12-17 10:23:06\n5.1.43:sp1|cpe:2.3:a:mysql:mysql:5.1.43:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.43:sp1::::::|2019-12-17 10:23:11\n5.1.44|cpe:2.3:a:mysql:mysql:5.1.44:::::::*|cpe:2.3:a:oracle:mysql:5.1.44:::::::*|2019-12-17 10:23:17\n5.1.45|cpe:2.3:a:mysql:mysql:5.1.45:::::::*|cpe:2.3:a:oracle:mysql:5.1.45:::::::*|2019-12-17 10:23:24\n5.1.46|cpe:2.3:a:mysql:mysql:5.1.46:::::::*|cpe:2.3:a:oracle:mysql:5.1.46:::::::*|2019-12-17 10:23:38\n5.1.46:sp1|cpe:2.3:a:mysql:mysql:5.1.46:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.46:sp1::::::|2019-12-17 10:23:31\n5.1.47|cpe:2.3:a:mysql:mysql:5.1.47:::::::*|cpe:2.3:a:oracle:mysql:5.1.47:::::::*|2019-12-17 10:23:45","metadata":{"State-Gated Retrieval":["Retain only CPE 2.3 entries in the MySQL 5.1 branch for which the vendor migration from mysql:mysql to oracle:mysql is clearly visible in the NVD Change History for all four vulnerabilities CVE-2010-3676, 3677, 3678, and 3680.","Every result must provide version_update, legacy_cpe, current_cpe, and remap_time_nvd.","Within the same version, entries without an update come before entries with an update, and output is sorted by numeric version in ascending order."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Current and deprecated MySQL 5.1 CPE search results yield candidate legacy/current CPE strings","The four target CVE pages and their Change History entries yield vendor-migration evidence, exact version_update strings, and remap timestamps","Final rows are produced only after taking the common mysql:mysql 5.1 -> oracle:mysql 5.1 migrations across all four CVEs and removing alias-only or 5.0 entries"],"control_dependency":["Legacy vendor mapping must be determined from Analysis Description plus Change History rather than from the current description/current CPE view","Include-deprecated results cannot be accepted wholesale because alias-only remaps must be filtered out","5.1-branch membership and sort order must be determined after the vendor-migration filter removes 5.0 and non-migration rows"],"freeze":{"historical_window":"The MySQL 5.1 branches visible in CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680, restricted to explicit mysql:mysql -> oracle:mysql vendor-migration events"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Retain only CPE 2.3 entries in the MySQL 5.1 branch for which the vendor migration from mysql:mysql to oracle:mysql is clearly visible in the NVD Change History for all four vulnerabilities CVE-2010-3676, 3677, 3678, and 3680.","Every result must provide version_update, legacy_cpe, current_cpe, and remap_time_nvd.","Within the same version, entries without an update come before entries with an update, and output is sorted by numeric version in ascending order."],"exclusion_conditions":["Exclude MySQL 5.0 branch entries.","Exclude entries that still belong to the old vendor mysql:mysql and only underwent internal version alias normalization without a vendor migration.","Exclude results that only read from the current Oracle MySQL 5.1 CPE state without using legacy mapping and Change History."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"Required literal first row `version_update|legacy_cpe|current_cpe|remap_time_nvd`","schema":["version_update","legacy_cpe","current_cpe","remap_time_nvd"],"version_update":"Sort by numeric MySQL version ascending; within the same base version, the empty update comes before any non-empty update suffix","legacy_cpe":"Preserve the exact legacy CPE 2.3 string","current_cpe":"Preserve the exact current CPE 2.3 string","remap_time_nvd":"Emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form","dedup_key":"(legacy_cpe, current_cpe)"}}} +{"task_id":"nvd_004-g","domain":"NVD","autonomy_type":"ordered table","instruction":"Identify which milestone versions of Apache Tomcat 9.0.0 (prior to the final release) appear in the NVD current affected-product configurations for all four vulnerabilities CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797, and whose NVD change history shows a CPE identifier migration from the legacy mN form to the current milestoneN form. This step is intended to clean up SBOM rules that still use the old Apache Tomcat 9.0.0.Mx notation. Here, mN refers to forms such as m1, m2, etc., while milestoneN refers to the corresponding notation currently used by NVD. Retain only those Apache Tomcat 9.0.0 milestone versions that satisfy both conditions. Exclude two categories: (1) milestone versions that do not simultaneously meet the four-CVE condition and appear only because of other Tomcat 9.0.0 prerelease vulnerabilities; (2) Tomcat 6, Tomcat 7, Tomcat 8, Tomcat 8.5, and any non-Tomcat products. Output a multi-row ordered table with columns milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd, sorted by the numeric milestone value in ascending order.","start_url":"https://nvd.nist.gov/products/cpe/search","output_format":"Output a multi-row ordered table with columns milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd, sorted by the numeric milestone value in ascending order.","oracle_output_cardinality":9,"oracle_answer":"milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd\nM1|cpe:2.3:a:apache:tomcat:9.0.0:m1:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone1:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM2|cpe:2.3:a:apache:tomcat:9.0.0:m2:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone2:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM3|cpe:2.3:a:apache:tomcat:9.0.0:m3:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone3:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM4|cpe:2.3:a:apache:tomcat:9.0.0:m4:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone4:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM5|cpe:2.3:a:apache:tomcat:9.0.0:m5:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone5:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM6|cpe:2.3:a:apache:tomcat:9.0.0:m6:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone6:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM7|cpe:2.3:a:apache:tomcat:9.0.0:m7:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone7:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM8|cpe:2.3:a:apache:tomcat:9.0.0:m8:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone8:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM9|cpe:2.3:a:apache:tomcat:9.0.0:m9:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone9:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18","metadata":{"State-Gated Retrieval":["Retain only Apache Tomcat 9.0.0 milestone versions that appear in the current affected-product scope of all four target CVEs: CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797.","These versions must also show a CPE Deprecation Remap from mN to milestoneN in the NVD Change History.","Finally, output sorted by numeric milestone value in ascending order, and the required_cves field must contain exactly these four specified CVEs."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the current milestoneN CPE search and detail pages yield the Tomcat milestone family and the legacy mN mapping anchors","the four target CVE pages and Change History entries yield the exact mN -> milestoneN deprecation remaps and the required-CVE intersection","final rows are produced only after taking the remaps common to all four target CVEs and sorting by numeric milestone"],"control_dependency":["the candidate milestone set must be determined from the four-target-CVE intersection rather than from all prerelease Tomcat CVEs","later remapped milestones such as M10+ must be excluded by applying the specified four-CVE boundary","only explicit NVD CPE Deprecation Remap events from mN to milestoneN count, so generic Tomcat prerelease visibility cannot be accepted as evidence"],"freeze":{"historical_window":"the Tomcat 9.0.0 prerelease milestones jointly covered by CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797, with remap evidence fixed to the 2023-12-08 11:41:18 NVD deprecation events"},"answer_type":"multi-row ordered table"},"all_involved_urls":{"fixed_entry_and_docs":["https://nvd.nist.gov/products/cpe/search","https://nvd.nist.gov/vuln/vulnerability-detail-pages"],"cpe_search_result_pages":["https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL","https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED","https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20m&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED","https://nvd.nist.gov/products/cpe/search/results?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED"],"representative_cpe_detail_pages":["https://nvd.nist.gov/products/cpe/detail/615922?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED","https://nvd.nist.gov/products/cpe/detail/615947?keyword=cpe%3A2.3%3Aa%3Aapache&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED"],"row_level_cpe_api_urls_m1_to_m9":["https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone2%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone3%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone4%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone5%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone6%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone7%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone8%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A","https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone9%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A"],"target_cve_detail_pages":["https://nvd.nist.gov/vuln/detail/CVE-2016-5018","https://nvd.nist.gov/vuln/detail/CVE-2016-6794","https://nvd.nist.gov/vuln/detail/CVE-2016-6796","https://nvd.nist.gov/vuln/detail/CVE-2016-6797"],"negative_control_cve_detail_pages":["https://nvd.nist.gov/vuln/detail/CVE-2016-6816","https://nvd.nist.gov/vuln/detail/CVE-2016-6817","https://nvd.nist.gov/vuln/detail/CVE-2019-0221"],"cve_change_history_api":["https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-5018&eventName=CPE%20Deprecation%20Remap","https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6794&eventName=CPE%20Deprecation%20Remap","https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6796&eventName=CPE%20Deprecation%20Remap","https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6797&eventName=CPE%20Deprecation%20Remap","https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6816&eventName=CPE%20Deprecation%20Remap","https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6817&eventName=CPE%20Deprecation%20Remap","https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2019-0221&eventName=CPE%20Deprecation%20Remap"],"representative_change_record_pages":["https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=04%2F18%2F2022T13%3A57%3A03.500-0400","https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=08%2F24%2F2017T09%3A11%3A40.690-0400"]},"rubric":{"inclusion_conditions":["Retain only Apache Tomcat 9.0.0 milestone versions that appear in the current affected-product scope of all four target CVEs: CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797.","These versions must also show a CPE Deprecation Remap from mN to milestoneN in the NVD Change History.","Finally, output sorted by numeric milestone value in ascending order, and the required_cves field must contain exactly these four specified CVEs."],"exclusion_conditions":["Exclude milestones that are included only because of other Tomcat 9.0.0 prerelease vulnerabilities, such as M10/M11 and later milestones.","Exclude Tomcat 6, 7, 8, 8.5, and any non-Tomcat products.","Exclude records that lack explicit NVD remap evidence and are merely visible on the current milestone page."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"required literal first row `milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd`","schema":["milestone","legacy_cpe","current_cpe","required_cves","remap_time_nvd"],"milestone":"emit the canonical milestone label `M1` through `M9` and sort by the numeric suffix ascending","legacy_cpe":"preserve the exact legacy CPE 2.3 string containing the short milestone token such as `m1`","current_cpe":"preserve the exact current CPE 2.3 string containing the full milestone token such as `milestone1`","required_cves":"emit the fixed literal `CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797`","remap_time_nvd":"emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form"}}} +{"task_id":"reptile_001-g","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"I am compiling a name concordance for early museum specimens of Indian snakes recorded in George A. Boulenger's 1890 work \"The Fauna of British India, Including Ceylon and Burma\". In the Reptile Database, identify entries that simultaneously satisfy the following conditions: the currently accepted name has been reassigned to a different genus compared with the name used in the book; the current species page still retains BMNH type specimen information; and the type locality still corresponds to India. For each qualifying entry, also retrieve the most recent historical binomial listed on the current species page that has not yet adopted the current genus name, and determine whether an exact search using that full old name uniquely identifies the entry. Output the results sorted alphabetically by accepted name in the format |||; join multiple entries with semicolons; if no qualifying entries exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output the results sorted alphabetically by accepted name in the format |||; join multiple entries with semicolons; if no qualifying entries exist, output NONE.","oracle_answer":"Argyrophis oatesii|Typhlops oatesii|UNIQUE|SYNTYPES;Dendrelaphis grandoculis|Ahaetulla grandoculis|UNIQUE|LECTOTYPE;Fowlea sanctijohannis|Xenochrophis sanctijohannis|UNIQUE|HOLOTYPE;Gerrhopilus beddomii|Typhlops beddomii|UNIQUE|SYNTYPES;Hebius khasiensis|Amphiesma khasiense|UNIQUE|LECTOTYPE;Hebius parallelus|Amphiesma parallelum|AMBIG|LECTOTYPE;Indotyphlops jerdoni|Typhlops jerdoni|UNIQUE|SYNTYPES;Myriopholis blanfordii|Leptotyphlops blanfordi|AMBIG|SYNTYPES","metadata":{"State-Gated Retrieval":["Candidates must come from the historical Indian snake collection entries in Boulenger 1890 \"Fauna of British India\".","The current Reptile Database species page must simultaneously satisfy: the species has been reassigned to a different genus; the page still retains BMNH type specimen information; and the type locality still corresponds to India.","On each qualifying page, select the most recent historical binomial that has not yet adopted the current genus name, perform an exact back-search using that old name, and then label it UNIQUE or AMBIG."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["The Boulenger 1890 historical sample and current accepted-species pages yield candidates that changed genus while retaining BMNH type data and India-compatible type locality.","Each accepted page yields the nearest pre-current-genus old label, the BMNH type status, and the historical/type-locality evidence anchoring the entity.","Final rows are produced only after the old-label exact back-search is evaluated for uniqueness without losing the original entity anchor."],"control_dependency":["When an exact old-label back-search now hits multiple species, the original anchored entity must be kept and the uniqueness label must be set to AMBIG.","Once a candidate has passed the historical-cluster, genus-shift, BMNH, and India-locality gates, later old-label ambiguity can only rewrite the uniqueness field, not the entity itself.","Candidate anchoring must be preserved across the two-stage workflow so that old-label search noise does not redirect the accepted-species row."],"freeze":{"historical_window":"The objectively existing reptile taxa in the George A. Boulenger 1890 British India sample, using Reptile Database accepted pages, synonym labels, BMNH type data, and type-locality text as nearly objective and highly stable reference information."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Candidates must come from the historical Indian snake collection entries in Boulenger 1890 \"Fauna of British India\".","The current Reptile Database species page must simultaneously satisfy: the species has been reassigned to a different genus; the page still retains BMNH type specimen information; and the type locality still corresponds to India.","On each qualifying page, select the most recent historical binomial that has not yet adopted the current genus name, perform an exact back-search using that old name, and then label it UNIQUE or AMBIG."],"exclusion_conditions":["Exclude entries where the current accepted name has not undergone a genus change, or where the page no longer retains BMNH type specimen information.","Exclude entries whose type locality does not correspond to India.","Do not discard candidates for which the exact old-name back-search is non-unique; such candidates should retain the original entity and be labeled AMBIG."],"normalization":{"field_separator":"|","record_separator":";","schema":["accepted name","old label","UNIQUE/AMBIG","BMNH status"],"accepted_name":"Emit the current accepted binomial exactly as shown in the reconciled source.","old_label":"Preserve the historical label exactly as used on the legacy branch.","UNIQUE/AMBIG":"Emit `UNIQUE` or `AMBIG` in uppercase.","BMNH_status":"Normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or SYNTYPES.","sorting_or_selection":"Accepted name alphabetical ascending."}}} +{"task_id":"reptile_002-g","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am compiling name correspondences between old labels and current accepted names for early museum specimens of Southeast Asian Lygosoma. In the current Lygosoma checklist, identify all accepted species that satisfy both of the following conditions: the species page lists a Riopa combination used by Smith (1935/1937) in its Synonym section, and that old name corresponds to more than one accepted species under the current classification. For each qualifying species, output the first-listed type specimen number, type status, and the region corresponding to the final type locality on that page. Output in alphabetical order by accepted name, using the format ||||; join multiple entries with semicolons. If no qualifying items exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output in alphabetical order by accepted name, using the format ||||; join multiple entries with semicolons. If no qualifying items exist, output NONE.","oracle_answer":"Lygosoma bampfyldei|Riopa bampfyldei|BMNH 1946.8.10.84|SYNTYPES|East Malaysia;Lygosoma peninsulare|Riopa bampfyldei|LSUHC 13857|HOLOTYPE|Peninsular Malaysia;Lygosoma schneideri|Riopa bampfyldei|NMBA 4743|HOLOTYPE|Indonesia","metadata":{"State-Gated Retrieval":["Retain only accepted species that can be traced from the Smith 1937 old-name chain to a current Lygosoma record and for which the type accession, type status, and locality can be read on the current page.","For each accepted record, output the accepted name, the corresponding old label, the type accession, the type status, and the locality.","If the same exact old name appears on multiple accepted species, retain them as separate chains."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the Smith 1937 old-name chain yields the three current Lygosoma accepted pages connected to Riopa bampfyldei / Lygosoma bampfyldei","each accepted page yields its own type accession, type status, and type locality needed to separate the homonymous old-name paths","final rows are produced only after the one-to-many old-name split is rebuilt and the three paths are re-anchored to their own type evidence"],"control_dependency":["same-specific-epithet matching cannot establish a one-to-one mapping when the same Smith 1937 old name appears on multiple accepted pages","once literal old-name reuse is exposed, the workflow must keep the original parallel three-chain state rather than collapsing to a one-to-one mapping","type accession and locality evidence must be read separately for each chain rather than patched onto the first stopping page"],"freeze":{"historical_window":"the objectively existing taxa linked to the Smith 1937 old-name cluster around Riopa bampfyldei, using Reptile Database accepted pages together with type accessions, statuses, and localities as nearly objective and highly stable reference information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Retain only accepted species that can be traced from the Smith 1937 old-name chain to a current Lygosoma record and for which the type accession, type status, and locality can be read on the current page.","For each accepted record, output the accepted name, the corresponding old label, the type accession, the type status, and the locality.","If the same exact old name appears on multiple accepted species, retain them as separate chains."],"exclusion_conditions":["Exclude results that assume the same species simply because the old name and current specific epithet match.","Exclude results that retain only the first chain when the same exact old name appears on multiple accepted pages.","Exclude results that do not re-verify the type accession and locality on each accepted page."],"normalization":{"field_separator":"|","record_separator":";","schema":["accepted","Smith-era Riopa label","first type code","type status","region"],"accepted":"emit the current accepted binomial exactly as shown in the reconciled source","Smith-era_Riopa_label":"preserve the Smith-era Riopa label exactly as used on the legacy branch","first_type_code":"emit the first accession code that follows the selected type-status statement","type_status":"normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES","region":"emit the modern geographic region label from the source reconciliation, such as East Malaysia or Peninsular Malaysia","sorting_or_selection":"accepted name alphabetical ascending"}}} +{"task_id":"reptile_003-g","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":10,"instruction":"I am compiling a name cross-reference for a batch of old collection cards that were still cataloged under the names Mabuya or Mabuia around 1980 and now need to be merged into the current Eutropis checklist. In the current Eutropis list, identify all entries that meet the following conditions: the first 1980-era label on the species page has the genus written as Mabuya or Mabuia; and when that 1980-era label is searched by name in the current list, it does not uniquely correspond to a single Eutropis entry but instead matches multiple current Eutropis entries. For each qualifying entry, output the current accepted name, that 1980-era label, the qualifier for that label on the page, and the first type status and type code listed on the current page. Output sorted alphabetically by 1980-era label, and within the same label by current accepted name, in the format |<1980 label>|||; join multiple entries with semicolons; if no qualifying entries exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output sorted alphabetically by 1980-era label, and within the same label by current accepted name, in the format |<1980 label>|||; join multiple entries with semicolons; if no qualifying entries exist, output NONE.","oracle_answer":"Eutropis indeprensa|Mabuya indeprensa|NONE|HOLOTYPE|CAS 85664;Eutropis sahulinghangganan|Mabuya indeprensa|PART-MISID|HOLOTYPE|PNM 9867;Eutropis multifasciata|Mabuya multifasciata|NONE|NEOTYPE|MZB 11912;Eutropis multicarinata|Mabuya multicarinata|NONE|HOLOTYPE|BMNH 1946.8.15.13-15;Eutropis borealis|Mabuya multicarinata borealis|NONE|HOLOTYPE|CAS 15447;Eutropis islamaliit|Mabuya multicarinata borealis|PART-MISID|HOLOTYPE|PNM 9847;Eutropis caraga|Mabuya multicarinata multicarinata|PART-MISID|HOLOTYPE|PNM 9845;Eutropis palauensis|Mabuya multicarinata multicarinata|PART-BYIMPL|HOLOTYPE|CAS 248251;Eutropis dattaroyi|Mabuya rudis|PART|HOLOTYPE|ZSI 25118;Eutropis rudis|Mabuya rudis|NONE|LECTOTYPE|BMNH 1946.8.15.26","metadata":{"State-Gated Retrieval":["Retain only those current Eutropis records whose synonym block contains, scanning top-down, a first old label starting with Mabuya or Mabuia and having the year 1980.","Then use that 1980-era old label for a default name back-search, and output the accepted name, old label, back-search qualifier, type status, and type specimen.","If the subsequent back-search reveals additional matching entries, revisit the earlier results and include them in the final output."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["current Eutropis detail pages yield the first 1980-tagged Mabuya/Mabuia synonym label for each accepted species","exact back-search on that 1980 old label yields the present accepted page, type status, and type specimen needed for the output row","final rows are produced only after the 1980-specific old-label anchor is rebuilt and the accepted-species set is expanded when back-search evidence reveals omitted entries"],"control_dependency":["the workflow must identify the first Mabuya/Mabuia label carrying the 1980 year rather than stopping at the first old label on the page","when old-label back-search reveals missing entries such as Eutropis dattaroyi, the accepted-species set must be expanded to include them rather than patched in place","accepted-page synonym parsing and back-search interpretation must stay coupled so that 1980 labels are not replaced by older but irrelevant names"],"freeze":{"historical_window":"the objectively existing Eutropis taxa represented in Reptile Database pages, using the synonym labels shown on each species page, especially the first Mabuya/Mabuia-form label tagged with the 1980 citation year, as nearly objective and highly stable reference information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Retain only those current Eutropis records whose synonym block contains, scanning top-down, a first old label starting with Mabuya or Mabuia and having the year 1980.","Then use that 1980-era old label for a default name back-search, and output the accepted name, old label, back-search qualifier, type status, and type specimen.","If the subsequent back-search reveals additional matching entries, revisit the earlier results and include them in the final output."],"exclusion_conditions":["Exclude results that mistakenly treat the first old label on the page as the first 1980-era old label.","Exclude results whose exact back-search on the 1980 old label points to only a single current Eutropis entry.","Exclude results that, when subsequent evidence reveals omitted entries, fail to revisit the earlier results and rebuild the accepted-species set."],"normalization":{"field_separator":"|","record_separator":";","schema":["accepted","1980 label","qualifier","type status","first type code"],"accepted":"emit the current accepted binomial exactly as shown in the reconciled source","1980_label":"preserve the 1980-era label exactly as used on the legacy branch","qualifier":"normalize to one of `NONE`, `PART`, `PART-MISID`, or `PART-BYIMPL`","type_status":"normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES","first_type_code":"emit the first accession code that follows the selected type-status statement","sorting_or_selection":{"primary":"1980 label alphabetical ascending","secondary":"accepted name alphabetical ascending"}}}} +{"task_id":"reptile_004-g","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":6,"instruction":"I am organizing a set of old Hemidactylus brookii museum cards that use the historical labels listed in the comments of the Hemidactylus brookii species page. Identify all old labels that are no longer considered synonyms of Hemidactylus brookii and for which the database provides a clear final synonym assignment. For each qualifying old label, output the currently accepted species it should be assigned to; if the synonym chain passes through an intermediate historical name, list that name, otherwise output DIRECT; also output the type status, type code, and the country of the type locality for that old label. Output the results in alphabetical order of the old labels, using the format |||||, with multiple entries separated by semicolons. If no qualifying entries exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output in alphabetical order of the old labels, using the format |||||, with multiple entries separated by semicolons. If no qualifying entries exist, output NONE.","oracle_answer":"Hemidactylus brooki leightoni|Hemidactylus angulatus|DIRECT|HOLOTYPE|BMNH 1946.8.25.65|Colombia;Hemidactylus brookii haitianus|Hemidactylus angulatus|DIRECT|LECTOTYPE|ZMH R22378|Haiti;Hemidactylus brookii parvimaculatus|Hemidactylus parvimaculatus|DIRECT|HOLOTYPE|NMSL No. RG. 15|Sri Lanka;Hemidactylus brookii subtriedroides|Hemidactylus murrayi|Hemidactylus tenkatei|LECTOTYPE|BMNH [subtriedroides] [tenkatei]|Myanmar;Hemidactylus gleadowi|Hemidactylus gleadowi|DIRECT|NEOTYPE|BMNH 1884.7.25.8|Pakistan;Hemidactylus tenkatei|Hemidactylus murrayi|DIRECT|LECTOTYPE|RMNH 4353|Indonesia","metadata":{"State-Gated Retrieval":["Each result must start from the specified old-label chain and ultimately determine the accepted name, bridge status, type status, type code, and locality from the current accepted species page.","For the subtriedroides branch, continue the chain through tenkatei to murrayi, output the final accepted name as Hemidactylus murrayi, and retain bridge=Hemidactylus tenkatei.","For branches such as haitianus and leightoni, read the locality and type lines specific to each branch, rather than borrowing the header information from the wrong accepted page."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the old-label chains from Hemidactylus angulatus and related names yield accepted pages, bridge names, and the type/locality lines for each path","comment, Types, and type-comment blocks yield the later evidence that tenkatei is further sunk into H. murrayi","final rows are produced only after each old-label path is re-anchored to its own locality/type line and the subtriedroides -> tenkatei -> murrayi bridge chain is completed"],"control_dependency":["type data must be taken from the locality/type line belonging to the actual old-label branch rather than from the header block of the wrong accepted page","stopping at the intermediate tenkatei bridge is insufficient; the workflow must continue to the later murrayi evidence and rewrite both tenkatei and subtriedroides final accepted names","bridge labels remain useful, but final accepted names and type lines must be determined from the deeper synonym chain"],"freeze":{"historical_window":"the objectively existing taxa in the Hemidactylus angulatus / brookii / murrayi complex, using Reptile Database locality, type, comment, and type-comment blocks as nearly objective and highly stable reference information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Each result must start from the specified old-label chain and ultimately determine the accepted name, bridge status, type status, type code, and locality from the current accepted species page.","For the subtriedroides branch, continue the chain through tenkatei to murrayi, output the final accepted name as Hemidactylus murrayi, and retain bridge=Hemidactylus tenkatei.","For branches such as haitianus and leightoni, read the locality and type lines specific to each branch, rather than borrowing the header information from the wrong accepted page."],"exclusion_conditions":["Exclude results that follow the wrong page hierarchy and apply the Holotype/locality from the H. angulatus page header to other branches.","Exclude results that stop early on the subtriedroides -> tenkatei chain without continuing to read the subsequent murrayi evidence.","Exclude results that fail to align the locality/type lines with the specific old-label branches one by one."],"normalization":{"field_separator":"|","record_separator":";","schema":["legacy label","accepted","bridge","type status","type code","country"],"legacy_label":"preserve the legacy label exactly as used on the source branch","accepted":"emit the current accepted binomial exactly as shown in the reconciled source","bridge":"emit `DIRECT` when no intermediate legacy bridge name is needed; otherwise emit the intermediate legacy name that links the branches","type_status":"normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or NEOTYPE","type_code":"take the type accession from the legacy-label branch rather than from a generic type line elsewhere on the page","country":"emit the modern English country name from the reconciled source branch","sorting_or_selection":"legacy label alphabetical ascending"}}} +{"task_id":"reptile_005-g","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I want to organize this synonymization record for an old Sri Lankan museum name in the current Naja list into a two-row comparison table. Output two rows with columns rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note. The first row should be ACCEPTED_NAME and the second row CONTESTED_NAME.","start_url":"https://reptile-database.reptarium.cz/advanced_search?genus=Naja&submit=Search","output_format":"Output a two-row comparison table with columns rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note.","oracle_answer":"1|ACCEPTED_NAME|Naja naja|SUBJECTIVE_JUNIOR_SYNONYM_OF_NAJA_NAJA|VALID_LECTOTYPE|ZMB 2796|restricted type locality: Sri Lanka\n2|CONTESTED_NAME|Naja polyocellata|SHI et al. 2022+SILVA et al. 2023|HOLOTYPE|BMNH 1946.1.18.50|invalid lectotype claim: NRM (= NHR) Lin-90","metadata":{"State-Gated Retrieval":["Within the current Naja list, identify the Sri Lanka contested-name branch: the name was recently reused as a distinct valid name, but the database now explicitly merges it back into the accepted name.","On the current Naja naja page, read the recent-use evidence, final synonym status, lectotype correction, restricted type locality, and the holotype information for the contested name itself.","The final output must organize the ACCEPTED_NAME side and the CONTESTED_NAME side into a two-row comparison table."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the current Naja species list and the Naja naja page yield the Sri Lanka contested-name branch, recent-use citations, and the accepted-name context","comment, Types, and type-comment blocks yield the final synonym treatment plus the valid and invalid lectotype assignments and the contested-name holotype","final rows are produced only after the accepted-name side and the contested-name side are reconciled on the current Naja naja page"],"control_dependency":["recent-use evidence for Naja polyocellata must be interpreted together with the current final synonym treatment shown on that page","lectotype status must be fixed from the combined Types and type-comment evidence rather than from a single provisional assignment","the accepted-name and contested-name rows are emitted together only after final status, type locality, and specimen roles are fixed"],"freeze":{"historical_window":"the objectively existing taxa in the Sri Lanka Naja branch, using current Reptile Database comment, Types, and type-comment blocks as nearly objective and highly stable reference information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Within the current Naja list, identify the Sri Lanka contested-name record: the name was recently reused in the literature as a distinct valid name, but the database now explicitly states that it should still be merged into the accepted name.","On the current Naja naja page, the result must jointly recover the recent-use evidence, final synonym status, lectotype correction, restricted type locality, and the holotype information for the contested name itself.","The final output must organize the ACCEPTED_NAME side and the CONTESTED_NAME side into a two-row comparison table."],"exclusion_conditions":["Exclude results that treat the recently revived contested name as the current accepted name.","Exclude results that stop at the Wallach 2014 lectotype designation and do not continue to the later comment and type-comment correction.","Exclude results that fail to output both the restricted type locality and the contested-name holotype."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","name_role","name","status_or_evidence","specimen_role","specimen_code","supporting_note"],"rank":"emit 1 for ACCEPTED_NAME and 2 for CONTESTED_NAME","name_role":["ACCEPTED_NAME","CONTESTED_NAME"],"name_fields":"use the current binomial spellings exactly","specimen_code_normalization":"preserve museum abbreviations, spaces, parentheses, and specimen punctuation exactly as the page shows","sorting_or_selection":"emit rows in the fixed order ACCEPTED_NAME then CONTESTED_NAME"}}} +{"task_id":"wateroffice_001-g","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am compiling historical daily flow comparison data for the Saint John River spring freshet and want to identify, along the Saint John River mainstem, the last station in the current monitoring network that still allows daily flow comparisons for March-April 1973 and March-April 2018, as well as the first downstream mainstem station that no longer satisfies that condition. Mark a station as PASS if the target windows have complete daily flow records, LEVEL_ONLY if only water level records are available, and FLOW_GAP if daily flow records exist but the target months are missing or incomplete. Output a two-row breakpoint table with columns rank|station_number|breakpoint_role|target_window_status|final_verdict. The first row should be LAST_USABLE and the second row should be FIRST_DOWNSTREAM_FAIL.","start_url":"https://wateroffice.ec.gc.ca/search/real_time_e.html","output_format":"Output a two-row breakpoint table with columns rank|station_number|breakpoint_role|target_window_status|final_verdict.","oracle_answer":"1|01AF002|LAST_USABLE|PASS|KEEP\n2|01AK003|FIRST_DOWNSTREAM_FAIL|LEVEL_ONLY|REJECT","metadata":{"State-Gated Retrieval":["Determine the last station still usable for the target historical-window comparison only within the Saint John River mainstem stations in the current monitoring network.","The historical availability page must distinguish Flow Data Availability from Daily Water Level Data Availability, and completeness for March-April 1973 and March-April 2018 must be checked.","The final output must provide both breakpoint rows, LAST_USABLE and FIRST_DOWNSTREAM_FAIL, under the same validation rule."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the current Saint John River mainstem station sequence provides the downstream order in which the breakpoints must be checked","per-station historical availability pages yield Flow Data Availability, Daily Water Level Data Availability, and target-month completeness for 1973 and 2018","the final breakpoint rows are produced only after the availability-page checks identify the last usable station and the first downstream failure under the same rule"],"control_dependency":["the breakpoint pair must be determined from historical availability that distinguishes flow from level-only evidence","target-year/month completeness must be checked on the availability page rather than inferred from the station list","the second row is emitted only after the first downstream failing mainstem station is fixed under the same validation rule"],"freeze":{"historical_window":"mainstem candidate stations evaluated within the fixed historical March/April daily-availability windows for 1973 and 2018, using station ordering and completeness signals as nearly stable reference information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Determine the last station still usable for the target historical-window comparison only within the Saint John River mainstem stations in the current monitoring network.","The historical availability page must distinguish Flow Data Availability from Daily Water Level Data Availability, and completeness for March-April 1973 and March-April 2018 must be checked.","The final output must provide both breakpoint rows, LAST_USABLE and FIRST_DOWNSTREAM_FAIL, under the same validation rule."],"exclusion_conditions":["Exclude results that determine the breakpoint directly from the current Saint John River mainstem station sequence using only a reference index.","Exclude results that mistakenly treat level-only evidence as satisfying the flow condition.","Exclude results that do not check each station's availability page to verify target-month completeness."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","station_number","breakpoint_role","target_window_status","final_verdict"],"rank":"emit `1` for LAST_USABLE and `2` for FIRST_DOWNSTREAM_FAIL","station_number":"preserve the station number exactly","breakpoint_role":"emit `LAST_USABLE` and `FIRST_DOWNSTREAM_FAIL` exactly","target_window_status":"emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly","final_verdict":"emit `KEEP` for the usable breakpoint row and `REJECT` for the downstream failing breakpoint row","stop_condition":["the last usable mainstem station is fixed under the availability-page validation rule","the first downstream failing mainstem station is fixed under the same validation rule before the two-row output is emitted"]}}} +{"task_id":"wateroffice_002-g","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"I am compiling historical daily flow records for the Bulkley River reach from Houston to Hazelton and want to determine which candidate mainstem stations on this reach truly have complete daily flow records for April-July 1948 and April-July 1950. Mark a station as PASS if the target windows have complete daily flow records, LEVEL_ONLY if only water level records are available, and FLOW_GAP if daily flow records exist but any target month from April to July is incomplete. Output a table in downstream-to-upstream order with columns rank|station_number|target_window_status|final_verdict.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a table in downstream-to-upstream order with columns rank|station_number|target_window_status|final_verdict.","oracle_answer":"1|08EE004|PASS|KEEP\n2|08EE001|LEVEL_ONLY|REJECT\n3|08EE005|FLOW_GAP|REJECT\n4|08EE003|FLOW_GAP|REJECT","metadata":{"State-Gated Retrieval":["First identify mainstem candidate stations on the Historical Results list that appear to cover 1948/1950 and carry a Flow label.","A station qualifies only if its availability page shows the target years in the Flow section and all of April-July marked C.","The final output must report target_window_status and final_verdict for each station in the same station set, ordered from downstream to upstream."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the Historical Results list yields four downstream-to-upstream mainstem candidates whose result rows span the target years and include Flow labels","each candidate's availability page yields whether the target years are in the Flow table and whether April–July is complete","the final ordered rows are produced only after all four stations are classified under the full Flow-table-and-Apr-Jul-C rule"],"control_dependency":["list-level year spans and coarse Flow tags must be confirmed by explicit target-month checks on the availability page","Hazelton, Smithers, and Houston candidate statuses must be fixed before the downstream-most KEEP row can be confirmed","row order and KEEP/REJECT labels must be emitted only after the full availability-page rule is applied to all four stations"],"freeze":{"historical_window":"the target mainstem stations tested within the fixed historical daily Flow-availability windows for 1948 and 1950, with April–July complete-C coverage used as nearly stable reference information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["First identify mainstem candidate stations on the Historical Results list that appear to cover 1948/1950 and carry a Flow label.","A station qualifies only if its availability page shows the target years in the Flow section and all of April-July marked C.","The final output must report target_window_status and final_verdict for each station in the same station set, ordered from downstream to upstream."],"exclusion_conditions":["Exclude stations deemed usable solely from list-level year spans and coarse Flow labels.","Exclude results that mark any LEVEL_ONLY or FLOW_GAP station as KEEP.","Exclude results that do not apply the full availability-page rule to all initially screened stations."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","station_number","target_window_status","final_verdict"],"rank":"emit 1 through 4 in downstream-to-upstream order within the validated station set","station_number":"preserve the station number exactly","target_window_status":"emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly","final_verdict":"emit `KEEP` or `REJECT` exactly","sorting_or_selection":"downstream to upstream within the validated Bulkley River mainstem station set","stop_condition":["all four initially screened stations are classified under the full availability-page rule","the ordered table is emitted only after the downstream-to-upstream sequence is fixed"]}}} +{"task_id":"wateroffice_003-g","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"I am compiling historical snowmelt daily flow data for the Thompson River from Chase to Spences Bridge. I need to identify which mainstem stations along this reach actually had daily flow records for both 1958 and 1971 (May–July). For each mainstem station that appears in the station list as covering 1958 and 1971 and having flow information, verify it station by station in downstream order from Chase to Spences Bridge. Output a table with columns: rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict. If a station has only water level records (no daily flow) for a target year, mark it LEVEL_ONLY. If daily flow records are missing or any of the May–July months is incomplete, mark it FLOW_GAP. Only if both years meet the criteria should final_verdict be KEEP; otherwise mark it REJECT.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a table with columns: rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict.","oracle_answer":"1|08LE031|SOUTH THOMPSON RIVER AT CHASE|PASS|PASS|KEEP\n2|08LE069|SOUTH THOMPSON RIVER AT MONTE CREEK|FLOW_GAP|LEVEL_ONLY|REJECT\n3|08LF023|THOMPSON RIVER AT KAMLOOPS|LEVEL_ONLY|LEVEL_ONLY|REJECT\n4|08LF033|THOMPSON RIVER NEAR SAVONA|FLOW_GAP|FLOW_GAP|REJECT\n5|08LF051|THOMPSON RIVER NEAR SPENCES BRIDGE|PASS|PASS|KEEP","metadata":{"State-Gated Retrieval":["All five candidate stations must be verified on their availability page: check whether the target year appears in the Flow table and whether May–July is entirely marked C.","For each station, output a PASS, LEVEL_ONLY, or FLOW_GAP judgment for both target years, then label it KEEP or REJECT accordingly.","The result order must follow the river-path sequence specified in the task."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["The river-path ordering yields five South Thompson/Thompson mainstem candidates.","Each station's availability page indicates whether 1958 and 1971 are present in the Flow table and whether May–July is complete.","Final rows are produced only after every candidate is classified under the stricter target-year and target-month Flow rule."],"control_dependency":["Overall year coverage on the results list must be confirmed by the availability page inside the Flow table.","Monte Creek, Savona, and Kamloops must be rejected by LEVEL_ONLY/FLOW_GAP evidence before the KEEP rows are final.","The river-order sequence remains fixed, but station statuses must be assigned only after the availability-page rule is applied to all five stations."],"freeze":{"historical_window":"The ordered South Thompson/Thompson mainstem candidates are tested within the fixed historical Flow-availability windows for 1958 and 1971, with May–July complete-C coverage used as nearly stable reference information."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["All five candidate stations must be verified on their availability page: check whether the target year appears in the Flow table and whether May–July is entirely marked C.","For each station, output a PASS, LEVEL_ONLY, or FLOW_GAP judgment for both target years, then label it KEEP or REJECT accordingly.","The result order must follow the river-path sequence specified in the task."],"exclusion_conditions":["Exclude results that treat overall year coverage on the list page as sufficient evidence.","Exclude results that fail to distinguish between Flow-table target-year and month completeness versus Level-only evidence.","Exclude results that do not apply the same availability-page rule uniformly to all five stations."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","station_number","station_name","1958_MayJul","1971_MayJul","final_verdict"],"rank":"use the fixed Chase-to-Spences-Bridge mainstem order from the reference index, not the transient search-result order","year_window_fields":"the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP","final_verdict":"emit `KEEP` or `REJECT` exactly"}}} +{"task_id":"wateroffice_004-g","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":13,"instruction":"I am compiling historical daily flow records for the main stem of the Columbia River from Fairmont Hot Springs to the International Boundary. I want to check, station by station, which Wateroffice gauges have complete daily flow records for May–October of 1955 and 1956. The candidate set is limited to main-stem Columbia River stations whose overall period of record spans both 1955 and 1956. Please evaluate each station in upstream-to-downstream order and output a table with columns: rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict. If the target year has only water-level records and no daily flow records, mark it as LEVEL_ONLY. If daily flow records for May–October of that year are complete, mark it as PASS. If daily flow records are absent or any month from May to October has incomplete records, mark it as FLOW_GAP. Only when both 1955 and 1956 meet the complete daily flow condition should final_verdict be KEEP; otherwise, it should be REJECT.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a table with columns: rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict.","oracle_answer":"1|08NA045|COLUMBIA RIVER NEAR FAIRMONT HOT SPRINGS|PASS|PASS|KEEP\n2|08NA004|COLUMBIA RIVER AT ATHALMER|LEVEL_ONLY|LEVEL_ONLY|REJECT\n3|08NA052|COLUMBIA RIVER NEAR EDGEWATER|PASS|FLOW_GAP|REJECT\n4|08NA002|COLUMBIA RIVER AT NICHOLSON|PASS|PASS|KEEP\n5|08NB005|COLUMBIA RIVER AT DONALD|PASS|PASS|KEEP\n6|08NB006|COLUMBIA RIVER AT SURPRISE RAPIDS|PASS|PASS|KEEP\n7|08ND007|COLUMBIA RIVER ABOVE NAGLE CREEK|PASS|PASS|KEEP\n8|08ND011|COLUMBIA RIVER ABOVE STEAMBOAT RAPIDS|FLOW_GAP|PASS|REJECT\n9|08ND006|COLUMBIA RIVER AT TWELVE MILE FERRY|PASS|PASS|KEEP\n10|08NE002|COLUMBIA RIVER AT CASTLEGAR|LEVEL_ONLY|LEVEL_ONLY|REJECT\n11|08NE049|COLUMBIA RIVER AT BIRCHBANK|PASS|PASS|KEEP\n12|08NE003|COLUMBIA RIVER AT TRAIL|LEVEL_ONLY|LEVEL_ONLY|REJECT\n13|08NE058|COLUMBIA RIVER AT INTERNATIONAL BOUNDARY|PASS|PASS|KEEP","metadata":{"State-Gated Retrieval":["All candidate Columbia River stations must be checked on their availability page to confirm that the target years appear in the Flow table and that May–October is marked entirely as C.","For each station, provide the KEEP/REJECT basis for both 1955 and 1956, distinguishing LEVEL_ONLY and FLOW_GAP cases from stations that only appear eligible from their overall year span.","The final table must preserve the order and fields specified in the task."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the Columbia River candidate ordering yields fourteen stations spanning the target years","each availability page yields whether 1955 and 1956 are present in the Flow table and whether May-October is complete","final rows are produced only after every station is classified under the stricter Flow-table-and-May-Oct-C rule"],"control_dependency":["list-level year spans must be confirmed by the availability page inside the Flow table","LEVEL_ONLY and FLOW_GAP evidence must be applied to each station before the KEEP/REJECT table is finalized","station-by-station verdicts and rejection reasons must be determined only after the full availability-page rule replaces the initial year-span screen"],"freeze":{"historical_window":"the ordered Columbia River candidates tested within the fixed historical Flow-availability windows for 1955 and 1956, with May-October complete-C coverage used as nearly stable reference information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["All candidate Columbia River stations must be checked on their availability page to confirm that the target years appear in the Flow table and that May–October is marked entirely as C.","For each station, provide the KEEP/REJECT basis for both 1955 and 1956, distinguishing LEVEL_ONLY and FLOW_GAP cases from stations that only appear eligible from their overall year span.","The final table must preserve the order and fields specified in the task."],"exclusion_conditions":["Exclude results that retain a station solely because its overall period spans 1955/1956.","Exclude results that fail to distinguish, station by station, between Flow-available, Level-only, and incomplete-month cases.","Exclude results that do not apply the full availability-page rule uniformly to all 14 stations."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","station_number","station_name","1955_MayOct","1956_MayOct","final_verdict"],"rank":"use the fixed upstream-to-downstream Columbia mainstem order from the reference index, not the transient search-result order","year_window_fields":"the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP","final_verdict":"emit `KEEP` or `REJECT` exactly"}}} +{"task_id":"wateroffice_005-g","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am organizing historical daily-flow records for the Peace River reach from Dunvegan Bridge to Fifth Meridian and want a three-row diagnostic table for the furthest-downstream reusable mainstem station, the first downstream failing station after it, and the provisional terminal station that an initial screen would misclassify as the downstream winner. If the target window satisfies the complete daily-flow condition, mark it as PASS. If the target year has only level records, mark it as LEVEL_ONLY. If daily-flow records exist but any target month from May through September is incomplete, mark it as FLOW_GAP. If the target year has neither daily-flow nor level records, mark it as NO_TARGET_RECORD. Output three rows with columns rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a three-row diagnostic table with columns rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count.","oracle_answer":"1|07HA001|FINAL_STATION|PASS|5|2\n2|07HD001|FIRST_BREAK_AFTER_FINAL|FLOW_GAP|5|2\n3|07KA002|PROVISIONAL_STATION|FLOW_GAP|5|2","metadata":{"State-Gated Retrieval":["Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian.","A genuinely reusable station must satisfy the availability-page rule that both 1966 and 1967 appear in the Flow table and that every month from May through September is complete.","The final output must jointly report FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION, while repeating provisional_count and final_count in every row."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the Peace River mainstem chain between Dunvegan Bridge and Fifth Meridian yields the initial station list and the downstream breakpoint positions that need revalidation","each availability page yields whether 1966 and 1967 are present in the Flow or Level tables and whether May-September is complete","final rows are produced only after the final station, the first downstream failure, and the provisional downstream winner are all fixed under the same availability-page validation rule"],"control_dependency":["station-level target-year Flow evidence must be validated by explicit May-September completeness checks on the availability page","the final downstream reusable station and the first downstream failure must be determined under the same validation rule rather than from the initial station screen","the provisional downstream winner is kept in the output only for reference after its FLOW_GAP status is confirmed on the availability page"],"freeze":{"historical_window":"the Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian, evaluated within the fixed historical 1966 and 1967 Flow-availability windows, with May-September complete-C coverage used as nearly stable reference information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian.","A genuinely reusable station must satisfy the availability-page rule that both 1966 and 1967 appear in the Flow table and that every month from May through September is complete.","The final output must jointly report FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION, while repeating provisional_count and final_count in every row."],"exclusion_conditions":["Exclude results that treat a station as usable simply because the target years have Flow records.","Exclude results that do not verify completeness month by month from May through September.","Exclude results that mark a station such as 07KA002 as FINAL_STATION when availability-page evidence shows FLOW_GAP."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","station_number","diagnosis_role","target_window_status","provisional_count","final_count"],"rank":"emit the fixed order 1, 2, 3 for FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION","station_number":"use uppercase WSC station codes exactly as the Reference Index and availability pages show","diagnosis_role":["FINAL_STATION","FIRST_BREAK_AFTER_FINAL","PROVISIONAL_STATION"],"target_window_status":["PASS","LEVEL_ONLY","FLOW_GAP","NO_TARGET_RECORD"],"count_fields":"repeat the global provisional_count and final_count in every row as plain integers","sorting_or_selection":"emit rows in the fixed diagnostic order FINAL_STATION, FIRST_BREAK_AFTER_FINAL, PROVISIONAL_STATION"}}} +{"task_id":"waterquality_001-g","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am compiling historical monitoring data for the middle Rio Grande and need to identify two monitoring locations suitable as sentinel sites for main-channel wastewater impacts. From the monitoring locations downstream of RIO GRANDE AT EMBUDO, NM that are confirmed to be on the Rio Grande mainstem, select two qualifying stations: the upstream station must be downstream of the Town of Bernalillo wastewater treatment plant outfall; the downstream station must be downstream of both the Town of Bernalillo and Rio Rancho No. 2 wastewater treatment plant outfalls. Both stations must simultaneously meet the following conditions: the station itself is not an outfall, facility, well, canal, or drainage ditch; the station type is labeled as River/Stream; records for Microbiological, Nutrient, Organics, Other, and Physical are all complete for 2015—2020; and the start years for Microbiological and Physical records are both earlier than 2010. If multiple mainstem stations in a given segment meet the conditions, select the one farthest upstream along the main channel. Output a single line in upstream-to-downstream order in the format ||, with the two segments separated by a comma.","start_url":"https://www.waterqualitydata.us/","output_format":"Output a single line in upstream-to-downstream order in the format ||, with the two segments separated by a comma.","oracle_answer":"SANDIAWQ_WQX-RG003|2004|2004,SANDIAWQ_WQX-RG008|2004|2004","metadata":{"State-Gated Retrieval":["Select two target stations only from Rio Grande mainstem monitoring stations downstream of RIO GRANDE AT EMBUDO, NM, and require both to be past the specified outfall locations.","The station detail page must explicitly indicate River/Stream, and records for Microbiological, Nutrient, Organics, Other, and Physical must fully cover 2015—2020, with start years for Microbiological and Physical both earlier than 2010.","Output the two stations in upstream-to-downstream order."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Provider/list views yield the Rio Grande mainstem candidates downstream of the Bernalillo and Rio Rancho No. 2 discharge points.","Detail pages yield flow position, location type, characteristic-group period-of-record coverage for 2015—2020, and the Microbiological/Physical baseline years.","Final rows are produced only after the corrected downstream sentry stations are fixed and ordered from upstream to downstream."],"control_dependency":["Provider-list stream tags are only provisional and must be confirmed on the detail page by both mainstem placement and location type.","Target-window presence is insufficient until full 2015—2020 coverage is confirmed on the detail page for all four groups.","Once RG002/RG007 fail the full detail-page checks, the workflow must continue downstream from the discharge-point starting position to RG003/RG008."],"freeze":{"historical_window":"Rio Grande mainstem stations downstream of the Town of Bernalillo and Rio Rancho No. 2 WWTP outfalls, validated against 2015—2020 coverage for Microbiological, Nutrient, Organics, Other, and Physical."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Select two target stations only from Rio Grande mainstem monitoring stations downstream of RIO GRANDE AT EMBUDO, NM, and require both to be past the specified outfall locations.","The station detail page must explicitly indicate River/Stream, and records for Microbiological, Nutrient, Organics, Other, and Physical must fully cover 2015—2020, with start years for Microbiological and Physical both earlier than 2010.","Output the two stations in upstream-to-downstream order."],"exclusion_conditions":["Exclude stations that have a shallow (Stream) tag on the provider list or records near the target window, but whose detail page does not satisfy flow position, location type, or full period-of-record conditions.","Exclude locations that are outfalls, facilities, wells, canals, or drainage ditches.","Exclude candidates such as RG002 and RG007 that are not qualified sentinel stations downstream of the corresponding outfalls."],"normalization":{"record_separator":",","field_separator":"|","schema_per_record":["MonitoringLocationIdentifier","Microbiological_start_year","Physical_start_year"],"ordering":"emit exactly two records from upstream to downstream","station_id":"use uppercase MonitoringLocationIdentifier","year_fields":"emit four-digit years as plain integers","selection":{"record_1":"the first qualifying mainstem station below the Bernalillo outfall","record_2":"the first qualifying mainstem station below both the Bernalillo and Rio Rancho No. 2 outfalls"},"stop_condition":["the Bernalillo branch stops only after its first qualifying mainstem station is fixed","the Rio Rancho No. 2 branch stops only after its first qualifying mainstem station is fixed","the two segments are emitted as one comma-joined line in upstream-to-downstream order"]}}} +{"task_id":"waterquality_002-g","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am analyzing trends in the lower Rio Grande from 2001 to 2010. From monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002, select one representative station for Hidalgo County and one for Cameron County. Each station must satisfy all of the following conditions: located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002; the monitoring location type on the station detail page must be River/Stream; and records for all four characteristic groups—Microbiological, Nutrient, Organics, Other, and Physical—must cover the period 2001–2010. If multiple stations in the same county qualify, select the one with the earliest year in which all four groups are simultaneously present. Output a single line with the Hidalgo segment first and the Cameron segment second, using the format :|||||, with the two segments separated by a comma.","start_url":"https://www.waterqualitydata.us/","output_format":"Output a single line with the Hidalgo segment first and the Cameron segment second, using the format :|||||, with the two segments separated by a comma.","oracle_answer":"Hidalgo:TCEQMAIN-15808|1998|1998|1998|1998|1998,Cameron:TCEQMAIN-13177|1995|1981|1981|1995|1981","metadata":{"State-Gated Retrieval":["Select one representative station for Hidalgo County and one for Cameron County only from monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002.","Candidate detail pages must show River/Stream as the monitoring location type, and records for all four characteristic groups—Microbiological, Nutrient, Organics, Other, and Physical—must cover 2001–2010.","If multiple stations in the same county qualify, select the one with the earliest year in which all four groups are simultaneously present."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the fixed downstream starting point and county split yield Hidalgo and Cameron candidate mainstem stations within HUC 13090002","detail pages yield River/Stream validity, the four characteristic-group start years, and the earliest year when all four groups are simultaneously present for 2001-2010 coverage","final rows are produced only after the county-specific searches are rerun from the fixed downstream starting point and then ranked by common-start year"],"control_dependency":["the Hidalgo search must preserve the \"below TCEQMAIN-13664\" downstream starting point rather than returning to the anchor station itself","a station is only provisional until all four characteristic groups are confirmed for the same MonitoringLocationIdentifier and tidal/intake conflicts are excluded on the detail page","county winners are valid only after late-start and non-river candidates are removed and the common-start-year tie-break is recomputed"],"freeze":{"historical_window":"stations below RIO GRANDE BELOW ANZALDUAS within HUC 13090002, split by Hidalgo and Cameron County, with Microbiological, Nutrient, Organics, Other, and Physical coverage over 2001-2010"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Select one representative station for Hidalgo County and one for Cameron County only from monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002.","Candidate detail pages must show River/Stream as the monitoring location type, and records for all four characteristic groups—Microbiological, Nutrient, Organics, Other, and Physical—must cover 2001–2010.","If multiple stations in the same county qualify, select the one with the earliest year in which all four groups are simultaneously present."],"exclusion_conditions":["Exclude results where the Hidalgo search loses the downstream starting point and brings the starting station itself back into the candidate set.","Exclude results that treat a single multi-select of the four characteristic groups as sufficient without verifying that all four belong to the same station ID.","Exclude stations with tidal, intake, late-start, or other conflicts clearly indicated on the detail page."],"normalization":{"record_separator":",","field_separator":"|","schema_per_record":["County:MonitoringLocationIdentifier","common_start_year","Microbiological_start_year","Nutrient_start_year","Organics_Other_start_year","Physical_start_year"],"ordering":"emit exactly two records, with Hidalgo first and Cameron second","county_prefix":"use the county label in title case, followed by : and the uppercase MonitoringLocationIdentifier","year_fields":"emit four-digit years as plain integers","common_start_year":"the earliest year in which all four required groups are simultaneously present for the chosen county station","stop_condition":["each county branch is rerun until one River/Stream station survives all four group checks","the county winner is fixed only after late-start and non-river candidates are excluded on the detail page","the two county segments are emitted on one line in the fixed Hidalgo-then-Cameron order"]}}} +{"task_id":"waterquality_003-g","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am compiling 2012–2018 water-quality reference data for the Brazos River mainstem downstream of Brazos Rv at Waco, TX. For each of the three specified HUCs that include Waco (12060202, 12070101, 12070104), I need to identify one TCEQ monitoring station suitable as a long-term reference for 2012–2018 along the Brazos River mainstem downstream of Brazos Rv at Waco, TX. Candidate stations must satisfy all of the following: be located within the corresponding HUC; have a monitoring-location type of River/Stream on the station detail page; have a station name that still corresponds to the Brazos River mainstem, not a tributary or other named waterbody; and have records covering 2012–2018 for all five characteristic groups—Inorganics, Major, Non-metals; Microbiological; Nutrient; Organics, Other; and Physical—meaning the station’s start year is no later than 2012 and its end year is no earlier than 2018. List the three results in upstream-to-downstream order, one per line, using the format: |||||||.","start_url":"https://www.waterqualitydata.us/","output_format":"List the three results in upstream-to-downstream order, one per line, using the format: |||||||.","oracle_answer":"12060202|TCEQMAIN-12037|2000|1991|2000|1991|1999|1991\n12070101|TCEQMAIN-12030|2006|1972|1972|1972|2006|1972\n12070104|TCEQMAIN-11848|1975|1974|1975|1974|1975|1974","metadata":{"State-Gated Retrieval":["The search must stay anchored downstream of Waco and look for Brazos mainstem monitoring stations within the three HUCs specified in the task.","Each candidate station must be checked separately across the five characteristic groups and then matched back to the same station ID, after which the detail page must verify full 2012–2018 coverage and mainstem semantics.","For each HUC, retain only the qualifying station with the earliest common start year, and output the start-year fields required by the task."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the fixed downstream starting point below Waco and the three target HUC searches yield the Brazos mainstem candidate stations","detail pages yield true downstream position, mainstem-vs-tributary semantics, and five-group period-of-record coverage across 2012-2018","final rows are produced only after the three HUC-specific searches are carried out, matched by station ID, and ranked by the earliest year when all five groups are jointly available"],"control_dependency":["the workflow must stay anchored downstream of Waco rather than reintroducing upstream stations such as TCEQMAIN-12044","name-based waterbody matches must be validated on the detail page by excluding tributaries such as LITTLE BRAZOS RIVER and confirming full-window coverage","station ranking must be determined after false positives from partial-window records are removed"],"freeze":{"historical_window":"Brazos River mainstem stations downstream of the Waco anchor evaluated within the fixed historical 2012-2018 window, using the HUC 12060202 / 12070101 / 12070104 split and five characteristic groups as largely stable reference information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["The search must stay anchored downstream of Waco and look for Brazos mainstem monitoring stations within the three HUCs specified in the task.","Each candidate station must be checked separately across the five characteristic groups and then matched back to the same station ID, after which the detail page must verify full 2012–2018 coverage and mainstem semantics.","For each HUC, retain only the qualifying station with the earliest common start year, and output the start-year fields required by the task."],"exclusion_conditions":["Exclude results that lose the downstream starting point below Waco and bring upstream stations back into the candidate set.","Exclude results that mistakenly treat tributaries such as LITTLE BRAZOS RIVER as the Brazos mainstem.","Exclude stations that have data near the query window but do not cover the entire 2012–2018 window."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["HUC","MonitoringLocationIdentifier","common_start_year","Inorganics_start","Microbiological_start","Nutrient_start","Organics_Other_start","Physical_start"],"HUC":"preserve the HUC exactly as emitted in the source result","MonitoringLocationIdentifier":"preserve the monitoring-location identifier exactly, for example `TCEQMAIN-12037`","common_start_year":"emit the maximum of the five per-group start years","selection_rule":"only keep mainstem river/stream sites whose five required groups all cover the target 2012-2018 window","sorting_or_selection":"upstream to downstream along the mainstem"}}} +{"task_id":"waterquality_004-g","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am reviewing toxic-pollutant-related water quality monitoring data for the Trinity River mainstem from 1993 to 2001, with the reach near FM 85 as the upstream boundary and the reach near Interstate 10 as the downstream boundary. I need to select one TCEQ long-term reference station for each of the upper, middle, and lower segments along the river.\nCandidate monitoring locations must simultaneously meet the following conditions: the monitoring location type in the station record is labeled River/Stream; the station name corresponds to the Trinity River mainstem, not a tributary, other named waterbody, or distributary channel; records for all six characteristic groups—Inorganics, Major, Non-metals; Microbiological; Nutrient; Organics, Other; Organics, PCBs; and Physical—must cover the period 1993–2001, specifically with a start year no later than 1993 and an end year no earlier than 2001. Output three rows in order from upstream to downstream along the river, each row formatted as ||||||||.","start_url":"https://www.waterqualitydata.us/","output_format":"Output three rows in order from upstream to downstream along the river, each row formatted as ||||||||.","oracle_answer":"12030105|TCEQMAIN-10924|1983|1982|1983|1982|1983|1983|1982\n12030202|TCEQMAIN-10897|1993|1969|1972|1972|1993|1974|1969\n12030203|TCEQMAIN-10892|1976|1969|1971|1972|1974|1976|1969","metadata":{"State-Gated Retrieval":["Only retain candidate stations that satisfy the Trinity River mainstem semantics and require all six characteristic groups to cover 1993–2001.","The six groups must be searched separately and then matched back to the same station ID, after which the detail page must verify full time-window coverage and completeness of the legacy toxics groups.","For each target segment, retain only the station that meets all group requirements and has the best common start year."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Trinity River mainstem candidate stations are generated from the target HUC searches and the six characteristic-group searches","detail pages yield River/Stream validity, 1993–2001 full-window coverage, and the group-specific start years needed for ranking","final rows are produced only after all six groups have been matched by station ID and detail-page validation removes partial-group and non-mainstem false positives"],"control_dependency":["each of the six characteristic groups must be evaluated separately and confirmed against the same station ID before a multi-select result can be retained","station names and River/Stream tags are insufficient until the detail page confirms Trinity mainstem semantics and 1993–2001 full-window coverage","candidate rejection and final ranking must be determined after applying the PCBs / Organics, Other gap checks"],"freeze":{"historical_window":"Trinity River mainstem stations validated within the fixed historical 1993–2001 window, using six characteristic groups and ranking by earliest joint availability plus group start years as largely stable reference information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Only retain candidate stations that satisfy the Trinity River mainstem semantics and require all six characteristic groups to cover 1993–2001.","The six groups must be searched separately and then matched back to the same station ID, after which the detail page must verify full time-window coverage and completeness of the legacy toxics groups.","For each target segment, retain only the station that meets all group requirements and has the best common start year."],"exclusion_conditions":["Exclude results that mistakenly treat a single multi-select of characteristic groups as sufficient to satisfy the requirement.","Exclude results that only check station names and River/Stream tags without verifying 1993–2001 full-window coverage.","Exclude stations that ignore missing PCBs or Organics, Other groups."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["HUC","MonitoringLocationIdentifier","common_start_year","Inorganics_start","Microbiological_start","Nutrient_start","Organics_Other_start","Organics_PCBs_start","Physical_start"],"HUC":"preserve the HUC exactly as emitted in the source result","MonitoringLocationIdentifier":"preserve the monitoring-location identifier exactly, for example `TCEQMAIN-10924`","common_start_year":"emit the maximum of the six per-group start years","selection_rule":"only keep mainstem river/stream sites whose six required groups all cover the target window","sorting_or_selection":"upstream to downstream along the mainstem"}}} +{"task_id":"waterquality_005-g","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":9,"instruction":"I am organizing integrated water-quality records for the lower Neches River during 1978-1984 and want a table of the nine Characteristic Group start years for the nearest qualifying TCEQ reference station downstream of NECHES RIVER AT CR 4915 that still represents the inland Neches River mainstem. Output a 9-row table with columns rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year, using the fixed nine-group order specified in the task.","start_url":"https://www.waterqualitydata.us/provider/STORET/TCEQMAIN/TCEQMAIN-10598/","output_format":"Output a 9-row table with columns rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year.","oracle_answer":"1|TCEQMAIN-10580|12020003|Hardin County|Biological, Algae, Phytoplankton|1972|1977\n2|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Major, Non-metals|1971|1977\n3|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Minor, Metals|1974|1977\n4|TCEQMAIN-10580|12020003|Hardin County|Microbiological|1972|1977\n5|TCEQMAIN-10580|12020003|Hardin County|Nutrient|1972|1977\n6|TCEQMAIN-10580|12020003|Hardin County|Organics, Other|1974|1977\n7|TCEQMAIN-10580|12020003|Hardin County|Organics, PCBs|1974|1977\n8|TCEQMAIN-10580|12020003|Hardin County|Organics, Pesticide|1977|1977\n9|TCEQMAIN-10580|12020003|Hardin County|Physical|1971|1977","metadata":{"State-Gated Retrieval":["Search only among TCEQ monitoring stations downstream of NECHES RIVER AT CR 4915 that still represent the inland Neches River mainstem.","A candidate station must cover 1978-1984 in all nine Characteristic Groups and, on the detail page, must still qualify as River/Stream, outside lake or reservoir waters, and outside the Sabine-Neches outlet boundary reach.","The final output must be centered on the single winning station and list group_start_year plus common_start_year row by row in the fixed nine-group order."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["the fixed downstream starting point at NECHES RIVER AT CR 4915 yields candidate inland mainstem stations across successive downstream HUCs","detail pages yield River/Stream validity, inland-vs-boundary semantics, and nine-group period-of-record coverage across 1978-1984","final rows are produced only after one winning station survives the inland-mainstem checks and the requirement that all nine groups match the same station, after which its nine group start years are emitted in the required order"],"control_dependency":["the nearest downstream mainstem station remains provisional until all nine characteristic groups have been checked separately and matched back to the same station ID","the downstream search must continue to the next mainstem HUC when the first candidate fails the nine-group coverage requirement","location semantics remain valid only after detail-page exclusion of lake/reservoir and Sabine-Neches boundary stations"],"freeze":{"historical_window":"Neches River inland mainstem stations downstream of NECHES RIVER AT CR 4915, validated within the fixed 1978-1984 window against nine characteristic groups as largely stable reference information"},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Search only among TCEQ monitoring stations downstream of NECHES RIVER AT CR 4915 that still represent the inland Neches River mainstem.","A candidate station must cover 1978-1984 in all nine Characteristic Groups and, on the detail page, must still qualify as River/Stream, outside lake or reservoir waters, and outside the Sabine-Neches outlet boundary reach.","The final output must be centered on the single winning station and list group_start_year plus common_start_year row by row in the fixed nine-group order."],"exclusion_conditions":["Exclude results that retain TCEQMAIN-10591 merely because it appears to be the nearest downstream mainstem station.","Exclude results that do not check the nine Characteristic Groups separately and verify that they all belong to the same station ID.","Exclude stations located in lake or reservoir waters or in the Sabine-Neches outlet boundary reach."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"omit the header row; emit data rows only","schema":["rank","MonitoringLocationIdentifier","HUC","County","characteristic_group","group_start_year","common_start_year"],"rank":"emit 1 through 9 in the fixed characteristic-group order required by the task","MonitoringLocationIdentifier":"use uppercase MonitoringLocationIdentifier","HUC":"emit the HUC as an 8-digit string with no separators","County":"use the county name exactly as shown on the detail page","characteristic_group":"preserve the group label exactly as listed in the task","year_fields":"emit four-digit years as plain integers","common_start_year":"repeat the earliest year in which all nine required groups are simultaneously present for the chosen station","sorting_or_selection":"emit rows in the fixed nine-group order stated in the task"}}} +{"task_id":"wonder_003-g","domain":"CDC_WONDER","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"For a public-health brief reviewing changes in U.S. home births in 2020, identify the months in which the home-birth rate among all mothers rose at least 25% compared with the same month in 2019. For those months, also provide the 2020 home-birth rates and relative changes for non-Hispanic Black and Hispanic mothers. Output a pipe-delimited table in calendar-month order with the fixed header row month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel. Write all values as plain numbers without percent signs.","start_url":"https://wonder.cdc.gov/natality-expanded-current.html","output_format":"Output a pipe-delimited table in calendar-month order with the fixed header row month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel. Write all values as plain numbers without percent signs.","oracle_answer":"month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel\nMay|1.03|1.49|45|0.74|54|0.55|57\nJune|1.04|1.31|26|0.66|20|0.48|30\nJuly|1.03|1.30|26|0.68|42|0.48|30\nAugust|1.02|1.29|26|0.69|50|0.48|26\nSeptember|1.01|1.31|30|0.73|43|0.54|54\nOctober|1.00|1.28|28|0.75|50|0.47|27\nNovember|0.99|1.30|31|0.73|43|0.55|67\nDecember|0.92|1.28|39|0.80|63|0.53|61","metadata":{"State-Gated Retrieval":["Compare the home-birth rates for all mothers in 2019 and 2020 by calendar month, retaining only months where the 2020 rate increased at least 25% relative to the same month in 2019.","The home-birth numerator must use the full home category, not Home intended alone.","For those qualifying months, also retrieve the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, along with their relative changes from the same month in 2019."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Monthly natality queries yield the 2019 vs 2020 home-birth rates for all mothers and the candidate month set.","Follow-up race/ethnicity queries yield the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, plus their same-month changes versus 2019.","Final rows are produced only after qualifying months are determined from rate growth, and the resulting month set is reused for both subgroup backfill chains."],"control_dependency":["Month selection must be based on relative rate increase rather than counts alone.","The home-birth numerator must use Residence or an equivalent full-home measure rather than Home intended alone before downstream subgroup queries run.","Subgroup columns must be generated from the resulting month set rather than appended to earlier rows."],"freeze":{"historical_window":"2019 and 2020 U.S. natality monthly home-birth rates for all mothers, non-Hispanic Black mothers, and Hispanic mothers."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Compare the home-birth rates for all mothers in 2019 and 2020 by calendar month, retaining only months where the 2020 rate increased at least 25% relative to the same month in 2019.","The home-birth numerator must use the full home category, not Home intended alone.","For those qualifying months, also retrieve the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, along with their relative changes from the same month in 2019."],"exclusion_conditions":["Exclude month-row sets that misinterpret \"rate increase of at least 25%\" as \"count increase of at least 25%.\"","Exclude results that use only the Home intended category instead of the full home numerator.","Exclude results that append subgroup columns based on an incorrect month set."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"required literal first row `month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel`","schema":["month","all_2019","all_2020","all_rel","black_2020","black_rel","hispanic_2020","hispanic_rel"],"month":"use the English month name and keep calendar order","numeric_fields":"all numeric outputs are plain numbers without a percent sign","relative_change_fields":"all_rel, black_rel, and hispanic_rel are emitted as integer percentages without the `%` character"}}} +{"task_id":"wonder_004-g","domain":"CDC_WONDER","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"From the 2021 U.S. infant mortality statistics by mother's race and Hispanic origin, identify all groups that are reported separately, have an infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death. For each qualifying group, provide the infant mortality rate, neonatal mortality rate (under 28 days), postneonatal mortality rate (28 days and older), the group's leading cause of death, the cause-specific rate, and the rank of that cause among all infant causes. Output a multi-row pipe-delimited table sorted by infant mortality rate descending, using the format: group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank.","start_url":"https://wonder.cdc.gov/lbd-current-expanded.html","output_format":"Output a multi-row pipe-delimited table sorted by infant mortality rate descending, using the format: group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank.","oracle_answer":"group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank\nnon-Hispanic Black|10.55|6.35|4.19|Short gestation and low birth weight|196.4|2\nnon-Hispanic American Indian or Alaska Native|7.46|3.83|3.67|Congenital malformations|134.0|1\nPuerto Rican|6.05|3.93|2.13|Short gestation and low birth weight|108.9|2","metadata":{"State-Gated Retrieval":["Retain only groups that are reported separately in the 2021 U.S. infant mortality statistics, have an infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death.","For each qualifying group, provide the infant rate, neonatal rate, postneonatal rate, top cause, cause rate, and the rank of that cause among all infant causes.","The leading cause must be determined by a group-level leading-cause query and verified using notes/reliability flags."],"dependency_type":"Data + Control","intra_chain":true,"inter_chain":true,"data_dependency":["Infant-mortality queries yield group-level overall, neonatal, and postneonatal rates for reportable mother race/Hispanic-origin groups.","Leading-cause queries and reliability notes yield each eligible group's top cause, cause-specific rate, and U.S. rank.","Final rows are produced only after the eligible-group set is rebuilt using both overall-rate and cause-specific-identifiability criteria."],"control_dependency":["Groups above the U.S. overall rate cannot be accepted until cause-specific reliability checks are run, which removes NHOPI.","Leading cause must be queried at the group level rather than inherited from an all-infants cause table.","The cause-rate multiplier must be defined as per 100,000 live births before downstream ranking/output."],"freeze":{"historical_window":"2021 U.S. infant mortality by mother race and Hispanic origin, including the group-level leading-cause tables and reliability notes."},"answer_type":"multi-row ordered table"},"rubric":{"inclusion_conditions":["Retain only groups that are reported separately in the 2021 U.S. infant mortality statistics, have an infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death.","For each qualifying group, provide the infant rate, neonatal rate, postneonatal rate, top cause, cause rate, and the rank of that cause among all infant causes.","The leading cause must be determined by a group-level leading-cause query and verified using notes/reliability flags."],"exclusion_conditions":["Exclude groups that, despite having an infant mortality rate above the U.S. overall rate, cannot provide a clearly identifiable leading cause due to cause-specific reliability issues.","Exclude results that inherit the top cause only from the all-infants cause table without performing a group-level leading-cause query.","Exclude results where the cause rate uses an incorrect rate multiplier and is not read per 100,000 live births."],"normalization":{"field_separator":"|","record_separator":"\n","header_row":"required literal first row `group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank`","schema":["group","infant_rate","neonatal_rate","postneonatal_rate","top_cause","cause_rate","us_rank"],"sorting_or_selection":"infant_rate descending","rate_fields":"infant_rate, neonatal_rate, and postneonatal_rate are per 1,000 live births; cause_rate is per 100,000 live births, but all four are emitted as plain numbers without unit text","top_cause":"emit the short cause label used in the oracle, not an expanded prose description","us_rank":"emit the integer rank of that same cause in the overall infant leading-cause list"}}} diff --git a/goal_hf.jsonl b/goal_hf.jsonl new file mode 100644 index 0000000000000000000000000000000000000000..99557b9489af2f4718e74d6edcfac71b76d01afa --- /dev/null +++ b/goal_hf.jsonl @@ -0,0 +1,50 @@ +{"task_id":"arxiv_001-g","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"I am organizing the research trajectory of dataset distillation and dataset condensation on arXiv from 2019 to 2021, aiming to identify machine learning papers that discuss using a small set of synthetic training data to replace large-scale training sets. From the 2019–2021 arXiv records, retain only entries whose primary category is Machine Learning; if a paper is only cross-listed into Machine Learning by another primary category, do not include it. Additionally, these papers must have a revision within the next calendar year after the initial submission, and the current record must still clearly indicate a subsequent publication venue. Output a table sorted by v1 submitted in ascending order, with columns: arXiv ID, term family, cue location, v1 submitted, first next-year version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying entries exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Output a table sorted by v1 submitted in ascending order, with columns: arXiv ID, term family, cue location, v1 submitted, first next-year version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying entries exist, output NONE.","oracle_answer":"arXiv ID|term family|cue location|v1 submitted|first next-year version|date of that version|primary category|publication-trail source|current publication clue\n1910.02551|Distillation|Title|2019-10-06|v3|2020-05-05|cs.LG|Related DOI|10.1109/IJCNN52387.2021.9533769\n2011.00050|Distillation|Abstract-only|2020-10-30|v2|2021-03-02|cs.LG|Comments|Accepted to ICLR 2021\n2107.13034|Distillation|Title|2021-07-27|v3|2022-01-17|cs.LG|Comments|NeurIPS 2021\n2110.04181|Condensation|Title|2021-10-08|v2|2022-04-21|cs.LG|Journal reference|Proceedings of the IEEE/CVF Winter Conference on Applications of Computer Vision 2023 (WACV)","metadata":"{\"State-Gated Retrieval\":[\"Only include arXiv records where v1 submitted falls between 2019-01-01 and 2021-12-31.\",\"The title or abstract must explicitly use terms from the dataset distillation or dataset condensation family, and the semantics must refer to replacing large-scale training sets with a small set of synthetic training data.\",\"The current primary category must be cs.LG; if a paper is only cross-listed into Machine Learning by another primary category, do not include it.\",\"The paper must have a revision within the next calendar year after the initial submission, and the current record must still clearly indicate a subsequent publication venue.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Root searches yield candidate arXiv IDs\",\"Each candidate abstract page yields primary category, v1 date, first next-year version, cue location, and publication-trail source\",\"Answer rows are produced only after deduplication and detail-page validation\"],\"control_dependency\":[\"Records must be filtered by original submission year, with per-record validation that a version in the next calendar year exists\",\"Cross-listed-only hits must be excluded, and the current primary category must be validated on abstract pages\",\"Searches must cover both Title and Abstract because valid distillation hits can appear only in the abstract\",\"Topic matches without a current publication trail still fail until the Comments, Journal reference, or Related DOI field is checked on the abstract page\"],\"freeze\":{\"historical_window\":\"v1 year in {2019, 2020, 2021}\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only include arXiv records where v1 submitted falls between 2019-01-01 and 2021-12-31.\",\"The title or abstract must explicitly use terms from the dataset distillation or dataset condensation family, and the semantics must refer to replacing large-scale training sets with a small set of synthetic training data.\",\"The current primary category must be cs.LG; if a paper is only cross-listed into Machine Learning by another primary category, do not include it.\",\"The paper must have a revision within the next calendar year after the initial submission, and the current record must still clearly indicate a subsequent publication venue.\"],\"exclusion_conditions\":[\"Exclude records whose current primary category is not cs.LG and that are only cross-listed to cs.LG.\",\"Exclude records where the title or abstract contains distillation/condensation terms but does not correspond to the dataset distillation or dataset condensation research line.\",\"Exclude records that have no version revision in the next calendar year, or whose current record contains no clearly visible publication clue.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"required literal first row shown in the oracle\",\"schema\":[\"arXiv ID\",\"term family\",\"cue location\",\"v1 submitted\",\"first next-year version\",\"date of that version\",\"primary category\",\"publication-trail source\",\"current publication clue\"],\"dedup_key\":\"bare arXiv ID without version suffix\",\"date_format\":\"YYYY-MM-DD\",\"term_family_extraction\":{\"allowed_families\":[\"Distillation\",\"Condensation\"],\"tie_break\":\"if both families appear, prefer the title hit; if both appear only in the abstract, keep the first abstract occurrence\"},\"cue_location\":{\"Title\":\"qualifying cue appears only in the title\",\"Abstract-only\":\"qualifying cue appears only in the abstract\",\"Title + Abstract\":\"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name\"},\"publication_trail_source\":[\"Comments\",\"Journal reference\",\"Related DOI\"],\"current_publication_clue\":\"keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue\",\"sorting_or_selection\":{\"primary\":\"v1 submitted ascending\",\"secondary\":\"arXiv ID ascending\"},\"stop_condition\":[\"all four corrected result pages are exhausted\",\"all unique candidate IDs are opened to abstract-page depth\",\"for every surviving candidate, the abstract page, current browse context, and publication-trail fields are checked before emitting the final ordered table\"]}}","all_involved_urls":"null"} +{"task_id":"arxiv_002-g","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":10,"instruction":"I am compiling a reading list of 2022 research on reasoning prompting for large language models. From arXiv papers whose first version (v1) was submitted in 2022, I want to select those whose title or abstract explicitly focuses on chain-of-thought or self-consistency reasoning and whose primary category is Computation and Language. Candidate papers must also have a version update in 2023, and the current arXiv record's Comments field must directly indicate a subsequent publication venue. Output a table sorted by the date of each paper's earliest 2023 version in ascending order, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2023 version, date of that version, primary category, publication clue. If no qualifying papers exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Output a table sorted by the date of each paper's earliest 2023 version in ascending order, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2023 version, date of that version, primary category, publication clue. If no qualifying papers exist, output NONE.","oracle_answer":"arXiv ID|cue family|cue location|v1 submitted|first 2023 version|date of that version|primary category|publication clue\n2210.01240|Chain-of-thought|Title + Abstract|2022-10-03|v2|2023-01-25|cs.CL|Published as a conference paper at ICLR 2023\n2205.11916|Chain-of-thought|Abstract-only|2022-05-24|v4|2023-01-29|cs.CL|Accepted to NeurIPS2022\n2203.11171|Self-consistency; Chain-of-thought|Title + Abstract|2022-03-21|v4|2023-03-07|cs.CL|Published at ICLR 2023; camera ready version at ICLR 2023\n2210.03629|Chain-of-thought|Abstract-only|2022-10-06|v3|2023-03-10|cs.CL|v3 is the ICLR camera ready version\n2210.03350|Chain-of-thought|Abstract-only|2022-10-07|v2|2023-05-23|cs.CL|To appear at Findings of EMNLP 2023\n2212.10001|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-01|cs.CL|ACL-23 Camera Ready\n2212.08061|Chain-of-thought|Abstract-only|2022-12-15|v2|2023-06-04|cs.CL|ACL 2023 Main Conference\n2212.10071|Chain-of-thought|Abstract-only|2022-12-20|v2|2023-06-13|cs.CL|ACL 2023 camera-ready\n2212.10509|Chain-of-thought|Title + Abstract|2022-12-20|v2|2023-06-23|cs.CL|ACL'23 Camera Ready\n2211.12588|Chain-of-thought; Self-consistency|Abstract-only|2022-11-22|v4|2023-10-23|cs.CL|Published at TMLR 2023","metadata":"{\"State-Gated Retrieval\":[\"Only retain arXiv papers whose v1 was submitted in 2022.\",\"The title or abstract must explicitly contain cues related to chain-of-thought or self-consistency.\",\"The current primary category must be cs.CL; do not include records that are only cross-listed from other primary categories.\",\"The paper must have a version update in 2023, and the current Comments field must clearly indicate a subsequent publication venue.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"root searches yield candidate arXiv IDs\",\"each candidate abstract page yields primary category, v1 date, first 2023 version, comments/publication clue\",\"answer rows are produced only after deduplication and detail-page validation\"],\"control_dependency\":[\"searches must cover both Title and Abstract fields because valid rows can appear only in the abstract\",\"cross-listed hits whose primary category is not cs.CL must be excluded, and the primary category must be validated on the abstract page\",\"topic-matched hits must be validated against a current Comments publication clue before they can be accepted\",\"2023 candidates must be identified by original submission year and full version-history checks, rather than by latest-date proxies\"],\"freeze\":{\"historical_window\":\"v1 submitted in 2022; version-history event in 2023\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only retain arXiv papers whose v1 was submitted in 2022.\",\"The title or abstract must explicitly contain cues related to chain-of-thought or self-consistency.\",\"The current primary category must be cs.CL; do not include records that are only cross-listed from other primary categories.\",\"The paper must have a version update in 2023, and the current Comments field must clearly indicate a subsequent publication venue.\"],\"exclusion_conditions\":[\"Exclude records whose current primary category is not cs.CL, even if they appear in relevant search results.\",\"Exclude records that contain only vague abbreviations or weak related hints, but whose title and abstract lack clear CoT/self-consistency semantics.\",\"Exclude records that have no 2023 version update, or whose current record lacks a direct publication clue.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"required literal first row shown in the oracle\",\"schema\":[\"arXiv ID\",\"cue family\",\"cue location\",\"v1 submitted\",\"first 2023 version\",\"date of that version\",\"primary category\",\"publication clue\"],\"dedup_key\":\"bare arXiv ID without version suffix\",\"date_format\":\"YYYY-MM-DD\",\"cue_family\":[\"Chain-of-thought\",\"Self-consistency\"],\"cue_location\":{\"Title\":\"qualifying cue appears only in the title\",\"Abstract-only\":\"qualifying cue appears only in the abstract\",\"Title + Abstract\":\"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name\"},\"publication_clue\":{\"source\":\"Comments field only\",\"extraction\":\"keep the shortest phrase that still preserves the current publication-status clue\"},\"sorting_or_selection\":{\"primary\":\"date of the earliest 2023 version ascending\",\"secondary\":\"arXiv ID ascending\"},\"stop_condition\":[\"all corrected result pages are exhausted\",\"all unique candidate IDs are opened to abstract-page depth\",\"for every surviving candidate, the current browse context, Comments field, and full Submission history are checked before emitting the final ordered table\"]}}","all_involved_urls":"null"} +{"task_id":"arxiv_003-g","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"I am compiling a reading list of early vision Transformer papers. From arXiv papers whose first version (v1) was submitted in Q4 2020, I want to select those whose title or abstract explicitly uses vision- or image-related Transformer terminology and whose primary category is Computer Vision and Pattern Recognition. Additionally, eligible papers must have had at least one updated version in 2021, and their current arXiv record must still directly indicate a subsequent publication venue. Output a table sorted in ascending order by the date of each paper's earliest 2021 version, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying papers exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Output a table sorted in ascending order by the date of each paper's earliest 2021 version, with columns: arXiv ID, cue family, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication-trail source, current publication clue. If no qualifying papers exist, output NONE.","oracle_answer":"arXiv ID|cue family|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication-trail source|current publication clue\n2101.01097|Vision Transformer|Abstract-only|2020-12-30|v2|2021-01-08|cs.CV|Journal reference|IEEE Int. Conf. on Image Processing (ICIP) 2021\n2012.12556|Visual Transformer; Vision Transformer|Title + Abstract|2020-12-23|v2|2021-01-15|cs.CV|Comments; Related DOI|Accepted by TPAMI 2022; 10.1109/TPAMI.2022.3152247\n2012.00364|Image Processing Transformer|Title + Abstract|2020-12-01|v3|2021-05-28|cs.CV|Comments|CVPR 2021\n2011.08019|Vision Transformer|Title + Abstract|2020-11-16|v2|2021-06-02|cs.CV|Comments|Accepted for Publication in IJCB2021\n2010.11929|Vision Transformer|Abstract-only|2020-10-22|v2|2021-06-03|cs.CV|Comments|ICLR camera-ready version","metadata":"{\"State-Gated Retrieval\":[\"Only include arXiv papers whose v1 submission date falls in Q4 2020.\",\"The title or abstract must explicitly contain vision- or image-related Transformer terminology.\",\"The current primary category must be cs.CV.\",\"The paper must have had an updated version in 2021, and the current record must still directly indicate a subsequent publication venue.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"root searches yield candidate arXiv IDs\",\"candidate abstract pages yield v1 submitted date, first 2021 version, primary category, cue location, and publication-trail source\",\"answer rows depend on deduplication plus detail-page validation\"],\"control_dependency\":[\"searches must cover both Title and Abstract because valid positives can appear only in the abstract\",\"candidate eligibility must be determined by the original-submission date window rather than by arXiv-ID or announcement intuition\",\"candidate filtering must use full Submission-history validation rather than most-recent-submission filtering\",\"searches must use the broader semantic cue state rather than a ViT-only entry point, because ViT-only hits can be false positives\",\"publication-trail false positives still require Comments / Journal reference / Related DOI validation before final inclusion\"],\"freeze\":{\"historical_window\":\"v1 submitted from 2020-10-01 through 2020-12-31; version-history event in 2021\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only include arXiv papers whose v1 submission date falls in Q4 2020.\",\"The title or abstract must explicitly contain vision- or image-related Transformer terminology.\",\"The current primary category must be cs.CV.\",\"The paper must have had an updated version in 2021, and the current record must still directly indicate a subsequent publication venue.\"],\"exclusion_conditions\":[\"Exclude records whose current primary category is not cs.CV and are only cross-listed.\",\"Exclude records that contain only weak cues such as Transformer/ViT but lack explicit vision- or image-related terminology in the title and abstract.\",\"Exclude records that had no version update in 2021 or whose current record contains no direct publication clue.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"required literal first row shown in the oracle\",\"schema\":[\"arXiv ID\",\"cue family\",\"cue location\",\"v1 submitted\",\"first 2021 version\",\"date of that version\",\"primary category\",\"publication-trail source\",\"current publication clue\"],\"dedup_key\":\"bare arXiv ID without version suffix\",\"date_format\":\"YYYY-MM-DD\",\"cue_family_extraction\":\"record every qualifying family actually present and join multiple families with `; ` in the emitted field\",\"cue_location\":{\"Title\":\"qualifying cue appears only in the title\",\"Abstract-only\":\"qualifying cue appears only in the abstract\",\"Title + Abstract\":\"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name\"},\"publication_trail_source\":[\"Comments\",\"Journal reference\",\"Related DOI\"],\"current_publication_clue\":\"keep the shortest phrase that still preserves venue or publication-status information; when sourced from Related DOI, drop the DOI prefix and keep only the informative clue\",\"sorting_or_selection\":{\"primary\":\"date of the earliest 2021 version ascending\",\"secondary\":\"arXiv ID ascending\"},\"stop_condition\":[\"all corrected result pages are exhausted\",\"all unique candidate IDs are opened to abstract-page depth\",\"for every surviving candidate, the abstract page, current browse context, Comments field, Journal reference, Related DOI, and full Submission history are checked before emitting the final ordered table\"]}}","all_involved_urls":"null"} +{"task_id":"arxiv_004-g","domain":"ARXIV","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"From arXiv papers whose first version was submitted in the first half of 2020, select those whose primary category is Machine Learning and whose title or abstract clearly focuses on certified robustness defenses. The research subject of each candidate paper must explicitly involve at least one of the following cues: randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor/poisoning, or partition aggregation. Additionally, these papers must have a version update in 2021, and the current arXiv record must still show a formal publication or acceptance destination. Output a table sorted in ascending order by the date of each paper's earliest 2021 version, with columns: arXiv ID, defense family, threat/topic cue, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.","start_url":"https://arxiv.org/search/advanced","output_format":"Output a table sorted in ascending order by the date of each paper's earliest 2021 version, with columns: arXiv ID, defense family, threat/topic cue, cue location, v1 submitted, first 2021 version, date of that version, primary category, publication clue. If no qualifying items exist, output NONE.","oracle_answer":"arXiv ID|defense family|threat/topic cue|cue location|v1 submitted|first 2021 version|date of that version|primary category|publication clue\n2002.10733|De-randomized smoothing; Randomized smoothing|patch attacks|Title + Abstract|2020-02-25|v3|2021-01-08|cs.LG|NeurIPS 2020\n2006.04062|Smoothed classifiers; Randomized smoothing|certified L2 robustness|Title + Abstract|2020-06-07|v4|2021-01-08|cs.LG|NeurIPS 2020\n2003.08904|RAB; Randomized smoothing|backdoor attacks|Title + Abstract|2020-03-19|v4|2021-02-26|cs.LG|IEEE Symposium on Security and Privacy 2023\n2006.14768|Deep Partition Aggregation|general poisoning attacks; label-flipping poisoning attacks|Title + Abstract|2020-06-26|v2|2021-03-18|cs.LG|ICLR 2021\n2002.12398|Transformation-specific smoothing; Randomized smoothing|semantic transformations|Title + Abstract|2020-02-27|v4|2021-09-17|cs.LG|2021 ACM SIGSAC Conference on Computer and Communications Security (CCS '21)","metadata":"{\"State-Gated Retrieval\":[\"Only include arXiv papers with v1 submitted between 2020-01-01 and 2020-06-30.\",\"The title or abstract must clearly focus on randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor or poisoning attacks, or partition aggregation.\",\"The current primary category must be cs.LG.\",\"Must have a version update in 2021, and the current record must show a formal publication or acceptance destination.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"root searches yield candidate arXiv IDs\",\"candidate abstract pages yield v1 date, primary category, full Submission history, cue location, and current publication clue\",\"final rows depend on deduplication plus detail-page validation\"],\"control_dependency\":[\"candidate filtering must use the original-submission window together with full 2021 version-history validation, because valid rows can have later newest versions\",\"cross-listed hits whose primary category is not the target category must be excluded, with category validation on detail pages\",\"searches must cover the broader certified-defense family, including partition-aggregation and backdoor/poisoning variants, rather than smoothing-only entries\",\"topic+venue hits must be confirmed by detail-history validation that a 2021 version actually exists\"],\"freeze\":{\"historical_window\":\"v1 submitted from 2020-01-01 through 2020-06-30; version-history event in 2021\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only include arXiv papers with v1 submitted between 2020-01-01 and 2020-06-30.\",\"The title or abstract must clearly focus on randomized smoothing, de-randomized smoothing, transformation-specific smoothing, smoothed classifiers, certified defenses against backdoor or poisoning attacks, or partition aggregation.\",\"The current primary category must be cs.LG.\",\"Must have a version update in 2021, and the current record must show a formal publication or acceptance destination.\"],\"exclusion_conditions\":[\"Exclude records whose current primary category is not cs.LG, even if semantically related.\",\"Exclude records that are only broadly related to robustness, defense, or backdoor/poisoning but do not meet the required certified-defense semantics.\",\"Exclude records without a 2021 version update or without a current publication clue.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"required literal first row shown in the oracle\",\"schema\":[\"arXiv ID\",\"defense family\",\"threat/topic cue\",\"cue location\",\"v1 submitted\",\"first 2021 version\",\"date of that version\",\"primary category\",\"publication clue\"],\"dedup_key\":\"bare arXiv ID without version suffix\",\"date_format\":\"YYYY-MM-DD\",\"defense_family_extraction\":\"record every qualifying defense family actually present and join multiple families with `; ` in the emitted field\",\"threat_topic_cue\":\"keep the shortest qualifying threat or topic cue that justifies inclusion\",\"cue_location\":{\"Title\":\"qualifying cue appears only in the title\",\"Abstract-only\":\"qualifying cue appears only in the abstract\",\"Title + Abstract\":\"qualifying cue appears in both title and abstract, or title carries only a generic cue while the abstract carries the specific family name\"},\"publication_clue\":\"keep the shortest phrase that still preserves venue or publication-status information\",\"sorting_or_selection\":{\"primary\":\"date of the earliest 2021 version ascending\",\"secondary\":\"arXiv ID ascending\"},\"stop_condition\":[\"all corrected result pages are exhausted\",\"all unique candidate IDs are opened to abstract-page depth\",\"for every surviving candidate, the abstract page, current browse context, Comments field, and full Submission history are checked before emitting the final ordered table\"]}}","all_involved_urls":"null"} +{"task_id":"census_001-g","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":20,"instruction":"Using the 2014–2018 American Community Survey 5-year estimates, identify North Carolina counties that simultaneously exhibit insufficient internet access, a high share of seniors living alone, limited transportation options, and low income. Candidate counties must meet all of the following conditions: at least 4,000 households with no internet access; a share of households with no internet access higher than the statewide share; a share of households with a householder aged 65 or older living alone higher than the statewide share; a share of households with no vehicle higher than the statewide share; and a median household income lower than the statewide median. All statewide comparisons must use the North Carolina statewide estimate from the same data release. List all qualifying counties in a single line ordered alphabetically by county name. Each county should be formatted as County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome, with counties separated by commas. Percentage fields should retain three decimal places without a percent sign.","start_url":"https://www.census.gov/data.html","output_format":"List all qualifying counties in a single line ordered alphabetically by county name. Each county should be formatted as County|NoInternetHH|NoInternetRatePct|SeniorLivingAloneSharePct|NoVehicleRatePct|MedianIncome, with counties separated by commas. Percentage fields should retain three decimal places without a percent sign.","oracle_answer":"Beaufort County|5988|30.986|16.083|7.664|43688,Bladen County|4194|30.026|13.681|10.417|32378,Cleveland County|11599|31.449|12.469|7.825|40393,Columbus County|7371|33.045|15.148|7.958|36398,Duplin County|7574|34.773|14.370|7.424|38850,Edgecombe County|7454|34.879|13.720|11.225|35516,Halifax County|7575|35.873|14.657|11.565|34251,Lenoir County|4923|21.292|15.614|11.699|38387,Nash County|8617|23.467|13.597|7.917|48362,Richmond County|5193|28.001|13.706|9.269|36091,Robeson County|19814|43.103|11.312|9.854|33679,Rockingham County|9938|26.714|14.166|7.164|42490,Rutherford County|7583|28.783|16.033|6.335|40347,Sampson County|8216|34.907|14.088|7.686|39068,Scotland County|4971|37.909|13.910|11.470|35617,Surry County|7595|26.203|13.762|6.779|41068,Vance County|5131|30.444|12.347|11.600|37282,Wayne County|9709|20.163|11.742|8.456|42192,Wilkes County|7046|24.849|14.773|5.992|40829,Wilson County|7652|23.817|13.322|9.540|42850","metadata":"{\"State-Gated Retrieval\":[\"Use only the 2014-2018 American Community Survey 5-year estimates for North Carolina counties, and use the North Carolina statewide value from the same release as the comparison baseline.\",\"Retain only counties with at least 4,000 households with no internet access, and where the share of households with no internet access, the share of households with a householder aged 65 or older living alone, and the share of households with no vehicle are all higher than the statewide shares, while the median household income is lower than the statewide median.\",\"Output the final results in alphabetical order by county name, retaining the six required fields.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the 2014-2018 ACS 5-year product and North Carolina county geography yield the full county candidate set plus the statewide baseline row\",\"the relevant ACS tables yield no-internet households, senior-living-alone share, no-vehicle share, and median household income for each county and the state baseline\",\"final rows are produced only after the 5-year product/geography setup is fixed consistently and the full county filtering chain is executed from B28002 through the downstream filters\"],\"control_dependency\":[\"the 2018 ACS 5-year Detailed Tables product must be used instead of the 2018 ACS 1-year product\",\"county coverage must be established under one consistent product-and-geography setup rather than by piecemeal fixes within the current table\",\"all downstream county comparisons must use the same 5-year statewide baseline and the same all-counties geography\"],\"freeze\":{\"historical_window\":\"2014-2018 American Community Survey 5-year estimates for North Carolina counties, using the North Carolina statewide row from the same release as the comparison baseline\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Use only the 2014-2018 American Community Survey 5-year estimates for North Carolina counties, and use the North Carolina statewide value from the same release as the comparison baseline.\",\"Retain only counties with at least 4,000 households with no internet access, and where the share of households with no internet access, the share of households with a householder aged 65 or older living alone, and the share of households with no vehicle are all higher than the statewide shares, while the median household income is lower than the statewide median.\",\"Output the final results in alphabetical order by county name, retaining the six required fields.\"],\"exclusion_conditions\":[\"Exclude results that incorrectly use the 2018 ACS 1-Year Estimates Detailed Tables or any data other than the 2014-2018 5-year release.\",\"Exclude results that do not use the North Carolina statewide row from the same release as the comparison baseline.\",\"Exclude any county that does not satisfy every threshold or statewide comparison condition.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"County\",\"NoInternetHH\",\"NoInternetRatePct\",\"SeniorLivingAloneSharePct\",\"NoVehicleRatePct\",\"MedianIncome\"],\"county\":\"use the county display name including the word `County` and excluding a trailing state suffix\",\"dedup_key\":\"county FIPS / GEOID\",\"percentage_fields\":\"all percentage fields are plain numbers with exactly three decimal places and no percent sign\",\"numeric_fields\":\"household counts and median income are emitted as plain integers without commas\",\"sorting_or_selection\":\"county name alphabetical ascending\",\"stop_condition\":[\"the North Carolina statewide threshold is fixed once from the designated table\",\"all 100 North Carolina counties are covered under the same table/product settings\",\"every surviving county is validated against all four required tables before emission\"]}}","all_involved_urls":"null"} +{"task_id":"census_002-g","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"Using the 2015–2019 American Community Survey 5-year estimates, identify New Mexico counties that simultaneously exhibit large renter populations, notable language barriers, limited internet access, transportation disadvantages, low income, and rental stress. These counties are intended to assess which areas were unsuitable for replacing in-person tenant legal aid with online self-service before the pandemic. Candidate counties must meet all of the following conditions: at least 2,500 renter-occupied households; at least 500 limited-English-speaking households; a share of limited-English-speaking households higher than the statewide share; a share of households with no internet access higher than the statewide share; a share of households with no vehicle higher than the statewide share; a median household income lower than the statewide median; and rental stress higher than the statewide level. Rental stress higher than the statewide level must be demonstrated by at least one of the following: a share of renter households with a rent-to-income ratio of 35% or higher that exceeds the statewide share, or a share of renter households with more than one occupant per room that exceeds the statewide share. All comparisons of “higher than statewide” or “lower than statewide” use the New Mexico statewide value from the same data release. Output a single line with all qualifying counties sorted alphabetically by county name. Each county is written as County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath, where StressPath must be RENT, CROWD, or BOTH. Separate multiple counties with commas. Percentage fields retain three decimal places with no percent sign.","start_url":"https://data.census.gov/advanced","output_format":"Output a single line with all qualifying counties sorted alphabetically by county name. Each county is written as County|RenterHH|LEPHH|LEPSharePct|NoInternetPct|NoVehiclePct|SevereRentBurdenPct|CrowdedRenterPct|MedianIncome|StressPath, where StressPath must be RENT, CROWD, or BOTH. Separate multiple counties with commas. Percentage fields retain three decimal places with no percent sign.","oracle_answer":"Doña Ana County|28729|7883|10.127|22.612|6.079|44.172|6.391|40973|BOTH,Luna County|3482|1109|12.455|34.030|8.165|42.700|1.407|29360|RENT,McKinley County|6090|1610|7.688|50.587|10.978|27.568|16.256|33834|CROWD,San Miguel County|3443|1200|10.337|38.470|7.684|47.376|2.440|30946|RENT,Taos County|2854|652|5.387|28.844|5.726|48.823|4.555|38329|RENT","metadata":"{\"State-Gated Retrieval\":[\"Use only New Mexico county data from the 2015–2019 American Community Survey 5-year estimates, and use the New Mexico statewide value from the same release as the comparison baseline.\",\"Candidate counties must have at least 2,500 renter households, at least 500 limited-English-speaking households, and LEP share, no-internet share, and no-vehicle share all higher than the statewide values, while median household income is lower than the statewide value.\",\"LEPHH must be computed by summing all four limited-English language groups in C16002. Retain only counties where at least one of Severe Rent Burden or Crowded Renter exceeds the statewide value, and write StressPath according to the rule.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the 2015-2019 ACS 5-year county geography yields New Mexico county candidates and the statewide baseline row\",\"C16002 and the downstream housing/income tables yield LEPHH, LEP share, no-internet share, no-vehicle share, severe rent burden, crowded-renter share, and median income for counties and the state baseline\",\"final rows are produced only after the LEPHH numerator is computed from all four limited-English language groups and the downstream stress-path filters are applied\"],\"control_dependency\":[\"the LEPHH numerator must be computed from all four limited-English language groups in C16002 rather than from Spanish-only counts\",\"county eligibility and StressPath labels must be determined from the LEPHH measure and statewide LEP baseline defined under that full four-group calculation\",\"the RENT / CROWD / BOTH classification must be determined by evaluating the same county set against both downstream housing-stress branches\"],\"freeze\":{\"historical_window\":\"2015-2019 American Community Survey 5-year estimates for New Mexico counties, using the New Mexico statewide row from the same release as the comparison baseline\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Use only New Mexico county data from the 2015–2019 American Community Survey 5-year estimates, and use the New Mexico statewide value from the same release as the comparison baseline.\",\"Candidate counties must have at least 2,500 renter households, at least 500 limited-English-speaking households, and LEP share, no-internet share, and no-vehicle share all higher than the statewide values, while median household income is lower than the statewide value.\",\"LEPHH must be computed by summing all four limited-English language groups in C16002. Retain only counties where at least one of Severe Rent Burden or Crowded Renter exceeds the statewide value, and write StressPath according to the rule.\"],\"exclusion_conditions\":[\"Exclude results that treat Spanish-only limited-English households as the entire LEPHH count.\",\"Exclude results that do not use the statewide baseline from the same release or do not recompute LEPHH/LEPSharePct/LEPShare_state.\",\"Exclude counties that do not satisfy the final stress-path condition of RENT, CROWD, or BOTH.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"County\",\"RenterHH\",\"LEPHH\",\"LEPSharePct\",\"NoInternetPct\",\"NoVehiclePct\",\"SevereRentBurdenPct\",\"CrowdedRenterPct\",\"MedianIncome\",\"StressPath\"],\"county\":\"use the county display name including the word `County` and excluding a trailing state suffix\",\"dedup_key\":\"county FIPS / GEOID\",\"LEPHH\":\"sum the four designated limited-English-proficient renter-household cells before emitting the integer total\",\"percentage_fields\":\"all percentage fields are plain numbers with exactly three decimal places and no percent sign\",\"numeric_fields\":\"household counts and median income are emitted as plain integers without commas\",\"StressPath\":{\"allowed_values\":[\"RENT\",\"CROWD\",\"BOTH\"],\"rule\":\"emit BOTH only when both the severe-rent-burden and crowded-renter signals survive; otherwise emit the single surviving label\"},\"sorting_or_selection\":\"county name alphabetical ascending\",\"stop_condition\":[\"all candidate counties are validated under the same geography and product settings\",\"the renter scope and LEP aggregation are checked before the final line is emitted\"]}}","all_involved_urls":"null"} +{"task_id":"census_003-g","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"Using the 2013–2017 American Community Survey 5-year estimates for California counties, identify counties where, for school meal material updates and annual parent information updates, relying solely on an English-only online portal is insufficient and paper materials with offline assistance must still be retained. Candidate counties must meet all of the following conditions: population aged 5–17 at least 75,000; among the population aged 5–17, the number of people who speak English \"not well\" or \"not at all\" is at least 2,000 and its share is higher than the statewide share; share of households without internet access higher than the statewide share; median household income lower than the statewide share; and at least two of three support-need signals higher than the statewide share. The three support-need signals are: share of households with no vehicle; share of minors living in households that received SSI, cash public assistance, or Food Stamps/SNAP in the past 12 months; and share of renter-occupied households with more than one occupant per room. All comparisons of \"higher than statewide\" or \"lower than statewide\" use the California statewide value from the same data release. Output all qualifying counties in a single line sorted alphabetically by county name. Each county is written as County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath, where SupportPath uses only the three labels BENEFITS, CROWD, and MOBILITY joined by + in that fixed order. Multiple counties are separated by commas.","start_url":"https://data.census.gov/advanced","output_format":"Output all qualifying counties in a single line sorted alphabetically by county name. Each county is written as County|SchoolAgePop|SchoolAgeLEP|LEPSharePct|NoInternetPct|NoVehiclePct|ChildBenefitSharePct|CrowdedRenterPct|MedianIncome|SupportPath, where SupportPath uses only the three labels BENEFITS, CROWD, and MOBILITY joined by + in that fixed order. Multiple counties are separated by commas.","oracle_answer":"Fresno County|200205|5127|2.561|20.588|8.686|46.388|13.967|48730|BENEFITS+CROWD+MOBILITY,Kern County|185802|4130|2.223|21.739|7.058|37.285|14.394|50826|BENEFITS+CROWD,Los Angeles County|1641669|37540|2.287|16.338|9.204|27.238|16.741|61015|BENEFITS+CROWD+MOBILITY,Tulare County|104542|2703|2.586|25.738|6.274|49.347|14.535|44871|BENEFITS+CROWD","metadata":"{\"State-Gated Retrieval\":[\"Use only California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline.\",\"Retain only counties with a population aged 5–17 of at least 75,000, a SchoolAgeLEP count of at least 2,000 with its share higher than the statewide share, a no-internet share higher than the statewide share, and a median household income lower than the statewide share.\",\"SchoolAgeLEP must be the sum of the eight not-well/not-at-all cells across the four major language groups in B16004. The final county must also have at least two of the three offline support signals (Mobility, Benefits, Crowd) higher than the statewide share.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the 2013-2017 ACS 5-year county geography yields California county candidates and the statewide baseline row\",\"B16004 and the downstream access/income/support tables yield SchoolAgeLEP, no-internet share, no-vehicle share, child-benefit share, crowded-renter share, and median income for counties and the statewide baseline\",\"final rows are produced only after the SchoolAgeLEP numerator is computed from all eight 1980-target language cells and the downstream support-path branches are applied\"],\"control_dependency\":[\"the SchoolAgeLEP numerator must be computed from the full eight-cell language set in B16004 rather than from only two Spanish LEP cells\",\"county eligibility and SupportPath labels must be determined from the LEP numerator and candidate set defined under that full eight-cell calculation\",\"the BENEFITS / CROWD / MOBILITY path labels must be determined by applying all three downstream support branches to the same county set\"],\"freeze\":{\"historical_window\":\"2013-2017 American Community Survey 5-year estimates for California counties, using the California statewide row from the same release as the comparison baseline\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Use only California county data from the 2013–2017 American Community Survey 5-year estimates, and use the California statewide value from the same release as the comparison baseline.\",\"Retain only counties with a population aged 5–17 of at least 75,000, a SchoolAgeLEP count of at least 2,000 with its share higher than the statewide share, a no-internet share higher than the statewide share, and a median household income lower than the statewide share.\",\"SchoolAgeLEP must be the sum of the eight not-well/not-at-all cells across the four major language groups in B16004. The final county must also have at least two of the three offline support signals (Mobility, Benefits, Crowd) higher than the statewide share.\"],\"exclusion_conditions\":[\"Exclude results that use only the two Spanish LEP rows without merging all eight target cells.\",\"Exclude results that do not rerun the B28011, B19013, B08201, B09010, and B25014 branches.\",\"Exclude counties whose final SupportPath does not have at least two signals higher than the statewide share.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"County\",\"SchoolAgePop\",\"SchoolAgeLEP\",\"LEPSharePct\",\"NoInternetPct\",\"NoVehiclePct\",\"ChildBenefitSharePct\",\"CrowdedRenterPct\",\"MedianIncome\",\"SupportPath\"],\"county\":\"use the county display name including the word `County` and excluding a trailing state suffix\",\"dedup_key\":\"county FIPS / GEOID\",\"SchoolAgeLEP\":\"sum the eight designated school-age LEP cells before emitting the integer total\",\"percentage_fields\":\"all percentage fields are plain numbers with exactly three decimal places and no percent sign\",\"numeric_fields\":\"population counts and median income are emitted as plain integers without commas\",\"SupportPath\":\"use only BENEFITS, CROWD, and MOBILITY, and when multiple labels apply join them with `+` in the fixed order BENEFITS+CROWD+MOBILITY\",\"sorting_or_selection\":\"county name alphabetical ascending\",\"stop_condition\":[\"all candidate counties are validated under the same geography and product settings\",\"the school-age LEP aggregation and all three support-signal gates are checked before the final line is emitted\"]}}","all_involved_urls":"null"} +{"task_id":"census_004-g","domain":"CENSUS_GOV","autonomy_type":"ordered table","oracle_output_cardinality":7,"instruction":"Using the 2012–2016 American Community Survey 5-year estimates, identify Pennsylvania counties with high elderly evacuation support needs that should conduct in-person outreach before winter storms. A candidate county must meet all of the following conditions: a population aged 65 and older of at least 15,000; a population aged 65 and older with ambulatory difficulty of at least 4,000, with its share of the 65+ population higher than the statewide share; a median household income below the statewide median; and at least two of four evacuation-support barriers above the statewide level. The four barriers are: share of households with a householder aged 65+ living alone, share of households with no vehicle, share of renter-occupied households with no vehicle, and mobile homes as a share of all housing units. All comparisons to the statewide level use the Pennsylvania statewide values from the same data release. Output all qualifying counties as a single line, sorted alphabetically by county name. Each county is formatted as County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath, with counties separated by commas. For BarrierPath, use only ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE, joined by + in that fixed order.","start_url":"https://www.census.gov/data.html","output_format":"Output all qualifying counties as a single line, sorted alphabetically by county name. Each county is formatted as County|SeniorPop|AmbulatoryDifficulty65Plus|AmbDiffPct|SeniorLivingAloneSharePct|NoVehiclePct|RenterNoVehiclePct|MobileHomePct|MedianIncome|BarrierPath, with counties separated by commas. For BarrierPath, use only ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE, joined by + in that fixed order.","oracle_answer":"Blair County|23013|5576|24.230|14.917|9.440|24.316|6.388|44033|ALONE+MOBILE_HOME, Cambria County|27058|6308|23.313|15.243|10.309|26.627|4.070|42917|ALONE+MOBILE_HOME+RENTER_NO_VEHICLE, Fayette County|25186|5886|23.370|14.961|9.302|22.290|10.489|40511|ALONE+MOBILE_HOME, Lycoming County|19486|4311|22.124|12.164|9.257|23.312|6.726|48731|ALONE+MOBILE_HOME, Mercer County|21537|4799|22.283|14.090|9.572|24.413|7.912|45831|ALONE+MOBILE_HOME, Philadelphia County|188185|56935|30.255|11.553|30.954|44.924|0.250|39770|NO_VEHICLE+RENTER_NO_VEHICLE, Schuylkill County|26613|6465|24.293|14.357|9.676|23.652|4.080|46573|ALONE+MOBILE_HOME","metadata":"{\"State-Gated Retrieval\":[\"Use only Pennsylvania county data from the 2012–2016 American Community Survey 5-year estimates, and use the Pennsylvania statewide values from the same release as the comparison baseline.\",\"Retain only counties with a 65+ population of at least 15,000, a 65+ ambulatory-difficulty population of at least 4,000 with a share above the statewide share, and a median household income below the statewide median.\",\"The 65+ ambulatory-difficulty numerator must combine the four target cells from B18105 for ages 65–74 and 75+, male and female. The final county must also have at least two of the four barriers (Alone, No Vehicle, Renter No Vehicle, Mobile Home) above the statewide level.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"ACS tables B01001 and B18105 yield county senior-population totals and the full 65+ ambulatory-difficulty numerator\",\"statewide comparison tables yield Pennsylvania baselines plus county barrier metrics for living alone, no vehicle, renter no vehicle, mobile home, and median income\",\"final rows are produced only after the county candidate set is defined from the full ambulatory-difficulty numerator and the downstream six-table filters are applied\"],\"control_dependency\":[\"the ambulatory-difficulty numerator must include the full 65+ population across 65–74 and 75+ and male and female cells rather than only the 75+ cells\",\"downstream county eligibility and barrier labels must be determined from the county candidate set defined under that full ambulatory numerator\",\"the at-least-two-barriers test must compare every county metric against the same Pennsylvania statewide baselines from the same ACS release\"],\"freeze\":{\"historical_window\":\"2012–2016 American Community Survey 5-year estimates for Pennsylvania counties, with Pennsylvania statewide baselines taken from the same release\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Use only Pennsylvania county data from the 2012–2016 American Community Survey 5-year estimates, and use the Pennsylvania statewide values from the same release as the comparison baseline.\",\"Retain only counties with a 65+ population of at least 15,000, a 65+ ambulatory-difficulty population of at least 4,000 with a share above the statewide share, and a median household income below the statewide median.\",\"The 65+ ambulatory-difficulty numerator must combine the four target cells from B18105 for ages 65–74 and 75+, male and female. The final county must also have at least two of the four barriers (Alone, No Vehicle, Renter No Vehicle, Mobile Home) above the statewide level.\"],\"exclusion_conditions\":[\"Exclude results that take only the 75-and-over ambulatory-difficulty cells and mistakenly treat them as the full 65+ count.\",\"Exclude results that do not use the Pennsylvania statewide baselines from the same release.\",\"Exclude counties whose final BarrierPath does not satisfy at least two barriers above the statewide level.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"County\",\"SeniorPop\",\"AmbulatoryDifficulty65Plus\",\"AmbDiffPct\",\"SeniorLivingAloneSharePct\",\"NoVehiclePct\",\"RenterNoVehiclePct\",\"MobileHomePct\",\"MedianIncome\",\"BarrierPath\"],\"county\":\"use the county display name including the word `County` and excluding a trailing state suffix\",\"dedup_key\":\"county FIPS / GEOID\",\"percentage_fields\":\"all percentage fields are plain numbers with exactly three decimal places and no percent sign\",\"numeric_fields\":\"population counts and median income are emitted as plain integers without commas\",\"BarrierPath\":\"use only ALONE, MOBILE_HOME, NO_VEHICLE, and RENTER_NO_VEHICLE, and when multiple labels apply join them with `+` in the fixed order ALONE+MOBILE_HOME+NO_VEHICLE+RENTER_NO_VEHICLE\",\"sorting_or_selection\":\"county name alphabetical ascending\",\"stop_condition\":[\"all candidate counties are validated under the same geography and product settings\",\"the senior ambulatory-difficulty gate and all barrier-signal gates are checked before the final line is emitted\"]}}","all_involved_urls":"null"} +{"task_id":"climategov_011-g","domain":"NOAA_NCEI_CLIMATE_AT_A_GLANCE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"Identify South Texas climate divisions that were near-normal or wetter over two longer periods and still had light heating demand in March 1966. Restrict the search strictly to the four divisions South Central, Upper Coast, South, and Lower Valley, using the exact names and numbering order from the official Texas climate-division page fragment.\n\nRetain only divisions that meet all three hard climate criteria: (1) the 10-month Palmer Z-Index anomaly ending February 1966 must be at least -0.05; (2) the 24-month Palmer Z-Index anomaly ending December 1966 must be at least -0.10; and (3) the actual March 1966 monthly Heating Degree Days value must be below 200°Df.\n\nSort qualifying divisions as follows: primary key is the sum of the February 1966 10-month Z-index anomaly and the December 1966 24-month Z-index anomaly, in descending order; secondary key is the March 1966 HDD actual value, in ascending order; tertiary key is the Texas division number, in ascending order.\n\nFinally, output all matching divisions as a single comma-separated string. Each entry must follow the format \"|||||\", where the moisture score is the sum of the two Z-index anomalies. If no division qualifies, output NONE in uppercase.","start_url":"https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national","output_format":"Output all matching divisions as a single comma-separated string. Each entry must follow the format \"|||||\", where the moisture score is the sum of the two Z-index anomalies. If no division qualifies, output NONE in uppercase.","oracle_answer":"7|South Central|0.72|0.35|194°Df|1.07,10|Lower Valley|0.28|0.67|106°Df|0.95,9|South|0.03|0.37|148°Df|0.40","metadata":"{\"State-Gated Retrieval\":[\"Filter only within the four South Texas divisions defined on the Texas divisional page: South Central, Upper Coast, South, and Lower Valley.\",\"Retain divisions that simultaneously satisfy: 1966-02 10-month Palmer Z-Index anomaly >= -0.05; 1966-12 24-month anomaly >= -0.10; 1966-03 1-month Heating Degree Days Value < 200°Df.\",\"Sort by sum of the two Z anomalies descending, then by 1966-03 HDD Value ascending, then by division number ascending.\"],\"dependency_type\":\"Data\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"The official Texas climate-division reference fixes the four South Texas division IDs and names that must be tracked across all later pages.\",\"The 1966-02 10-month Palmer Z-Index anomaly page and the 1966-12 24-month Palmer Z-Index anomaly page jointly identify the four target South Texas divisions.\",\"The 1966-03 1-month Heating Degree Days Value page supplies the last filter; final rows are produced only after intersecting the three divisional screens and then sorting by summed Z-anomaly score, HDD value, and division number.\"],\"freeze\":{\"historical_window\":\"Texas climate divisions South Central, Upper Coast, South, and Lower Valley; metrics are fixed to the 1966-02 10-month Palmer Z-Index anomaly, 1966-12 24-month anomaly, and 1966-03 1-month Heating Degree Days Value pages.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Filter only within the four South Texas divisions defined on the Texas divisional page: South Central, Upper Coast, South, and Lower Valley.\",\"Retain divisions that simultaneously satisfy: 1966-02 10-month Palmer Z-Index anomaly >= -0.05; 1966-12 24-month anomaly >= -0.10; 1966-03 1-month Heating Degree Days Value < 200°Df.\",\"Sort by sum of the two Z anomalies descending, then by 1966-03 HDD Value ascending, then by division number ascending.\"],\"exclusion_conditions\":[\"Exclude any Texas divisional results outside the four specified South Texas divisions.\",\"Exclude results that misread the 1966-03 HDD page filter field as Anomaly instead of Value.\",\"Exclude any division that fails any time window or threshold condition.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"texas_division_no\",\"division_name\",\"feb_1966_10mo_z_text\",\"dec_1966_24mo_z_text\",\"mar_1966_hdd_text\",\"moisture_score\"],\"texas_division_no\":\"Canonical output uses the short Texas climate-division number; the scorer may accept an equivalent four-digit form, but the emitted oracle uses the short number.\",\"raw_text_fields\":\"The two Z-index anomaly fields and the March 1966 HDD field preserve the raw displayed text; comparison may ignore optional trailing HDD unit text such as `°Df`.\",\"moisture_score\":\"Compute as February 1966 10-month Z-index anomaly plus December 1966 24-month Z-index anomaly, formatted with exactly two decimal places.\",\"sorting_or_selection\":{\"primary\":\"moisture_score descending\",\"secondary\":\"March 1966 HDD actual value ascending after numeric normalization\",\"tertiary\":\"Texas division number ascending\"},\"eligibility_rule\":\"Each Texas division is counted once per requested window; if any required window value is missing, exclude the division.\",\"stop_condition\":[\"All candidate Texas divisions are checked under the same base period and anomaly windows.\",\"The unique ordered output string is resolved before emission.\"]}}","all_involved_urls":"null"} +{"task_id":"climategov_012-g","domain":"NOAA_NCEI_CLIMATE_AT_A_GLANCE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am researching historical climate patterns in Texas and want to find similar historical years as references for shoulder-season operational planning. To do this, I need to identify specific Texas climate divisions in NOAA's Climate at a Glance database. The divisions I am looking for must have experienced a shift from a dry long-term moisture background back toward near-normal or wetter conditions in the early 20th century, and must have had light heating loads in two different shoulder-season windows.\n\nSpecifically, the selected divisions must satisfy all four of the following hard climate criteria: first, the 10-month Palmer Z-Index anomaly ending April 1907 must be no higher than -0.30; second, the 10-month Z-Index anomaly ending April 1923 must be no lower than -0.20; third, the 2-month Heating Degree Days (HDD) actual value ending May 1915 must be below 50°Df; and fourth, the 5-month HDD actual value ending October 1922 must be below 20°Df.\n\nAfter identifying the qualifying divisions, sort them according to the following rules. The primary sort key is the \"rebound score\", defined as the April 1923 10-month Z-Index anomaly minus the April 1907 10-month Z-Index anomaly, sorted in descending order. In case of a tie, place the division with the smaller October 1922 5-month HDD actual value first. If still tied, place the division with the smaller Texas division number first.\n\nFinally, output all matching divisions as a single comma-separated string. Each matching item must be formatted exactly as: \"|<4-digit division ID>||||||\". If after checking all divisions none meet the combined criteria, output NONE in uppercase.","start_url":"https://www.ncei.noaa.gov/access/monitoring/climate-at-a-glance/national","output_format":"Output all matching divisions as a single comma-separated string. Each matching item must be formatted exactly as: \"|<4-digit division ID>||||||\". If after checking all divisions none meet the combined criteria, output NONE in uppercase.","oracle_answer":"10|4110|Lower Valley|-0.36|1.46|10°Df|7°Df|1.82,9|4109|South|-0.33|0.53|23°Df|16°Df|0.86\n10|4110|Lower Valley|-0.36|1.46|10|7|1.82,9|4109|South|-0.33|0.53|23|16|0.86","metadata":"{\"State-Gated Retrieval\":[\"Retain only Texas divisions that satisfy all four historical conditions: the 10-month Palmer Z-Index anomaly for April 1907 must be no higher than -0.30; the 10-month anomaly for April 1923 must be no lower than -0.20; the 2-month HDD Value for May 1915 must be less than 50°Df; and the 5-month HDD Value for October 1922 must be less than 20°Df.\",\"The rebound score is defined as the April 1923 10-month anomaly minus the April 1907 10-month anomaly.\",\"Sort first by rebound score descending, then by the October 1922 5-month HDD Value ascending, then by Texas division number ascending.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Texas divisional pages yield the 1907-04 and 1923-04 10-month Palmer Z-Index anomalies plus the 1915-05 2-month and 1922-10 5-month HDD values for each division.\",\"The rebound score and the two shoulder-season HDD values are computed only after the same set of candidate divisions survives all four historical filters.\",\"The final output is produced after sorting the surviving divisions by rebound score, then 1922-10 HDD value, then division number.\"],\"control_dependency\":[\"The workflow must cover the 1907, 1923, and 1915 pages as well as the 1922-10 5-month HDD page.\",\"Both HDD pages must be read from Value rather than Anomaly.\",\"The final rebound ranking must be determined after the 1922-10 5-month HDD page excludes 7 South Central and 8 Upper Coast, using ReboundScore as the ordering basis.\"],\"freeze\":{\"historical_window\":\"Texas climate divisions evaluated on the 1907-04 and 1923-04 10-month Palmer Z-Index anomaly pages, the 1915-05 2-month HDD Value page, and the 1922-10 5-month HDD Value page.\"},\"answer_type\":\"mixed multi-line output\"}","rubric":"{\"inclusion_conditions\":[\"Retain only Texas divisions that satisfy all four historical conditions: the 10-month Palmer Z-Index anomaly for April 1907 must be no higher than -0.30; the 10-month anomaly for April 1923 must be no lower than -0.20; the 2-month HDD Value for May 1915 must be less than 50°Df; and the 5-month HDD Value for October 1922 must be less than 20°Df.\",\"The rebound score is defined as the April 1923 10-month anomaly minus the April 1907 10-month anomaly.\",\"Sort first by rebound score descending, then by the October 1922 5-month HDD Value ascending, then by Texas division number ascending.\"],\"exclusion_conditions\":[\"Exclude results that stop after filtering only the 1907, 1923, and 1915 pages without also reading the 1922-10 5-month HDD page.\",\"Exclude results that mistakenly read the 1915 or 1922 HDD page as Anomaly instead of Value.\",\"Exclude any division that does not satisfy any one of the historical window conditions.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"texas_division_no\",\"division_id_4digit\",\"division_name\",\"apr_1907_10mo_z_text\",\"apr_1923_10mo_z_text\",\"may_1915_2mo_hdd_text\",\"oct_1922_5mo_hdd_text\",\"rebound_score\"],\"texas_division_no\":\"Emit the short Texas climate-division number in field 1 and the four-digit division ID in field 2.\",\"raw_text_fields\":\"The two Z-index anomaly fields preserve the raw displayed text; the two HDD fields preserve the raw displayed text, but comparison may ignore an optional trailing °Df suffix.\",\"rebound_score\":\"Compute as the April 1923 10-month Z-index anomaly minus the April 1907 10-month Z-index anomaly, formatted with exactly two decimal places.\",\"sorting_or_selection\":{\"primary\":\"rebound_score descending\",\"secondary\":\"October 1922 HDD actual value ascending after numeric normalization\",\"tertiary\":\"Texas division number ascending\"},\"answer_set_note\":\"The current oracle stores two equivalent answer sets: one preserves the HDD unit suffixes and one strips them; treat the two HDD columns as equivalent after optional °Df removal.\",\"stop_condition\":[\"All candidate Texas divisions are checked under the same anomaly and HDD windows.\",\"The unique ordered output string is resolved before emission.\"]}}","all_involved_urls":"null"} +{"task_id":"comptox_010-g","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"Among the following five substances found in records related to painted products in Europe—aniline, cobalt, chromium, 3,3'-dichlorobenzidine, and dibenz[a,h]anthracene—select those whose pages explicitly contain the record 'Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe'. For each qualifying substance, produce a consolidated list that integrates historical keyword status and the deepest-level use categories. First, for each substance, count how many of the following five dated historical keywords are present (presence only, ignoring any leading numbers): Substances in Products - Canada (4/2014), Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children's Safe Product Act (4/2020), OEHHA Proposition 65 (1/2023). Also record the earliest and latest year-month among the hits. Second, for each substance, retain one category that best reflects its current use. After excluding the use category to which the above-mentioned painted-products record belongs, establish for each substance a terminal-use profile along two dimensions: 'daily consumer goods' (with the broad-category selection priority Formulation → Article → Occupation) and 'production materials' (with the broad-category selection priority Occupation → Article → Formulation). Finally, sort all substances by historical keyword hit count in descending order; for ties, sort by the number of products at the selected consumer-side node in descending order.","start_url":"https://comptox.epa.gov/chemexpo/","output_format":"Output format: |||||||||||||. Results separated by commas; if no qualifying items exist, output NONE.","oracle_answer":"DTXSID8020090|5|2014-04|2023-01|Formulation|272|295|type|4|Occupation|301|356|family|27,DTXSID1031040|3|2018-10|2023-01|Formulation|77|94|type|7|Occupation|301|400|family|308,DTXSID9020409|2|2019-03|2023-01|Occupation|321|321|general|11|Occupation|321|321|general|11,DTXSID6020432|2|2019-03|2023-01|Article|313|313|general|1|Occupation|301|356|family|27,DTXSID3031022|1|2023-01|2023-01|Formulation|77|95|type|4|Occupation|301|356|family|185","metadata":"{\"State-Gated Retrieval\":[\"Screen only the five specified substances, and the target substance page must explicitly contain the record 'Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe'.\",\"Count whether each of the five specified dated keywords appears, and record the earliest and latest year-month among the hits.\",\"Then independently select one consumer-side route and one production-material-side route, the former following Formulation → Article → Occupation and the latter following Occupation → Article → Formulation, and refine each route separately to its deepest level.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"each chemical page yields the five dated historical keywords, the Europe body-paint/tattoo-ink qualifying record, and the earliest/latest dated-hit months\",\"PUC category paths yield one consumer-side route chosen by Formulation -> Article -> Occupation and one source-side route chosen independently by Occupation -> Article -> Formulation\",\"final rows are produced only after the consumer-side and source-side routes are selected and refined separately for each chemical\"],\"control_dependency\":[\"the source-side route must be selected independently from the consumer-side route\",\"for each chemical, the second route refinement must follow the production-material priority order rather than the daily-consumer route\",\"family/type/general outputs must be determined only after both route selections are made independently\"],\"freeze\":{\"historical_window\":\"the five named substances as objectively existing chemicals, using their ChemExpo chemical pages, PUC category paths, keyword-state evidence, and Europe body-paint/tattoo-ink presence as relatively stable classification signals\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Screen only the five specified substances, and the target substance page must explicitly contain the record 'Arts and crafts/Office supplies - body paint - tattoo ink, detected, Europe'.\",\"Count whether each of the five specified dated keywords appears, and record the earliest and latest year-month among the hits.\",\"Then independently select one consumer-side route and one production-material-side route, the former following Formulation → Article → Occupation and the latter following Occupation → Article → Formulation, and refine each route separately to its deepest level.\"],\"exclusion_conditions\":[\"Exclude substances that do not contain the specified Europe painted-products/tattoo-ink record.\",\"Exclude results that directly reuse the same consumer-side route for the production-material side.\",\"Exclude results that do not independently select and refine both routes according to the specified priority orders.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"DTXSID\",\"hit_count\",\"earliest\",\"latest\",\"consumer_kind\",\"consumer_general_puc_id\",\"consumer_terminal_puc_id\",\"consumer_level\",\"consumer_products\",\"material_kind\",\"material_general_puc_id\",\"material_terminal_puc_id\",\"material_level\",\"material_products\"],\"dated_hits\":\"count only the exact dated keyword strings defined in the source rubric\",\"date_format\":\"YYYY-MM\",\"kind\":\"the kind fields use the canonical labels Article, Formulation, or Occupation\",\"level\":\"the level fields use the canonical labels general, family, or type\",\"products_source\":\"the Products counts come from the local chemical-detail node for the selected branch, not from an overall aggregate shown elsewhere on the site\",\"sorting_or_selection\":{\"primary\":\"hit_count descending\",\"secondary\":\"consumer_products descending\",\"tertiary\":\"DTXSID ascending\"}}}","all_involved_urls":"null"} +{"task_id":"comptox_011-g","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":6,"instruction":"In ChemExpo, for each of the six substances, determine whether it appears more often in material-contact uses or manufacturing-source uses, then select the most representative use category from the corresponding direction. Specifically, the scope is limited to these six substances: Di(2-Ethylhexyl) Phthalate, Melamine, Tris(2-Ethylhexyl) Phosphate, 4,5-Dihydro-2-Mercaptoimidazole, Phthalic Acid, and Triphenyl Phosphates Tert-Butylated. For each substance, three sets of data must be checked: first, a 'material-contact score' obtained by summing the occurrences of five specific labels (Indirect additives food contact (10/2018), Europe, Food contact items, Food contact items, Japan, entries containing 'Toys and children's products', and entries containing 'artificial_saliva' or 'artificial_sweat'); second, a 'manufacturing-source score' obtained by summing the occurrences of two specific labels (drinking_water, Europe, manufacturing, plastic_additive and Europe, plastic_additive); third, a regulatory profile generated by counting the total hits of four date-keyword labels (Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children's Safe Product Act (4/2020), OEHHA Proposition 65 (1/2023)) and extracting the earliest and latest month-year range spanned. Based on this, if the material-contact score is strictly greater than the manufacturing-source score, the substance is considered to favor material contact, and the most representative category is selected in the order Article → Formulation → Occupation; otherwise, it is considered to favor manufacturing source, and the selection order is Occupation → Article → Formulation. After determining the category, at each level, follow only the subcategory with the highest product count, continuing until no further subdivision is possible; if there is a tie at the same level, select the one with the smaller PUC ID.","start_url":"https://comptox.epa.gov/chemexpo/","output_format":"Finally, sort the substances by datedHits in descending order; for ties, sort by Products of the selected node in descending order. Output format: ||||||||||||. Results are separated by commas; if datedHits is 0, write NA for both earliest and latest.","oracle_answer":"DTXSID5020607|5|2|4|2018-10|2023-01|contact|Article|309|493|family|1|23|58,DTXSID5020601|4|1|3|2018-10|2023-01|contact|Article|309|309|general|1|5836|1827,DTXSID6020802|4|2|1|2018-10|2018-10|contact|Article|313|313|general|15|1104|675,DTXSID8021484|3|1|1|2018-10|2018-10|contact|Occupation|321|321|general|8|28313|4200,DTXSID0021414|5|0|1|2018-10|2018-10|contact|Article|309|309|general|3|5836|1827,DTXSID20872645|0|1|0|NA|NA|source|Occupation|318|381|family|5|274|107","metadata":"{\"State-Gated Retrieval\":[\"Only consider the six specified substances, and first compute contactHits, sourceHits, and datedHits on the chemical page.\",\"prioritySide must be determined by these historical signals first, then select the most representative current use category along the corresponding direction.\",\"The current route selection must continue drilling down according to the given kind priority and the same-level smaller PUC ID rule.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"each chemical page yields contactHits, sourceHits, datedHits, and the earliest/latest dated-hit months from the historical keyword set\",\"after the priority side is chosen, the corresponding current PUC category path yields the representative kind, PUC path, product counts, and curated-chemical counts\",\"final rows are produced only after the historical hit scores determine the side first and the current route is then chosen with the side-specific priority and tie-break rules\"],\"control_dependency\":[\"historical contact/source signal scores must take priority over current maximum-Products paths\",\"the priority side must be determined from contactHits, sourceHits, and datedHits rather than from current visibility alone\",\"PUC path tie-breaks are valid only after the correct side has been fixed and the route has been traced under that side's rules\"],\"freeze\":{\"historical_window\":\"the six named substances as objectively existing chemicals, using their ChemExpo chemical pages, PUC category paths, historical keyword families, and keyword-hit evidence as relatively stable classification signals\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only consider the six specified substances, and first compute contactHits, sourceHits, and datedHits on the chemical page.\",\"prioritySide must be determined by these historical signals first, then select the most representative current use category along the corresponding direction.\",\"The current route selection must continue drilling down according to the given kind priority and the same-level smaller PUC ID rule.\"],\"exclusion_conditions\":[\"Exclude results that ignore historical signals and directly select the path with the maximum currently visible Products on the chemical page.\",\"Exclude results that start PUC route selection without first determining the contact/source direction.\",\"Exclude results where same-level tie-breaks do not follow the smaller PUC ID rule.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"DTXSID\",\"contactHits\",\"sourceHits\",\"datedHits\",\"earliest\",\"latest\",\"prioritySide\",\"PUCkind\",\"generalPUCID\",\"terminalPUCID\",\"level\",\"Products\",\"PUCDocuments\",\"PUCCuratedChemicals\"],\"dated_hits\":\"count only the exact dated keyword strings defined in the source rubric\",\"date_format\":\"YYYY-MM; if datedHits is 0, earliest and latest are both `NA`\",\"prioritySide\":\"emit `contact` when contactHits > sourceHits; otherwise emit `source`\",\"kind\":\"the PUCkind field uses the canonical labels Article, Formulation, or Occupation\",\"level\":\"the level field uses the canonical labels general, family, or type\",\"products_source\":\"Products comes from the selected terminal chemical-detail node\",\"terminal_statistics\":\"PUCDocuments and PUCCuratedChemicals come from the selected terminal PUC detail page Additional Statistics block\",\"sorting_or_selection\":{\"primary\":\"datedHits descending\",\"secondary\":\"Products descending\",\"tertiary\":\"DTXSID ascending\"}}}","all_involved_urls":"null"} +{"task_id":"comptox_012-g","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I want to first screen for Formulation categories with many products in ChemExpo, and then from each category pick one specific product type that carries a child or aerosol label and is most worth prioritizing. Specifically, I am looking for a set of results: for each Formulation category with a total product count of at least 15,000, find one optimal specific product type. This target type must belong to the first family under that category's default display order that meets the following conditions: the family has a total product count of at least 3,000 and no assumed attributes, and it must have product types whose allowed attributes include 'aerosol' and 'child', with those types themselves having no assumed attributes. Then, among all qualifying 'aerosol' and 'child' types under that family, select the one with the highest product share (type product count divided by family cumulative product count). In case of a tie in share, prioritize in order: higher Product Count, more Curated Chemicals, or smaller PUC ID, until a single winner is determined. Finally, retain one final result: prefer the specific product type with the higher product share; if shares are equal, compare Product Count, Curated Chemicals, and PUC ID in that order, retaining the type with the higher count, more chemicals, or smaller ID, until a single final type is obtained.","start_url":"https://comptox.epa.gov/chemexpo/visualizations/","output_format":"Finally, output results sorted by final share descending, in the format: |||||. Join results with commas and no spaces. If no qualifying results exist, output NONE.","oracle_answer":"48|42|62|child|2160/3531|583,137|197|210|child|6934/16904|1135","metadata":"{\"State-Gated Retrieval\":[\"First, retain only Formulation categories with a total product count of at least 15,000.\",\"In each candidate family, both an aerosol-side type and a child-side type must be found: the family itself must have no assumed attributes and a total product count of at least 3,000; both types must also have no assumed attributes.\",\"All selections within a family and between the two sides must follow the specified tie-break rules: share, Product Count, Curated Chemicals, PUC ID.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"The Formulation summary yields the high-product candidate families whose total product count is at least 15,000.\",\"Within each family, lower-level type pages yield the aerosol and child candidates, their assumed/allowed attributes, product counts, shares, and curated-chemical counts.\",\"Final rows are produced only after a family survives both aerosol and child branches and the winning type is selected by the layered share/product/chemical/PUC tie-break rules.\"],\"control_dependency\":[\"Both the aerosol and child branches within the same family must be fully checked before that family can be retained.\",\"If one side is missing, the workflow must reject the family and continue to the next sibling family rather than stop at the first partial hit.\",\"The final winner can be selected only after both sides have been independently optimized within the family and then compared against each other.\"],\"freeze\":{\"historical_window\":\"ChemExpo Formulation families as objectively existing catalog families, especially large families with total product count >= 15,000, evaluated by family/type identity and product/chemical counts as relatively stable catalog descriptors.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"First, retain only Formulation categories with a total product count of at least 15,000.\",\"In each candidate family, both an aerosol-side type and a child-side type must be found: the family itself must have no assumed attributes and a total product count of at least 3,000; both types must also have no assumed attributes.\",\"All selections within a family and between the two sides must follow the specified tie-break rules: share, Product Count, Curated Chemicals, PUC ID.\"],\"exclusion_conditions\":[\"Exclude results that stop as soon as a usable type is found on either side, without requiring the same family to cover both aerosol and child sides.\",\"Exclude results that stop as soon as one side is missing instead of continuing to check sibling families at the same level.\",\"Exclude results that do not follow the specified layered tie-break rules to select the winning type within the family and as the final winner.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"generalPUCID\",\"familyPUCID\",\"typePUCID\",\"side\",\"share\",\"CuratedChemicals\"],\"dedup_key\":\"(generalPUCID, familyPUCID, typePUCID, side)\",\"side\":\"emit the lower-case branch label exactly as determined in the source workflow\",\"share\":\"canonical output uses the raw fraction `type Products / family Cumulative Products` rather than a decimal\",\"CuratedChemicals\":\"emit the integer count from the selected type-level node\",\"sorting_or_selection\":{\"primary\":\"share descending by numeric fraction value\",\"secondary\":\"type-level Products descending\",\"tertiary\":\"CuratedChemicals descending, then PUC IDs ascending as tie-breaks\"}}}","all_involved_urls":"null"} +{"task_id":"comptox_013-g","domain":"COMPTOX_CHEMEXPO","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"In ChemExpo, for the five substances Di(2-Ethylhexyl) Phthalate, Melamine, Phthalic Acid, Tris(2-Ethylhexyl) Phosphate, and Triphenyl Phosphates Tert-Butylated, check whether their historical labels are consistent with their current uses. The scope is limited to these five substances. For each substance, examine three groups of data. First, the material-contact score: check whether each of the following five label types appears, scoring 1 point per type: Indirect additives food contact (10/2018), Europe, Food contact items, Food contact items, Japan, any keyword containing Toys and children's products, and any keyword containing artificial_saliva or artificial_sweat. Second, the production-source score: check whether each of the following two label types appears, scoring 1 point per type: drinking_water, Europe, manufacturing, plastic_additive and Europe, plastic_additive. Third, dated-keyword hits: check only whether each of the following four keywords appears: Indirect additives food contact (10/2018), OEHHA Proposition 65 (3/2019), WA Children's Safe Product Act (4/2020), OEHHA Proposition 65 (1/2023); record the number of hits and the earliest and latest year-month among the hits. Then, if the material-contact score is strictly greater than the production-source score, treat it as leaning toward material contact and select a historically recommended category following the order Article → Formulation → Occupation; otherwise treat it as leaning toward production source and select following the order Occupation → Article → Formulation. After determining the category, follow the subcategory with the most products downward until no further subdivision is possible; if there is a tie at the same level, take the one with the smaller PUC ID. Separately, also find the current dominant category for this substance, ignoring historical clues, directly finding the path with the most products among all use categories, again following downward until no further subdivision is possible, breaking ties by smaller PUC ID. Finally, compare the two results: if the current dominant category is Article or Formulation and the historical clue also points to material contact, record ALIGNED; if the current dominant category is Occupation and the historical clue also points to production source, record ALIGNED; otherwise record MISALIGNED.","start_url":"https://comptox.epa.gov/chemexpo/","output_format":"Output MISALIGNED records first; within the same group, sort by dated hits descending; if hits are equal, sort by current dominant category product count descending. Format: |||||||||||||||||. Separate records with commas. If dated hits is 0, write NA for both earliest and latest.","oracle_answer":"DTXSID6020802|4|2|1|2018-10|2018-10|material|Article|Furniture and furnishings|Furniture and furnishings|general|15|Occupation|Raw materials|fireproof coatings|type|24|MISALIGNED,DTXSID8021484|3|1|1|2018-10|2018-10|material|Occupation|Laboratory supplies|Laboratory supplies|general|8|Occupation|Laboratory supplies|Laboratory supplies|general|8|MISALIGNED,DTXSID5020607|5|2|4|2018-10|2023-01|material|Article|Construction and building materials|flooring|family|1|Formulation|Home maintenance|paint|type|112|ALIGNED,DTXSID0021414|5|0|1|2018-10|2018-10|material|Article|Construction and building materials|Construction and building materials|general|3|Article|Construction and building materials|Construction and building materials|general|3|ALIGNED,DTXSID20872645|0|1|0|NA|NA|source|Occupation|Industrial products|hydraulic fluid|family|5|Occupation|Industrial products|hydraulic fluid|family|5|ALIGNED","metadata":"{\"State-Gated Retrieval\":[\"Work only on the five specified substances, and first compute materialHits, sourceHits, and datedHits from the keyword-set blocks.\",\"The historically recommended category must be derived independently from these historical signals; the current dominant category must be derived separately from the current use path.\",\"Finally, compare only whether the broad direction of the historically recommended category and the current dominant category match, and mark ALIGNED or MISALIGNED accordingly.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"each chemical page yields materialHits, sourceHits, datedHits, and the historical recommendation side implied by the keyword set\",\"an independent current PUC category path yields the current dominant category, path labels, and classification counts for the same chemical\",\"final rows are produced only after the historical recommendation and current dominant category are computed independently and then compared at the coarse side level\"],\"control_dependency\":[\"the historical recommendation must be determined from the keyword-set evidence rather than from the current largest category\",\"historical recommendation must be computed from the keyword-set evidence before alignment is judged\",\"ALIGNED / MISALIGNED status is valid only after the historical and current category directions have been derived independently and then compared\"],\"freeze\":{\"historical_window\":\"the five named substances as objectively existing chemicals, using their ChemExpo chemical pages, PUC category paths, and specified keyword-set evidence as relatively stable recommendation signals\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Work only on the five specified substances, and first compute materialHits, sourceHits, and datedHits from the keyword-set blocks.\",\"The historically recommended category must be derived independently from these historical signals; the current dominant category must be derived separately from the current use path.\",\"Finally, compare only whether the broad direction of the historically recommended category and the current dominant category match, and mark ALIGNED or MISALIGNED accordingly.\"],\"exclusion_conditions\":[\"Exclude results that only look at the current largest category and directly treat it as the historically recommended category.\",\"Exclude results that default to ALIGNED for all cases without independently deriving the historically recommended category.\",\"Exclude results that do not compute the historical and current paths separately but mix signals in the same route.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"DTXSID\",\"materialHits\",\"sourceHits\",\"datedHits\",\"earliest\",\"latest\",\"historySide\",\"recommendedKind\",\"recommendedGeneral\",\"recommendedTerminal\",\"recommendedLevel\",\"recommendedProducts\",\"currentKind\",\"currentGeneral\",\"currentTerminal\",\"currentLevel\",\"currentProducts\",\"status\"],\"dated_hits\":\"count only the exact dated keyword strings defined in the source rubric\",\"date_format\":\"YYYY-MM; if datedHits is 0, earliest and latest are both `NA`\",\"historySide\":\"emit the lower-case historical winner `material` or `source`\",\"recommended_fields\":\"these fields describe the historically suggested path\",\"current_fields\":\"these fields describe the current dominant path\",\"kind\":\"the kind fields use the canonical labels Article, Formulation, or Occupation\",\"level\":\"the level fields use the canonical labels general, family, or type\",\"status\":\"emit `ALIGNED` or `MISALIGNED` exactly\",\"sorting_or_selection\":{\"primary\":\"status with MISALIGNED before ALIGNED\",\"secondary\":\"datedHits descending\",\"tertiary\":\"currentProducts descending\",\"quaternary\":\"DTXSID ascending\"}}}","all_involved_urls":"null"} +{"task_id":"consumerfinance_008-g","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"For CFPB administrative enforcement actions filed between 2022-01-01 and 2024-12-31, produce a core-amount extraction report covering three product categories: Deposits, Furnishing, and Prepaid. For each category, identify the first action in the website’s default display order that satisfies all of the following: the action detail page provides both a Consent Order and a press release; the Products label corresponds exclusively and exactly to the target category; and the page explicitly states a consumer redress amount exceeding $5,000,000 along with a separate civil money penalty. After locating these three target actions, extract from each action’s Consent Order PDF the first occurrence of the consumer redress amount and the civil money penalty amount in the body text, along with their physical page numbers (PDF page 1 is p1).","start_url":"https://www.consumerfinance.gov/enforcement/actions/","output_format":"Output the results strictly in alphabetical order of the product category’s English name, using the format |||||p||p. Join entries with commas and no spaces. If no qualifying case is found for a category, output |NONE.","oracle_answer":"Deposits|Bank of America, N.A.|2023-CFPB-0006|2023-07-11|$80,400,000|p11|$60,000,000|p14,Furnishing|Hyundai Capital America|2022-CFPB-0005|2022-07-26|$13,200,000|p31|$6,000,000|p35,Prepaid|U.S. Bank National Association|2023-CFPB-0019|2023-12-19|$5,700,000|p22|$15,000,000|p26","metadata":"{\"State-Gated Retrieval\":[\"Consider only administrative enforcement actions on the CFPB Enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.\",\"For each of the three product categories (Deposits, Furnishing, Prepaid), search top-down in the current default order for the first action that simultaneously satisfies: the page provides a Consent Order and a Press release; the Products label corresponds one-to-one with the target category; and the action detail page explicitly states consumer redress > $5,000,000 and also includes a civil money penalty.\",\"Finally, extract from the correct Consent Order the first-occurrence amounts and page numbers for consumer redress and civil money penalty.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Enforcement-action list pages yield product-branch candidate actions in current default order.\",\"Each action detail page and linked consent-order PDF yield product singularity, document-stack presence, redress and civil-money-penalty amounts, and first-occurrence pages.\",\"Final rows are emitted only after identifying, for each product, the first action that survives detail-page and PDF validation.\"],\"control_dependency\":[\"List-level “has Consent Order + Press release” hits must be validated on the detail page for product singularity and money thresholds.\",\"Prepaid candidates force document-level disambiguation among Consent Order, Stipulation, and terminating-order PDFs.\",\"Per-product first-match selection must explicitly skip rejected candidates and validate downstream PDFs before it is finalized.\"],\"freeze\":{\"historical_window\":\"Administrative enforcement actions with Initial filing date from 2022-01-01 through 2024-12-31; current default case ordering and currently linked action documents.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Consider only administrative enforcement actions on the CFPB Enforcement actions page whose Initial filing date falls between 2022-01-01 and 2024-12-31.\",\"For each of the three product categories (Deposits, Furnishing, Prepaid), search top-down in the current default order for the first action that simultaneously satisfies: the page provides a Consent Order and a Press release; the Products label corresponds one-to-one with the target category; and the action detail page explicitly states consumer redress > $5,000,000 and also includes a civil money penalty.\",\"Finally, extract from the correct Consent Order the first-occurrence amounts and page numbers for consumer redress and civil money penalty.\"],\"exclusion_conditions\":[\"Exclude cases where Products is not a single target category, or where the case appears relevant only at the list level but fails validation on the detail page.\",\"Exclude cases that do not clearly satisfy redress > $5M and a separate civil money penalty.\",\"Exclude cases that mistakenly use a Stipulation or Order Terminating the Consent Order in place of the required Consent Order.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"Product\",\"Respondent\",\"Docket\",\"FilingDate\",\"RedressUSD\",\"RedressPage\",\"PenaltyUSD\",\"PenaltyPage\"],\"product_order\":\"alphabetical by Product name\",\"fallback_row\":\"if a product has no qualifying case, emit `|NONE`\",\"date_format\":\"FilingDate uses YYYY-MM-DD\",\"money_fields\":\"canonical output preserves the dollar sign and commas from the oracle, but equivalent comparison may ignore `$` and commas and compare the numeric USD amount\",\"page_fields\":\"page fields use the canonical `pN` form\",\"document_scope\":\"extract both money amounts from the Consent Order PDF only; do not substitute a stipulation, termination order, or other companion document\",\"selection_rule\":\"for each product, keep the first action in the default filtered order that fully satisfies every gate in the source rubric\"}}","all_involved_urls":"null"} +{"task_id":"consumerfinance_009-g","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I want to organize the annual household financial stability survey reports in CFPB Reports, whose latest version page links directly to the 2023 and 2022 editions. I am interested in topics that appeared in the 2022 edition but no longer appear in subsequent annual reports, excluding the topic specifically used to mark \"belongs to the same survey series.\" For each such topic, I need the following information: the earliest subsequent year in which it disappeared; the first report not belonging to this series among the results related to these topics from 2022 and earlier; the total number of related resources listed in that report, how many of them link back to the same survey series, how many of those linked reports have appendices with letter labels and at least three sections; and the title, publication date, and appendix letter range of the final selected report.","start_url":"https://www.consumerfinance.gov/data-research/research-reports/","output_format":"Output a single line per topic, sorted alphabetically by topic name: |||||||||","oracle_answer":"Saving|2023|Consumer Savings App Strategies and Savings Outcomes|2022-12-07|4|2|1|Emergency Savings and Financial Security: Insights from the Making Ends Meet Survey and Consumer Credit Panel|2022-03-23|A-D,Student loans|2023|Report of the CFPB Education Loan Ombudsman|2022-10-20|0|0|0|NONE|NONE|NONE","metadata":"{\"State-Gated Retrieval\":[\"First, identify the CFPB household financial well-being annual report series whose latest version links directly to the 2023 and 2022 editions.\",\"Using the 2022 edition as the baseline, retain only topics that appear in 2022 but are no longer retained in subsequent annual reports, and exclude the topic specifically marked as \\\"belongs to the same survey series.\\\"\",\"For each topic, find the earliest non-series pivot report from 2022 or earlier, then count its directly listed related resources, how many link back to the same survey series, how many qualify under the appendix rule, and the appendix span of the final qualifying report.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"current CFPB Reports pages yield the 2024 -> 2023 -> 2022 annual-survey chain and the 2022 topic baseline\",\"report detail pages and report-search results yield first-disappearance year, pivot report title/date, related-resource counts, and links back to the annual-survey series\",\"final rows are produced only after separating the first jump target from later return-to-series counting\"],\"control_dependency\":[\"requiring the pivot report itself to link back to the same survey series incorrectly rules out valid topic rows\",\"title extraction must use the pivot detail page rather than search-result snippets\",\"related-resource expansion must continue even when the pivot report itself does not link back to the same survey series\"],\"freeze\":{\"historical_window\":\"currently linked 2024, 2023, and 2022 CFPB household financial well-being annual reports; topic disappearance is judged over that three-year chain, and pivot-report search is restricted to 2022-and-earlier reports\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"First, identify the CFPB household financial well-being annual report series whose latest version links directly to the 2023 and 2022 editions.\",\"Using the 2022 edition as the baseline, retain only topics that appear in 2022 but are no longer retained in subsequent annual reports, and exclude the topic specifically marked as \\\"belongs to the same survey series.\\\"\",\"For each topic, find the earliest non-series pivot report from 2022 or earlier, then count its directly listed related resources, how many link back to the same survey series, how many qualify under the appendix rule, and the appendix span of the final qualifying report.\"],\"exclusion_conditions\":[\"Exclude topics that are still retained in subsequent annual reports.\",\"Exclude results that incorrectly treat \\\"the pivot report itself must link back to the same survey series\\\" as a hard condition for column 3.\",\"Exclude search results that directly belong to the same survey series or reports after 2022.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"topic\",\"first-missing-year\",\"pivot-report-or-NONE\",\"pivot-date-or-NONE\",\"direct-related-count\",\"same-series-count\",\"qualified-count\",\"representative-report-or-NONE\",\"publication-date-or-NONE\",\"appendix-span-or-NONE\"],\"topic_order\":\"alphabetical by topic name\",\"date_format\":\"pivot-date and publication-date use YYYY-MM-DD when present\",\"appendix_span\":\"canonical span uses compact labels such as `A-D`\",\"none_rule\":\"if qualified-count is 0, representative-report, publication-date, and appendix-span are all `NONE`\"}}","all_involved_urls":"null"} +{"task_id":"consumerfinance_010-g","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I want to clearly organize the two waves of the Debt Collection Rule issued by the CFPB in 2020, including their respective proposal sources, delayed-effective-date arrangements, final effective dates, and the accompanying quick-reference PDF information on the implementation page. Specifically, I need the following: the exact issue date of each Final Rule; the originating proposed rule source and name, and the public comment deadline; whether the 2021 delayed-effective-date proposed rule applies to this batch of final rules, its public comment deadline, and the actual effective date that ultimately took effect; the quick-reference PDF file name on the official implementation page, and the first subheading in the body (excluding introductory or background paragraphs).","start_url":"https://www.consumerfinance.gov/rules-policy/final-rules/","output_format":"Output the two waves as a single-line string sorted by final-rule issue date from earliest to latest, identifying each wave by its final rule issue month (YYYY-MM):\n||||||||","oracle_answer":"2020-10|2020-10-30|2019-05-07 main|2019-09-18|YES|2021-05-19|2021-11-30|Executive summary of the October 2020 final rule|Coverage and Definitions,2020-12|2020-12-18|2019-05-07 main+2020-02-21 supplemental|2019-09-18+2020-08-04|YES|2021-05-19|2021-11-30|Executive summary of the December 2020 final rule|Validation Information Requirements and Disclosures","metadata":"{\"State-Gated Retrieval\":[\"The two 2020 Debt Collection Practices (Regulation F) final rules that share the same name must be processed separately, not merged into one.\",\"For each wave, independently confirm: the issue date, the corresponding proposal chain and public comment deadlines, whether the 2021 delayed-effective-date proposed rule covers it and its comment deadline, the final effective date, the corresponding implementation quick-reference PDF, and the first subheading in that PDF after skipping the introduction.\",\"The detail page, proposal chain, and summary PDF for the October wave and the December wave must each be verified independently.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"final-rules index pages and rule-development pages yield the two 2020 Regulation F final-rule waves and their proposal branches\",\"each final-rule detail page, delayed-effective-date proposal page, and implementation quick-reference PDF yields the wave-specific dates, linked proposals, comment deadlines, and first summary heading\",\"final rows are produced only after the October and December waves are traced separately end to end\"],\"control_dependency\":[\"two same-title final rules force correction from name-based collapsing to issue-date branching\",\"proposal-chain validation must be done per wave; otherwise the later December chain contaminates the October row\",\"implementation PDFs must be matched back to the correct wave rather than accepting the latest quick-reference page\"],\"freeze\":{\"historical_window\":\"the 2020-10 and 2020-12 Debt Collection Rule final-rule waves, their linked 2020 proposal pages, the 2021 delayed-effective-date proposal, and the current implementation-page quick-reference PDFs\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"The two 2020 Debt Collection Practices (Regulation F) final rules that share the same name must be processed separately, not merged into one.\",\"For each wave, independently confirm: the issue date, the corresponding proposal chain and public comment deadlines, whether the 2021 delayed-effective-date proposed rule covers it and its comment deadline, the final effective date, the corresponding implementation quick-reference PDF, and the first subheading in that PDF after skipping the introduction.\",\"The detail page, proposal chain, and summary PDF for the October wave and the December wave must each be verified independently.\"],\"exclusion_conditions\":[\"Exclude results that merge the two identically named 2020 final rules into one.\",\"Exclude results that project the December wave's proposal chain or executive-summary heading onto the October wave.\",\"Exclude results that are not independently verified against each wave's own final-rule detail page and corresponding PDF.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"wave\",\"final-rule-date\",\"proposal-chain\",\"proposal-comment-closes\",\"delay-proposal-applied\",\"delay-proposal-comments-close\",\"controlling-effective-date\",\"quick-reference-pdf\",\"summary-heading\"],\"wave\":\"wave is the final-rule issue month in YYYY-MM\",\"date_format\":\"all standalone date fields use YYYY-MM-DD\",\"proposal_chain\":\"canonical chain joins proposal milestones with `+`, using pieces such as `2019-05-07 main` or `2020-02-21 supplemental` in chronological order\",\"proposal_comment_closes\":\"join multiple comment-close dates with `+` in the same order as proposal_chain\",\"delay_proposal_applied\":\"emit `YES` when a delay proposal is part of the chain; otherwise emit `NO`\",\"quick_reference_pdf\":\"use the displayed quick-reference PDF title, not the filename\",\"summary_heading\":\"use the first substantive heading from the final-rule PDF\",\"sorting_or_selection\":\"final-rule-date ascending\"}}","all_involved_urls":"null"} +{"task_id":"consumerfinance_011-g","domain":"CFPB_REPORTS","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"On the CFPB enforcement actions page, find the most recent 2024 administrative enforcement action that has since been terminated, separately for Credit Cards and Deposits, and align the termination order with the corresponding clause information in the original Consent Order. Specifically, identify one action for each of the two Products labels: Credit Cards and Deposits. The candidate pool is limited to administrative enforcement actions under Enforcement actions with an Initial filing date between 2024-01-01 and 2024-12-31. For each product label, select the action with the latest Initial filing date among those meeting all of the following conditions (if tied, pick the one with the smaller docket number): Initial filing date between 2024-01-01 and 2024-12-31; case status changed to Expired, Terminated, or Dismissed; the document set includes a Consent Order, a Stipulation, an Order Terminating the Consent Order, and a press release; and the Products label currently maps uniquely to the target product. For each selected action, extract the following from its Order Terminating the Consent Order: TerminationDate (the termination date); TerminationAuthority (the exact text of the termination authority at its first occurrence); TermAuthorityPage (the PDF physical page number where this text first appears). Additionally, find the first explicit reference to a paragraph number of the original Consent Order within the termination order text; if it reads \"Paragraphs X and Y\", take only X. Then go back to the original Consent Order and find the section heading that contains that paragraph.","start_url":"https://www.consumerfinance.gov/enforcement/actions/","output_format":"Finally, output a single-line string in alphabetical order by product name: ||||||p||. If a product has no qualifying case, output: |NONE","oracle_answer":"Credit Cards|Apple Inc.|2024-CFPB-0012|2024-10-23|2025-09-22|12 U.S.C. § 5563(b)(3)|p1|83|ADMINISTRATIVE PROVISIONS,Deposits|Navy Federal Credit Union|2024-CFPB-0014|2024-11-07|2025-07-01|12 U.S.C. § 5563(b)(3)|p1|106|ADMINISTRATIVE PROVISIONS","metadata":"{\"State-Gated Retrieval\":[\"Consider only administrative enforcement actions with an Initial filing date in 2024, and search for cases separately under Credit Cards and Deposits.\",\"The case must have a status of Expired, Terminated, or Dismissed, and the page must simultaneously provide a Consent Order, Stipulation, Order Terminating the Consent Order, and Press release, with the Products label mapping one-to-one to the target category.\",\"For each category, retain only the most recent qualifying case determined by Initial filing date, and compile the corresponding clause information from the termination order and the original Consent Order.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Enforcement-action list pages yield 2024 candidate actions by product branch.\",\"Each action detail page and linked Consent Order, Stipulation, Order Terminating the Consent Order, and Press release documents yield status, initial filing date, single-product validity, and clause references.\",\"Final rows are selected only after per-product comparison on Initial filing date and document-stack validation.\"],\"control_dependency\":[\"\\\"Latest\\\" must be determined by Initial filing date rather than termination date.\",\"Product filters on the list page are insufficient until the action detail page confirms a single matching product.\",\"Clause extraction in the terminating order must stay aligned with the original Consent Order rather than a superficially similar section.\"],\"freeze\":{\"historical_window\":\"Administrative enforcement actions with Initial filing date from 2024-01-01 through 2024-12-31; current action status and currently linked Consent Order, Stipulation, terminating-order, and Press release documents.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Consider only administrative enforcement actions with an Initial filing date in 2024, and search for cases separately under Credit Cards and Deposits.\",\"The case must have a status of Expired, Terminated, or Dismissed, and the page must simultaneously provide a Consent Order, Stipulation, Order Terminating the Consent Order, and Press release, with the Products label mapping one-to-one to the target category.\",\"For each category, retain only the most recent qualifying case determined by Initial filing date, and compile the corresponding clause information from the termination order and the original Consent Order.\"],\"exclusion_conditions\":[\"Exclude results that use termination date instead of Initial filing date to determine \\\"latest\\\".\",\"Exclude cases with an incomplete document stack or where Products does not map to a single target category.\",\"Exclude cases where the required clause correspondence between the terminating order and the original Consent Order cannot be established.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"Product\",\"Respondent\",\"Docket\",\"InitialFilingDate\",\"TerminationDate\",\"TerminationAuthority\",\"TermAuthorityPage\",\"ReferencedParagraph\",\"ConsentSectionHeading\"],\"product_order\":\"Alphabetical by Product name\",\"fallback_row\":\"If a product has no qualifying case, emit `|NONE`\",\"date_format\":\"InitialFilingDate and TerminationDate use YYYY-MM-DD\",\"termination_authority\":\"Use the canonical statute string extracted from the termination order\",\"page_fields\":\"TermAuthorityPage uses the canonical `pN` form\",\"ReferencedParagraph\":\"Emit the paragraph number as a plain numeric string\",\"ConsentSectionHeading\":\"Emit the uppercase heading of the consent-order section containing the referenced paragraph\"}}","all_involved_urls":"null"} +{"task_id":"consumerfinance_012-g","domain":"CFPB_COMPLAINT_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am preparing an internal outreach memo on historical complaint clusters and want to track a specific set of complaints: in the CFPB Complaint Database, identify complaints under the current product bucket covering credit reporting and other personal consumer reports, received between 2018-01-01 and 2021-12-31, tagged as Servicemember, with a public narrative, and whose text explicitly mentions medical bills or doctors. Please provide two representative complaint clusters: the first is the peak month of this cohort; the second is the latest month in this cohort whose complaint count is still at least half of the peak count. For each cluster, report the total complaint count for that month, the state with the highest complaint count in that month and its count, the company with the highest complaint count in that state and month and its count, and the earliest complaint received by that company in that state and month, including its ID, date, Issue, and Sub-issue. Output a single line with Peak first and LatestHalfPeak second, using the format: ||||||||||.","start_url":"https://www.consumerfinance.gov/data-research/consumer-complaints/","output_format":"Output a single line with Peak first and LatestHalfPeak second, using the format: ||||||||||. Join the Peak and LatestHalfPeak clusters with a comma. For ties: months are ordered chronologically; states are ordered by state abbreviation alphabetically ascending, taking the first; companies are ordered by company name alphabetically ascending, taking the first; for the earliest complaint, if multiple complaints share the same date, take the one with the smallest Complaint ID.","oracle_answer":"Peak|2018-02|46|CA|28|TRANSUNION INTERMEDIATE HOLDINGS, INC.|9|2806154|2018-02-07|Improper use of your report|Reporting company used your report improperly,LatestHalfPeak|2021-11|23|CA|12|EQUIFAX, INC.|3|4928768|2021-11-19|Problem with a credit reporting company's investigation into an existing problem|Their investigation did not fix an error on your report","metadata":"{\"State-Gated Retrieval\":[\"Only consider complaints under the current product bucket for credit reporting / other personal consumer reports, received from 2018-01-01 to 2021-12-31, tagged as Servicemember, with a public narrative, and whose text explicitly mentions medical bills or doctors.\",\"The first cluster must be the peak month of this cohort; the second cluster must be the latest month in this cohort whose complaint count is at least half of the peak count.\",\"For each cluster, recompute the top company within the corresponding month-state subset, then locate the earliest complaint received by that company in that state and month.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"current complaint-form taxonomy yields the product bucket that contains credit reporting / other personal consumer reports\",\"filtered complaint records yield month counts, month-state subsets, top companies, and earliest complaint details inside each chosen subset\",\"final rows are produced only after peak month and latest-half-peak month are determined, and each downstream aggregate is computed inside its narrower month-state cohort\"],\"control_dependency\":[\"the latest month must be defined as the latest month whose count is at least ceil(PeakCount / 2)\",\"overall top-company counts cannot be projected into a month-state subset without recomputation\",\"earliest complaint selection is only valid after the month, state, and company filters are all frozen\"],\"freeze\":{\"historical_window\":\"Complaint Database records received from 2018-01-01 through 2021-12-31 under the current product-bucket mapping for the credit-reporting / other personal consumer reports family; Servicemember + public narrative + medical bills/doctors text cohort\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only consider complaints under the current product bucket for credit reporting / other personal consumer reports, received from 2018-01-01 to 2021-12-31, tagged as Servicemember, with a public narrative, and whose text explicitly mentions medical bills or doctors.\",\"The first cluster must be the peak month of this cohort; the second cluster must be the latest month in this cohort whose complaint count is at least half of the peak count.\",\"For each cluster, recompute the top company within the corresponding month-state subset, then locate the earliest complaint received by that company in that state and month.\"],\"exclusion_conditions\":[\"Exclude results that directly treat the latest month with any complaints as the second cluster.\",\"Exclude results that first find an overall top company in the full cohort and then project it onto a month-state subset.\",\"Exclude results that do not first derive the half-peak threshold from PeakCount.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"Cluster\",\"Month\",\"MonthComplaints\",\"TopState\",\"StateComplaints\",\"TopCompany\",\"CompanyComplaints\",\"EarliestComplaintID\",\"EarliestDate\",\"Issue\",\"SubIssue\"],\"cluster_order\":[\"Peak\",\"LatestHalfPeak\"],\"date_format\":{\"Month\":\"YYYY-MM\",\"EarliestDate\":\"YYYY-MM-DD\"},\"TopState\":\"use the uppercase two-letter state abbreviation\",\"TopCompany\":\"use the company display name as shown in the source data\",\"tie_breaks\":\"for tied months use chronological order; for tied states use state-code alphabetical order; for tied companies use company-name alphabetical order; for the earliest complaint use EarliestDate ascending then Complaint ID ascending\",\"SubIssue\":\"emit `NONE` when the complaint row has no sub-issue value\"}}","all_involved_urls":"null"} +{"task_id":"consumerfinance_013-g","domain":"CFPB_COMPLAINT_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am collecting data for an internal crypto-complaint concentration memo and need to identify two representative complaint-month clusters from the CFPB complaint database and extract their core data records.\nThe data must come from a specific cohort: the product category must correspond to the current form’s bucket for Virtual currency, with the sub-product explicitly set to Virtual currency; the time window is strictly 2019-08-26 through 2022-08-26.\nWithin this cohort, the two characteristic months to identify are:\n• Original peak month (AllCompanies): the month with the absolute highest complaint volume in the cohort without removing any company.\n• Residual peak month (ResidualAfterTop2): after identifying the two companies with the highest complaint volume in the original peak month and completely removing all records of those two companies from the entire three-year analysis period, the month with the highest complaint volume that emerges from the remaining data.\nFor these two specific months, I need detailed attributes: total complaints for that month, the names of the two removed companies and their combined complaint contribution in the original peak month, the state with the highest complaint volume in that month and its volume, and the earliest complaint detail (including ID, date, Issue, and Sub-issue) for the most complained-about company within that state and month.\nPlease confirm the identity of these two months and output one formatted string per month with no spaces, in the order AllCompanies first, ResidualAfterTop2 second. The field sequence per row is strictly: ||||||||||||\nSpecial notes:\n• The field must be filled with AllCompanies or ResidualAfterTop2 accordingly.\n• ExcludedTop2Companies and ExcludedTop2PeakMonthComplaints in both rows refer to the two companies identified from the original peak month and their combined complaint volume at that time.\n• The four Earliest-related fields must correspond to the earliest complaint record for the top company in that state and month.\n• To ensure a unique answer: output the two records in the order AllCompanies, ResidualAfterTop2; list ExcludedTop2Companies in descending order of their complaint volume in the original peak month, breaking ties alphabetically by field value; if the earliest complaint date is tied, take the one with the smallest Complaint ID.","start_url":"https://www.consumerfinance.gov/data-research/consumer-complaints/","output_format":"Output one formatted string per row with no spaces, in the order AllCompanies first, ResidualAfterTop2 second. The field sequence per row is strictly: ||||||||||||.","oracle_answer":"AllCompanies|2021-05|336|Coinbase, Inc.+BAM Management US Holdings Inc.|226|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,ResidualAfterTop2|2020-06|180|Coinbase, Inc.+BAM Management US Holdings Inc.|226|OH|28|PNC Bank N.A.|22|3687376|2020-06-07|Other transaction problem|NONE","metadata":"{\"State-Gated Retrieval\":[\"Only consider Complaint Database records under the current product bucket for Virtual currency, with sub-product Virtual currency, and received between 2019-08-26 and 2022-08-26.\",\"First determine the AllCompanies original peak month, then identify the top two companies by complaint volume in that peak month.\",\"These two companies must be completely removed from the entire three-year cohort, then recompute the residual peak month and all downstream fields based on the remaining cohort.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"current complaint-form taxonomy yields the product bucket for Virtual currency\",\"complaint records within the fixed three-year cohort yield the all-company peak month, per-month top companies, and residual-cohort recomputations after company removal\",\"final rows are produced only after the top-2 companies from the original peak month are removed from the full cohort and downstream aggregates are computed on the resulting cohort\"],\"control_dependency\":[\"peak-month top companies must be removed from the entire cohort, not only from the original peak month\",\"residual peak detection must be computed from the rewritten cohort rather than by local patching of the original month\",\"downstream state / company / earliest-complaint fields are valid only after the global company-removal step is locked\"],\"freeze\":{\"historical_window\":\"Complaint Database records received from 2019-08-26 through 2022-08-26 under the current product-bucket mapping for Virtual currency\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only consider Complaint Database records under the current product bucket for Virtual currency, with sub-product Virtual currency, and received between 2019-08-26 and 2022-08-26.\",\"First determine the AllCompanies original peak month, then identify the top two companies by complaint volume in that peak month.\",\"These two companies must be completely removed from the entire three-year cohort, then recompute the residual peak month and all downstream fields based on the remaining cohort.\"],\"exclusion_conditions\":[\"Exclude results that only locally delete the top-2 company records from the original peak month.\",\"Exclude results that do not reapply the top-2 company set to the entire cohort before recomputing the residual peak.\",\"Exclude downstream state, company, or earliest-complaint fields based on a cohort that has not been recomputed after removal.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"Cluster\",\"Month\",\"MonthComplaints\",\"ExcludedTop2Companies\",\"ExcludedTop2PeakMonthComplaints\",\"TopState\",\"StateComplaints\",\"TopCompany\",\"CompanyComplaints\",\"EarliestComplaintID\",\"EarliestDate\",\"Issue\",\"SubIssue\"],\"cluster_order\":[\"AllCompanies\",\"ResidualAfterTop2\"],\"date_format\":{\"Month\":\"YYYY-MM\",\"EarliestDate\":\"YYYY-MM-DD\"},\"ExcludedTop2Companies\":\"join the two excluded company names with `+` in source-peak complaint-count descending order, breaking ties alphabetically\",\"TopState\":\"use the uppercase two-letter state abbreviation\",\"TopCompany\":\"use the company display name as shown in the source data\",\"tie_breaks\":\"for the earliest complaint use EarliestDate ascending then Complaint ID ascending\",\"SubIssue\":\"emit `NONE` when the complaint row has no sub-issue value\"}}","all_involved_urls":"null"} +{"task_id":"consumerfinance_014-g","domain":"CFPB_COMPLAINT_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"I am writing an internal crypto-complaint sensitivity waterfall memo and need to extract four characteristic months (Clusters) at different filtering stages from the CFPB complaint database, along with their core data.\n\nThe underlying complaint cohort has clear boundaries: time is strictly limited to between 2020-01-01 and 2022-08-26, and it includes only complaint records classified under the \"Virtual currency\" subcategory within the current product taxonomy.\n\nBased on this underlying cohort, I need to identify four characteristic peak months representing different successive exclusion stages:\n• BaselinePeak: The absolute peak month with the highest total complaint volume in the initial complaint pool.\n• AfterDominantPublicResponse: After globally removing all complaints related to the dominant Company public response from the BaselinePeak month, the new peak month in the remaining data pool.\n• AfterDominantPublicResponseAndIssue: After further globally removing all complaints related to the dominant Issue from the second-round peak month, the third-round peak month formed from the remaining data.\n• AfterDominantPublicResponseIssueAndCompany: After finally globally removing all complaints related to the most complained-about Company from the third-round peak month, the final peak month that emerges from the remaining data.\n\nFor these four characteristic months, I need their data under each respective filtering state: total complaints for that month, the new exclusion dimension triggered in this round (NewExclusionType) and its specific value (NewExclusionValue), the frequency of that excluded value in its \"source peak month\", the state with the highest complaint volume in that month and its complaint count, the most complained-about company within that state and its complaint count, and the detailed information (ID, date, Issue, and Sub-issue) of the earliest complaint received by that top company in that state and characteristic month.\n\nPlease confirm the identity and data for these four characteristic months, and output four formatted strings with no spaces, strictly in the specific order: BaselinePeak, AfterDominantPublicResponse, AfterDominantPublicResponseAndIssue, AfterDominantPublicResponseIssueAndCompany. The field sequence for each row must be fixed as:\n|||||||||||||\n\nFor ties, always select in ascending lexicographic order; for the earliest complaint with the same date, select by ascending Complaint ID numerically. Normalize all empty values to NONE before sorting.","start_url":"https://www.consumerfinance.gov/data-research/consumer-complaints/","output_format":"Output four formatted strings with no spaces, strictly in the specific order: BaselinePeak, AfterDominantPublicResponse, AfterDominantPublicResponseAndIssue, AfterDominantPublicResponseIssueAndCompany. The field sequence for each row must be fixed as: |||||||||||||. For ties, always select in ascending lexicographic order; for the earliest complaint with the same date, select by ascending Complaint ID numerically. Normalize all empty values to NONE before sorting.","oracle_answer":"BaselinePeak|2021-05|336|NONE|NONE|0|CA|58|Coinbase, Inc.|21|4341451|2021-05-01|Money was not available when promised|NONE,AfterDominantPublicResponse|2022-07|31|Company public response|NONE|321|CA|6|BANK OF AMERICA, NATIONAL ASSOCIATION|4|5735227|2022-07-05|Other transaction problem|NONE,AfterDominantPublicResponseAndIssue|2021-10|13|Issue|Fraud or scam|26|TX|2|BANK OF AMERICA, NATIONAL ASSOCIATION|1|4821611|2021-10-18|Other transaction problem|NONE,AfterDominantPublicResponseIssueAndCompany|2021-06|8|Company|Foris DAX, Inc.|5|NC|3|TRUIST FINANCIAL CORPORATION|2|4462160|2021-06-15|Money was not available when promised|NONE","metadata":"{\"State-Gated Retrieval\":[\"Only consider Complaint Database records under the Virtual currency subcategory within the current product bucket, with a received date between 2020-01-01 and 2022-08-26.\",\"Sequentially determine the peak months for the four stages: BaselinePeak, AfterDominantPublicResponse, AfterDominantIssue, and AfterDominantCompany, as required by the task.\",\"Each identified dominant Company public response, dominant Issue, and dominant Company must be written back to the corresponding upstream residual cohort, globally removed, and then the next round of statistics must be recalculated.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"current complaint-form taxonomy yields the product bucket for Virtual currency\",\"complaint records yield the baseline peak plus the dominant Company public response, dominant Issue, and dominant Company at successive residual-peak states\",\"final rows are produced only after each dominant value is applied to the full upstream residual cohort and then used to determine the next peak\"],\"control_dependency\":[\"dominant values found in a peak month cannot be deleted only inside that month; each must be propagated to the full upstream cohort\",\"each new residual peak depends on the prior round's global rewrite, so local month-by-month deletion gives the wrong chain\",\"downstream counts and exemplar complaints are valid only after the full three-stage waterfall is executed\"],\"freeze\":{\"historical_window\":\"Complaint Database records received from 2020-01-01 through 2022-08-26 under the current product-bucket mapping for Virtual currency\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only consider Complaint Database records under the Virtual currency subcategory within the current product bucket, with a received date between 2020-01-01 and 2022-08-26.\",\"Sequentially determine the peak months for the four stages: BaselinePeak, AfterDominantPublicResponse, AfterDominantIssue, and AfterDominantCompany, as required by the task.\",\"Each identified dominant Company public response, dominant Issue, and dominant Company must be written back to the corresponding upstream residual cohort, globally removed, and then the next round of statistics must be recalculated.\"],\"exclusion_conditions\":[\"Exclude results that only delete records locally within the current peak month without writing back to the entire upstream cohort.\",\"Exclude results that do not re-find the next peak month on each round's residual cohort.\",\"Exclude intermediate or final fields based on downstream statistics that were not recalculated globally.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"Cluster\",\"Month\",\"MonthComplaints\",\"NewExclusionType\",\"NewExclusionValue\",\"NewExclusionCountInSourcePeak\",\"TopState\",\"StateComplaints\",\"TopCompany\",\"CompanyComplaints\",\"EarliestComplaintID\",\"EarliestDate\",\"Issue\",\"SubIssue\"],\"cluster_order\":[\"BaselinePeak\",\"AfterDominantPublicResponse\",\"AfterDominantPublicResponseAndIssue\",\"AfterDominantPublicResponseIssueAndCompany\"],\"date_format\":{\"Month\":\"YYYY-MM\",\"EarliestDate\":\"YYYY-MM-DD\"},\"NewExclusionType\":\"emit the canonical exclusion-type label from the source workflow; when no new exclusion is applied, emit `NONE`\",\"NewExclusionValue\":\"emit the canonical excluded value; when no value exists, emit `NONE`\",\"TopState\":\"use the uppercase two-letter state abbreviation\",\"TopCompany\":\"use the company display name as shown in the source data\",\"tie_breaks\":\"normalize empty values to `NONE` before sorting; for other ties use lexicographic order ascending, and for the earliest complaint use EarliestDate ascending then Complaint ID ascending\",\"SubIssue\":\"emit `NONE` when the complaint row has no sub-issue value\"}}","all_involved_urls":"null"} +{"task_id":"europemc_001-g","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":21,"instruction":"I want to consolidate into a single line the admission variables actually used by several prediction schemes in this 2020 COVID-19 mortality risk prediction paper, so that it is easy to see which variables overlap across schemes and which appear only in the comparator schemes.\nSpecifically, the target paper is a 2020 open-access review whose title contains all three terms \"prognosis model\", \"mortality risk\", and \"COVID-19\", and whose main text discusses Wuhan inpatients.\nThe variables to retain fall into two categories: (1) admission variables that appear in both the Random Forest and XGBoost variable importance rankings; (2) admission variables that do not appear in both rankings but are additional variables present in the CURB-65 or NEWS schemes used by the authors as comparators.\nFormat each variable as follows:\nvariable~RF_rank_or_0~XGB_rank_or_0~F~C~N~X\nwhere:\n\t•\tRF is the variable's rank in the Random Forest ranking, or 0 if absent;\n\t•\tXGB is the variable's rank in the XGBoost ranking used in the paper, or 0 if absent;\n\t•\tF, C, N, X indicate, respectively, whether the variable entered the authors' final logistic regression model, belongs to CURB-65, belongs to NEWS, and belongs to the XGBoost model used as a comparator in the paper.\nFinally, sort all variables alphabetically by variable name, join them with | into a single line; if the target paper cannot be found, output NONE.","start_url":"https://europepmc.org/advancesearch","output_format":"Format each variable as follows:\nvariable~RF_rank_or_0~XGB_rank_or_0~F~C~N~X\nwhere:\n\t•\tRF is the variable's rank in the Random Forest ranking, or 0 if absent;\n\t•\tXGB is the variable's rank in the XGBoost ranking used in the paper, or 0 if absent;\n\t•\tF, C, N, X indicate, respectively, whether the variable entered the authors' final logistic regression model, belongs to CURB-65, belongs to NEWS, and belongs to the XGBoost model used as a comparator in the paper.\nFinally, sort all variables alphabetically by variable name, join them with | into a single line; if the target paper cannot be found, output NONE.","oracle_answer":"Age~4~2~1~1~0~0|Alanine aminotransferase~17~11~0~0~0~0|Aspartate transaminase~6~4~0~0~0~0|Blood urea nitrogen~5~7~0~1~0~0|Confusion~0~0~0~1~1~0|CRP~2~6~1~0~0~1|Creatinine~9~13~0~0~0~0|Diastolic pressure~16~17~0~1~0~0|Heart rate~15~14~0~0~1~0|LDH~1~1~1~0~0~1|Lymphocyte count~3~5~0~0~0~1|Monocytes~12~16~0~0~0~0|Neutrophil~7~3~0~0~0~0|Normal platelet~10~9~0~0~0~0|Oxygen inhalation~0~0~0~0~1~0|Respiratory rate~11~10~0~1~1~0|SPO2~0~0~0~0~1~0|Systolic pressure~13~12~0~1~1~0|Temperature~18~18~0~0~1~0|Total bilirubin~14~15~0~0~0~0|White blood cell~8~8~0~0~0~0","metadata":"{\"State-Gated Retrieval\":[\"First locate the target paper: a 2020 open-access review whose title contains all three terms \\\"prognosis model\\\", \\\"mortality risk\\\", and \\\"COVID-19\\\", and whose main text discusses Wuhan inpatients.\",\"Retain only two categories of variables: admission variables that appear in both the Random Forest and XGBoost rankings; or admission variables that, although not appearing in both rankings, belong to the CURB-65 or NEWS comparator schemes.\",\"For each variable, annotate the RF rank, XGB rank, and whether it belongs to the final logistic regression, CURB-65, NEWS, and the comparator XGBoost model as required, then output sorted alphabetically by variable name.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Europe PMC search results and the target open-access article yield the candidate Wuhan COVID mortality-risk review\",\"article tables and discussion sections yield RF/XGBoost rankings, final logistic-regression inclusion, and comparator-variable memberships for CURB-65 / NEWS / external XGBoost\",\"final rows are produced only after overlapping variables and comparator-only variables are merged into one normalized variable table\"],\"control_dependency\":[\"comparator-only variables must be captured from the discussion definitions rather than from Table 2 + Table 3 alone\",\"comparator membership must be read from the article's explicit scheme definitions rather than inferred from common clinical usage\",\"variable normalization must wait until RF/XGBoost overlap and comparator-only additions are both complete\"],\"freeze\":{\"historical_window\":\"the 2020 open-access COVID-19 mortality-risk review about Wuhan inpatients; variable inclusion and comparator definitions are taken from the article's current full-text tables and discussion\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"First locate the target paper: a 2020 open-access review whose title contains all three terms \\\"prognosis model\\\", \\\"mortality risk\\\", and \\\"COVID-19\\\", and whose main text discusses Wuhan inpatients.\",\"Retain only two categories of variables: admission variables that appear in both the Random Forest and XGBoost rankings; or admission variables that, although not appearing in both rankings, belong to the CURB-65 or NEWS comparator schemes.\",\"For each variable, annotate the RF rank, XGB rank, and whether it belongs to the final logistic regression, CURB-65, NEWS, and the comparator XGBoost model as required, then output sorted alphabetically by variable name.\"],\"exclusion_conditions\":[\"Exclude admission variables that appear in neither both RF and XGB rankings nor the CURB-65 / NEWS additional variables.\",\"Exclude results that stop at Table 2 + Table 3 without proceeding to the discussion to read the comparator definitions.\",\"Exclude results that infer comparator variables from common knowledge rather than verifying against the paper's explicit definitions.\"],\"normalization\":{\"field_separator\":\"~\",\"record_separator\":\"|\",\"schema\":[\"variable\",\"RF_rank_or_0\",\"XGB_rank_or_0\",\"F\",\"C\",\"N\",\"X\"],\"variable\":\"use the variable wording normalized in the article tables; keep `Systolic pressure` and `Diastolic pressure` as separate variables\",\"rank_fields\":\"RF_rank_or_0 and XGB_rank_or_0 are positive integer ranks when present, otherwise 0\",\"boolean_fields\":\"F, C, N, and X are emitted as 1 or 0 only\",\"sorting_or_selection\":\"variable name alphabetical ascending\",\"stop_condition\":[\"the shared variable set from Table 2 and Table 3 is fully resolved\",\"the comparator definitions for CURB-65, NEWS, and the comparison XGBoost model are fixed before the final line is emitted\"]}}","all_involved_urls":"null"} +{"task_id":"europemc_002-g","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":6,"instruction":"Track Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline review by ClinicalTrials.gov identifier, and check whether they persist in the 2022 and 2023 open-access reviews of the same series. Only include studies that were Phase 1 in the 2021 review and can still be found under the same ClinicalTrials.gov identifier in both the 2022 and 2023 reviews. Do not rely on drug names alone, as they may change. Output all qualifying studies as a single line in the format: NCT~2021 drug~2022 phase~2022 drug~2023 phase~2023 drug, sorted by NCT ascending and joined by |. If the three papers cannot be found, output NONE.","start_url":"https://europepmc.org/advancesearch","output_format":"Output all qualifying studies as a single line in the format: NCT~2021 drug~2022 phase~2022 drug~2023 phase~2023 drug, sorted by NCT ascending and joined by |. If no qualifying studies exist, output NONE.","oracle_answer":"NCT03277573~Salsalate~P1~Salsalate~P1~Salsalate|NCT03634007~AAVrh.10hAPOE2~P1~LX1001~P2~LX1001|NCT03748303~Allopregnanolone (Allo)~P1~Allopregnanolone~P1~Allopregnanolone|NCT04149860~Lu AF87908~P1~Lu AF87908~P1~Lu AF87908|NCT04451408~LY3372993~P1~LY3372993~P1~LY3372993|NCT04500847~Emtricitabine~P1~Emtricitabine~P1~Emtricitabine","metadata":"{\"State-Gated Retrieval\":[\"Only use Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline article as the baseline.\",\"Whether a study is retained in 2022 and 2023 must be determined by exact matching on the same ClinicalTrials.gov NCT identifier, not by drug name alone.\",\"Only retain studies that can be found under the same NCT in both 2022 and 2023, and output them sorted by NCT ascending.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the 2021, 2022, and 2023 pipeline reviews yield the 2021 Phase 1 baseline cohort and the later-year lookup tables\",\"article tables yield exact ClinicalTrials.gov NCT IDs, yearly phase labels, and yearly drug names for the same study\",\"final rows are produced only after 2021 baseline studies are re-identified in both later reviews by exact NCT matching\"],\"control_dependency\":[\"continuation must be matched by exact NCT rather than by drug name, because drug names drift across years\",\"2022 and 2023 lookups must use the fixed 2021 Phase 1 NCT set as the starting cohort rather than later-year table membership alone\",\"yearly phase/name fields are only valid after the same NCT is confirmed across all three reviews\"],\"freeze\":{\"historical_window\":\"the 2021, 2022, and 2023 open-access Alzheimer's disease drug development pipeline reviews; the baseline is the 2021 Phase 1 cohort and continuation is matched by exact ClinicalTrials.gov NCT\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only use Phase 1 studies from the 2021 Alzheimer's disease drug development pipeline article as the baseline.\",\"Whether a study is retained in 2022 and 2023 must be determined by exact matching on the same ClinicalTrials.gov NCT identifier, not by drug name alone.\",\"Only retain studies that can be found under the same NCT in both 2022 and 2023, and output them sorted by NCT ascending.\"],\"exclusion_conditions\":[\"Exclude results that are continued only by drug name without exact matching on the same ClinicalTrials.gov identifier.\",\"Exclude studies found only in 2022 or only in 2023, not continuously retained in both years.\",\"Exclude studies not in the 2021 baseline Phase 1 set.\"],\"normalization\":{\"field_separator\":\"~\",\"record_separator\":\"|\",\"schema\":[\"NCT\",\"agent_2021\",\"phase_2022\",\"agent_2022\",\"phase_2023\",\"agent_2023\"],\"NCT\":\"use the exact ClinicalTrials.gov identifier as the cross-year identity key\",\"phase_fields\":\"normalize phases to P1, P2, or P3; if the same NCT appears multiple times in a year, keep the highest phase for that year\",\"agent_fields\":\"keep the agent text as shown in each year-specific table\",\"sorting_or_selection\":\"NCT ascending\"}}","all_involved_urls":"null"} +{"task_id":"europemc_003-g","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"Identify the candidate molecules predicted in the 2023 \"Antibodies to Watch\" article to file their first marketing applications in 2022–2023, and determine which of them have actually received first approval or entered first regulatory review in the 2024 installment of the same series.\nSpecifically, the scope is limited to the open-access full texts of the 2023 and 2024 \"Antibodies to Watch\" articles in Europe PMC. Retain only those molecules that were listed in the 2023 article as **\"predicted to file first marketing applications in 2022–2023\"** and that, by the 2024 article, have either been approved or have entered first regulatory review.\nFor each qualifying molecule, output a record in the format:\nINN~2023_category~2023_prediction_label~2024_status~2024_indication~2024_region\nwhere:\n\t•\t2023_category is NC (non-cancer) or CA (cancer);\n\t•\t2024_status is A (first approval) or R (first regulatory review).\nFinally, sort records alphabetically by INN, join them with | into a single line, and output that line. If neither article can be found, output NONE.","start_url":"https://europepmc.org/advancesearch","output_format":"For each qualifying molecule, output: INN~2023_category~2023_prediction_label~2024_status~2024_indication~2024_region\nwhere:\n\t•\t2023_category is NC (non-cancer) or CA (cancer);\n\t•\t2024_status is A (first approval) or R (first regulatory review).\nSort records alphabetically by INN, join them with | into a single line, and output that line. If neither article can be found, output NONE.","oracle_answer":"Cosibelimab~CA~MAA,Q2 2023~R~Squamous cell carcinoma~US|Elranatamab~CA~2023~A~Multiple myeloma~US,EU,Switzerland,Brazil|Garadacimab~NC~BLA,2023~R~Hereditary angioedema~EU|Odronextamab~CA~BLA,H2 2022~R~Diffuse large B-cell lymphoma~US,EU|Pozelimab~NC~BLA,H2 2022~A~CHAPLE disease~US|Suciraslimab~NC~NDA,2023~R~Rheumatoid arthritis~China|Talquetamab~CA~2023–25~A~Multiple myeloma~US,EU,UK,Switzerland|Zolbetuximab~CA~BLA,2023~R~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China","metadata":"{\"State-Gated Retrieval\":[\"First, in the 2023 Antibodies to Watch article, identify all candidate molecules predicted to file first marketing applications in 2022–2023.\",\"Then, in the 2024 article of the same series, check each of these molecules and retain only those that have received first approval or entered first regulatory review.\",\"The 2024 status must distinguish A = first approval from R = first regulatory review, and the 2024 indication and region must be included.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the 2023 Antibodies to Watch article yields the forecast baseline of candidates expected to file in 2022-2023\",\"the 2024 article tables yield first-approval outcomes, first-regulatory-review outcomes, indications, and regions for the same INNs\",\"final rows are produced only after Table 1 approvals and Table 2 first-review candidates are merged back onto the 2023 forecast cohort\"],\"control_dependency\":[\"both 2024 Table 1 and Table 2 must be read so that first-review-but-not-yet-approved candidates are retained\",\"2024 status coding must distinguish approval from first regulatory review instead of collapsing both into a single positive match\",\"region and indication fields are valid only after the 2023 forecast cohort is reconciled against both 2024 tables\"],\"freeze\":{\"historical_window\":\"the 2023 and 2024 open-access Antibodies to Watch articles; baseline candidates come from the 2023 forecast set and 2024 outcomes come from current Table 1 plus Table 2\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"First, in the 2023 Antibodies to Watch article, identify all candidate molecules predicted to file first marketing applications in 2022–2023.\",\"Then, in the 2024 article of the same series, check each of these molecules and retain only those that have received first approval or entered first regulatory review.\",\"The 2024 status must distinguish A = first approval from R = first regulatory review, and the 2024 indication and region must be included.\"],\"exclusion_conditions\":[\"Exclude results that only check approvals in 2024 Table 1 without also consulting Table 2 for first-regulatory-review candidates.\",\"Exclude molecules not in the 2023 forecast baseline.\",\"Exclude candidates that in 2024 have neither received first approval nor entered first regulatory review.\"],\"normalization\":{\"field_separator\":\"~\",\"record_separator\":\"|\",\"schema\":[\"INN\",\"category_2023\",\"prediction_label_2023\",\"status_2024\",\"indication_2024\",\"region_2024\"],\"category_2023\":\"emit `NC` or `CA` exactly\",\"prediction_label_2023\":\"keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H2 2022`\",\"status_2024\":\"emit `A` for first approval and `R` for first regulatory review\",\"region_2024\":\"preserve the raw region string but remove spaces after commas, for example `US,EU`\",\"sorting_or_selection\":\"INN alphabetical ascending\"}}","all_involved_urls":"null"} +{"task_id":"europemc_004-g","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":9,"instruction":"I am evaluating the accuracy of annual antibody watchlist predictions. Based on the Europe PMC database, I need to identify a set of candidate antibodies (INNs) whose progress has clearly lagged behind, and extract their status changes over the three-year period.\nThese target antibodies are special because their dynamics are continuously recorded across three open-access full-text articles in the Antibodies to Watch series from 2022, 2023, and 2024. Specifically, they were originally listed as \"expected to be submitted for review soon\" in the 2022 article, but due to delays, they remained as candidates on the watchlist in the 2023 article. Screening should be done at the antibody-candidate level, not by exact name string matching. If the 2022 article uses a drug code, project name, or other identifiable name, and the 2023 or 2024 article explicitly provides its correspondence to a specific INN, it should be treated as the same candidate entity, and the confirmed INN should be used in the final output.\nFor these continuously delayed candidate antibodies, I need to determine their final status in the 2024 article: whether they finally received first approval, are in first regulatory review, remain on a subsequent watchlist, or have completely disappeared from the main 2024 article list.\nPlease help me identify this set of antibodies and output the extracted parameters as a single-line string joined by |, strictly sorted alphabetically by INN. If the three target articles cannot all be found in the database, output NONE. The internal field order for each antibody must be fixed as: INN~2022 category~2022 phase~2023 prediction label~2024 status~2024 phase or NA~2024 indication or NA~2024 region or NA. No extra spaces should be added around the delimiters in the output, but original spaces within fields should be preserved. Use CA/NC uniformly for 2022 category, P2/P3 for phase, and A/R/F/D for 2024 status, representing First approved, In first regulatory review, subsequent watchlist, and disappeared from the 2024 main article list, respectively.","start_url":"https://europepmc.org/advancesearch","output_format":"Output the extracted parameters as a single-line string joined by |, strictly sorted alphabetically by INN. If the three target articles cannot all be found in the database, output NONE. The internal field order for each antibody must be fixed as: INN~2022 category~2022 phase~2023 prediction label~2024 status~2024 phase or NA~2024 indication or NA~2024 region or NA. No extra spaces should be added around the delimiters in the output, but original spaces within fields should be preserved. Use CA/NC uniformly for 2022 category, P2/P3 for phase, and A/R/F/D for 2024 status, representing First approved, In first regulatory review, subsequent watchlist, and disappeared from the 2024 main article list, respectively.","oracle_answer":"Apamistamab-I-131~CA~P3~BLA,H1 2023~F~P3~Ablation of bone marrow prior to transplantation in AML patients~NA|Bentracimab~NC~P3~BLA,Q4 2022~F~P3~Reversal of the antiplatelet effects of ticagrelor~NA|Cosibelimab~CA~P3~MAA,Q2 2023~R~NA~Squamous cell carcinoma~US|Erfonrilimab~CA~P3~NDA~F~P3~Pancreatic ductal adenocarcinoma~NA|Odronextamab~CA~P2~BLA,H2 2022~R~NA~Diffuse large B-cell lymphoma~US,EU|Talquetamab~CA~P2~2023-25~A~NA~Multiple myeloma~US,EU,UK,Switzerland|Tiragolumab~CA~P3~2023~F~P3~NSCLC~NA|Zanidatamab~CA~P2~2023~D~NA~NA~NA|Zolbetuximab~CA~P3~BLA,2023~R~NA~HER2-negative gastric or gastroesophageal junction adenocarcinoma~US,EU,Japan,China","metadata":"{\"State-Gated Retrieval\":[\"Start with the 2022 Antibodies to Watch candidates listed as \\\"expected to be submitted for review soon\\\" as the baseline, but retain only those molecules that still remain as watchlist candidates in the 2023 same-series article.\",\"For these continuously delayed candidates, then determine their final status in the 2024 article: first approved, in first regulatory review, or completely absent from Tables 1-4.\",\"Name comparison must handle the Apamistamab naming drift; complete absence in 2024 must be explicitly encoded as D.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the 2022, 2023, and 2024 Antibodies to Watch articles yield the 2022 soon-to-file baseline, 2023 carry-over membership, and 2024 status tables\",\"article tables and full-text naming context yield name normalizations, 2024 table presence/absence, and final status labels for each carried-over INN\",\"final rows are produced only after 2022 candidates are filtered by 2023 carry-over status and then resolved against 2024 Tables 1-4 plus explicit absence\"],\"control_dependency\":[\"2022 candidates must first be filtered by 2023 carry-over status before they are matched against the 2024 tables\",\"Apamistamab naming drift forces explicit normalization before 2024 lookup\",\"complete 2024 absence must be emitted as D rather than treated as a lookup failure\"],\"freeze\":{\"historical_window\":\"the 2022, 2023, and 2024 open-access Antibodies to Watch articles; the 2022 baseline is filtered by 2023 carry-over status and then checked against 2024 Tables 1-4, with explicit absence retained as a status\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Start with the 2022 Antibodies to Watch candidates listed as \\\"expected to be submitted for review soon\\\" as the baseline, but retain only those molecules that still remain as watchlist candidates in the 2023 same-series article.\",\"For these continuously delayed candidates, then determine their final status in the 2024 article: first approved, in first regulatory review, or completely absent from Tables 1-4.\",\"Name comparison must handle the Apamistamab naming drift; complete absence in 2024 must be explicitly encoded as D.\"],\"exclusion_conditions\":[\"Exclude results that directly match the 2022 baseline against 2024 by literal string matching without first applying the 2023 carry-over filter.\",\"Exclude matching results that do not handle the Apamistamab naming drift.\",\"Exclude cases where complete absence in 2024 is treated as a lookup failure rather than a status that must be output.\"],\"normalization\":{\"field_separator\":\"~\",\"record_separator\":\"|\",\"schema\":[\"INN\",\"category_2022\",\"phase_2022\",\"prediction_label_2023\",\"status_2024\",\"phase_or_NA_2024\",\"indication_or_NA_2024\",\"region_or_NA_2024\"],\"category_2022\":\"emit `NC` or `CA` exactly\",\"phase_2022\":\"normalize stage labels such as `Phase 3` to `P3` and `Pivotal Phase 2` to `P2`\",\"prediction_label_2023\":\"keep the label content inside the parentheses and remove spaces after commas, for example `BLA,H1 2023`\",\"status_2024\":\"emit one of `A`, `R`, `F`, or `D` exactly\",\"conditional_fields_2024\":\"if status is A or R, phase_or_NA_2024 must be `NA` and region_or_NA_2024 must carry the raw region string; if status is F, region_or_NA_2024 is `NA` and phase_or_NA_2024 carries the normalized phase; if status is D, all three trailing 2024 fields are `NA`\",\"naming_exception\":\"preserve the fixed source exception around the Apamistamab-I-131 naming variant instead of over-normalizing the INN\",\"sorting_or_selection\":\"INN alphabetical ascending\"}}","all_involved_urls":"null"} +{"task_id":"europemc_005-g","domain":"EUROPEPMC_PMC","autonomy_type":"ordered table","oracle_output_cardinality":20,"instruction":"I am compiling a cross-platform summary of predictors for COVID-19 inpatient outcome trajectories. This task centers on a 2024 WHO global individual patient data validation paper and its three linked original model papers. In this 2024 validation paper, four prognostic models ultimately completed external validation in low- and middle-income country data. We need to identify which distinct admission variables each of these four models used in their actual evaluations.\nFor each admission variable identified, we need to determine its characteristics in actual use: first, its matching difficulty in the WHO platform baseline table, i.e., whether it can be matched directly under the same or a substantively equivalent name or must go through a fixed mapping; second, its source background, i.e., whether it belongs to the model with the strongest performance in validation, the model with calibration closest to ideal, or an original model that explicitly used dynamic data.\nTo ensure consistency, model abbreviations, performance attributions, dynamic-data attributes, and variable conflicts shall be based on verifiable model descriptions, summary performance results, method explanations, and field definitions in the target literature; any variable naming or mapping differences shall be marked with a conservative correspondence that maintains cross-model interpretability.\nIf all four articles (the one validation paper and the three original model papers) can be found in the database, please organize all extracted variable information and output it as a single string with no spaces, joining records by | in strict alphabetical order of variable names (if the four articles cannot be found, output NONE).\nFormat requirement: each variable's internal information must be written in the fixed format variable~category~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict. Boolean states use 1 for yes and 0 for no; WHO baseline table matching uses E for a direct or substantively equivalent-name match and M for fixed mapping required.","start_url":"https://europepmc.org/advancesearch","output_format":"If all four articles (the one validation paper and the three original model papers) can be found in the database, organize all extracted variable information and output it as a single string with no spaces, joining records by | in strict alphabetical order of variable names; if the four articles cannot be found, output NONE. Each variable's internal information must be written in the fixed format variable~category~B~W~Zh~Zo~WHOfield~WHOx~TopAUC~BestCal~Dyn~Conflict. Boolean states use 1 for yes and 0 for no; WHO baseline table matching uses E for a direct or substantively equivalent-name match and M for fixed mapping required.","oracle_answer":"Age~DEM~1~1~1~1~Age~E~1~1~1~0|Cancer~COM~0~0~1~0~Cancer~E~1~0~0~0|Chronic kidney disease~COM~0~0~0~1~CKD~M~0~0~0~1|Chronic lung disease~COM~0~0~1~0~Pulmonary disease~M~1~0~0~0|Chronic renal disease~COM~0~0~1~0~CKD~M~1~0~0~1|Coronary heart disease~COM~0~1~0~0~CHD~M~0~0~0~1|Cough~SYM~0~0~1~0~Cough~E~1~0~0~0|Diabetes mellitus~COM~0~0~1~0~Diabetes~M~1~0~0~0|Diarrhea~SYM~0~0~1~0~Diarrhea~E~1~0~0~0|Dyspnea~SYM~0~0~1~0~Dyspnea~E~1~0~0~0|Fever~VIT~0~0~0~1~Body temperature~M~0~0~0~0|Heart disease~COM~0~0~1~0~CHD~M~1~0~0~1|Hypertension~COM~0~1~1~0~Hypertension~E~1~0~0~0|Immunocompromised status~COM~0~0~1~0~Immunosuppression~M~1~0~0~0|O2 saturation~VIT~1~0~0~0~Oxygen saturation~M~0~1~1~0|Respiratory rate~VIT~1~0~0~1~Respiratory rate~E~0~1~1~0|Sex~DEM~0~0~1~0~Men~M~1~0~0~0|Smoking~DEM~1~0~0~0~Smoking~E~0~1~1~1|Smoking status~DEM~0~0~0~1~Smoking~M~0~0~0~1|Systolic blood pressure~VIT~0~0~0~1~Systolic blood pressure~E~0~0~0~0","metadata":"{\"State-Gated Retrieval\":[\"First, in the 2024 WHO global individual patient data validation paper, identify the four prognostic models that successfully completed external validation in LMIC data, and trace back to the three corresponding original model papers.\",\"For each predictor, retain the original wording from WHO Table 1, and annotate its matching method in the WHO baseline table as E or M, and whether it comes from the TopAUC, BestCal, or Dyn model.\",\"When encountering a predictor that is conceptually merged on the WHO side, trace back to the original Wang/Zhou papers to split it apart before recalculating the relevant fields.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the 2024 WHO global validation paper yields the four externally validated models and the WHO-side predictor wording/mapping baseline\",\"the three original model papers yield model-specific predictor wordings, dynamic-data flags, and conflicts hidden by WHO-side conceptual merging\",\"final rows are produced only after WHO predictors are kept separate, traced back to the original papers, and then re-annotated for mapping and model provenance\"],\"control_dependency\":[\"conceptually merged WHO predictors must be split back out when the original Wang/Zhou papers expose distinct variables\",\"Table 2 mapping decisions are not valid until Table 1 wording and original-paper predictor sets are reconciled\",\"TopAUC / BestCal / Dyn flags must be determined after the predictor split is applied correctly\"],\"freeze\":{\"historical_window\":\"the 2024 WHO global IPD validation paper and the three linked original COVID prognosis-model papers, using their current open-access full texts and tables\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"First, in the 2024 WHO global individual patient data validation paper, identify the four prognostic models that successfully completed external validation in LMIC data, and trace back to the three corresponding original model papers.\",\"For each predictor, retain the original wording from WHO Table 1, and annotate its matching method in the WHO baseline table as E or M, and whether it comes from the TopAUC, BestCal, or Dyn model.\",\"When encountering a predictor that is conceptually merged on the WHO side, trace back to the original Wang/Zhou papers to split it apart before recalculating the relevant fields.\"],\"exclusion_conditions\":[\"Exclude results that directly merge conceptually similar predictors after WHO Table 1 without tracing back to the original papers for splitting.\",\"Exclude results that rely solely on WHO Table 2 for loose mapping without incorporating the original paper wording.\",\"Exclude results that fix TopAUC / BestCal / Dyn annotations before the predictor split correction is applied.\"],\"normalization\":{\"field_separator\":\"~\",\"record_separator\":\"|\",\"schema\":[\"variable\",\"category\",\"B\",\"W\",\"Zh\",\"Zo\",\"WHOfield\",\"WHOx\",\"TopAUC\",\"BestCal\",\"Dyn\",\"Conflict\"],\"variable_set\":\"the candidate variable set comes only from the WHO validation Table 1 and remains at the original 20 predictors\",\"conflict_groups\":\"do not pre-merge the three source conflict groups `Smoking`/`Smoking status`, `Chronic renal disease`/`Chronic kidney disease`, and `Coronary heart disease`/`Heart disease` before applying the conflict flag\",\"boolean_fields\":\"B, W, Zh, Zo, TopAUC, BestCal, Dyn, and Conflict are emitted as 1 or 0 only\",\"WHOx\":\"emit `E` for exact WHO matches or direct matches under a substantively equivalent name, `M` for the fixed mapped match, and `NA` when no WHO field matches\",\"sorting_or_selection\":\"variable name alphabetical ascending\"}}","all_involved_urls":"null"} +{"task_id":"genome_001-g","domain":"KEGG_BRITE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"From KEGG, identify immunosuppressants used for ulcerative colitis that have been approved in Japan by the end of June 2025 and carry clear cytochrome P450 (CYP) metabolism or inhibition evidence. For each qualifying drug, retain its Japanese therapeutic classification code, ATC code, corresponding target branch, and Japan first approval date. Output a single-line string sorted by Japan first approval date from earliest to latest, formatted as ||||; separate multiple entries with commas; if no qualifying items exist, output NONE.","start_url":"https://www.genome.jp/kegg/brite.html","output_format":"Output a single-line string sorted by Japan first approval date from earliest to latest, formatted as ||||; separate multiple entries with commas; if no qualifying items exist, output NONE.","oracle_answer":"D09783|3999|L04AF01|JAK1/JAK2/JAK3/TYK2|2013/3/25,D11048|3999|L04AF03|JAK1|2020/1/23,D10931|2399|L04AE05|S1PR1/S1PR4/S1PR5|2025/6/24","metadata":"{\"State-Gated Retrieval\":[\"Within the scope of KEGG immunosuppressants for ulcerative colitis, retain only those approved in Japan by 2025-06-30 and carrying clear CYP-related metabolism information or CYP inhibition evidence.\",\"Each candidate drug must be re-verified against the corrected UC drug list for Japanese therapeutic classification, ATC, target branch, CYP evidence, and Japan first approval date.\",\"Finally, output sorted by Japan first approval date from earliest to latest.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"KEGG disease H01466 and linked drug entries yield the ulcerative-colitis immunosuppressant candidate set\",\"each candidate drug entry yields Japanese class, ATC, target branch, CYP metabolism/inhibition evidence, and Japan approval date\",\"final rows are produced only after the full UC candidate set is determined and every candidate is checked against CYP evidence and PMDA timing\"],\"control_dependency\":[\"the candidate set must include Japanese class 3999 UC drugs when the disease page exposes them rather than being limited to 2399 alone\",\"target / CYP / PMDA validation must be applied across the full candidate set rather than only the old 2399 subset\",\"entries without explicit CYP evidence may be dropped only after the full candidate set has been established\"],\"freeze\":{\"historical_window\":\"KEGG ulcerative-colitis drug entries as objectively existing drug entities, using target, CYP, Japan-class, and related entry metadata as relatively stable annotations\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Within the scope of KEGG immunosuppressants for ulcerative colitis, retain only those approved in Japan by 2025-06-30 and carrying clear CYP-related metabolism information or CYP inhibition evidence.\",\"Each candidate drug must be re-verified against the corrected UC drug list for Japanese therapeutic classification, ATC, target branch, CYP evidence, and Japan first approval date.\",\"Finally, output sorted by Japan first approval date from earliest to latest.\"],\"exclusion_conditions\":[\"Exclude results that incorrectly lock the upstream scope to the 2399 digestive branch without falling back to the full UC drug list.\",\"Exclude entries without clear CYP-related metabolism information or CYP inhibition evidence.\",\"Exclude entries with a Japan approval date after 2025-06-30 or that are not within the KEGG UC immunosuppressant scope.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"DRUG_ID\",\"JP_class\",\"ATC\",\"Target_branch\",\"JP_date\"],\"dedup_key\":\"DRUG_ID\",\"JP_date\":\"use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value\",\"Target_branch\":\"emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`\",\"sorting_or_selection\":{\"primary\":\"JP_date ascending\",\"secondary\":\"DRUG_ID ascending\"}}}","all_involved_urls":"null"} +{"task_id":"genome_002-g","domain":"KEGG_GENOME","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"From the KEGG host–symbiont examples, identify animal endosymbiosis cases whose bacterial symbiont KEGG GENOME entry was already recorded by the end of 2005 and whose bacterial symbiont genome contains a clearly named extra replicon. Additionally, the names of these replicons must directly correspond to amino acid biosynthesis modules on the host–symbiont joint pathway map. For the surviving case(s), list all qualifying pathway–module–replicon combinations. Output a single-line string in the format |||||, sorted by pathway ID in ascending order, with entries separated by commas. If no qualifying items exist, output NONE. Use KEGG organism codes for species identifiers.","start_url":"https://www.genome.jp/kegg/genome/","output_format":"Output a single-line string in the format |||||, sorted by pathway ID in ascending order, with entries separated by commas. If no qualifying items exist, output NONE. Use KEGG organism codes for species identifiers.","oracle_answer":"api+buc|buc|00290|M00432|pLeu|2000,api+buc|buc|00400|M00023|pTrp|2000","metadata":"{\"State-Gated Retrieval\":[\"Retain only host–symbiont examples where the bacterial symbiont KEGG GENOME Created year is no later than 2005 and the genome carries a named extra replicon.\",\"The names of these replicons must directly correspond to amino acid biosynthesis modules on the host–symbiont joint pathway page.\",\"Finally, output all qualifying pathway–module–replicon records from the surviving case(s), sorted by pathway ID in ascending order.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"KEGG host–symbiont examples and symbiont genome pages yield the pre-2006 candidate pairs and named extra replicons\",\"Joint pathway maps, module pages, and genome annotations yield the pathway–module–replicon links attributable to the symbiont side\",\"Final rows are produced only after the surviving host–symbiont pair is validated against both replicon existence and module support on the joint pathway page\"],\"control_dependency\":[\"Only branches satisfying the named-plasmid requirement may be retained, so the bmy+wbm branch must be excluded when the wbm genome page fails that requirement\",\"Module retrieval must use the api+buc pathway state and the 00400 view, because that view is the one that actually exposes M00023\",\"Module support is valid only after symbiont-side evidence for both M00023 and M00432 is validated in the selected pathway state\"],\"freeze\":{\"historical_window\":\"KEGG host–symbiont examples as objectively existing biological entities, using joint pathway, module, and genome replicon annotations as relatively stable structural information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Retain only host–symbiont examples where the bacterial symbiont KEGG GENOME Created year is no later than 2005 and the genome carries a named extra replicon.\",\"The names of these replicons must directly correspond to amino acid biosynthesis modules on the host–symbiont joint pathway page.\",\"Finally, output all qualifying pathway–module–replicon records from the surviving case(s), sorted by pathway ID in ascending order.\"],\"exclusion_conditions\":[\"Exclude cases like bmy+wbm where the symbiont genome page does not satisfy the named-plasmid requirement.\",\"Exclude results that only follow pathway names along pages such as 00380 without returning to the joint pathway page to verify module evidence.\",\"Exclude records where the replicon–module relationship cannot be directly established on the joint pathway map.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema\":[\"group\",\"symbiont\",\"pathway\",\"module\",\"replicon\",\"created_year\"],\"group\":\"Use the canonical host–symbiont group label from the source workflow, such as `api+buc`\",\"symbiont\":\"Use the bare lowercase KEGG organism code\",\"pathway\":\"Emit the numeric KEGG pathway ID without a `map` prefix\",\"module\":\"Normalize the KEGG module identifier to the `Mxxxxx` form\",\"replicon\":\"Preserve the named extra replicon exactly as displayed in the source, such as `pLeu` or `pTrp`\",\"created_year\":\"Emit the four-digit created year\",\"sorting_or_selection\":\"Pathway numeric ascending\"}}","all_involved_urls":"null"} +{"task_id":"genome_004-g","domain":"KEGG_BRITE","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"I am compiling an ordered table of systemic drugs approved for plaque psoriasis in Japan. Include only active ingredients that were approved in Japan by the end of 2024, are used for systemic treatment of plaque psoriasis, and target the IL-17/IL-23 signaling axis. Exclude topical drugs and systemic drugs acting through other axes. Output multiple rows sorted by Japan first approval date from earliest to latest; for drugs approved on the same day, sort by DRUG_ID ascending. Each row format: ||||.","start_url":"https://www.kegg.jp/brite/br08301","output_format":"Output multiple rows sorted by Japan first approval date from earliest to latest; for drugs approved on the same day, sort by DRUG_ID ascending. Each row format: ||||.","oracle_answer":"D09967|Secukinumab|L04AC10|IL17A|2014/12/26\nD10061|Brodalumab|L04AC12|IL17RA|2016/7/4\nD10071|Ixekizumab|L04AC13|IL17A|2016/7/4\nD10438|Guselkumab|L04AC16|IL23A|2018/3/23\nD11052|Risankizumab|L04AC18|IL23A|2019/3/26\nD10400|Tildrakizumab|L04AC17|IL23A|2020/6/29\nD11550|Bimekizumab|L04AC21|IL17A/IL17F|2022/1/20\nD11817|Deucravacitinib|L04AF07|TYK2|2022/9/26","metadata":"{\"State-Gated Retrieval\":[\"Retain only active ingredients that were approved in Japan by 2024-12-31, are used for systemic treatment of plaque psoriasis, and genuinely act on the IL-17/IL-23 signaling axis.\",\"The candidate set must cover the ligand side, receptor side, and TYK2 kinase side, not only the interleukin ligand side.\",\"Final entries sorted by Japan first approval date ascending; for the same date, sort by DRUG_ID ascending.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"KEGG disease/drug entry points yield the Japan-approved systemic plaque-psoriasis drug cohort through 2024-12-31\",\"each drug entry yields target branch, ATC, systemic-use validity, and Japan approval date for IL-17/IL-23-axis candidates\",\"final rows are produced only after ligand-side, receptor-side, and kinase-side candidates are jointly reconciled and re-sorted by Japan approval date\"],\"control_dependency\":[\"entry-point coverage must include receptor-side IL17RA and kinase-side TYK2 mechanisms when downstream drug pages expose them, rather than staying ligand-only\",\"Ustekinumab must be removed only when target interpretation shows IL12 + IL23A rather than the IL-17/IL-23-axis criterion required here\",\"systemic-use, Japanese 3999, and PMDA-date filtering must be applied after each expansion of the candidate set rather than attached to the earlier ligand-only state\"],\"freeze\":{\"historical_window\":\"KEGG plaque-psoriasis systemic-drug entries as objectively existing drug entities, using target-branch and related drug-entry metadata as relatively stable annotations\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Retain only active ingredients that were approved in Japan by 2024-12-31, are used for systemic treatment of plaque psoriasis, and genuinely act on the IL-17/IL-23 signaling axis.\",\"The candidate set must cover the ligand side, receptor side, and TYK2 kinase side, not only the interleukin ligand side.\",\"Final entries sorted by Japan first approval date ascending; for the same date, sort by DRUG_ID ascending.\"],\"exclusion_conditions\":[\"Exclude topical drugs, non-systemic drugs, or entries outside the specified historical freeze window.\",\"Exclude Ustekinumab, whose actual target is IL12 + IL23A, because it does not meet the IL-17/IL-23 axis criterion required here.\",\"Exclude results that miss Brodalumab or Deucravacitinib due to considering only the ligand side.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"DRUG_ID\",\"Name\",\"ATC\",\"Target_branch\",\"PMDA_date\"],\"PMDA_date\":\"use the canonical KEGG-style date format YYYY/M/D with no zero-padding requirement beyond the source value\",\"Target_branch\":\"emit the most specific target branch visible in the source path; when multiple parallel branches survive, join them with `/`\",\"sorting_or_selection\":{\"primary\":\"PMDA_date ascending\",\"secondary\":\"DRUG_ID ascending\"}}}","all_involved_urls":"null"} +{"task_id":"genome_004-g","domain":"KEGG_GENOME","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am preparing a handout for a primate evolution course and want a two-row comparison table for this vitamin C metabolism exception pattern. Output two rows with columns rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year. The first row should be EXCEPTION_CLADE and the second row RETAINED_SISTER_CLADE. Use KEGG organism codes for the example species.","start_url":"https://www.genome.jp/kegg/kegg2.html","output_format":"Output a two-row comparison table with columns rank|clade_role|parent_clade|clade|anomaly_pathway|contrast_pathway|retained_upstream_module|vitamin_c_synthesis_module|vitamin_c_module_status|example_org|cutoff_year.","oracle_answer":"1|EXCEPTION_CLADE|Primates|Haplorrhini|map00053|map00040|M00014|M00129|LOST|csyr|2022\n2|RETAINED_SISTER_CLADE|Primates|Strepsirrhini|map00053|map00040|M00014|M00129|RETAINED|oga|2022","metadata":"{\"State-Gated Retrieval\":[\"Search only among primate genome entries established by the end of 2022, and isolate the anomalous lower-level clade that retains the upstream glucuronate module M00014 but lacks the animal-type vitamin C biosynthesis module M00129.\",\"That anomalous clade must be paired with a sister branch under the same higher-level split, and the sister branch must still retain M00129.\",\"The final output must place the anomalous branch and the retained sister branch into a two-row comparison table, including the required pathway, module, and example-species fields.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the KEGG primate clade pages and genome entries yield candidate subclades and example species established through the cutoff year\",\"the pathway and module views yield M00014 and M00129 presence/absence evidence for the exception clade and its sister branch\",\"final rows are produced only after the exception clade and retained sister branch are jointly validated under the same parent split and paired with example organisms\"],\"control_dependency\":[\"the exception clade remains provisional until both the sister-branch contrast and the example-species checks succeed\",\"the comparison view must make retained M00014 and missing M00129 visible together\",\"the two output rows are emitted together only after the exception clade and retained sister branch are fixed under the same parent split\"],\"freeze\":{\"historical_window\":\"the objectively existing primate genome entries established on or before 2022, using current KEGG clade, pathway, and module pages as relatively stable reference information for comparing retained M00014 against lost M00129\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Search only among primate genome entries established by the end of 2022, and isolate the anomalous lower-level clade that retains the upstream glucuronate module M00014 but lacks the animal-type vitamin C biosynthesis module M00129.\",\"That anomalous clade must have a contrastable sister branch, and that sister branch must still retain M00129.\",\"The final output must place the anomalous branch and the retained sister branch into a two-row comparison table, including the required pathway, module, and example-species fields.\"],\"exclusion_conditions\":[\"Exclude results that stop at Simiiformes without checking the broader boundary and therefore miss Haplorrhini.\",\"Exclude pathway views that do not make the M00014 versus M00129 contrast visible together.\",\"Exclude candidate clades that have not been validated against a retained sister branch.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"clade_role\",\"parent_clade\",\"clade\",\"anomaly_pathway\",\"contrast_pathway\",\"retained_upstream_module\",\"vitamin_c_synthesis_module\",\"vitamin_c_module_status\",\"example_org\",\"cutoff_year\"],\"rank\":\"emit 1 for EXCEPTION_CLADE and 2 for RETAINED_SISTER_CLADE\",\"clade_role\":[\"EXCEPTION_CLADE\",\"RETAINED_SISTER_CLADE\"],\"pathway_normalization\":\"emit KEGG pathway ids with the map prefix\",\"module_normalization\":\"emit KEGG module ids with the leading M\",\"vitamin_c_module_status\":[\"LOST\",\"RETAINED\"],\"organism_code\":\"use bare KEGG organism codes in lowercase, not species names\",\"cutoff_year\":\"use a four-digit year; this task is frozen at 2022\",\"sorting_or_selection\":\"emit rows in the fixed order EXCEPTION_CLADE then RETAINED_SISTER_CLADE\"}}","all_involved_urls":"null"} +{"task_id":"nvd_001-g","domain":"NVD","autonomy_type":"ordered table","instruction":"Identify which milestone versions of Apache Tomcat 9.0.0, released before the final GA release, are both affected by all four specified CVEs and have a CPE name notation change in NVD history. A CPE name notation change means the same milestone version was recorded as mN in older records but changed to milestoneN in current records. The search scope is limited to Apache Tomcat 9.0.0 milestone versions; these versions must appear in the current NVD affected product configurations for CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797. Exclude milestone versions brought in only by other Tomcat 9.0.0 pre-release related vulnerabilities, and also exclude Tomcat 6, Tomcat 7, Tomcat 8, Tomcat 8.5, and all non-Tomcat products. Output a multi-row ordered table with columns: milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd, sorted by milestone number in ascending order.","start_url":"https://nvd.nist.gov/vuln/search#/nvd/home?resultType=records","output_format":"Output a multi-row ordered table with columns: milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd, sorted by milestone number in ascending order.","oracle_output_cardinality":3,"oracle_answer":"CVE:2018-7543|1.2.32|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2018-17207|1.2.42|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2020-11738|1.3.28|lite+pro|ModifiedAnalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02","metadata":"{\"State-Gated Retrieval\":[\"Retain only Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator and whose deprecated vendor chain traces back to snapcreek:duplicator.\",\"Each candidate CVE must satisfy all of the following in its Change History: the Initial Analysis was not yet lite/lite+pro; the first change to lite or lite+pro occurred in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurred on 2026-02-02.\",\"The final output retains only CVE rows that meet all three conditions above.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"NVD product/CPE search pages yield the current awesomemotive:duplicator family and the deprecated snapcreek:duplicator lineage\",\"each target CVE detail page and Change History yield the Initial Analysis state, the first lite/lite+pro analysis event, and the 2026-02-02 vendor-remap event\",\"final rows are produced only after candidate CVEs are intersected on both snapcreek -> awesomemotive migration and later introduction of lite/lite+pro in NIST analysis history\"],\"control_dependency\":[\"the search must include the deprecated snapcreek lineage rather than only the current product state\",\"vendor migration alone is insufficient until detail-level history confirms that lite/lite+pro was introduced after Initial Analysis\",\"candidate CVEs must be filtered against the full change-history chronology, excluding any whose Initial Analysis already contained lite\"],\"freeze\":{\"historical_window\":\"Duplicator CVEs published from 2018-01-01 through 2024-12-31, evaluated against NVD analysis history up to the 2026-02-02 snapcreek -> awesomemotive vendor-remap events\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Retain only Duplicator-related CVEs whose current product line belongs to awesomemotive:duplicator and whose deprecated vendor chain traces back to snapcreek:duplicator.\",\"Each candidate CVE must satisfy all of the following in its Change History: the Initial Analysis was not yet lite/lite+pro; the first change to lite or lite+pro occurred in a NIST analysis event on 2021-10-18; and a snapcreek -> awesomemotive vendor remap occurred on 2026-02-02.\",\"The final output retains only CVE rows that meet all three conditions above.\"],\"exclusion_conditions\":[\"Exclude results that rely only on the current description or current product state without tracing back to the deprecated snapcreek chain and Change History.\",\"Exclude CVEs whose Initial Analysis was already lite/lite+pro.\",\"Exclude records without a 2026-02-02 vendor remap or that do not belong to the Duplicator product line.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\",\",\"schema_note\":\"the current source docx rubric, evidence, and oracle answer use a Duplicator CVE rowset, even though the instruction/output_format text still describes a Tomcat milestone task; normalization therefore follows the checked oracle row schema rather than the stale milestone wording\",\"schema\":[\"CVE\",\"lite_upper_version\",\"lite_vs_lite+pro\",\"analysis_event@date\",\"snapcreek_to_awesomemotive@date\"],\"CVE\":\"emit the identifier in the canonical `CVE:YYYY-NNNN` form used by the oracle\",\"lite_vs_lite+pro\":\"emit `lite` or `lite+pro` exactly\",\"analysis_event@date\":\"emit `Reanalysis@YYYY-MM-DD` or `ModifiedAnalysis@YYYY-MM-DD` exactly as supported by the source record\",\"snapcreek_to_awesomemotive@date\":\"emit the ownership-transfer event as `snapcreek->awesomemotive@YYYY-MM-DD`\",\"sorting_or_selection\":{\"primary\":\"NVD published date ascending\",\"secondary\":\"CVE ascending\"}}}","all_involved_urls":"null"} +{"task_id":"nvd_002-g","instruction":"We are compiling an exception list of legacy MySQL 5.1 assets left after Oracle's acquisition of MySQL. We need to identify which old CPE 2.3 entries whose name prefix still reads mysql:mysql were explicitly remapped by NIST to the corresponding oracle:mysql entries in the NVD history records for four InnoDB denial-of-service vulnerabilities. Start with CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680. For each vulnerability, examine the relevant CPE change records in NVD and find MySQL 5.1 entries where the prefix changed from mysql:mysql to oracle:mysql in all four vulnerabilities. During screening, retain only records that underwent this legacy-to-current prefix migration; exclude MySQL 5.0 branch entries and entries that only performed version alias normalization within the old mysql:mysql prefix. Finally, output a multi-row ordered table with columns version_update | legacy_cpe | current_cpe | remap_time_nvd, sorted by numeric version in ascending order; within the same version, records with an empty update field come before those with a non-empty update.","domain":"NVD","autonomy_type":"ordered table","oracle_output_cardinality":44,"start_url":"https://nvd.nist.gov/products/cpe/search","output_format":"Output a multi-row ordered table with columns version_update | legacy_cpe | current_cpe | remap_time_nvd, sorted by numeric version in ascending order; within the same version, entries without an update come before entries with an update.","oracle_answer":"version_update|legacy_cpe|current_cpe|remap_time_nvd\n5.1.1|cpe:2.3:a:mysql:mysql:5.1.1:::::::*|cpe:2.3:a:oracle:mysql:5.1.1:::::::*|2019-12-17 15:04:33\n5.1.2|cpe:2.3:a:mysql:mysql:5.1.2:::::::*|cpe:2.3:a:oracle:mysql:5.1.2:::::::*|2019-12-17 15:04:39\n5.1.3|cpe:2.3:a:mysql:mysql:5.1.3:::::::*|cpe:2.3:a:oracle:mysql:5.1.3:::::::*|2019-12-17 15:04:46\n5.1.4|cpe:2.3:a:mysql:mysql:5.1.4:::::::*|cpe:2.3:a:oracle:mysql:5.1.4:::::::*|2019-12-17 15:04:53\n5.1.10|cpe:2.3:a:mysql:mysql:5.1.10:::::::*|cpe:2.3:a:oracle:mysql:5.1.10:::::::*|2019-12-17 15:05:30\n5.1.11|cpe:2.3:a:mysql:mysql:5.1.11:::::::*|cpe:2.3:a:oracle:mysql:5.1.11:::::::*|2019-12-17 15:05:37\n5.1.12|cpe:2.3:a:mysql:mysql:5.1.12:::::::*|cpe:2.3:a:oracle:mysql:5.1.12:::::::*|2019-12-17 15:05:45\n5.1.13|cpe:2.3:a:mysql:mysql:5.1.13:::::::*|cpe:2.3:a:oracle:mysql:5.1.13:::::::*|2019-12-17 15:05:52\n5.1.14|cpe:2.3:a:mysql:mysql:5.1.14:::::::*|cpe:2.3:a:oracle:mysql:5.1.14:::::::*|2019-12-17 15:05:59\n5.1.15|cpe:2.3:a:mysql:mysql:5.1.15:::::::*|cpe:2.3:a:oracle:mysql:5.1.15:::::::*|2019-12-17 15:06:07\n5.1.16|cpe:2.3:a:mysql:mysql:5.1.16:::::::*|cpe:2.3:a:oracle:mysql:5.1.16:::::::*|2019-12-17 15:06:14\n5.1.17|cpe:2.3:a:mysql:mysql:5.1.17:::::::*|cpe:2.3:a:oracle:mysql:5.1.17:::::::*|2019-12-17 15:06:21\n5.1.18|cpe:2.3:a:mysql:mysql:5.1.18:::::::*|cpe:2.3:a:oracle:mysql:5.1.18:::::::*|2019-12-17 15:06:27\n5.1.19|cpe:2.3:a:mysql:mysql:5.1.19:::::::*|cpe:2.3:a:oracle:mysql:5.1.19:::::::*|2019-12-17 15:06:34\n5.1.20|cpe:2.3:a:mysql:mysql:5.1.20:::::::*|cpe:2.3:a:oracle:mysql:5.1.20:::::::*|2019-12-17 15:06:42\n5.1.21|cpe:2.3:a:mysql:mysql:5.1.21:::::::*|cpe:2.3:a:oracle:mysql:5.1.21:::::::*|2019-12-17 15:06:50\n5.1.22|cpe:2.3:a:mysql:mysql:5.1.22:::::::*|cpe:2.3:a:oracle:mysql:5.1.22:::::::*|2019-12-17 15:06:56\n5.1.23:a|cpe:2.3:a:mysql:mysql:5.1.23:a::::::|cpe:2.3:a:oracle:mysql:5.1.23:a::::::|2019-12-17 15:23:28\n5.1.24|cpe:2.3:a:mysql:mysql:5.1.24:::::::*|cpe:2.3:a:oracle:mysql:5.1.24:::::::*|2019-12-17 15:07:03\n5.1.25|cpe:2.3:a:mysql:mysql:5.1.25:::::::*|cpe:2.3:a:oracle:mysql:5.1.25:::::::*|2019-12-17 15:07:10\n5.1.26|cpe:2.3:a:mysql:mysql:5.1.26:::::::*|cpe:2.3:a:oracle:mysql:5.1.26:::::::*|2019-12-17 15:07:17\n5.1.27|cpe:2.3:a:mysql:mysql:5.1.27:::::::*|cpe:2.3:a:oracle:mysql:5.1.27:::::::*|2019-12-17 15:07:24\n5.1.28|cpe:2.3:a:mysql:mysql:5.1.28:::::::*|cpe:2.3:a:oracle:mysql:5.1.28:::::::*|2019-12-17 15:07:31\n5.1.29|cpe:2.3:a:mysql:mysql:5.1.29:::::::*|cpe:2.3:a:oracle:mysql:5.1.29:::::::*|2019-12-17 15:07:38\n5.1.30|cpe:2.3:a:mysql:mysql:5.1.30:::::::*|cpe:2.3:a:oracle:mysql:5.1.30:::::::*|2019-12-17 15:07:46\n5.1.31:sp1|cpe:2.3:a:mysql:mysql:5.1.31:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.31:sp1::::::|2019-12-17 15:23:35\n5.1.33|cpe:2.3:a:mysql:mysql:5.1.33:::::::*|cpe:2.3:a:oracle:mysql:5.1.33:::::::*|2019-12-17 15:07:55\n5.1.34:sp1|cpe:2.3:a:mysql:mysql:5.1.34:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.34:sp1::::::|2019-12-17 15:23:42\n5.1.35|cpe:2.3:a:mysql:mysql:5.1.35:::::::*|cpe:2.3:a:oracle:mysql:5.1.35:::::::*|2019-12-17 15:08:03\n5.1.36|cpe:2.3:a:mysql:mysql:5.1.36:::::::*|cpe:2.3:a:oracle:mysql:5.1.36:::::::*|2019-12-17 15:08:10\n5.1.37:sp1|cpe:2.3:a:mysql:mysql:5.1.37:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.37:sp1::::::|2019-12-17 15:23:49\n5.1.38|cpe:2.3:a:mysql:mysql:5.1.38:::::::*|cpe:2.3:a:oracle:mysql:5.1.38:::::::*|2019-12-17 15:08:17\n5.1.39|cpe:2.3:a:mysql:mysql:5.1.39:::::::*|cpe:2.3:a:oracle:mysql:5.1.39:::::::*|2019-12-17 10:22:31\n5.1.40|cpe:2.3:a:mysql:mysql:5.1.40:::::::*|cpe:2.3:a:oracle:mysql:5.1.40:::::::*|2019-12-17 10:22:46\n5.1.40:sp1|cpe:2.3:a:mysql:mysql:5.1.40:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.40:sp1::::::|2019-12-17 10:22:39\n5.1.41|cpe:2.3:a:mysql:mysql:5.1.41:::::::*|cpe:2.3:a:oracle:mysql:5.1.41:::::::*|2019-12-17 10:22:52\n5.1.42|cpe:2.3:a:mysql:mysql:5.1.42:::::::*|cpe:2.3:a:oracle:mysql:5.1.42:::::::*|2019-12-17 10:22:59\n5.1.43|cpe:2.3:a:mysql:mysql:5.1.43:::::::*|cpe:2.3:a:oracle:mysql:5.1.43:::::::*|2019-12-17 10:23:06\n5.1.43:sp1|cpe:2.3:a:mysql:mysql:5.1.43:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.43:sp1::::::|2019-12-17 10:23:11\n5.1.44|cpe:2.3:a:mysql:mysql:5.1.44:::::::*|cpe:2.3:a:oracle:mysql:5.1.44:::::::*|2019-12-17 10:23:17\n5.1.45|cpe:2.3:a:mysql:mysql:5.1.45:::::::*|cpe:2.3:a:oracle:mysql:5.1.45:::::::*|2019-12-17 10:23:24\n5.1.46|cpe:2.3:a:mysql:mysql:5.1.46:::::::*|cpe:2.3:a:oracle:mysql:5.1.46:::::::*|2019-12-17 10:23:38\n5.1.46:sp1|cpe:2.3:a:mysql:mysql:5.1.46:sp1::::::|cpe:2.3:a:oracle:mysql:5.1.46:sp1::::::|2019-12-17 10:23:31\n5.1.47|cpe:2.3:a:mysql:mysql:5.1.47:::::::*|cpe:2.3:a:oracle:mysql:5.1.47:::::::*|2019-12-17 10:23:45","metadata":"{\"State-Gated Retrieval\":[\"Retain only CPE 2.3 entries in the MySQL 5.1 branch for which the vendor migration from mysql:mysql to oracle:mysql is clearly visible in the NVD Change History for all four vulnerabilities CVE-2010-3676, 3677, 3678, and 3680.\",\"Every result must provide version_update, legacy_cpe, current_cpe, and remap_time_nvd.\",\"Within the same version, entries without an update come before entries with an update, and output is sorted by numeric version in ascending order.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Current and deprecated MySQL 5.1 CPE search results yield candidate legacy/current CPE strings\",\"The four target CVE pages and their Change History entries yield vendor-migration evidence, exact version_update strings, and remap timestamps\",\"Final rows are produced only after taking the common mysql:mysql 5.1 -> oracle:mysql 5.1 migrations across all four CVEs and removing alias-only or 5.0 entries\"],\"control_dependency\":[\"Legacy vendor mapping must be determined from Analysis Description plus Change History rather than from the current description/current CPE view\",\"Include-deprecated results cannot be accepted wholesale because alias-only remaps must be filtered out\",\"5.1-branch membership and sort order must be determined after the vendor-migration filter removes 5.0 and non-migration rows\"],\"freeze\":{\"historical_window\":\"The MySQL 5.1 branches visible in CVE-2010-3676, CVE-2010-3677, CVE-2010-3678, and CVE-2010-3680, restricted to explicit mysql:mysql -> oracle:mysql vendor-migration events\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Retain only CPE 2.3 entries in the MySQL 5.1 branch for which the vendor migration from mysql:mysql to oracle:mysql is clearly visible in the NVD Change History for all four vulnerabilities CVE-2010-3676, 3677, 3678, and 3680.\",\"Every result must provide version_update, legacy_cpe, current_cpe, and remap_time_nvd.\",\"Within the same version, entries without an update come before entries with an update, and output is sorted by numeric version in ascending order.\"],\"exclusion_conditions\":[\"Exclude MySQL 5.0 branch entries.\",\"Exclude entries that still belong to the old vendor mysql:mysql and only underwent internal version alias normalization without a vendor migration.\",\"Exclude results that only read from the current Oracle MySQL 5.1 CPE state without using legacy mapping and Change History.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"Required literal first row `version_update|legacy_cpe|current_cpe|remap_time_nvd`\",\"schema\":[\"version_update\",\"legacy_cpe\",\"current_cpe\",\"remap_time_nvd\"],\"version_update\":\"Sort by numeric MySQL version ascending; within the same base version, the empty update comes before any non-empty update suffix\",\"legacy_cpe\":\"Preserve the exact legacy CPE 2.3 string\",\"current_cpe\":\"Preserve the exact current CPE 2.3 string\",\"remap_time_nvd\":\"Emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form\",\"dedup_key\":\"(legacy_cpe, current_cpe)\"}}","all_involved_urls":"null"} +{"task_id":"nvd_004-g","domain":"NVD","autonomy_type":"ordered table","instruction":"Identify which milestone versions of Apache Tomcat 9.0.0 (prior to the final release) appear in the NVD current affected-product configurations for all four vulnerabilities CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797, and whose NVD change history shows a CPE identifier migration from the legacy mN form to the current milestoneN form. This step is intended to clean up SBOM rules that still use the old Apache Tomcat 9.0.0.Mx notation. Here, mN refers to forms such as m1, m2, etc., while milestoneN refers to the corresponding notation currently used by NVD. Retain only those Apache Tomcat 9.0.0 milestone versions that satisfy both conditions. Exclude two categories: (1) milestone versions that do not simultaneously meet the four-CVE condition and appear only because of other Tomcat 9.0.0 prerelease vulnerabilities; (2) Tomcat 6, Tomcat 7, Tomcat 8, Tomcat 8.5, and any non-Tomcat products. Output a multi-row ordered table with columns milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd, sorted by the numeric milestone value in ascending order.","start_url":"https://nvd.nist.gov/products/cpe/search","output_format":"Output a multi-row ordered table with columns milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd, sorted by the numeric milestone value in ascending order.","oracle_output_cardinality":9,"oracle_answer":"milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd\nM1|cpe:2.3:a:apache:tomcat:9.0.0:m1:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone1:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM2|cpe:2.3:a:apache:tomcat:9.0.0:m2:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone2:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM3|cpe:2.3:a:apache:tomcat:9.0.0:m3:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone3:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM4|cpe:2.3:a:apache:tomcat:9.0.0:m4:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone4:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM5|cpe:2.3:a:apache:tomcat:9.0.0:m5:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone5:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM6|cpe:2.3:a:apache:tomcat:9.0.0:m6:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone6:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM7|cpe:2.3:a:apache:tomcat:9.0.0:m7:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone7:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM8|cpe:2.3:a:apache:tomcat:9.0.0:m8:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone8:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18\nM9|cpe:2.3:a:apache:tomcat:9.0.0:m9:::::::*|cpe:2.3:a:apache:tomcat:9.0.0:milestone9:::::::*|CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797|2023-12-08 11:41:18","metadata":"{\"State-Gated Retrieval\":[\"Retain only Apache Tomcat 9.0.0 milestone versions that appear in the current affected-product scope of all four target CVEs: CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797.\",\"These versions must also show a CPE Deprecation Remap from mN to milestoneN in the NVD Change History.\",\"Finally, output sorted by numeric milestone value in ascending order, and the required_cves field must contain exactly these four specified CVEs.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the current milestoneN CPE search and detail pages yield the Tomcat milestone family and the legacy mN mapping anchors\",\"the four target CVE pages and Change History entries yield the exact mN -> milestoneN deprecation remaps and the required-CVE intersection\",\"final rows are produced only after taking the remaps common to all four target CVEs and sorting by numeric milestone\"],\"control_dependency\":[\"the candidate milestone set must be determined from the four-target-CVE intersection rather than from all prerelease Tomcat CVEs\",\"later remapped milestones such as M10+ must be excluded by applying the specified four-CVE boundary\",\"only explicit NVD CPE Deprecation Remap events from mN to milestoneN count, so generic Tomcat prerelease visibility cannot be accepted as evidence\"],\"freeze\":{\"historical_window\":\"the Tomcat 9.0.0 prerelease milestones jointly covered by CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797, with remap evidence fixed to the 2023-12-08 11:41:18 NVD deprecation events\"},\"answer_type\":\"multi-row ordered table\"}","all_involved_urls":"{\"fixed_entry_and_docs\":[\"https://nvd.nist.gov/products/cpe/search\",\"https://nvd.nist.gov/vuln/vulnerability-detail-pages\"],\"cpe_search_result_pages\":[\"https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL\",\"https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20milestone&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED\",\"https://nvd.nist.gov/products/cpe/search/results?keyword=apache%20tomcat%209.0.0%20m&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED\",\"https://nvd.nist.gov/products/cpe/search/results?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED\"],\"representative_cpe_detail_pages\":[\"https://nvd.nist.gov/products/cpe/detail/615922?keyword=cpe%3A2.3%3Aa%3Aapache%3Atomcat&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED\",\"https://nvd.nist.gov/products/cpe/detail/615947?keyword=cpe%3A2.3%3Aa%3Aapache&namingFormat=2.3&orderBy=CPEURI&status=FINAL%2CDEPRECATED\"],\"row_level_cpe_api_urls_m1_to_m9\":[\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone1%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone2%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone3%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone4%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone5%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone6%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone7%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone8%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\",\"https://services.nvd.nist.gov/rest/json/cpes/2.0?cpeMatchString=cpe%3A2.3%3Aa%3Aapache%3Atomcat%3A9.0.0%3Amilestone9%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A%3A%2A\"],\"target_cve_detail_pages\":[\"https://nvd.nist.gov/vuln/detail/CVE-2016-5018\",\"https://nvd.nist.gov/vuln/detail/CVE-2016-6794\",\"https://nvd.nist.gov/vuln/detail/CVE-2016-6796\",\"https://nvd.nist.gov/vuln/detail/CVE-2016-6797\"],\"negative_control_cve_detail_pages\":[\"https://nvd.nist.gov/vuln/detail/CVE-2016-6816\",\"https://nvd.nist.gov/vuln/detail/CVE-2016-6817\",\"https://nvd.nist.gov/vuln/detail/CVE-2019-0221\"],\"cve_change_history_api\":[\"https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-5018&eventName=CPE%20Deprecation%20Remap\",\"https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6794&eventName=CPE%20Deprecation%20Remap\",\"https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6796&eventName=CPE%20Deprecation%20Remap\",\"https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6797&eventName=CPE%20Deprecation%20Remap\",\"https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6816&eventName=CPE%20Deprecation%20Remap\",\"https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2016-6817&eventName=CPE%20Deprecation%20Remap\",\"https://services.nvd.nist.gov/rest/json/cvehistory/2.0?cveId=CVE-2019-0221&eventName=CPE%20Deprecation%20Remap\"],\"representative_change_record_pages\":[\"https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=04%2F18%2F2022T13%3A57%3A03.500-0400\",\"https://nvd.nist.gov/vuln/detail/CVE-2016-5018/change-record?changeRecordedOn=08%2F24%2F2017T09%3A11%3A40.690-0400\"]}","rubric":"{\"inclusion_conditions\":[\"Retain only Apache Tomcat 9.0.0 milestone versions that appear in the current affected-product scope of all four target CVEs: CVE-2016-5018, CVE-2016-6794, CVE-2016-6796, and CVE-2016-6797.\",\"These versions must also show a CPE Deprecation Remap from mN to milestoneN in the NVD Change History.\",\"Finally, output sorted by numeric milestone value in ascending order, and the required_cves field must contain exactly these four specified CVEs.\"],\"exclusion_conditions\":[\"Exclude milestones that are included only because of other Tomcat 9.0.0 prerelease vulnerabilities, such as M10/M11 and later milestones.\",\"Exclude Tomcat 6, 7, 8, 8.5, and any non-Tomcat products.\",\"Exclude records that lack explicit NVD remap evidence and are merely visible on the current milestone page.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"required literal first row `milestone|legacy_cpe|current_cpe|required_cves|remap_time_nvd`\",\"schema\":[\"milestone\",\"legacy_cpe\",\"current_cpe\",\"required_cves\",\"remap_time_nvd\"],\"milestone\":\"emit the canonical milestone label `M1` through `M9` and sort by the numeric suffix ascending\",\"legacy_cpe\":\"preserve the exact legacy CPE 2.3 string containing the short milestone token such as `m1`\",\"current_cpe\":\"preserve the exact current CPE 2.3 string containing the full milestone token such as `milestone1`\",\"required_cves\":\"emit the fixed literal `CVE-2016-5018;CVE-2016-6794;CVE-2016-6796;CVE-2016-6797`\",\"remap_time_nvd\":\"emit the NVD remap timestamp in `YYYY-MM-DD HH:MM:SS` form\"}}"} +{"task_id":"reptile_001-g","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"I am compiling a name concordance for early museum specimens of Indian snakes recorded in George A. Boulenger's 1890 work \"The Fauna of British India, Including Ceylon and Burma\". In the Reptile Database, identify entries that simultaneously satisfy the following conditions: the currently accepted name has been reassigned to a different genus compared with the name used in the book; the current species page still retains BMNH type specimen information; and the type locality still corresponds to India. For each qualifying entry, also retrieve the most recent historical binomial listed on the current species page that has not yet adopted the current genus name, and determine whether an exact search using that full old name uniquely identifies the entry. Output the results sorted alphabetically by accepted name in the format |||; join multiple entries with semicolons; if no qualifying entries exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output the results sorted alphabetically by accepted name in the format |||; join multiple entries with semicolons; if no qualifying entries exist, output NONE.","oracle_answer":"Argyrophis oatesii|Typhlops oatesii|UNIQUE|SYNTYPES;Dendrelaphis grandoculis|Ahaetulla grandoculis|UNIQUE|LECTOTYPE;Fowlea sanctijohannis|Xenochrophis sanctijohannis|UNIQUE|HOLOTYPE;Gerrhopilus beddomii|Typhlops beddomii|UNIQUE|SYNTYPES;Hebius khasiensis|Amphiesma khasiense|UNIQUE|LECTOTYPE;Hebius parallelus|Amphiesma parallelum|AMBIG|LECTOTYPE;Indotyphlops jerdoni|Typhlops jerdoni|UNIQUE|SYNTYPES;Myriopholis blanfordii|Leptotyphlops blanfordi|AMBIG|SYNTYPES","metadata":"{\"State-Gated Retrieval\":[\"Candidates must come from the historical Indian snake collection entries in Boulenger 1890 \\\"Fauna of British India\\\".\",\"The current Reptile Database species page must simultaneously satisfy: the species has been reassigned to a different genus; the page still retains BMNH type specimen information; and the type locality still corresponds to India.\",\"On each qualifying page, select the most recent historical binomial that has not yet adopted the current genus name, perform an exact back-search using that old name, and then label it UNIQUE or AMBIG.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"The Boulenger 1890 historical sample and current accepted-species pages yield candidates that changed genus while retaining BMNH type data and India-compatible type locality.\",\"Each accepted page yields the nearest pre-current-genus old label, the BMNH type status, and the historical/type-locality evidence anchoring the entity.\",\"Final rows are produced only after the old-label exact back-search is evaluated for uniqueness without losing the original entity anchor.\"],\"control_dependency\":[\"When an exact old-label back-search now hits multiple species, the original anchored entity must be kept and the uniqueness label must be set to AMBIG.\",\"Once a candidate has passed the historical-cluster, genus-shift, BMNH, and India-locality gates, later old-label ambiguity can only rewrite the uniqueness field, not the entity itself.\",\"Candidate anchoring must be preserved across the two-stage workflow so that old-label search noise does not redirect the accepted-species row.\"],\"freeze\":{\"historical_window\":\"The objectively existing reptile taxa in the George A. Boulenger 1890 British India sample, using Reptile Database accepted pages, synonym labels, BMNH type data, and type-locality text as nearly objective and highly stable reference information.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Candidates must come from the historical Indian snake collection entries in Boulenger 1890 \\\"Fauna of British India\\\".\",\"The current Reptile Database species page must simultaneously satisfy: the species has been reassigned to a different genus; the page still retains BMNH type specimen information; and the type locality still corresponds to India.\",\"On each qualifying page, select the most recent historical binomial that has not yet adopted the current genus name, perform an exact back-search using that old name, and then label it UNIQUE or AMBIG.\"],\"exclusion_conditions\":[\"Exclude entries where the current accepted name has not undergone a genus change, or where the page no longer retains BMNH type specimen information.\",\"Exclude entries whose type locality does not correspond to India.\",\"Do not discard candidates for which the exact old-name back-search is non-unique; such candidates should retain the original entity and be labeled AMBIG.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\";\",\"schema\":[\"accepted name\",\"old label\",\"UNIQUE/AMBIG\",\"BMNH status\"],\"accepted_name\":\"Emit the current accepted binomial exactly as shown in the reconciled source.\",\"old_label\":\"Preserve the historical label exactly as used on the legacy branch.\",\"UNIQUE/AMBIG\":\"Emit `UNIQUE` or `AMBIG` in uppercase.\",\"BMNH_status\":\"Normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or SYNTYPES.\",\"sorting_or_selection\":\"Accepted name alphabetical ascending.\"}}","all_involved_urls":"null"} +{"task_id":"reptile_002-g","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am compiling name correspondences between old labels and current accepted names for early museum specimens of Southeast Asian Lygosoma. In the current Lygosoma checklist, identify all accepted species that satisfy both of the following conditions: the species page lists a Riopa combination used by Smith (1935/1937) in its Synonym section, and that old name corresponds to more than one accepted species under the current classification. For each qualifying species, output the first-listed type specimen number, type status, and the region corresponding to the final type locality on that page. Output in alphabetical order by accepted name, using the format ||||; join multiple entries with semicolons. If no qualifying items exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output in alphabetical order by accepted name, using the format ||||; join multiple entries with semicolons. If no qualifying items exist, output NONE.","oracle_answer":"Lygosoma bampfyldei|Riopa bampfyldei|BMNH 1946.8.10.84|SYNTYPES|East Malaysia;Lygosoma peninsulare|Riopa bampfyldei|LSUHC 13857|HOLOTYPE|Peninsular Malaysia;Lygosoma schneideri|Riopa bampfyldei|NMBA 4743|HOLOTYPE|Indonesia","metadata":"{\"State-Gated Retrieval\":[\"Retain only accepted species that can be traced from the Smith 1937 old-name chain to a current Lygosoma record and for which the type accession, type status, and locality can be read on the current page.\",\"For each accepted record, output the accepted name, the corresponding old label, the type accession, the type status, and the locality.\",\"If the same exact old name appears on multiple accepted species, retain them as separate chains.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the Smith 1937 old-name chain yields the three current Lygosoma accepted pages connected to Riopa bampfyldei / Lygosoma bampfyldei\",\"each accepted page yields its own type accession, type status, and type locality needed to separate the homonymous old-name paths\",\"final rows are produced only after the one-to-many old-name split is rebuilt and the three paths are re-anchored to their own type evidence\"],\"control_dependency\":[\"same-specific-epithet matching cannot establish a one-to-one mapping when the same Smith 1937 old name appears on multiple accepted pages\",\"once literal old-name reuse is exposed, the workflow must keep the original parallel three-chain state rather than collapsing to a one-to-one mapping\",\"type accession and locality evidence must be read separately for each chain rather than patched onto the first stopping page\"],\"freeze\":{\"historical_window\":\"the objectively existing taxa linked to the Smith 1937 old-name cluster around Riopa bampfyldei, using Reptile Database accepted pages together with type accessions, statuses, and localities as nearly objective and highly stable reference information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Retain only accepted species that can be traced from the Smith 1937 old-name chain to a current Lygosoma record and for which the type accession, type status, and locality can be read on the current page.\",\"For each accepted record, output the accepted name, the corresponding old label, the type accession, the type status, and the locality.\",\"If the same exact old name appears on multiple accepted species, retain them as separate chains.\"],\"exclusion_conditions\":[\"Exclude results that assume the same species simply because the old name and current specific epithet match.\",\"Exclude results that retain only the first chain when the same exact old name appears on multiple accepted pages.\",\"Exclude results that do not re-verify the type accession and locality on each accepted page.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\";\",\"schema\":[\"accepted\",\"Smith-era Riopa label\",\"first type code\",\"type status\",\"region\"],\"accepted\":\"emit the current accepted binomial exactly as shown in the reconciled source\",\"Smith-era_Riopa_label\":\"preserve the Smith-era Riopa label exactly as used on the legacy branch\",\"first_type_code\":\"emit the first accession code that follows the selected type-status statement\",\"type_status\":\"normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES\",\"region\":\"emit the modern geographic region label from the source reconciliation, such as East Malaysia or Peninsular Malaysia\",\"sorting_or_selection\":\"accepted name alphabetical ascending\"}}","all_involved_urls":"null"} +{"task_id":"reptile_003-g","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":10,"instruction":"I am compiling a name cross-reference for a batch of old collection cards that were still cataloged under the names Mabuya or Mabuia around 1980 and now need to be merged into the current Eutropis checklist. In the current Eutropis list, identify all entries that meet the following conditions: the first 1980-era label on the species page has the genus written as Mabuya or Mabuia; and when that 1980-era label is searched by name in the current list, it does not uniquely correspond to a single Eutropis entry but instead matches multiple current Eutropis entries. For each qualifying entry, output the current accepted name, that 1980-era label, the qualifier for that label on the page, and the first type status and type code listed on the current page. Output sorted alphabetically by 1980-era label, and within the same label by current accepted name, in the format |<1980 label>|||; join multiple entries with semicolons; if no qualifying entries exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output sorted alphabetically by 1980-era label, and within the same label by current accepted name, in the format |<1980 label>|||; join multiple entries with semicolons; if no qualifying entries exist, output NONE.","oracle_answer":"Eutropis indeprensa|Mabuya indeprensa|NONE|HOLOTYPE|CAS 85664;Eutropis sahulinghangganan|Mabuya indeprensa|PART-MISID|HOLOTYPE|PNM 9867;Eutropis multifasciata|Mabuya multifasciata|NONE|NEOTYPE|MZB 11912;Eutropis multicarinata|Mabuya multicarinata|NONE|HOLOTYPE|BMNH 1946.8.15.13-15;Eutropis borealis|Mabuya multicarinata borealis|NONE|HOLOTYPE|CAS 15447;Eutropis islamaliit|Mabuya multicarinata borealis|PART-MISID|HOLOTYPE|PNM 9847;Eutropis caraga|Mabuya multicarinata multicarinata|PART-MISID|HOLOTYPE|PNM 9845;Eutropis palauensis|Mabuya multicarinata multicarinata|PART-BYIMPL|HOLOTYPE|CAS 248251;Eutropis dattaroyi|Mabuya rudis|PART|HOLOTYPE|ZSI 25118;Eutropis rudis|Mabuya rudis|NONE|LECTOTYPE|BMNH 1946.8.15.26","metadata":"{\"State-Gated Retrieval\":[\"Retain only those current Eutropis records whose synonym block contains, scanning top-down, a first old label starting with Mabuya or Mabuia and having the year 1980.\",\"Then use that 1980-era old label for a default name back-search, and output the accepted name, old label, back-search qualifier, type status, and type specimen.\",\"If the subsequent back-search reveals additional matching entries, revisit the earlier results and include them in the final output.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"current Eutropis detail pages yield the first 1980-tagged Mabuya/Mabuia synonym label for each accepted species\",\"exact back-search on that 1980 old label yields the present accepted page, type status, and type specimen needed for the output row\",\"final rows are produced only after the 1980-specific old-label anchor is rebuilt and the accepted-species set is expanded when back-search evidence reveals omitted entries\"],\"control_dependency\":[\"the workflow must identify the first Mabuya/Mabuia label carrying the 1980 year rather than stopping at the first old label on the page\",\"when old-label back-search reveals missing entries such as Eutropis dattaroyi, the accepted-species set must be expanded to include them rather than patched in place\",\"accepted-page synonym parsing and back-search interpretation must stay coupled so that 1980 labels are not replaced by older but irrelevant names\"],\"freeze\":{\"historical_window\":\"the objectively existing Eutropis taxa represented in Reptile Database pages, using the synonym labels shown on each species page, especially the first Mabuya/Mabuia-form label tagged with the 1980 citation year, as nearly objective and highly stable reference information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Retain only those current Eutropis records whose synonym block contains, scanning top-down, a first old label starting with Mabuya or Mabuia and having the year 1980.\",\"Then use that 1980-era old label for a default name back-search, and output the accepted name, old label, back-search qualifier, type status, and type specimen.\",\"If the subsequent back-search reveals additional matching entries, revisit the earlier results and include them in the final output.\"],\"exclusion_conditions\":[\"Exclude results that mistakenly treat the first old label on the page as the first 1980-era old label.\",\"Exclude results whose exact back-search on the 1980 old label points to only a single current Eutropis entry.\",\"Exclude results that, when subsequent evidence reveals omitted entries, fail to revisit the earlier results and rebuild the accepted-species set.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\";\",\"schema\":[\"accepted\",\"1980 label\",\"qualifier\",\"type status\",\"first type code\"],\"accepted\":\"emit the current accepted binomial exactly as shown in the reconciled source\",\"1980_label\":\"preserve the 1980-era label exactly as used on the legacy branch\",\"qualifier\":\"normalize to one of `NONE`, `PART`, `PART-MISID`, or `PART-BYIMPL`\",\"type_status\":\"normalize the type-status field to uppercase labels such as HOLOTYPE or SYNTYPES\",\"first_type_code\":\"emit the first accession code that follows the selected type-status statement\",\"sorting_or_selection\":{\"primary\":\"1980 label alphabetical ascending\",\"secondary\":\"accepted name alphabetical ascending\"}}}","all_involved_urls":"null"} +{"task_id":"reptile_004-g","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":6,"instruction":"I am organizing a set of old Hemidactylus brookii museum cards that use the historical labels listed in the comments of the Hemidactylus brookii species page. Identify all old labels that are no longer considered synonyms of Hemidactylus brookii and for which the database provides a clear final synonym assignment. For each qualifying old label, output the currently accepted species it should be assigned to; if the synonym chain passes through an intermediate historical name, list that name, otherwise output DIRECT; also output the type status, type code, and the country of the type locality for that old label. Output the results in alphabetical order of the old labels, using the format |||||, with multiple entries separated by semicolons. If no qualifying entries exist, output NONE.","start_url":"https://reptile-database.reptarium.cz/advanced_search","output_format":"Output in alphabetical order of the old labels, using the format |||||, with multiple entries separated by semicolons. If no qualifying entries exist, output NONE.","oracle_answer":"Hemidactylus brooki leightoni|Hemidactylus angulatus|DIRECT|HOLOTYPE|BMNH 1946.8.25.65|Colombia;Hemidactylus brookii haitianus|Hemidactylus angulatus|DIRECT|LECTOTYPE|ZMH R22378|Haiti;Hemidactylus brookii parvimaculatus|Hemidactylus parvimaculatus|DIRECT|HOLOTYPE|NMSL No. RG. 15|Sri Lanka;Hemidactylus brookii subtriedroides|Hemidactylus murrayi|Hemidactylus tenkatei|LECTOTYPE|BMNH [subtriedroides] [tenkatei]|Myanmar;Hemidactylus gleadowi|Hemidactylus gleadowi|DIRECT|NEOTYPE|BMNH 1884.7.25.8|Pakistan;Hemidactylus tenkatei|Hemidactylus murrayi|DIRECT|LECTOTYPE|RMNH 4353|Indonesia","metadata":"{\"State-Gated Retrieval\":[\"Each result must start from the specified old-label chain and ultimately determine the accepted name, bridge status, type status, type code, and locality from the current accepted species page.\",\"For the subtriedroides branch, continue the chain through tenkatei to murrayi, output the final accepted name as Hemidactylus murrayi, and retain bridge=Hemidactylus tenkatei.\",\"For branches such as haitianus and leightoni, read the locality and type lines specific to each branch, rather than borrowing the header information from the wrong accepted page.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the old-label chains from Hemidactylus angulatus and related names yield accepted pages, bridge names, and the type/locality lines for each path\",\"comment, Types, and type-comment blocks yield the later evidence that tenkatei is further sunk into H. murrayi\",\"final rows are produced only after each old-label path is re-anchored to its own locality/type line and the subtriedroides -> tenkatei -> murrayi bridge chain is completed\"],\"control_dependency\":[\"type data must be taken from the locality/type line belonging to the actual old-label branch rather than from the header block of the wrong accepted page\",\"stopping at the intermediate tenkatei bridge is insufficient; the workflow must continue to the later murrayi evidence and rewrite both tenkatei and subtriedroides final accepted names\",\"bridge labels remain useful, but final accepted names and type lines must be determined from the deeper synonym chain\"],\"freeze\":{\"historical_window\":\"the objectively existing taxa in the Hemidactylus angulatus / brookii / murrayi complex, using Reptile Database locality, type, comment, and type-comment blocks as nearly objective and highly stable reference information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Each result must start from the specified old-label chain and ultimately determine the accepted name, bridge status, type status, type code, and locality from the current accepted species page.\",\"For the subtriedroides branch, continue the chain through tenkatei to murrayi, output the final accepted name as Hemidactylus murrayi, and retain bridge=Hemidactylus tenkatei.\",\"For branches such as haitianus and leightoni, read the locality and type lines specific to each branch, rather than borrowing the header information from the wrong accepted page.\"],\"exclusion_conditions\":[\"Exclude results that follow the wrong page hierarchy and apply the Holotype/locality from the H. angulatus page header to other branches.\",\"Exclude results that stop early on the subtriedroides -> tenkatei chain without continuing to read the subsequent murrayi evidence.\",\"Exclude results that fail to align the locality/type lines with the specific old-label branches one by one.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\";\",\"schema\":[\"legacy label\",\"accepted\",\"bridge\",\"type status\",\"type code\",\"country\"],\"legacy_label\":\"preserve the legacy label exactly as used on the source branch\",\"accepted\":\"emit the current accepted binomial exactly as shown in the reconciled source\",\"bridge\":\"emit `DIRECT` when no intermediate legacy bridge name is needed; otherwise emit the intermediate legacy name that links the branches\",\"type_status\":\"normalize the type-status field to uppercase labels such as HOLOTYPE, LECTOTYPE, or NEOTYPE\",\"type_code\":\"take the type accession from the legacy-label branch rather than from a generic type line elsewhere on the page\",\"country\":\"emit the modern English country name from the reconciled source branch\",\"sorting_or_selection\":\"legacy label alphabetical ascending\"}}","all_involved_urls":"null"} +{"task_id":"reptile_005-g","domain":"REPTILE_DATABASE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I want to organize this synonymization record for an old Sri Lankan museum name in the current Naja list into a two-row comparison table. Output two rows with columns rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note. The first row should be ACCEPTED_NAME and the second row CONTESTED_NAME.","start_url":"https://reptile-database.reptarium.cz/advanced_search?genus=Naja&submit=Search","output_format":"Output a two-row comparison table with columns rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note.","oracle_answer":"1|ACCEPTED_NAME|Naja naja|SUBJECTIVE_JUNIOR_SYNONYM_OF_NAJA_NAJA|VALID_LECTOTYPE|ZMB 2796|restricted type locality: Sri Lanka\n2|CONTESTED_NAME|Naja polyocellata|SHI et al. 2022+SILVA et al. 2023|HOLOTYPE|BMNH 1946.1.18.50|invalid lectotype claim: NRM (= NHR) Lin-90","metadata":"{\"State-Gated Retrieval\":[\"Within the current Naja list, identify the Sri Lanka contested-name branch: the name was recently reused as a distinct valid name, but the database now explicitly merges it back into the accepted name.\",\"On the current Naja naja page, read the recent-use evidence, final synonym status, lectotype correction, restricted type locality, and the holotype information for the contested name itself.\",\"The final output must organize the ACCEPTED_NAME side and the CONTESTED_NAME side into a two-row comparison table.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the current Naja species list and the Naja naja page yield the Sri Lanka contested-name branch, recent-use citations, and the accepted-name context\",\"comment, Types, and type-comment blocks yield the final synonym treatment plus the valid and invalid lectotype assignments and the contested-name holotype\",\"final rows are produced only after the accepted-name side and the contested-name side are reconciled on the current Naja naja page\"],\"control_dependency\":[\"recent-use evidence for Naja polyocellata must be interpreted together with the current final synonym treatment shown on that page\",\"lectotype status must be fixed from the combined Types and type-comment evidence rather than from a single provisional assignment\",\"the accepted-name and contested-name rows are emitted together only after final status, type locality, and specimen roles are fixed\"],\"freeze\":{\"historical_window\":\"the objectively existing taxa in the Sri Lanka Naja branch, using current Reptile Database comment, Types, and type-comment blocks as nearly objective and highly stable reference information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Within the current Naja list, identify the Sri Lanka contested-name record: the name was recently reused in the literature as a distinct valid name, but the database now explicitly states that it should still be merged into the accepted name.\",\"On the current Naja naja page, the result must jointly recover the recent-use evidence, final synonym status, lectotype correction, restricted type locality, and the holotype information for the contested name itself.\",\"The final output must organize the ACCEPTED_NAME side and the CONTESTED_NAME side into a two-row comparison table.\"],\"exclusion_conditions\":[\"Exclude results that treat the recently revived contested name as the current accepted name.\",\"Exclude results that stop at the Wallach 2014 lectotype designation and do not continue to the later comment and type-comment correction.\",\"Exclude results that fail to output both the restricted type locality and the contested-name holotype.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"name_role\",\"name\",\"status_or_evidence\",\"specimen_role\",\"specimen_code\",\"supporting_note\"],\"rank\":\"emit 1 for ACCEPTED_NAME and 2 for CONTESTED_NAME\",\"name_role\":[\"ACCEPTED_NAME\",\"CONTESTED_NAME\"],\"name_fields\":\"use the current binomial spellings exactly\",\"specimen_code_normalization\":\"preserve museum abbreviations, spaces, parentheses, and specimen punctuation exactly as the page shows\",\"sorting_or_selection\":\"emit rows in the fixed order ACCEPTED_NAME then CONTESTED_NAME\"}}","all_involved_urls":"null"} +{"task_id":"wateroffice_001-g","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am compiling historical daily flow comparison data for the Saint John River spring freshet and want to identify, along the Saint John River mainstem, the last station in the current monitoring network that still allows daily flow comparisons for March-April 1973 and March-April 2018, as well as the first downstream mainstem station that no longer satisfies that condition. Mark a station as PASS if the target windows have complete daily flow records, LEVEL_ONLY if only water level records are available, and FLOW_GAP if daily flow records exist but the target months are missing or incomplete. Output a two-row breakpoint table with columns rank|station_number|breakpoint_role|target_window_status|final_verdict. The first row should be LAST_USABLE and the second row should be FIRST_DOWNSTREAM_FAIL.","start_url":"https://wateroffice.ec.gc.ca/search/real_time_e.html","output_format":"Output a two-row breakpoint table with columns rank|station_number|breakpoint_role|target_window_status|final_verdict.","oracle_answer":"1|01AF002|LAST_USABLE|PASS|KEEP\n2|01AK003|FIRST_DOWNSTREAM_FAIL|LEVEL_ONLY|REJECT","metadata":"{\"State-Gated Retrieval\":[\"Determine the last station still usable for the target historical-window comparison only within the Saint John River mainstem stations in the current monitoring network.\",\"The historical availability page must distinguish Flow Data Availability from Daily Water Level Data Availability, and completeness for March-April 1973 and March-April 2018 must be checked.\",\"The final output must provide both breakpoint rows, LAST_USABLE and FIRST_DOWNSTREAM_FAIL, under the same validation rule.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the current Saint John River mainstem station sequence provides the downstream order in which the breakpoints must be checked\",\"per-station historical availability pages yield Flow Data Availability, Daily Water Level Data Availability, and target-month completeness for 1973 and 2018\",\"the final breakpoint rows are produced only after the availability-page checks identify the last usable station and the first downstream failure under the same rule\"],\"control_dependency\":[\"the breakpoint pair must be determined from historical availability that distinguishes flow from level-only evidence\",\"target-year/month completeness must be checked on the availability page rather than inferred from the station list\",\"the second row is emitted only after the first downstream failing mainstem station is fixed under the same validation rule\"],\"freeze\":{\"historical_window\":\"mainstem candidate stations evaluated within the fixed historical March/April daily-availability windows for 1973 and 2018, using station ordering and completeness signals as nearly stable reference information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Determine the last station still usable for the target historical-window comparison only within the Saint John River mainstem stations in the current monitoring network.\",\"The historical availability page must distinguish Flow Data Availability from Daily Water Level Data Availability, and completeness for March-April 1973 and March-April 2018 must be checked.\",\"The final output must provide both breakpoint rows, LAST_USABLE and FIRST_DOWNSTREAM_FAIL, under the same validation rule.\"],\"exclusion_conditions\":[\"Exclude results that determine the breakpoint directly from the current Saint John River mainstem station sequence using only a reference index.\",\"Exclude results that mistakenly treat level-only evidence as satisfying the flow condition.\",\"Exclude results that do not check each station's availability page to verify target-month completeness.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"station_number\",\"breakpoint_role\",\"target_window_status\",\"final_verdict\"],\"rank\":\"emit `1` for LAST_USABLE and `2` for FIRST_DOWNSTREAM_FAIL\",\"station_number\":\"preserve the station number exactly\",\"breakpoint_role\":\"emit `LAST_USABLE` and `FIRST_DOWNSTREAM_FAIL` exactly\",\"target_window_status\":\"emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly\",\"final_verdict\":\"emit `KEEP` for the usable breakpoint row and `REJECT` for the downstream failing breakpoint row\",\"stop_condition\":[\"the last usable mainstem station is fixed under the availability-page validation rule\",\"the first downstream failing mainstem station is fixed under the same validation rule before the two-row output is emitted\"]}}","all_involved_urls":"null"} +{"task_id":"wateroffice_002-g","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":4,"instruction":"I am compiling historical daily flow records for the Bulkley River reach from Houston to Hazelton and want to determine which candidate mainstem stations on this reach truly have complete daily flow records for April-July 1948 and April-July 1950. Mark a station as PASS if the target windows have complete daily flow records, LEVEL_ONLY if only water level records are available, and FLOW_GAP if daily flow records exist but any target month from April to July is incomplete. Output a table in downstream-to-upstream order with columns rank|station_number|target_window_status|final_verdict.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a table in downstream-to-upstream order with columns rank|station_number|target_window_status|final_verdict.","oracle_answer":"1|08EE004|PASS|KEEP\n2|08EE001|LEVEL_ONLY|REJECT\n3|08EE005|FLOW_GAP|REJECT\n4|08EE003|FLOW_GAP|REJECT","metadata":"{\"State-Gated Retrieval\":[\"First identify mainstem candidate stations on the Historical Results list that appear to cover 1948/1950 and carry a Flow label.\",\"A station qualifies only if its availability page shows the target years in the Flow section and all of April-July marked C.\",\"The final output must report target_window_status and final_verdict for each station in the same station set, ordered from downstream to upstream.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the Historical Results list yields four downstream-to-upstream mainstem candidates whose result rows span the target years and include Flow labels\",\"each candidate's availability page yields whether the target years are in the Flow table and whether April–July is complete\",\"the final ordered rows are produced only after all four stations are classified under the full Flow-table-and-Apr-Jul-C rule\"],\"control_dependency\":[\"list-level year spans and coarse Flow tags must be confirmed by explicit target-month checks on the availability page\",\"Hazelton, Smithers, and Houston candidate statuses must be fixed before the downstream-most KEEP row can be confirmed\",\"row order and KEEP/REJECT labels must be emitted only after the full availability-page rule is applied to all four stations\"],\"freeze\":{\"historical_window\":\"the target mainstem stations tested within the fixed historical daily Flow-availability windows for 1948 and 1950, with April–July complete-C coverage used as nearly stable reference information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"First identify mainstem candidate stations on the Historical Results list that appear to cover 1948/1950 and carry a Flow label.\",\"A station qualifies only if its availability page shows the target years in the Flow section and all of April-July marked C.\",\"The final output must report target_window_status and final_verdict for each station in the same station set, ordered from downstream to upstream.\"],\"exclusion_conditions\":[\"Exclude stations deemed usable solely from list-level year spans and coarse Flow labels.\",\"Exclude results that mark any LEVEL_ONLY or FLOW_GAP station as KEEP.\",\"Exclude results that do not apply the full availability-page rule to all initially screened stations.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"station_number\",\"target_window_status\",\"final_verdict\"],\"rank\":\"emit 1 through 4 in downstream-to-upstream order within the validated station set\",\"station_number\":\"preserve the station number exactly\",\"target_window_status\":\"emit `PASS`, `LEVEL_ONLY`, or `FLOW_GAP` exactly\",\"final_verdict\":\"emit `KEEP` or `REJECT` exactly\",\"sorting_or_selection\":\"downstream to upstream within the validated Bulkley River mainstem station set\",\"stop_condition\":[\"all four initially screened stations are classified under the full availability-page rule\",\"the ordered table is emitted only after the downstream-to-upstream sequence is fixed\"]}}","all_involved_urls":"null"} +{"task_id":"wateroffice_003-g","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":5,"instruction":"I am compiling historical snowmelt daily flow data for the Thompson River from Chase to Spences Bridge. I need to identify which mainstem stations along this reach actually had daily flow records for both 1958 and 1971 (May–July). For each mainstem station that appears in the station list as covering 1958 and 1971 and having flow information, verify it station by station in downstream order from Chase to Spences Bridge. Output a table with columns: rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict. If a station has only water level records (no daily flow) for a target year, mark it LEVEL_ONLY. If daily flow records are missing or any of the May–July months is incomplete, mark it FLOW_GAP. Only if both years meet the criteria should final_verdict be KEEP; otherwise mark it REJECT.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a table with columns: rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict.","oracle_answer":"1|08LE031|SOUTH THOMPSON RIVER AT CHASE|PASS|PASS|KEEP\n2|08LE069|SOUTH THOMPSON RIVER AT MONTE CREEK|FLOW_GAP|LEVEL_ONLY|REJECT\n3|08LF023|THOMPSON RIVER AT KAMLOOPS|LEVEL_ONLY|LEVEL_ONLY|REJECT\n4|08LF033|THOMPSON RIVER NEAR SAVONA|FLOW_GAP|FLOW_GAP|REJECT\n5|08LF051|THOMPSON RIVER NEAR SPENCES BRIDGE|PASS|PASS|KEEP","metadata":"{\"State-Gated Retrieval\":[\"All five candidate stations must be verified on their availability page: check whether the target year appears in the Flow table and whether May–July is entirely marked C.\",\"For each station, output a PASS, LEVEL_ONLY, or FLOW_GAP judgment for both target years, then label it KEEP or REJECT accordingly.\",\"The result order must follow the river-path sequence specified in the task.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"The river-path ordering yields five South Thompson/Thompson mainstem candidates.\",\"Each station's availability page indicates whether 1958 and 1971 are present in the Flow table and whether May–July is complete.\",\"Final rows are produced only after every candidate is classified under the stricter target-year and target-month Flow rule.\"],\"control_dependency\":[\"Overall year coverage on the results list must be confirmed by the availability page inside the Flow table.\",\"Monte Creek, Savona, and Kamloops must be rejected by LEVEL_ONLY/FLOW_GAP evidence before the KEEP rows are final.\",\"The river-order sequence remains fixed, but station statuses must be assigned only after the availability-page rule is applied to all five stations.\"],\"freeze\":{\"historical_window\":\"The ordered South Thompson/Thompson mainstem candidates are tested within the fixed historical Flow-availability windows for 1958 and 1971, with May–July complete-C coverage used as nearly stable reference information.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"All five candidate stations must be verified on their availability page: check whether the target year appears in the Flow table and whether May–July is entirely marked C.\",\"For each station, output a PASS, LEVEL_ONLY, or FLOW_GAP judgment for both target years, then label it KEEP or REJECT accordingly.\",\"The result order must follow the river-path sequence specified in the task.\"],\"exclusion_conditions\":[\"Exclude results that treat overall year coverage on the list page as sufficient evidence.\",\"Exclude results that fail to distinguish between Flow-table target-year and month completeness versus Level-only evidence.\",\"Exclude results that do not apply the same availability-page rule uniformly to all five stations.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"station_number\",\"station_name\",\"1958_MayJul\",\"1971_MayJul\",\"final_verdict\"],\"rank\":\"use the fixed Chase-to-Spences-Bridge mainstem order from the reference index, not the transient search-result order\",\"year_window_fields\":\"the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP\",\"final_verdict\":\"emit `KEEP` or `REJECT` exactly\"}}","all_involved_urls":"null"} +{"task_id":"wateroffice_004-g","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":13,"instruction":"I am compiling historical daily flow records for the main stem of the Columbia River from Fairmont Hot Springs to the International Boundary. I want to check, station by station, which Wateroffice gauges have complete daily flow records for May–October of 1955 and 1956. The candidate set is limited to main-stem Columbia River stations whose overall period of record spans both 1955 and 1956. Please evaluate each station in upstream-to-downstream order and output a table with columns: rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict. If the target year has only water-level records and no daily flow records, mark it as LEVEL_ONLY. If daily flow records for May–October of that year are complete, mark it as PASS. If daily flow records are absent or any month from May to October has incomplete records, mark it as FLOW_GAP. Only when both 1955 and 1956 meet the complete daily flow condition should final_verdict be KEEP; otherwise, it should be REJECT.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a table with columns: rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict.","oracle_answer":"1|08NA045|COLUMBIA RIVER NEAR FAIRMONT HOT SPRINGS|PASS|PASS|KEEP\n2|08NA004|COLUMBIA RIVER AT ATHALMER|LEVEL_ONLY|LEVEL_ONLY|REJECT\n3|08NA052|COLUMBIA RIVER NEAR EDGEWATER|PASS|FLOW_GAP|REJECT\n4|08NA002|COLUMBIA RIVER AT NICHOLSON|PASS|PASS|KEEP\n5|08NB005|COLUMBIA RIVER AT DONALD|PASS|PASS|KEEP\n6|08NB006|COLUMBIA RIVER AT SURPRISE RAPIDS|PASS|PASS|KEEP\n7|08ND007|COLUMBIA RIVER ABOVE NAGLE CREEK|PASS|PASS|KEEP\n8|08ND011|COLUMBIA RIVER ABOVE STEAMBOAT RAPIDS|FLOW_GAP|PASS|REJECT\n9|08ND006|COLUMBIA RIVER AT TWELVE MILE FERRY|PASS|PASS|KEEP\n10|08NE002|COLUMBIA RIVER AT CASTLEGAR|LEVEL_ONLY|LEVEL_ONLY|REJECT\n11|08NE049|COLUMBIA RIVER AT BIRCHBANK|PASS|PASS|KEEP\n12|08NE003|COLUMBIA RIVER AT TRAIL|LEVEL_ONLY|LEVEL_ONLY|REJECT\n13|08NE058|COLUMBIA RIVER AT INTERNATIONAL BOUNDARY|PASS|PASS|KEEP","metadata":"{\"State-Gated Retrieval\":[\"All candidate Columbia River stations must be checked on their availability page to confirm that the target years appear in the Flow table and that May–October is marked entirely as C.\",\"For each station, provide the KEEP/REJECT basis for both 1955 and 1956, distinguishing LEVEL_ONLY and FLOW_GAP cases from stations that only appear eligible from their overall year span.\",\"The final table must preserve the order and fields specified in the task.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the Columbia River candidate ordering yields fourteen stations spanning the target years\",\"each availability page yields whether 1955 and 1956 are present in the Flow table and whether May-October is complete\",\"final rows are produced only after every station is classified under the stricter Flow-table-and-May-Oct-C rule\"],\"control_dependency\":[\"list-level year spans must be confirmed by the availability page inside the Flow table\",\"LEVEL_ONLY and FLOW_GAP evidence must be applied to each station before the KEEP/REJECT table is finalized\",\"station-by-station verdicts and rejection reasons must be determined only after the full availability-page rule replaces the initial year-span screen\"],\"freeze\":{\"historical_window\":\"the ordered Columbia River candidates tested within the fixed historical Flow-availability windows for 1955 and 1956, with May-October complete-C coverage used as nearly stable reference information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"All candidate Columbia River stations must be checked on their availability page to confirm that the target years appear in the Flow table and that May–October is marked entirely as C.\",\"For each station, provide the KEEP/REJECT basis for both 1955 and 1956, distinguishing LEVEL_ONLY and FLOW_GAP cases from stations that only appear eligible from their overall year span.\",\"The final table must preserve the order and fields specified in the task.\"],\"exclusion_conditions\":[\"Exclude results that retain a station solely because its overall period spans 1955/1956.\",\"Exclude results that fail to distinguish, station by station, between Flow-available, Level-only, and incomplete-month cases.\",\"Exclude results that do not apply the full availability-page rule uniformly to all 14 stations.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"station_number\",\"station_name\",\"1955_MayOct\",\"1956_MayOct\",\"final_verdict\"],\"rank\":\"use the fixed upstream-to-downstream Columbia mainstem order from the reference index, not the transient search-result order\",\"year_window_fields\":\"the two year-window fields emit only PASS, LEVEL_ONLY, or FLOW_GAP\",\"final_verdict\":\"emit `KEEP` or `REJECT` exactly\"}}","all_involved_urls":"null"} +{"task_id":"wateroffice_005-g","domain":"WATER_OFFICE","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am organizing historical daily-flow records for the Peace River reach from Dunvegan Bridge to Fifth Meridian and want a three-row diagnostic table for the furthest-downstream reusable mainstem station, the first downstream failing station after it, and the provisional terminal station that an initial screen would misclassify as the downstream winner. If the target window satisfies the complete daily-flow condition, mark it as PASS. If the target year has only level records, mark it as LEVEL_ONLY. If daily-flow records exist but any target month from May through September is incomplete, mark it as FLOW_GAP. If the target year has neither daily-flow nor level records, mark it as NO_TARGET_RECORD. Output three rows with columns rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count.","start_url":"https://wateroffice.ec.gc.ca/search/historical_e.html","output_format":"Output a three-row diagnostic table with columns rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count.","oracle_answer":"1|07HA001|FINAL_STATION|PASS|5|2\n2|07HD001|FIRST_BREAK_AFTER_FINAL|FLOW_GAP|5|2\n3|07KA002|PROVISIONAL_STATION|FLOW_GAP|5|2","metadata":"{\"State-Gated Retrieval\":[\"Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian.\",\"A genuinely reusable station must satisfy the availability-page rule that both 1966 and 1967 appear in the Flow table and that every month from May through September is complete.\",\"The final output must jointly report FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION, while repeating provisional_count and final_count in every row.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the Peace River mainstem chain between Dunvegan Bridge and Fifth Meridian yields the initial station list and the downstream breakpoint positions that need revalidation\",\"each availability page yields whether 1966 and 1967 are present in the Flow or Level tables and whether May-September is complete\",\"final rows are produced only after the final station, the first downstream failure, and the provisional downstream winner are all fixed under the same availability-page validation rule\"],\"control_dependency\":[\"station-level target-year Flow evidence must be validated by explicit May-September completeness checks on the availability page\",\"the final downstream reusable station and the first downstream failure must be determined under the same validation rule rather than from the initial station screen\",\"the provisional downstream winner is kept in the output only for reference after its FLOW_GAP status is confirmed on the availability page\"],\"freeze\":{\"historical_window\":\"the Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian, evaluated within the fixed historical 1966 and 1967 Flow-availability windows, with May-September complete-C coverage used as nearly stable reference information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Screen only among Peace River mainstem stations between Dunvegan Bridge and Fifth Meridian.\",\"A genuinely reusable station must satisfy the availability-page rule that both 1966 and 1967 appear in the Flow table and that every month from May through September is complete.\",\"The final output must jointly report FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION, while repeating provisional_count and final_count in every row.\"],\"exclusion_conditions\":[\"Exclude results that treat a station as usable simply because the target years have Flow records.\",\"Exclude results that do not verify completeness month by month from May through September.\",\"Exclude results that mark a station such as 07KA002 as FINAL_STATION when availability-page evidence shows FLOW_GAP.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"station_number\",\"diagnosis_role\",\"target_window_status\",\"provisional_count\",\"final_count\"],\"rank\":\"emit the fixed order 1, 2, 3 for FINAL_STATION, FIRST_BREAK_AFTER_FINAL, and PROVISIONAL_STATION\",\"station_number\":\"use uppercase WSC station codes exactly as the Reference Index and availability pages show\",\"diagnosis_role\":[\"FINAL_STATION\",\"FIRST_BREAK_AFTER_FINAL\",\"PROVISIONAL_STATION\"],\"target_window_status\":[\"PASS\",\"LEVEL_ONLY\",\"FLOW_GAP\",\"NO_TARGET_RECORD\"],\"count_fields\":\"repeat the global provisional_count and final_count in every row as plain integers\",\"sorting_or_selection\":\"emit rows in the fixed diagnostic order FINAL_STATION, FIRST_BREAK_AFTER_FINAL, PROVISIONAL_STATION\"}}","all_involved_urls":"null"} +{"task_id":"waterquality_001-g","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am compiling historical monitoring data for the middle Rio Grande and need to identify two monitoring locations suitable as sentinel sites for main-channel wastewater impacts. From the monitoring locations downstream of RIO GRANDE AT EMBUDO, NM that are confirmed to be on the Rio Grande mainstem, select two qualifying stations: the upstream station must be downstream of the Town of Bernalillo wastewater treatment plant outfall; the downstream station must be downstream of both the Town of Bernalillo and Rio Rancho No. 2 wastewater treatment plant outfalls. Both stations must simultaneously meet the following conditions: the station itself is not an outfall, facility, well, canal, or drainage ditch; the station type is labeled as River/Stream; records for Microbiological, Nutrient, Organics, Other, and Physical are all complete for 2015—2020; and the start years for Microbiological and Physical records are both earlier than 2010. If multiple mainstem stations in a given segment meet the conditions, select the one farthest upstream along the main channel. Output a single line in upstream-to-downstream order in the format ||, with the two segments separated by a comma.","start_url":"https://www.waterqualitydata.us/","output_format":"Output a single line in upstream-to-downstream order in the format ||, with the two segments separated by a comma.","oracle_answer":"SANDIAWQ_WQX-RG003|2004|2004,SANDIAWQ_WQX-RG008|2004|2004","metadata":"{\"State-Gated Retrieval\":[\"Select two target stations only from Rio Grande mainstem monitoring stations downstream of RIO GRANDE AT EMBUDO, NM, and require both to be past the specified outfall locations.\",\"The station detail page must explicitly indicate River/Stream, and records for Microbiological, Nutrient, Organics, Other, and Physical must fully cover 2015—2020, with start years for Microbiological and Physical both earlier than 2010.\",\"Output the two stations in upstream-to-downstream order.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Provider/list views yield the Rio Grande mainstem candidates downstream of the Bernalillo and Rio Rancho No. 2 discharge points.\",\"Detail pages yield flow position, location type, characteristic-group period-of-record coverage for 2015—2020, and the Microbiological/Physical baseline years.\",\"Final rows are produced only after the corrected downstream sentry stations are fixed and ordered from upstream to downstream.\"],\"control_dependency\":[\"Provider-list stream tags are only provisional and must be confirmed on the detail page by both mainstem placement and location type.\",\"Target-window presence is insufficient until full 2015—2020 coverage is confirmed on the detail page for all four groups.\",\"Once RG002/RG007 fail the full detail-page checks, the workflow must continue downstream from the discharge-point starting position to RG003/RG008.\"],\"freeze\":{\"historical_window\":\"Rio Grande mainstem stations downstream of the Town of Bernalillo and Rio Rancho No. 2 WWTP outfalls, validated against 2015—2020 coverage for Microbiological, Nutrient, Organics, Other, and Physical.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Select two target stations only from Rio Grande mainstem monitoring stations downstream of RIO GRANDE AT EMBUDO, NM, and require both to be past the specified outfall locations.\",\"The station detail page must explicitly indicate River/Stream, and records for Microbiological, Nutrient, Organics, Other, and Physical must fully cover 2015—2020, with start years for Microbiological and Physical both earlier than 2010.\",\"Output the two stations in upstream-to-downstream order.\"],\"exclusion_conditions\":[\"Exclude stations that have a shallow (Stream) tag on the provider list or records near the target window, but whose detail page does not satisfy flow position, location type, or full period-of-record conditions.\",\"Exclude locations that are outfalls, facilities, wells, canals, or drainage ditches.\",\"Exclude candidates such as RG002 and RG007 that are not qualified sentinel stations downstream of the corresponding outfalls.\"],\"normalization\":{\"record_separator\":\",\",\"field_separator\":\"|\",\"schema_per_record\":[\"MonitoringLocationIdentifier\",\"Microbiological_start_year\",\"Physical_start_year\"],\"ordering\":\"emit exactly two records from upstream to downstream\",\"station_id\":\"use uppercase MonitoringLocationIdentifier\",\"year_fields\":\"emit four-digit years as plain integers\",\"selection\":{\"record_1\":\"the first qualifying mainstem station below the Bernalillo outfall\",\"record_2\":\"the first qualifying mainstem station below both the Bernalillo and Rio Rancho No. 2 outfalls\"},\"stop_condition\":[\"the Bernalillo branch stops only after its first qualifying mainstem station is fixed\",\"the Rio Rancho No. 2 branch stops only after its first qualifying mainstem station is fixed\",\"the two segments are emitted as one comma-joined line in upstream-to-downstream order\"]}}","all_involved_urls":"null"} +{"task_id":"waterquality_002-g","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":2,"instruction":"I am analyzing trends in the lower Rio Grande from 2001 to 2010. From monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002, select one representative station for Hidalgo County and one for Cameron County. Each station must satisfy all of the following conditions: located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002; the monitoring location type on the station detail page must be River/Stream; and records for all four characteristic groups—Microbiological, Nutrient, Organics, Other, and Physical—must cover the period 2001–2010. If multiple stations in the same county qualify, select the one with the earliest year in which all four groups are simultaneously present. Output a single line with the Hidalgo segment first and the Cameron segment second, using the format :|||||, with the two segments separated by a comma.","start_url":"https://www.waterqualitydata.us/","output_format":"Output a single line with the Hidalgo segment first and the Cameron segment second, using the format :|||||, with the two segments separated by a comma.","oracle_answer":"Hidalgo:TCEQMAIN-15808|1998|1998|1998|1998|1998,Cameron:TCEQMAIN-13177|1995|1981|1981|1995|1981","metadata":"{\"State-Gated Retrieval\":[\"Select one representative station for Hidalgo County and one for Cameron County only from monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002.\",\"Candidate detail pages must show River/Stream as the monitoring location type, and records for all four characteristic groups—Microbiological, Nutrient, Organics, Other, and Physical—must cover 2001–2010.\",\"If multiple stations in the same county qualify, select the one with the earliest year in which all four groups are simultaneously present.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the fixed downstream starting point and county split yield Hidalgo and Cameron candidate mainstem stations within HUC 13090002\",\"detail pages yield River/Stream validity, the four characteristic-group start years, and the earliest year when all four groups are simultaneously present for 2001-2010 coverage\",\"final rows are produced only after the county-specific searches are rerun from the fixed downstream starting point and then ranked by common-start year\"],\"control_dependency\":[\"the Hidalgo search must preserve the \\\"below TCEQMAIN-13664\\\" downstream starting point rather than returning to the anchor station itself\",\"a station is only provisional until all four characteristic groups are confirmed for the same MonitoringLocationIdentifier and tidal/intake conflicts are excluded on the detail page\",\"county winners are valid only after late-start and non-river candidates are removed and the common-start-year tie-break is recomputed\"],\"freeze\":{\"historical_window\":\"stations below RIO GRANDE BELOW ANZALDUAS within HUC 13090002, split by Hidalgo and Cameron County, with Microbiological, Nutrient, Organics, Other, and Physical coverage over 2001-2010\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Select one representative station for Hidalgo County and one for Cameron County only from monitoring stations located below RIO GRANDE BELOW ANZALDUAS and still within HUC 13090002.\",\"Candidate detail pages must show River/Stream as the monitoring location type, and records for all four characteristic groups—Microbiological, Nutrient, Organics, Other, and Physical—must cover 2001–2010.\",\"If multiple stations in the same county qualify, select the one with the earliest year in which all four groups are simultaneously present.\"],\"exclusion_conditions\":[\"Exclude results where the Hidalgo search loses the downstream starting point and brings the starting station itself back into the candidate set.\",\"Exclude results that treat a single multi-select of the four characteristic groups as sufficient without verifying that all four belong to the same station ID.\",\"Exclude stations with tidal, intake, late-start, or other conflicts clearly indicated on the detail page.\"],\"normalization\":{\"record_separator\":\",\",\"field_separator\":\"|\",\"schema_per_record\":[\"County:MonitoringLocationIdentifier\",\"common_start_year\",\"Microbiological_start_year\",\"Nutrient_start_year\",\"Organics_Other_start_year\",\"Physical_start_year\"],\"ordering\":\"emit exactly two records, with Hidalgo first and Cameron second\",\"county_prefix\":\"use the county label in title case, followed by : and the uppercase MonitoringLocationIdentifier\",\"year_fields\":\"emit four-digit years as plain integers\",\"common_start_year\":\"the earliest year in which all four required groups are simultaneously present for the chosen county station\",\"stop_condition\":[\"each county branch is rerun until one River/Stream station survives all four group checks\",\"the county winner is fixed only after late-start and non-river candidates are excluded on the detail page\",\"the two county segments are emitted on one line in the fixed Hidalgo-then-Cameron order\"]}}","all_involved_urls":"null"} +{"task_id":"waterquality_003-g","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am compiling 2012–2018 water-quality reference data for the Brazos River mainstem downstream of Brazos Rv at Waco, TX. For each of the three specified HUCs that include Waco (12060202, 12070101, 12070104), I need to identify one TCEQ monitoring station suitable as a long-term reference for 2012–2018 along the Brazos River mainstem downstream of Brazos Rv at Waco, TX. Candidate stations must satisfy all of the following: be located within the corresponding HUC; have a monitoring-location type of River/Stream on the station detail page; have a station name that still corresponds to the Brazos River mainstem, not a tributary or other named waterbody; and have records covering 2012–2018 for all five characteristic groups—Inorganics, Major, Non-metals; Microbiological; Nutrient; Organics, Other; and Physical—meaning the station’s start year is no later than 2012 and its end year is no earlier than 2018. List the three results in upstream-to-downstream order, one per line, using the format: |||||||.","start_url":"https://www.waterqualitydata.us/","output_format":"List the three results in upstream-to-downstream order, one per line, using the format: |||||||.","oracle_answer":"12060202|TCEQMAIN-12037|2000|1991|2000|1991|1999|1991\n12070101|TCEQMAIN-12030|2006|1972|1972|1972|2006|1972\n12070104|TCEQMAIN-11848|1975|1974|1975|1974|1975|1974","metadata":"{\"State-Gated Retrieval\":[\"The search must stay anchored downstream of Waco and look for Brazos mainstem monitoring stations within the three HUCs specified in the task.\",\"Each candidate station must be checked separately across the five characteristic groups and then matched back to the same station ID, after which the detail page must verify full 2012–2018 coverage and mainstem semantics.\",\"For each HUC, retain only the qualifying station with the earliest common start year, and output the start-year fields required by the task.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the fixed downstream starting point below Waco and the three target HUC searches yield the Brazos mainstem candidate stations\",\"detail pages yield true downstream position, mainstem-vs-tributary semantics, and five-group period-of-record coverage across 2012-2018\",\"final rows are produced only after the three HUC-specific searches are carried out, matched by station ID, and ranked by the earliest year when all five groups are jointly available\"],\"control_dependency\":[\"the workflow must stay anchored downstream of Waco rather than reintroducing upstream stations such as TCEQMAIN-12044\",\"name-based waterbody matches must be validated on the detail page by excluding tributaries such as LITTLE BRAZOS RIVER and confirming full-window coverage\",\"station ranking must be determined after false positives from partial-window records are removed\"],\"freeze\":{\"historical_window\":\"Brazos River mainstem stations downstream of the Waco anchor evaluated within the fixed historical 2012-2018 window, using the HUC 12060202 / 12070101 / 12070104 split and five characteristic groups as largely stable reference information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"The search must stay anchored downstream of Waco and look for Brazos mainstem monitoring stations within the three HUCs specified in the task.\",\"Each candidate station must be checked separately across the five characteristic groups and then matched back to the same station ID, after which the detail page must verify full 2012–2018 coverage and mainstem semantics.\",\"For each HUC, retain only the qualifying station with the earliest common start year, and output the start-year fields required by the task.\"],\"exclusion_conditions\":[\"Exclude results that lose the downstream starting point below Waco and bring upstream stations back into the candidate set.\",\"Exclude results that mistakenly treat tributaries such as LITTLE BRAZOS RIVER as the Brazos mainstem.\",\"Exclude stations that have data near the query window but do not cover the entire 2012–2018 window.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"HUC\",\"MonitoringLocationIdentifier\",\"common_start_year\",\"Inorganics_start\",\"Microbiological_start\",\"Nutrient_start\",\"Organics_Other_start\",\"Physical_start\"],\"HUC\":\"preserve the HUC exactly as emitted in the source result\",\"MonitoringLocationIdentifier\":\"preserve the monitoring-location identifier exactly, for example `TCEQMAIN-12037`\",\"common_start_year\":\"emit the maximum of the five per-group start years\",\"selection_rule\":\"only keep mainstem river/stream sites whose five required groups all cover the target 2012-2018 window\",\"sorting_or_selection\":\"upstream to downstream along the mainstem\"}}","all_involved_urls":"null"} +{"task_id":"waterquality_004-g","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"I am reviewing toxic-pollutant-related water quality monitoring data for the Trinity River mainstem from 1993 to 2001, with the reach near FM 85 as the upstream boundary and the reach near Interstate 10 as the downstream boundary. I need to select one TCEQ long-term reference station for each of the upper, middle, and lower segments along the river.\nCandidate monitoring locations must simultaneously meet the following conditions: the monitoring location type in the station record is labeled River/Stream; the station name corresponds to the Trinity River mainstem, not a tributary, other named waterbody, or distributary channel; records for all six characteristic groups—Inorganics, Major, Non-metals; Microbiological; Nutrient; Organics, Other; Organics, PCBs; and Physical—must cover the period 1993–2001, specifically with a start year no later than 1993 and an end year no earlier than 2001. Output three rows in order from upstream to downstream along the river, each row formatted as ||||||||.","start_url":"https://www.waterqualitydata.us/","output_format":"Output three rows in order from upstream to downstream along the river, each row formatted as ||||||||.","oracle_answer":"12030105|TCEQMAIN-10924|1983|1982|1983|1982|1983|1983|1982\n12030202|TCEQMAIN-10897|1993|1969|1972|1972|1993|1974|1969\n12030203|TCEQMAIN-10892|1976|1969|1971|1972|1974|1976|1969","metadata":"{\"State-Gated Retrieval\":[\"Only retain candidate stations that satisfy the Trinity River mainstem semantics and require all six characteristic groups to cover 1993–2001.\",\"The six groups must be searched separately and then matched back to the same station ID, after which the detail page must verify full time-window coverage and completeness of the legacy toxics groups.\",\"For each target segment, retain only the station that meets all group requirements and has the best common start year.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Trinity River mainstem candidate stations are generated from the target HUC searches and the six characteristic-group searches\",\"detail pages yield River/Stream validity, 1993–2001 full-window coverage, and the group-specific start years needed for ranking\",\"final rows are produced only after all six groups have been matched by station ID and detail-page validation removes partial-group and non-mainstem false positives\"],\"control_dependency\":[\"each of the six characteristic groups must be evaluated separately and confirmed against the same station ID before a multi-select result can be retained\",\"station names and River/Stream tags are insufficient until the detail page confirms Trinity mainstem semantics and 1993–2001 full-window coverage\",\"candidate rejection and final ranking must be determined after applying the PCBs / Organics, Other gap checks\"],\"freeze\":{\"historical_window\":\"Trinity River mainstem stations validated within the fixed historical 1993–2001 window, using six characteristic groups and ranking by earliest joint availability plus group start years as largely stable reference information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Only retain candidate stations that satisfy the Trinity River mainstem semantics and require all six characteristic groups to cover 1993–2001.\",\"The six groups must be searched separately and then matched back to the same station ID, after which the detail page must verify full time-window coverage and completeness of the legacy toxics groups.\",\"For each target segment, retain only the station that meets all group requirements and has the best common start year.\"],\"exclusion_conditions\":[\"Exclude results that mistakenly treat a single multi-select of characteristic groups as sufficient to satisfy the requirement.\",\"Exclude results that only check station names and River/Stream tags without verifying 1993–2001 full-window coverage.\",\"Exclude stations that ignore missing PCBs or Organics, Other groups.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"HUC\",\"MonitoringLocationIdentifier\",\"common_start_year\",\"Inorganics_start\",\"Microbiological_start\",\"Nutrient_start\",\"Organics_Other_start\",\"Organics_PCBs_start\",\"Physical_start\"],\"HUC\":\"preserve the HUC exactly as emitted in the source result\",\"MonitoringLocationIdentifier\":\"preserve the monitoring-location identifier exactly, for example `TCEQMAIN-10924`\",\"common_start_year\":\"emit the maximum of the six per-group start years\",\"selection_rule\":\"only keep mainstem river/stream sites whose six required groups all cover the target window\",\"sorting_or_selection\":\"upstream to downstream along the mainstem\"}}","all_involved_urls":"null"} +{"task_id":"waterquality_005-g","domain":"WATER_QUALITY_PORTAL","autonomy_type":"ordered table","oracle_output_cardinality":9,"instruction":"I am organizing integrated water-quality records for the lower Neches River during 1978-1984 and want a table of the nine Characteristic Group start years for the nearest qualifying TCEQ reference station downstream of NECHES RIVER AT CR 4915 that still represents the inland Neches River mainstem. Output a 9-row table with columns rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year, using the fixed nine-group order specified in the task.","start_url":"https://www.waterqualitydata.us/provider/STORET/TCEQMAIN/TCEQMAIN-10598/","output_format":"Output a 9-row table with columns rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year.","oracle_answer":"1|TCEQMAIN-10580|12020003|Hardin County|Biological, Algae, Phytoplankton|1972|1977\n2|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Major, Non-metals|1971|1977\n3|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Minor, Metals|1974|1977\n4|TCEQMAIN-10580|12020003|Hardin County|Microbiological|1972|1977\n5|TCEQMAIN-10580|12020003|Hardin County|Nutrient|1972|1977\n6|TCEQMAIN-10580|12020003|Hardin County|Organics, Other|1974|1977\n7|TCEQMAIN-10580|12020003|Hardin County|Organics, PCBs|1974|1977\n8|TCEQMAIN-10580|12020003|Hardin County|Organics, Pesticide|1977|1977\n9|TCEQMAIN-10580|12020003|Hardin County|Physical|1971|1977","metadata":"{\"State-Gated Retrieval\":[\"Search only among TCEQ monitoring stations downstream of NECHES RIVER AT CR 4915 that still represent the inland Neches River mainstem.\",\"A candidate station must cover 1978-1984 in all nine Characteristic Groups and, on the detail page, must still qualify as River/Stream, outside lake or reservoir waters, and outside the Sabine-Neches outlet boundary reach.\",\"The final output must be centered on the single winning station and list group_start_year plus common_start_year row by row in the fixed nine-group order.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"the fixed downstream starting point at NECHES RIVER AT CR 4915 yields candidate inland mainstem stations across successive downstream HUCs\",\"detail pages yield River/Stream validity, inland-vs-boundary semantics, and nine-group period-of-record coverage across 1978-1984\",\"final rows are produced only after one winning station survives the inland-mainstem checks and the requirement that all nine groups match the same station, after which its nine group start years are emitted in the required order\"],\"control_dependency\":[\"the nearest downstream mainstem station remains provisional until all nine characteristic groups have been checked separately and matched back to the same station ID\",\"the downstream search must continue to the next mainstem HUC when the first candidate fails the nine-group coverage requirement\",\"location semantics remain valid only after detail-page exclusion of lake/reservoir and Sabine-Neches boundary stations\"],\"freeze\":{\"historical_window\":\"Neches River inland mainstem stations downstream of NECHES RIVER AT CR 4915, validated within the fixed 1978-1984 window against nine characteristic groups as largely stable reference information\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Search only among TCEQ monitoring stations downstream of NECHES RIVER AT CR 4915 that still represent the inland Neches River mainstem.\",\"A candidate station must cover 1978-1984 in all nine Characteristic Groups and, on the detail page, must still qualify as River/Stream, outside lake or reservoir waters, and outside the Sabine-Neches outlet boundary reach.\",\"The final output must be centered on the single winning station and list group_start_year plus common_start_year row by row in the fixed nine-group order.\"],\"exclusion_conditions\":[\"Exclude results that retain TCEQMAIN-10591 merely because it appears to be the nearest downstream mainstem station.\",\"Exclude results that do not check the nine Characteristic Groups separately and verify that they all belong to the same station ID.\",\"Exclude stations located in lake or reservoir waters or in the Sabine-Neches outlet boundary reach.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"omit the header row; emit data rows only\",\"schema\":[\"rank\",\"MonitoringLocationIdentifier\",\"HUC\",\"County\",\"characteristic_group\",\"group_start_year\",\"common_start_year\"],\"rank\":\"emit 1 through 9 in the fixed characteristic-group order required by the task\",\"MonitoringLocationIdentifier\":\"use uppercase MonitoringLocationIdentifier\",\"HUC\":\"emit the HUC as an 8-digit string with no separators\",\"County\":\"use the county name exactly as shown on the detail page\",\"characteristic_group\":\"preserve the group label exactly as listed in the task\",\"year_fields\":\"emit four-digit years as plain integers\",\"common_start_year\":\"repeat the earliest year in which all nine required groups are simultaneously present for the chosen station\",\"sorting_or_selection\":\"emit rows in the fixed nine-group order stated in the task\"}}","all_involved_urls":"null"} +{"task_id":"wonder_003-g","domain":"CDC_WONDER","autonomy_type":"ordered table","oracle_output_cardinality":8,"instruction":"For a public-health brief reviewing changes in U.S. home births in 2020, identify the months in which the home-birth rate among all mothers rose at least 25% compared with the same month in 2019. For those months, also provide the 2020 home-birth rates and relative changes for non-Hispanic Black and Hispanic mothers. Output a pipe-delimited table in calendar-month order with the fixed header row month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel. Write all values as plain numbers without percent signs.","start_url":"https://wonder.cdc.gov/natality-expanded-current.html","output_format":"Output a pipe-delimited table in calendar-month order with the fixed header row month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel. Write all values as plain numbers without percent signs.","oracle_answer":"month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel\nMay|1.03|1.49|45|0.74|54|0.55|57\nJune|1.04|1.31|26|0.66|20|0.48|30\nJuly|1.03|1.30|26|0.68|42|0.48|30\nAugust|1.02|1.29|26|0.69|50|0.48|26\nSeptember|1.01|1.31|30|0.73|43|0.54|54\nOctober|1.00|1.28|28|0.75|50|0.47|27\nNovember|0.99|1.30|31|0.73|43|0.55|67\nDecember|0.92|1.28|39|0.80|63|0.53|61","metadata":"{\"State-Gated Retrieval\":[\"Compare the home-birth rates for all mothers in 2019 and 2020 by calendar month, retaining only months where the 2020 rate increased at least 25% relative to the same month in 2019.\",\"The home-birth numerator must use the full home category, not Home intended alone.\",\"For those qualifying months, also retrieve the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, along with their relative changes from the same month in 2019.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Monthly natality queries yield the 2019 vs 2020 home-birth rates for all mothers and the candidate month set.\",\"Follow-up race/ethnicity queries yield the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, plus their same-month changes versus 2019.\",\"Final rows are produced only after qualifying months are determined from rate growth, and the resulting month set is reused for both subgroup backfill chains.\"],\"control_dependency\":[\"Month selection must be based on relative rate increase rather than counts alone.\",\"The home-birth numerator must use Residence or an equivalent full-home measure rather than Home intended alone before downstream subgroup queries run.\",\"Subgroup columns must be generated from the resulting month set rather than appended to earlier rows.\"],\"freeze\":{\"historical_window\":\"2019 and 2020 U.S. natality monthly home-birth rates for all mothers, non-Hispanic Black mothers, and Hispanic mothers.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Compare the home-birth rates for all mothers in 2019 and 2020 by calendar month, retaining only months where the 2020 rate increased at least 25% relative to the same month in 2019.\",\"The home-birth numerator must use the full home category, not Home intended alone.\",\"For those qualifying months, also retrieve the 2020 home-birth rates for non-Hispanic Black and Hispanic mothers, along with their relative changes from the same month in 2019.\"],\"exclusion_conditions\":[\"Exclude month-row sets that misinterpret \\\"rate increase of at least 25%\\\" as \\\"count increase of at least 25%.\\\"\",\"Exclude results that use only the Home intended category instead of the full home numerator.\",\"Exclude results that append subgroup columns based on an incorrect month set.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"required literal first row `month|all_2019|all_2020|all_rel|black_2020|black_rel|hispanic_2020|hispanic_rel`\",\"schema\":[\"month\",\"all_2019\",\"all_2020\",\"all_rel\",\"black_2020\",\"black_rel\",\"hispanic_2020\",\"hispanic_rel\"],\"month\":\"use the English month name and keep calendar order\",\"numeric_fields\":\"all numeric outputs are plain numbers without a percent sign\",\"relative_change_fields\":\"all_rel, black_rel, and hispanic_rel are emitted as integer percentages without the `%` character\"}}","all_involved_urls":"null"} +{"task_id":"wonder_004-g","domain":"CDC_WONDER","autonomy_type":"ordered table","oracle_output_cardinality":3,"instruction":"From the 2021 U.S. infant mortality statistics by mother's race and Hispanic origin, identify all groups that are reported separately, have an infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death. For each qualifying group, provide the infant mortality rate, neonatal mortality rate (under 28 days), postneonatal mortality rate (28 days and older), the group's leading cause of death, the cause-specific rate, and the rank of that cause among all infant causes. Output a multi-row pipe-delimited table sorted by infant mortality rate descending, using the format: group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank.","start_url":"https://wonder.cdc.gov/lbd-current-expanded.html","output_format":"Output a multi-row pipe-delimited table sorted by infant mortality rate descending, using the format: group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank.","oracle_answer":"group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank\nnon-Hispanic Black|10.55|6.35|4.19|Short gestation and low birth weight|196.4|2\nnon-Hispanic American Indian or Alaska Native|7.46|3.83|3.67|Congenital malformations|134.0|1\nPuerto Rican|6.05|3.93|2.13|Short gestation and low birth weight|108.9|2","metadata":"{\"State-Gated Retrieval\":[\"Retain only groups that are reported separately in the 2021 U.S. infant mortality statistics, have an infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death.\",\"For each qualifying group, provide the infant rate, neonatal rate, postneonatal rate, top cause, cause rate, and the rank of that cause among all infant causes.\",\"The leading cause must be determined by a group-level leading-cause query and verified using notes/reliability flags.\"],\"dependency_type\":\"Data + Control\",\"intra_chain\":true,\"inter_chain\":true,\"data_dependency\":[\"Infant-mortality queries yield group-level overall, neonatal, and postneonatal rates for reportable mother race/Hispanic-origin groups.\",\"Leading-cause queries and reliability notes yield each eligible group's top cause, cause-specific rate, and U.S. rank.\",\"Final rows are produced only after the eligible-group set is rebuilt using both overall-rate and cause-specific-identifiability criteria.\"],\"control_dependency\":[\"Groups above the U.S. overall rate cannot be accepted until cause-specific reliability checks are run, which removes NHOPI.\",\"Leading cause must be queried at the group level rather than inherited from an all-infants cause table.\",\"The cause-rate multiplier must be defined as per 100,000 live births before downstream ranking/output.\"],\"freeze\":{\"historical_window\":\"2021 U.S. infant mortality by mother race and Hispanic origin, including the group-level leading-cause tables and reliability notes.\"},\"answer_type\":\"multi-row ordered table\"}","rubric":"{\"inclusion_conditions\":[\"Retain only groups that are reported separately in the 2021 U.S. infant mortality statistics, have an infant mortality rate above the U.S. overall rate, and have a clearly identifiable leading cause of death.\",\"For each qualifying group, provide the infant rate, neonatal rate, postneonatal rate, top cause, cause rate, and the rank of that cause among all infant causes.\",\"The leading cause must be determined by a group-level leading-cause query and verified using notes/reliability flags.\"],\"exclusion_conditions\":[\"Exclude groups that, despite having an infant mortality rate above the U.S. overall rate, cannot provide a clearly identifiable leading cause due to cause-specific reliability issues.\",\"Exclude results that inherit the top cause only from the all-infants cause table without performing a group-level leading-cause query.\",\"Exclude results where the cause rate uses an incorrect rate multiplier and is not read per 100,000 live births.\"],\"normalization\":{\"field_separator\":\"|\",\"record_separator\":\"\\n\",\"header_row\":\"required literal first row `group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank`\",\"schema\":[\"group\",\"infant_rate\",\"neonatal_rate\",\"postneonatal_rate\",\"top_cause\",\"cause_rate\",\"us_rank\"],\"sorting_or_selection\":\"infant_rate descending\",\"rate_fields\":\"infant_rate, neonatal_rate, and postneonatal_rate are per 1,000 live births; cause_rate is per 100,000 live births, but all four are emitted as plain numbers without unit text\",\"top_cause\":\"emit the short cause label used in the oracle, not an expanded prose description\",\"us_rank\":\"emit the integer rank of that same cause in the overall infant leading-cause list\"}}","all_involved_urls":"null"}