{"kind":"task","effective_mode":"full","benchmark":{"kind":"benchmark","effective_mode":"full","slug":"musr","formal_name":"MuSR","introduction":"MuSR poses multistep soft reasoning problems over algorithmically generated narratives. It has three domains — murder mysteries, object placements and team allocation — and this catalogue imports all three domains, 756 problems in total.","introduction_ja":"","introduction_en":"","category":"Category not supplied","task_count":null,"acquisition_status":"Acquisition status not supplied","official_url":"https://zayne-sprague.github.io/MuSR/","indexing_mode":"index","profile":{"resources":[],"task_format":"","scoring":"","metric":"","size":"","answer_access":"","license":"","citation":"","maintainer":"","released":"","why_hard":"","related":[],"history":"","construction":"","limitations":"","saturation":"","scores":[]}},"task_id":"65e3ea80-4c8a-5fd3-b149-05ca23db00ef","task_key":"default--team~5fallocation--65e3ea80-4c8a-5fd3-b149-05ca23db00ef","task_revision_id":"1","upstream_id":"","short_description":"Given the story, how would you uniquely allocate each person to make sure both…","config":"default","split":"team_allocation","body":"{\"choices\":\"['Frontend coding: James, Backend coding: Ethan and Olivia', 'Frontend coding: Olivia, Backend coding: Ethan and James', 'Frontend coding: Ethan, Backend coding: James and Olivia']\",\"narrative\":\"Nestled in the heart of Silicon Valley, my tech company stands as a shining symbol of innovation. We are committed to developing revolutionary solutions for intricate technological challenges, propelling us towards a brighter future. The driving force behind this creative powerhouse is my dedicated team, the cornerstone of our triumphant journey. Among them are James, Olivia, and Ethan, each a vital cog in our machine. Their roles in the upcoming tasks of Frontend and Backend coding are yet to be determined, but their contributions will undoubtedly be instrumental in our continued success.\\n\\nAmong the renowned members of my illustrious team are James, Olivia, and Ethan, each exceptional in their way, whose roles and responsibilities play a key role in our upcoming projects that involve Frontend and Backend coding.\\n\\nBeen the diligent leader I am, I keep close tabs on their skillsets and predilections. One of my most seasoned folks, Ethan, is quite an enigma. Despite his relentless discomfort with UI/UX design, he has managed to contribute remarkably; although there might be room for finesse. With a past characterized by work that mostly catered to server-side programming, Ethan has often confessed his challenges with intricate algorithms and data structures.\\n\\nHis 'code fast and fix later' mantra, however, did cause a friction between him and James at times. A recent project did make me contemplate about Ethan's place in backend coding, particularly because of system crashes triggered by his contributions.\\n\\nJames, on the other hand, is laser-focused and meticulous. His background in designing complex database management systems single-handedly, speaks volumes about his capabilities. When I think 'Backend', James often springs to mind. His penchant for backend tasks is evident in his constant volunteering. \\n\\nWhile he does like to tinker with user interfaces, it isn't his primary calling. James values his solitude, often preferring to work individually. His dedication was evident in the incident last month when he single-handedly fixed a critical bug in our website's navigation menu.\\n\\nOlivia, my third virtuoso, is remarkably synergistic. Having often seen her collaborating with Ethan and discussing issues, I know her strengths lie in group efforts. However, she continues to wrestle with her understanding of database concepts and struggles with CSS and Javascript, often asking for assistance. On a recent backend project, her code had to be significantly reworked by her peers which left her relatively disheartened. UI design also seems to test her patience.\\n\\nDespite these, her collaboration with Ethan resulted in a successful debugging operation. Their lauding of one another's skills highlighted the strengths of their collaboration. While some of their individual skills may be lacking, it is certain that together, their potential is limitless.\\n\\nAssigning these talents to the right tasks is crucial, for it decides the course of our journey. Know that they are exceptional, each with their strengths and areas they struggle with. But like a jigsaw puzzle, they need to fit perfectly to create the complete picture. After all, a company's success lies heavily on the shoulders of its team players, in how they harmonize their capabilities with their assigned roles. Yes, my tech firm relies upon their alchemy and tapping into their potential to carve a path into the future.\",\"question\":\"Given the story, how would you uniquely allocate each person to make sure both tasks are accomplished efficiently?\"}","display_format":"text","language":"","answer_status":"published","assets":[],"source_url":"https://zayne-sprague.github.io/MuSR/","history":"initial import","indexing_mode":"index","subproblems":[],"grids":[]}