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: <legacy label>|<accepted>|<bridge>|<type status>|<type code>|<country>; separate entries with semicolons; if no qualifying entries exist, output NONE.

Output a single line with entries sorted alphabetically by legacy label: <legacy label>|<accepted>|<bridge>|<type status>|<type code>|<country>; separate entries with semicolons; if no qualifying entries exist, output NONE.

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

{"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"}

{"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."}}


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.

Output a two-row comparison table with columns rank|name_role|name|status_or_evidence|specimen_role|specimen_code|supporting_note.

1|ACCEPTED_NAME|Naja naja|SUBJECTIVE_JUNIOR_SYNONYM_OF_NAJA_NAJA|VALID_LECTOTYPE|ZMB 2796|restricted type locality: Sri Lanka
2|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

{"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"}

{"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"}}


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.

Output a two-row breakpoint table with columns rank|station_number|breakpoint_role|target_window_status|final_verdict.

{"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"}

{"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"]}}


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.

Output a table in downstream-to-upstream order with columns rank|station_number|target_window_status|final_verdict.

1|08EE004|PASS|KEEP
2|08EE001|LEVEL_ONLY|REJECT
3|08EE005|FLOW_GAP|REJECT
4|08EE003|FLOW_GAP|REJECT

{"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"}

{"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"]}}


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.

Output a table with columns rank|station_number|station_name|1958_MayJul|1971_MayJul|final_verdict, ordered downstream from Chase to Spences Bridge.

1|08LE031|SOUTH THOMPSON RIVER AT CHASE|PASS|PASS|KEEP
2|08LE069|SOUTH THOMPSON RIVER AT MONTE CREEK|FLOW_GAP|LEVEL_ONLY|REJECT
3|08LF023|THOMPSON RIVER AT KAMLOOPS|LEVEL_ONLY|LEVEL_ONLY|REJECT
4|08LF033|THOMPSON RIVER NEAR SAVONA|FLOW_GAP|FLOW_GAP|REJECT
5|08LF051|THOMPSON RIVER NEAR SPENCES BRIDGE|PASS|PASS|KEEP

{"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"}

{"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"}}


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.

Output a table in upstream-to-downstream order with columns: rank|station_number|station_name|1955_MayOct|1956_MayOct|final_verdict.

1|08NA045|COLUMBIA RIVER NEAR FAIRMONT HOT SPRINGS|PASS|PASS|KEEP
2|08NA004|COLUMBIA RIVER AT ATHALMER|LEVEL_ONLY|LEVEL_ONLY|REJECT
3|08NA052|COLUMBIA RIVER NEAR EDGEWATER|PASS|FLOW_GAP|REJECT
4|08NA002|COLUMBIA RIVER AT NICHOLSON|PASS|PASS|KEEP
5|08NB005|COLUMBIA RIVER AT DONALD|PASS|PASS|KEEP
6|08NB006|COLUMBIA RIVER AT SURPRISE RAPIDS|PASS|PASS|KEEP
7|08ND007|COLUMBIA RIVER ABOVE NAGLE CREEK|PASS|PASS|KEEP
8|08ND011|COLUMBIA RIVER ABOVE STEAMBOAT RAPIDS|FLOW_GAP|PASS|REJECT
9|08ND006|COLUMBIA RIVER AT TWELVE MILE FERRY|PASS|PASS|KEEP
10|08NE002|COLUMBIA RIVER AT CASTLEGAR|LEVEL_ONLY|LEVEL_ONLY|REJECT
11|08NE049|COLUMBIA RIVER AT BIRCHBANK|PASS|PASS|KEEP
12|08NE003|COLUMBIA RIVER AT TRAIL|LEVEL_ONLY|LEVEL_ONLY|REJECT
13|08NE058|COLUMBIA RIVER AT INTERNATIONAL BOUNDARY|PASS|PASS|KEEP

{"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"}

{"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"}}


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.

Output a three-row diagnostic table with columns rank|station_number|diagnosis_role|target_window_status|provisional_count|final_count.

{"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"}

{"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"}}


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: <mainstem station ID>|<Microbiological start year>|<Physical start year>, with the two segments separated by a comma.

Output a single-line string in upstream-to-downstream order: <mainstem station ID>|<Microbiological start year>|<Physical start year>, with the two segments separated by a comma.

{"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"}

{"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"]}}


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: <County>:<MonitoringLocationIdentifier>|<common_start_year>|<Microbiological_start_year>|<Nutrient_start_year>|<Organics_Other_start_year>|<Physical_start_year>, with the two segments separated by a comma.

Output a single-line string in the order Hidalgo then Cameron: <County>:<MonitoringLocationIdentifier>|<common_start_year>|<Microbiological_start_year>|<Nutrient_start_year>|<Organics_Other_start_year>|<Physical_start_year>, with the two segments separated by a comma.

{"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"}

{"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"]}}


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: <HUC>|<MonitoringLocationIdentifier>|<earliest year when all five categories are jointly available>|<Inorganics, Major, Non-metals start year>|<Microbiological start year>|<Nutrient start year>|<Organics, Other start year>|<Physical start year>.

List the 3 results in order from upstream to downstream, each row formatted as: <HUC>|<MonitoringLocationIdentifier>|<earliest year when all five categories are jointly available>|<Inorganics, Major, Non-metals start year>|<Microbiological start year>|<Nutrient start year>|<Organics, Other start year>|<Physical start year>.

{"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"}

{"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"}}


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.

Starting 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.

Finally, list three rows from upstream to downstream along the river, each in the format: <HUC>|<MonitoringLocationIdentifier>|<earliest year with all six categories>|<Inorganics, Major, Non-metals start year>|<Microbiological start year>|<Nutrient start year>|<Organics, Other start year>|<Organics, PCBs start year>|<Physical start year>.

List three rows from upstream to downstream along the river, each in the format: <HUC>|<MonitoringLocationIdentifier>|<earliest year with all six categories>|<Inorganics, Major, Non-metals start year>|<Microbiological start year>|<Nutrient start year>|<Organics, Other start year>|<Organics, PCBs start year>|<Physical start year>.

{"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"}

{"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"}}


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.

Output a 9-row table with columns rank|MonitoringLocationIdentifier|HUC|County|characteristic_group|group_start_year|common_start_year.

1|TCEQMAIN-10580|12020003|Hardin County|Biological, Algae, Phytoplankton|1972|1977
2|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Major, Non-metals|1971|1977
3|TCEQMAIN-10580|12020003|Hardin County|Inorganics, Minor, Metals|1974|1977
4|TCEQMAIN-10580|12020003|Hardin County|Microbiological|1972|1977
5|TCEQMAIN-10580|12020003|Hardin County|Nutrient|1972|1977
6|TCEQMAIN-10580|12020003|Hardin County|Organics, Other|1974|1977
7|TCEQMAIN-10580|12020003|Hardin County|Organics, PCBs|1974|1977
8|TCEQMAIN-10580|12020003|Hardin County|Organics, Pesticide|1977|1977
9|TCEQMAIN-10580|12020003|Hardin County|Physical|1971|1977

{"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"}

{"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"}}


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.

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.

{"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"}

{"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."}}


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.

group|infant_rate|neonatal_rate|postneonatal_rate|top_cause|cause_rate|us_rank
Black non-Hispanic|10.55|6.35|4.19|Short gestation and low birth weight|196.4|2
American Indian or Alaska Native non-Hispanic|7.46|3.83|3.67|Congenital malformations|134.0|1
Puerto Rican Hispanic|6.05|3.93|2.13|Short gestation and low birth weight|108.9|2

{"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"}

{"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"}}