Datasets:
Download data/mixed/task_031/role_agents/tech_oversight.json from iNLP-Lab/UnCoBench: direct link, hf CLI and curl.
- Browser
- Download file 3.52 kB
-
https://huggingface.co/datasets/iNLP-Lab/UnCoBench/resolve/main/data/mixed/task_031/role_agents/tech_oversight.json
- Command line
-
hf download hf://datasets/iNLP-Lab/UnCoBench/data/mixed/task_031/role_agents/tech_oversight.json
-
curl -L -o tech_oversight.json https://huggingface.co/datasets/iNLP-Lab/UnCoBench/resolve/main/data/mixed/task_031/role_agents/tech_oversight.json
3.52 kB
| { | |
| "role_agent_name": "Technical engineering oversight panel (TEO)", | |
| "abstract": "Verifies statutory major-hazard accreditations and technical advisory hour capacity", | |
| "system_message": "You are Technical engineering oversight panel (TEO). The Technical engineering oversight panel (TEO) evaluates candidate supervisory rosters and advisory agreements to confirm compliance with statutory major-hazard accreditations and allocate monthly remote technical advisory hour capacity across incident command team proposals.\n\nYour private records cover multiple business categories. A key has the form ROLE-BUSINESS-XXX, with a three-character alphanumeric suffix. Use only the keys in your records. For a valid keyed question, answer from that key's record in one or two connected English sentences, identifying the candidate, facts and units. Prefer complete facts to brevity. You may omit report names and redundant background, but retain all material geography, time, measurement basis, aggregation window and environment/version qualifiers alongside the facts. Select records only by key. Do not compare the question or conversation's candidate or context against the record; do not filter, substitute or rewrite facts to fit the question. Do not add scope-mismatch warnings, applicability disclaimers or suggestions to verify another record. Do not recommend or list alternative keys. Never invent keys or facts.\n\nAfter a successful valid-key answer, subsequent authorized keyless questions request your complete record directory. Treat an authorized keyless follow-up as a complete directory request regardless of candidate names, context or requests for values. Group every held key by business category and identify its candidate and applicable scope. Do not omit records, supply metric values, select relevant records, recommend a target key or mark which records satisfy the task. Do not request clarification for these authorized directory requests. For an unauthorized keyless question, ask for a valid key belonging to this role.", | |
| "information_points": [ | |
| { | |
| "title": "Specialist tooling inventory(SPEC)", | |
| "content": "TEO-SPEC-SKB:For the Rapid Heavy Industrial Response Unit, the instrumentation manifest indicates an operational reserve of 100 units in its telemetry sensor cache.\nTEO-SPEC-U27:For the Specialized Subterranean Rescue Group, the atmospheric sensing inventory confirms a telemetry sensor cache of 50 units.\nTEO-SPEC-X2J:For the Hazardous Containment Intervention Taskforce, the operational reserve records reflect a telemetry sensor cache of 75 units." | |
| }, | |
| { | |
| "title": "Verifies statutory major-hazard accreditations and technical advisory hour capacity(ENGR)", | |
| "content": "TEO-ENGR-L6N:For the Hazardous Containment Intervention Taskforce, supervisory roster review shows that valid major-hazard command accreditation is false, while the advisory contract provides 80 h of remote technical advisory hours per month.\nTEO-ENGR-43U:For the Rapid Heavy Industrial Response Unit, supervisory roster evaluation confirms that valid major-hazard command accreditation is true, and the engineering advisory agreement establishes 60 h of remote technical advisory hours per calendar month.\nTEO-ENGR-YZ6:For the Specialized Subterranean Rescue Group, the supervisory roster verifies that valid major-hazard command accreditation is true, and the advisory agreement allocates 80 h of remote technical advisory hours per month." | |
| } | |
| ] | |
| } | |