{"id": "v27-valid-0000", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "NOVEMBER ONE SEVEN XRAY XRAY NUMBER TWO FOLLOW THE ARCHER ON SHORT FINAL over"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"sequencing\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0001", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven X-ray X-ray, San Carlos Tower, maintain pattern altitude one thousand, report midfield downwind."}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"altitude_instruction\", \"slots\": {\"altitude\": \"one thousand\"}, \"text\": \"\"}, {\"intent\": \"report_request\", \"slots\": {\"pattern_leg\": \"midfield downwind\"}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0002", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven X-ray X-ray, radar contact, climb and maintain three thousand, proceed direct SUNOL."}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"radar_identification\", \"slots\": {}, \"text\": \"\"}, {\"intent\": \"altitude_instruction\", \"slots\": {\"direction\": \"climb\", \"altitude\": \"3000\"}, \"text\": \"\"}, {\"intent\": \"direct_to\", \"slots\": {\"fix\": \"SUNOL\"}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0003", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven X-ray X-ray, make a left three sixty on downwind for spacing."}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"spacing_instruction\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0004", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven Xray Xray Make A Left Three Sixty On Downwind For Spacing Traffic Piper On Extended Base You'll Follow After Your Three Hundred Sixty"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"spacing_instruction\", \"slots\": {\"direction\": \"left\", \"pattern_leg\": \"downwind\"}, \"text\": \"\"}, {\"intent\": \"traffic_advisory\", \"slots\": {}, \"text\": \"\"}, {\"intent\": \"sequencing\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0005", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "runway two eight cleared to land"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"other\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0006", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "Lafayette Ground Ground. Warrior 31862. At general aviation parking. Ready to taxi, with information Whiskey. VFR."}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"taxi_instruction\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0007", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "TOWER NOVEMBER ONE SEVEN XRAY XRAY TEN MILES NORTH OF LAFAYETTE TWO THOUSAND FIVE HUNDRED INBOUND FOR LANDING AT LAFAYETTE"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"comm_request\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0008", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": ", you're number four, follow the Cherokee when he turns base"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"sequencing\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0009", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": ", extend downwind, traffic turning base"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"extend_downwind\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0010", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "N17XX LAFIETT TOWER CAUTION WIND SHEER REPORTED MAKE RIGHT TRAFFIC RUNWAY FIVE CLEARED FOR TAKEOFF"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"weather_advisory\", \"slots\": {}, \"text\": \"\"}, {\"intent\": \"pattern_entry\", \"slots\": {\"pattern_leg\": \"right traffic\"}, \"text\": \"\"}, {\"intent\": \"takeoff_clearance\", \"slots\": {\"runway\": \"five\"}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0011", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "TURN FINAL RUNWAY TWO EIGHT WIND THREE ZERO ZERO AT EIGHT CLEARED TO LAND ADS BE TRAFFIC CLEARED"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"other\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0012", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "REMAIN CLEAR TRAFFIC INBOUND OVER"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"other\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0013", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "2. TRAFFIC TO FOLLOW STRAIGHT IN RUNWAY TWO THREE NOVEMBER ONE SEVEN XRAY XRAY over"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"sequencing\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0014", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "Chicago Center NOVEMBER ONE SEVEN XRAY XRAY ONE TWO MILES NORTHWEST OF LAFIETTE AT ONE THOUSAND TWO HUNDRED REQUEST FLIGHT FOLLOWING INTO INDIANAPOLIS EAGLE CREEK"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"comm_request\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0015", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "All Aircraft Six In The Pattern Sequencing In Progress"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"informational\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0016", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "N17XX SAN CARLOS TOWER MAINTAIN PATTERN ALTITUDE ONE THOUSAND REPORT MIDFIELD DOWNWIND"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"altitude_instruction\", \"slots\": {\"altitude\": \"one thousand\"}, \"text\": \"\"}, {\"intent\": \"report_request\", \"slots\": {\"pattern_leg\": \"midfield downwind\"}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0017", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "ADIZ PENETRATION AHEAD MAINTAIN TWO WAY RADIO COMMUNICATION SQUAWK FOUR TWO THREE ONE MODE C REQUIRED"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"informational\", \"slots\": {}, \"text\": \"\"}, {\"intent\": \"squawk_code_set\", \"slots\": {\"transponder_code\": \"4231\"}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0018", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "traffic advisory aircraft at your one o'clock two miles no factor"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"traffic_advisory\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0019", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "All aircraft, Flight Service Station, VFR conditions"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"informational\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0020", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven X-ray X-ray, NorCal Departure, level two thousand five hundred, proceeding direct San Carlos"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"position_report\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0021", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "PALLO ALTO TRAFFIC N17XX SOUTHBOUND OFF PALLO ALTO ONE THOUSAND EIGHT HUNDRED ENGINE EMERGENCY REMAINING CLEARED OF THE PATTERN"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"ctaf_broadcast\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0022", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven X-ray X-ray, turn right heading one five zero, descend to two thousand, maintain VFR."}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"heading_instruction\", \"slots\": {\"direction\": \"right\", \"heading\": \"150\"}, \"text\": \"\"}, {\"intent\": \"altitude_instruction\", \"slots\": {\"direction\": \"descend\", \"altitude\": \"2000\"}, \"text\": \"\"}, {\"intent\": \"vfr_instruction\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0023", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "REMAIN CLEAR AIRCRAFT ON DEPARTURE OVER"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"other\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0024", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "Continue Downwind Traffic Bonanza On Final"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"traffic_advisory\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0025", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "Transition approved. November One Seven X-ray X-ray."}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"acknowledgment\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0026", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "NUMBER TWO FOLLOW THE ARCHER ON SHORT FINAL"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"sequencing\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0027", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven X-ray X-ray, resume normal speed."}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"speed_assignment\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0028", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "REMAIN CLEAR ADIS TRAFFIC INBOUND over"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"informational\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0029", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "TOWER NOVEMBER ONE SEVEN XRAY XRAY TEN MILES NORTH OF LAFAYETTE TWO THOUSAND FIVE HUNDRED REQUEST ENTRY TO CLASS B AIRSPACE"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"comm_request\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0030", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "NOVEMBER ONE SEVEN XRAY XRAY INDIANAPOLIS APPROACH ENTER LEFT DOWNWIND RUNWAY TWO THREE LEFT CONTACT INDIANAPOLIS TOWER ONE TWO ZERO DECIMAL NINER over"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"pattern_entry\", \"slots\": {\"pattern_leg\": \"left downwind\", \"runway\": \"two three left\"}, \"text\": \"\"}, {\"intent\": \"frequency_change\", \"slots\": {\"facility\": \"Indianapolis Tower\", \"frequency\": \"one two zero point niner\"}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0031", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "NOVEMBER ONE SEVEN XRAY XRAY RUNWAY THREE ONE CLEARED FOR THE OPTION"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"cleared_option\", \"slots\": {\"runway\": \"three one\"}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0032", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "NOVEMBER ONE SEVEN XRAY XRAY LAFIETT TOWER RUNWAY FIVE CLEARED FOR TAKEOFF MAKE RIGHT TRAFFIC FOR NORTH DEPARTURE OVER"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"takeoff_clearance\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0033", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "Reid-Hillview traffic. November One Seven X-ray X-ray. Departing Runway three one, north departure. Reid-Hillview."}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"ctaf_broadcast\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0034", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven Xray Xray Fss Radar State Request"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"comm_request\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0035", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": ", cleared to land runway three one, traffic Cessna on close base"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"landing_clearance\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0036", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "NOVEMBER ONE SEVEN XRAY XRAY NORCAL DEPARTURE MAINTAIN HEADING TWO SEVEN ZERO TRAFFIC CLEARED REPORT WHEN TRAFFIC PASSED"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"other\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0037", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "Exit Left Right At Alpha Contact Ground On One One Niner Decimal Three November One Seven Xray Xray"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"frequency_change\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0038", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven X-ray X-ray, Indianapolis Approach, say airspeed."}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"verification_request\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0039", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "Taxi To Parking Via Bravo"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"taxi_instruction\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0040", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "REMAIN CLEAR TRAFFIC INBOUND"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"other\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0041", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": ", SAN CARLO'S TOWER LEFT BASE RUNWAY THREE ZERO CLEARED TOUCH AND GO."}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"cleared_touch_and_go\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0042", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "N17XX SAN CARLOS TOWER SHORT FINAL RUNWAY THREE ZERO CLEARED TO LAND"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"position_report\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0043", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "READ HILL VIEW TRAFFIC NOVEMBER ONE SEVEN XRAY XRAY HOLDING SHORT RUNWAY THREE ONE READ HILL VIEW"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"ctaf_broadcast\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0044", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "EXIT RIGHT AT C2 CONTACT GROUND AT ONE HUNDRED TWENTY ONE POINT NINER WARRIOR THIRTY ONE THOUSAND EIGHT HUNDRED SIXTY TWO over"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"taxi_instruction\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0045", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven Xray Xray Egle Creek Tower Runway Two Seven Left Cleared To Land"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"landing_clearance\", \"slots\": {\"runway\": \"two seven left\"}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0046", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "NOVEMBER ONE SEVEN XRAY XRAY NORCAL DEPARTURE CLIMBING THROUGH ONE THOUSAND MAINTAINING TWO THOUSAND FIVE HUNDRED DIRECT SAN CARLOS"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"position_report\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0047", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "CROSS RUNWAY ONE ZERO AT BRAVO AND TAXI TO RUNWAY FIVE NOVEMBER ONE SEVEN XRAY XRAY"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"taxi_instruction\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0048", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven Xray Xray Report Base Runway Three Zero"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"report_request\", \"slots\": {\"pattern_leg\": \"base\", \"runway\": \"three zero\"}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0049", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven X-ray X-ray, traffic eleven o'clock, one mile, helicopter northbound, no factor."}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"traffic_advisory\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0050", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven Xray Xray Flight Service With A Briefing Copied Conditions Vfr"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"informational\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0051", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "LAFAYETTE TOWER Cessna ONE SEVEN XRAY XRAY RUNWAY FIVE READY FOR DEPARTURE NORTH DEPARTURE"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"comm_request\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0052", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "Mayday, Mayday, Mayday. Bakersfield Tower, November One Seven X-ray X-ray. Bird strike. Intend landing at Bakersfield. Ten miles south, at three thousand five hundred. IFR pilot."}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"emergency_declaration\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0053", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "REMAIN CLEAR ADIS TRAFFIC INBOUND"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"informational\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0054", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "TRAFFIC IN THE PATTERN PALLO ALTO TRAFFIC CESSNA ONE TWO THREE ALPHA BRAVO ENTERING LEFT DOWNWIND RUNWAY THREE ONE PALLO ALTO over"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"ctaf_broadcast\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0055", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven X-ray X-ray, Eagle Creek Tower, number two for Runway two seven left, traffic turning final"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"sequencing\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0056", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "Altimeter THIRTY POINT ZERO TWO TRANSITION APPROVED WARRIOR THIRTY ONE THOUSAND EIGHT HUNDRED SIXTY TWO"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"altimeter_setting\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0057", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "RUNWAY FIVE CLEARED FOR TAKEOFF MAKE RIGHT TRAFFIC FOR NORTH DEPARTURE"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"takeoff_clearance\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0058", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "CONTINUE THE THREE SIXTY REPORT WHEN COMPLETE YOU'RE DOING WELL"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"spacing_instruction\", \"slots\": {}, \"text\": \"\"}, {\"intent\": \"report_request\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0059", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "Pan pan pan pan pan pan Riverside TOWER NOVEMBER ONE SEVEN XRAY XRAY"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"emergency_declaration\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0060", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "N17XX LLOYS ANGELS GROUND ADIS PENETRATION PROCEEDURES COMPLETE DVFR FLIGHT PLAN PROPERLY CLOSED ALL SECURITY REQUIREMENTS MET PARKING AVAILABLE AT TERMINAL HAVE A GOOD DAY"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"informational\", \"slots\": {}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0061", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "HELICOPTER ENTER PATTERN"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"unknown\", \"slots\": {}, \"text\": \"HELICOPTER ENTER PATTERN\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0062", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "November One Seven Xray Xray Lafiette Ground Taxi To Runway Five Via Alpha Cross Runway One Zero At Alpha"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"taxi_instruction\", \"slots\": {\"runway\": \"five\", \"route\": \"Alpha\"}, \"text\": \"\"}, {\"intent\": \"runway_crossing\", \"slots\": {\"runway\": \"one zero\", \"taxiway\": \"Alpha\"}, \"text\": \"\"}], \"abstain_reason\": null}"}]} {"id": "v27-valid-0063", "conversations": [{"role": "system", "content": "You are an ATC parser. Parse the air traffic control transmission into a JSON object.\n\nOUTPUT SCHEMA (always emit `segments` list, even single-intent turns):\n{\n \"segments\": [\n {\"intent\": , \"slots\": {: }, \"text\": }\n ],\n \"abstain_reason\": null | \n}\n\nIntent enum (51 values, includes `unknown` for ambiguous/garbled):\nacknowledgment, altimeter_setting, altitude_instruction, approach_clearance, cleared_option, cleared_touch_and_go, comm_request, correction, crossing_restriction, ctaf_broadcast, departure_instruction, direct_to, disregard, emergency_declaration, extend_downwind, frequency_change, go_around, ground_hold, heading_instruction, hold_for_release, hold_instruction, hold_short, ident, ifr_clearance, informational, landing_clearance, line_up_and_wait, missed_approach, other, pattern_entry, position_report, radar_identification, radar_status, release, report_request, route_amendment, route_clearance, runway_crossing, sequencing, short_approach, spacing_instruction, speed_assignment, squawk_code_set, takeoff_clearance, taxi_instruction, traffic_advisory, unable_response, verification_request, vfr_instruction, weather_advisory, unknown\n\nSlot keys (lowercase only): altimeter_setting, altitude, approach_type, call_sign, clock_position, direction, distance, facility, fix, frequency, heading, pattern_leg, route, runway, speed, taxiway, time, transponder_code, turn_direction, sequence\n\nRules:\n1. Compound transmissions get multiple segments — split by comma, period, or new clause.\n2. Single-intent transmissions still emit one segment in the list.\n3. Use `unknown` intent + `abstain_reason` when transcript is garbled, partial, or doesn't match any enum.\n4. Slots is FMM-relevant subset only — do NOT include callsign or facility unless required for the action.\n5. Output ONLY the JSON object."}, {"role": "user", "content": "NOVEMBER ONE SEVEN X-RAY X-RAY LAFIETTE TOWER HOLD SHORT RUNWAY FIVE TRAFFIC ON SHORT FINAL"}, {"role": "assistant", "content": "{\"segments\": [{\"intent\": \"hold_short\", \"slots\": {\"runway\": \"five\"}, \"text\": \"\"}, {\"intent\": \"traffic_advisory\", \"slots\": {\"pattern_leg\": \"short final\"}, \"text\": \"\"}], \"abstain_reason\": null}"}]}