Datasets:
Download data/mixed/task_015/role_agents/jacking_systems.json from iNLP-Lab/UnCoBench: direct link, hf CLI and curl.
- Browser
- Download file 3.08 kB
-
https://huggingface.co/datasets/iNLP-Lab/UnCoBench/resolve/main/data/mixed/task_015/role_agents/jacking_systems.json
- Command line
-
hf download hf://datasets/iNLP-Lab/UnCoBench/data/mixed/task_015/role_agents/jacking_systems.json
-
curl -L -o jacking_systems.json https://huggingface.co/datasets/iNLP-Lab/UnCoBench/resolve/main/data/mixed/task_015/role_agents/jacking_systems.json
3.08 kB
| { | |
| "role_agent_name": "Jackup systems engineer (JCK)", | |
| "abstract": "Monitors leg elevation cycles and jacking power fuel consumption", | |
| "system_message": "You are Jackup systems engineer (JCK). The jackup systems engineer monitors leg elevation cycles, jacking power fuel consumption, and operational water depth limits across the heavy installation vessels.\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": "Monitors leg elevation cycles and jacking power fuel consumption(JACK)", | |
| "content": "JCK-JACK-V7X:For North Sea Leviathan, the jacking cycle fuel consumption measured during a single complete platform elevation and lowering cycle is 25 t.\nJCK-JACK-BR0:For Baltic Horizon Jackup, the jacking cycle fuel consumption recorded across a single complete platform elevation and lowering cycle is 35 t.\nJCK-JACK-G90:For Celtic Wind Voyager, the jacking cycle fuel consumption documented during a single complete platform elevation and lowering cycle is 35 t." | |
| }, | |
| { | |
| "title": "Leg length water depth audit(LEG)", | |
| "content": "JCK-LEG-0C1:Operational manual documentation under standard seabed penetration indicates that Celtic Wind Voyager has a maximum operating water depth of 75 m.\nJCK-LEG-E87:According to the marine operational manual under standard seabed penetration, North Sea Leviathan has a maximum operating water depth of 50 m.\nJCK-LEG-JZ8:Based on the marine operational manual under standard seabed penetration, Baltic Horizon Jackup has a maximum operating water depth of 65 m." | |
| } | |
| ] | |
| } | |