[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$apiParty6fBuHLCPZ1LTYs42XHdVbjpSDOYYPYzyxeAGwSN5Tp8":3,"$apiPartyvyMEa8x1da9VSsXxWh72aEqTUkOfgXCwSfv0eoxNy_s":563,"$apiPartyvyMEa8x1da9VSsXxWh72aEqTUkOfgXCwSfv0eoxNy_s$H93EERW16b":563},{"product_data":4,"scene_data":21,"task_data":407,"modality_data":441,"domain_data":478},[5,9,12,15,18],{"name":6,"value":7,"add_value":8,"describe":8},"Rivo","1","",{"name":10,"value":11,"add_value":8,"describe":8},"Cubo","2",{"name":13,"value":14,"add_value":8,"describe":8},"Moye","3",{"name":16,"value":17,"add_value":8,"describe":8},"Juro","4",{"name":19,"value":20,"add_value":8,"describe":8},"Ordo","5",[22,73,135,197,232,267,302,337,372],{"name":23,"value":7,"add_value":24,"describe":25,"children":26},"Home & Indoor","sofa","AI enhances everyday home life. Our datasets cover real indoor scenes to support smart devices, robotics, and home intelligence.",[27,29,31,33,35,37,40,43,46,49,52,55,58,61,64,67,70],{"name":28,"value":7},"Living Room",{"name":30,"value":11},"Bedroom",{"name":32,"value":14},"Kitchen",{"name":34,"value":17},"Dining Area",{"name":36,"value":20},"Bathroom",{"name":38,"value":39},"Entrance \u002F Foyer","6",{"name":41,"value":42},"Corridor \u002F Hallway","7",{"name":44,"value":45},"Staircase","8",{"name":47,"value":48},"Home Office","9",{"name":50,"value":51},"Hobby \u002F Game Room","10",{"name":53,"value":54},"Worship Space","11",{"name":56,"value":57},"Garage","12",{"name":59,"value":60},"Utility \u002F Laundry Room","13",{"name":62,"value":63},"Pantry","14",{"name":65,"value":66},"Basement","15",{"name":68,"value":69},"Garden","16",{"name":71,"value":72},"Balcony","17",{"name":74,"value":11,"add_value":75,"describe":76,"children":77},"Office & Educational","workshop","AI is reshaping work and learning. Our datasets capture offices and classrooms to power automation and next-generation productivity tools.",[78,81,84,87,90,93,96,99,102,105,108,111,114,117,120,123,126,129,132],{"name":79,"value":80},"Open Office","18",{"name":82,"value":83},"Private Office","19",{"name":85,"value":86},"Co-working Space","20",{"name":88,"value":89},"Reception \u002F Lobby","21",{"name":91,"value":92},"Conference Room","22",{"name":94,"value":95},"Huddle Room \u002F Booth","23",{"name":97,"value":98},"Lecture Hall \u002F Auditorium","24",{"name":100,"value":101},"Classroom","25",{"name":103,"value":104},"Science Laboratory","26",{"name":106,"value":107},"Library","27",{"name":109,"value":110},"Design Studio","28",{"name":112,"value":113},"Pantry \u002F Breakroom","29",{"name":115,"value":116},"Cafeteria \u002F Canteen","30",{"name":118,"value":119},"Restroom (Commercial)","31",{"name":121,"value":122},"Gymnasium \u002F Sports Hall","32",{"name":124,"value":125},"Server Room","33",{"name":127,"value":128},"Mailroom \u002F Logistics","34",{"name":130,"value":131},"Janitorial Closet","35",{"name":133,"value":134},"Corridor \u002F Elevators","36",{"name":136,"value":14,"add_value":137,"describe":138,"children":139},"Healthcare & Medical","love-and-help","AI is advancing modern healthcare. Our datasets include clinics and hospitals to enable clinical insights and medical automation.",[140,143,146,149,152,155,158,161,164,167,170,173,176,179,182,185,188,191,194],{"name":141,"value":142},"Operating Theatre \u002F OR","37",{"name":144,"value":145},"Consultation Room","38",{"name":147,"value":148},"Treatment Room","39",{"name":150,"value":151},"Dental Clinic","40",{"name":153,"value":154},"Inpatient Ward","41",{"name":156,"value":157},"Nurse Station","42",{"name":159,"value":160},"ICU","43",{"name":162,"value":163},"NICU (Neonatal ICU)","44",{"name":165,"value":166},"Emergency Room (ER)","45",{"name":168,"value":169},"Hospital Corridor","46",{"name":171,"value":172},"Waiting Area","47",{"name":174,"value":175},"CT\u002FMRI","48",{"name":177,"value":178},"Medical Laboratory","49",{"name":180,"value":181},"Phlebotomy Room","50",{"name":183,"value":184},"Rehabilitation Gym","51",{"name":186,"value":187},"Assisted Living Room","52",{"name":189,"value":190},"Pharmacy","53",{"name":192,"value":193},"Sterile Processing Dept","54",{"name":195,"value":196},"Medical Storage","55",{"name":198,"value":17,"add_value":199,"describe":200,"children":201},"Business & Public Service","business","AI is elevating commercial and public services. Our datasets span retail, dining, and service centers to improve intelligent operations.",[202,205,208,211,214,217,220,223,226,229],{"name":203,"value":204},"Shopping Mall Atrium","86",{"name":206,"value":207},"Supermarket Shelf","87",{"name":209,"value":210},"Self-Checkout Counter","88",{"name":212,"value":213},"Restaurant Dining Hall","89",{"name":215,"value":216},"Commercial Kitchen","90",{"name":218,"value":219},"Hotel Lobby","91",{"name":221,"value":222},"Subway Platform","92",{"name":224,"value":225},"Security Checkpoint","93",{"name":227,"value":228},"Underground Parking","94",{"name":230,"value":231},"Bank Teller Zone","95",{"name":233,"value":20,"add_value":234,"describe":235,"children":236},"Industrial & Manufacturing","robot-arm","AI is modernizing industry. Our datasets capture factories and logistics spaces to support robotics and intelligent manufacturing.",[237,240,243,246,249,252,255,258,261,264],{"name":238,"value":239},"Final Assembly Line","96",{"name":241,"value":242},"Quality Control Station","97",{"name":244,"value":245},"Robotic Welding Cell","98",{"name":247,"value":248},"CNC Machining Center","99",{"name":250,"value":251},"Cleanroom","100",{"name":253,"value":254},"Automated Warehouse","101",{"name":256,"value":257},"Loading Dock","102",{"name":259,"value":260},"Sorting Center","103",{"name":262,"value":263},"Chemical Plant","104",{"name":265,"value":266},"Power Substation","105",{"name":268,"value":39,"add_value":269,"describe":270,"children":271},"Transportation & Driving","car","AI is revolutionizing mobility. Our datasets capture road networks, vehicle dynamics and traffic scenarios to support autonomous driving and intelligent transportation systems.",[272,275,278,281,284,287,290,293,296,299],{"name":273,"value":274},"Urban Intersection","56",{"name":276,"value":277},"Highway \u002F Expressway","57",{"name":279,"value":280},"Tunnel","58",{"name":282,"value":283},"Roundabout","59",{"name":285,"value":286},"School \u002F Hospital Zone","60",{"name":288,"value":289},"Toll Station","61",{"name":291,"value":292},"Construction Zone","62",{"name":294,"value":295},"Parking Garage","63",{"name":297,"value":298},"Driver Cabin","64",{"name":300,"value":301},"Adverse Weather","65",{"name":303,"value":42,"add_value":304,"describe":305,"children":306},"Outdoor & Construction","tent-tree","AI is optimizing outdoor operations. Our datasets capture construction sites, open-air work zones and outdoor infrastructure to support smart construction and autonomous outdoor machinery.",[307,310,313,316,319,322,325,328,331,334],{"name":308,"value":309},"Excavation Site","66",{"name":311,"value":312},"Scaffolding Area","67",{"name":314,"value":315},"Material Storage Yard","68",{"name":317,"value":318},"Site Entrance","69",{"name":320,"value":321},"Roadwork Zone","70",{"name":323,"value":324},"Bridge Infrastructure","71",{"name":326,"value":327},"Transmission Line","72",{"name":329,"value":330},"Open-pit Mine","73",{"name":332,"value":333},"Tunneling Site","74",{"name":335,"value":336},"Post-Disaster Rubble","75",{"name":338,"value":45,"add_value":339,"describe":340,"children":341},"Nature, Aerial & Aquatic","global-loop","AI is exploring the natural world. Our datasets capture terrestrial landscapes, aerial vistas and aquatic ecosystems to support environmental monitoring and autonomous exploration systems.",[342,345,348,351,354,357,360,363,366,369],{"name":343,"value":344},"Deep Forest","76",{"name":346,"value":347},"Farmland \u002F Crops","77",{"name":349,"value":350},"River \u002F Lake","78",{"name":352,"value":353},"Open Ocean","79",{"name":355,"value":356},"Underwater Coral Reef","80",{"name":358,"value":359},"Fish Farm","81",{"name":361,"value":362},"Mountain Terrain","82",{"name":364,"value":365},"Urban Low Altitude","83",{"name":367,"value":368},"Fire Scene","84",{"name":370,"value":371},"Desert \u002F Gobi","85",{"name":373,"value":48,"add_value":374,"describe":375,"children":376},"Virtul & Digital","siri","AI is reshaping the virtual realm. Our datasets capture digital twins, virtual environments and simulated spaces to support metaverse development and intelligent digital interaction.",[377,380,383,386,389,392,395,398,401,404],{"name":378,"value":379},"VR Social Space","106",{"name":381,"value":382},"Synthetic Driving Sim","107",{"name":384,"value":385},"Digital Twin City","108",{"name":387,"value":388},"FPS \u002F MOBA Game","109",{"name":390,"value":391},"Robotics Gym","110",{"name":393,"value":394},"AR Navigation","111",{"name":396,"value":397},"Virtual Showroom","112",{"name":399,"value":400},"Code \u002F IDE Interface","113",{"name":402,"value":403},"App GUI Screen","114",{"name":405,"value":406},"Synthetic Face\u002FID","115",[408,411,414,417,420,423,426,429,432,435,438],{"name":409,"value":7,"add_value":410,"describe":8},"Classification","rubric",{"name":412,"value":11,"add_value":413,"describe":8},"Detection","radar",{"name":415,"value":14,"add_value":416,"describe":8},"Segmentation","segmentation",{"name":418,"value":17,"add_value":419,"describe":8},"Tacking","crosshairs",{"name":421,"value":20,"add_value":422,"describe":8},"Estimation","streamline",{"name":424,"value":39,"add_value":425,"describe":8},"QA","qa",{"name":427,"value":42,"add_value":428,"describe":8},"Recognition","finger-scan",{"name":430,"value":45,"add_value":431,"describe":8},"Control","control",{"name":433,"value":48,"add_value":434,"describe":8},"Extraction","extraction",{"name":436,"value":51,"add_value":437,"describe":8},"Retrieval","retrieval",{"name":439,"value":54,"add_value":440,"describe":8},"Forecast","forecast",[442,445,448,451,454,457,460,463,466,469,472,475],{"name":443,"value":7,"add_value":444,"describe":8},"Audio","audio",{"name":446,"value":11,"add_value":447,"describe":8},"Image","image",{"name":449,"value":14,"add_value":450,"describe":8},"Text","text",{"name":452,"value":17,"add_value":453,"describe":8},"Video","video",{"name":455,"value":20,"add_value":456,"describe":8},"Multi","multi",{"name":458,"value":39,"add_value":459,"describe":8},"Document","document",{"name":461,"value":42,"add_value":462,"describe":8},"Time-Series","time-series",{"name":464,"value":45,"add_value":465,"describe":8},"3D cloud","cloud",{"name":467,"value":48,"add_value":468,"describe":8},"Code","code",{"name":470,"value":51,"add_value":471,"describe":8},"Event","event",{"name":473,"value":54,"add_value":474,"describe":8},"Motion","motion",{"name":476,"value":57,"add_value":477,"describe":8},"Interaction","interaction",[479,482,487,491,494,499,504,509,514,519,524,528,532,536,540,544,548,552,556,559],{"id":480,"value":480,"name":233,"intro":481,"add_value":234,"describe":481},2,"智能质检：利用图像识别、多模态模型对产品外观或声音、振动等数据进行分析，自动识别缺陷，提高质量控制效率。\n工业知识问答与文档理解：通过大模型理解和总结技术文档、操作手册，实现快速问答、知识检索和培训支持。\n安全监测与风险预警：实时分析视频、传感器和操作日志，识别潜在危险行为或异常状态，提前预警，保障人员和设备安全。",{"id":483,"value":483,"name":484,"intro":485,"add_value":486,"describe":485},3,"Finance & Insurance","风险评估与预测：分析大量客户数据，评估信用风险、市场风险等，预测违约概率、股价走势等，辅助金融机构决策。\n智能投顾：根据客户风险偏好、资产状况等，提供个性化投资组合建议，实时调整投资策略。\n反欺诈检测：通过分析交易数据、用户行为，识别异常交易和欺诈行为，保障金融安全。","funds",{"id":488,"value":488,"name":489,"intro":490,"add_value":269,"describe":490},1,"Transport & Automotive","智能座舱：打造多模态交互的 AI 座舱，通过语音、手势、面部识别等实现人机交互，如语音控制导航、音乐播放。\n驾驶员状态监测：识别疲劳、分心、抽烟、打电话等行为，通过大模型判断危险等级，触发相应提醒或干预机制。\n智能驾驶：AI 用于环境感知、路径规划与决策控制，使车辆能识别道路、行人、障碍物等，实现自适应巡航、自动泊车、车道保持等功能，提升驾驶安全性与便利性。",{"id":492,"value":492,"name":136,"intro":493,"add_value":137,"describe":493},4,"医学影像诊断：分析 CT、MRI 等影像，辅助医生检测疾病、识别病灶，如 AI 系统可快速发现肺部结节。\n医患对话助手：通过自然语言处理理解患者问题，提供初步健康建议或就诊指导，缓解医生接诊压力。\n智能健康管理：根据用户健康数据，提供个性化健康建议、疾病预警，如智能手环结合 AI 分析用户运动、睡眠、心率等数据。",{"id":495,"value":495,"name":496,"intro":497,"add_value":498,"describe":497},6,"Smart Devices","多模态交互：支持语音、手势、眼神等多种交互方式，如 AI 眼镜可通过语音指令实现翻译、搜索功能。\n智能感知与处理：使设备能感知环境、理解用户需求，如智能音箱根据环境噪音自动调节音量。\n个性化服务：根据用户使用习惯和偏好，提供个性化功能与服务，如智能手表为用户定制运动健身计划。","microscope",{"id":500,"value":500,"name":501,"intro":502,"add_value":503,"describe":502},8,"Law & Government","智能法律问答：面向公众或企业用户，提供合规、劳动法、婚姻继承、知识产权等常见法律问题的智能解答。\n合同审查与风险识别：利用大模型分析合同内容，识别潜在风险条款、漏洞或不合理约定，提升合同审核质量。\n法律知识图谱构建：自动梳理法规、案例、条文之间的引用关系，构建语义化知识图谱，支持智能分析和推理。","hammer",{"id":505,"value":505,"name":506,"intro":507,"add_value":508,"describe":507},7,"Education & Training","个性化学习：根据学生学习进度、能力和知识掌握情况，推送个性化学习内容与练习，如智能辅导系统为学生制定专属学习计划。\n智能教学辅助：AI 助教协助教师进行作业批改、答疑解惑，还可分析教学数据，为教师提供教学反馈，优化教学方法。\n虚拟学习环境：利用 AI 创建虚拟实验、历史场景等，让学生沉浸式学习，如在虚拟化学实验室中进行实验操作。","degree-hat",{"id":510,"value":510,"name":511,"intro":512,"add_value":513,"describe":512},5,"Agriculture & Food","作物病虫害识别与防治：通过图像识别分析农作物叶片、果实等症状，识别病虫害类型，给出防治建议，减少产量损失。\n农产品质量检测：利用图像和传感器数据，识别果蔬等农产品的成熟度、外观缺陷，进行自动分级，提高市场竞争力。\n农情监测与预测：利用卫星遥感、气象和传感器数据，结合大模型预测作物长势、干旱、洪涝等农情变化。","ph-farm",{"id":515,"value":515,"name":516,"intro":517,"add_value":518,"describe":517},9,"Retail & E-commerce","智能客服：通过自然语言对话理解用户需求，提供产品推荐、订单查询、退换货支持等服务，提升客户满意度。\n个性化营销推荐：基于用户浏览、购买、偏好等行为数据，生成个性化推荐内容与优惠策略，提高转化率和客单价。\n商品内容生成：自动撰写商品标题、卖点描述、使用说明等内容，适用于海量SKU的内容生产与多语言发布。","buy",{"id":520,"value":520,"name":521,"intro":522,"add_value":523,"describe":8},10,"Security & Protection",null,"safe-shield-line",{"id":525,"value":525,"name":526,"intro":522,"add_value":527,"describe":8},11,"Environment & Climate","weather",{"id":529,"value":529,"name":530,"intro":522,"add_value":531,"describe":8},12,"Energy & Resource","energy-leaf",{"id":533,"value":533,"name":534,"intro":522,"add_value":535,"describe":8},13,"Express & Logistics","speed-outline",{"id":537,"value":537,"name":538,"intro":522,"add_value":539,"describe":8},15,"Sports","baseball-outline",{"id":541,"value":541,"name":542,"intro":522,"add_value":543,"describe":8},16,"General Data","daily-booth",{"id":545,"value":545,"name":546,"intro":522,"add_value":547,"describe":8},17,"Content & Media","media",{"id":549,"value":549,"name":550,"intro":522,"add_value":551,"describe":8},18,"Construction","construction",{"id":553,"value":553,"name":554,"intro":522,"add_value":555,"describe":8},19,"IT & Telecom","tech",{"id":557,"value":557,"name":558,"intro":522,"add_value":498,"describe":8},20,"Science & Research",{"id":560,"value":560,"name":561,"intro":522,"add_value":562,"describe":8},21,"Language & Culture","lang",{"id":564,"unique_code":565,"title":566,"icon":8,"intro":567,"cate":483,"detail":568,"create_time":569,"update_time":570,"price":571,"view_count":505,"download_count":572,"unit":572,"amount":573,"is_create_order":572,"enterprise_id":488,"seo_keywords":574,"seo_description":575,"data_format":576,"file_size":577,"apply_scene":578,"training_task":579,"version":580,"dataset_type_id":492,"dataset_scene_id":500,"sample_file":581,"banner":8,"unit_name":8,"cate_name":449,"icon_url":8,"banner_url":8,"sample_file_url":8,"data_dict":582,"qa_list":635,"sample_metadatas":652,"text_sample_content":698,"enterprise_name":699,"enterprise_logo":700,"data_distribution":701},1271,"7b67a1a09a179616ea6aad6cdc5195aa","Licensing Contract Exceptions and Ambiguous Clause QA Benchmark Dataset","Improve contract question answering with text-grounded examples of easily misread exceptions, conditions, and conflicts in licensing agreements.","\u003Cp>This benchmark covers challenging licensing contract excerpts involving authorization exceptions, cross-referenced definitions, conditional rights, order of precedence, conflicting clauses, and obligations that survive termination. Each excerpt is paired with a question and a text-grounded reference answer, with supporting evidence, reasoning steps, and structured clause interpretations. The dataset supports domain-specific supervised fine-tuning and evaluation focused on long-tail language, limiting conditions, and easily confused provisions.\u003C\u002Fp>","2026-10-15 18:48:38","2026-10-19 17:19:12","0.00",0,5000,"licensing contract dataset,contract QA benchmark,legal text question answering,licensing clause interpretation,contract ambiguity analysis,contract evidence localization,legal domain SFT,contract conflict detection","A licensing contract QA benchmark covering authorization exceptions, conditional rights, clause conflicts, and post-termination duties, with evidence and reason","JSON","0.3GB","licensing contract review, ambiguous clause interpretation, contract compliance analysis","contract question answering, clause interpretation, exception and conflict reasoning","V1.0","rivo\u002Fsample-packages\u002Fcda2e20f-a19b-43c0-be42-4e9ee50b7e79\u002F20261015.zip",[583,588,593,598,603,608,614,620,625,630],{"id":572,"name":584,"field":585,"intro":586,"type":587},"File Name","file_name","File name","string",{"id":589,"name":590,"field":591,"intro":592,"type":587},9344,"Reference Answer","answer","An accurate, complete answer grounded in the contract excerpt and the question.",{"id":594,"name":595,"field":596,"intro":597,"type":587},9345,"Question","question","A legal or contractual interpretation question about the source text that must be answered using the text.",{"id":599,"name":600,"field":601,"intro":602,"type":587},9346,"Answer Type","answer_type","Identifies the primary type of answer required by the question.",{"id":604,"name":605,"field":606,"intro":607,"type":587},9347,"Contract Source Excerpt","source_text","The licensing contract text or relevant context to analyze, preserving clause numbers, limiting conditions, and cross-references.",{"id":609,"name":610,"field":611,"intro":612,"type":613},9348,"Cited Evidence","cited_evidence","Contract clause locations and excerpts supporting the answer, with their relevance to the conclusion.","object",{"id":615,"name":616,"field":617,"intro":618,"type":619},9349,"Reasoning Steps","reasoning_steps","Verifiable analysis steps showing how textual evidence, conditions, exceptions, and conclusions relate.","array",{"id":621,"name":622,"field":623,"intro":624,"type":619},9350,"Issue Categories","issue_categories","One or more labels identifying applicable types of challenging contract language.",{"id":626,"name":627,"field":628,"intro":629,"type":613},9351,"Ambiguity Analysis","ambiguity_analysis","Identifies whether a clause permits multiple reasonable interpretations and records competing readings and the basis for resolving them.",{"id":631,"name":632,"field":633,"intro":634,"type":613},9352,"Structured Clause Interpretation","structured_interpretation","A structured representation of the rights, applicable conditions, exceptions, order of precedence, and post-termination duties discussed in the answer.",[636,640,644,648],{"id":637,"question":638,"answer":639},6535,"Which licensing contract challenges are covered?","The dataset covers authorization exceptions, cross-referenced definitions, conditional rights, order of precedence, conflicting clauses, and obligations that survive termination. Each example includes a question and a reference answer based on the contract text.",{"id":641,"question":642,"answer":643},6536,"Are answers supported by evidence from the contract?","Yes. The data includes source excerpts, cited evidence, and verifiable reasoning steps to help users check how an answer follows from the text's conditions, exceptions, and scope.",{"id":645,"question":646,"answer":647},6537,"Which training and evaluation tasks does it support?","It supports closed-domain question answering, clause interpretation, evidence localization, and complex condition reasoning for licensing contracts. Use it for domain-specific supervised fine-tuning or to evaluate a model's understanding of long-tail wording and ambiguity.",{"id":649,"question":650,"answer":651},6538,"How can I access the dataset and confirm its license?","Check the current product page for available access methods, file specifications, and license terms. Before using the data for training, evaluation, or commercial applications, confirm the permitted scope and comply with applicable contract-text and data-use requirements.",[653,670,684],{"id":654,"relate_table":655,"relate_id":656,"file_size":572,"file_name":657,"path":8,"duration":572,"cate":483,"file_format":658,"audio_rate":8,"audio_channel":522,"audio_bit_depth":522,"quality":8,"annotation":659,"cate_name":660,"answer":661,"question":662,"answer_type":663,"source_text":664,"cited_evidence":665,"reasoning_steps":666,"issue_categories":667,"ambiguity_analysis":668,"structured_interpretation":669},15213,"union_cubo",292815056,"样例_3.json","json","{\"answer\": \"Yes, but only to the extent retained within the limits provided in the clauses. The Licensee must immediately cease exercising the license rights and delete all copies within its control within ten business days; the exception is that it may retain one archival copy solely for legal, regulatory, or internal audit compliance, and such copy may not be used for production, development, distribution, or other business purposes. Backup copies created in accordance with the usual backup cycle may be retained until normally overwritten, but they must be inaccessible to ordinary users, may not be actively used to restore daily business, and may not be used to restore any license rights. Obligations that survive termination include the five-year confidentiality obligation and the two-year obligation to retain audit records relating to license fees and scope of use.\", \"question\": \"After termination of the Agreement, may the Licensee continue to retain archival copies and backup copies of the Licensed Software? Which obligations survive?\", \"answer_type\": \"Post-Termination Survival Assessment\", \"source_text\": \"12.1 Cessation of Use and Deletion After Termination: After termination of this Agreement or expiry of the license term, the Licensee shall immediately cease exercising the license rights granted under this Agreement, delete all copies of the Licensed Software within its control within ten business days, and submit proof of deletion to the Licensor. However, the Licensee may retain one archival copy kept solely to comply with legal, regulatory, or internal audit requirements, and such copy may not be used for production, development, distribution, or other business purposes. 12.2 Backup Copies: Backup copies created in accordance with the usual information technology backup cycle may be retained until they are overwritten in the normal cycle, but they must remain inaccessible to ordinary users and may not be actively invoked to restore daily business; if invoked for disaster recovery, no license rights may be restored. 12.3 Confidentiality Obligations: Confidentiality obligations concerning the Licensed Software and its technical materials shall survive termination of the Agreement for five years. 12.4 Audit Records: Records relating to license fee calculation and scope of use shall be retained for two years after termination to enable completion of audits for the period before termination.\", \"cited_evidence\": \"{\\\"clauses\\\": [{\\\"clause_label\\\": \\\"Article 12.1 Cessation of Use and Deletion After Termination\\\", \\\"quoted_text\\\": \\\"After termination of this Agreement or expiry of the license term, the Licensee shall immediately cease exercising the license rights granted under this Agreement, delete all copies of the Licensed Software within its control within ten business days, and submit proof of deletion to the Licensor. However, the Licensee may retain one archival copy kept solely to comply with legal, regulatory, or internal audit requirements.\\\", \\\"relevance\\\": \\\"This article establishes the post-termination cessation of use and deletion obligations and expressly permits retention of one archival copy subject to strict purpose limitations.\\\"}, {\\\"clause_label\\\": \\\"Article 12.2 Backup Copies\\\", \\\"quoted_text\\\": \\\"Backup copies created in accordance with the usual information technology backup cycle may be retained until they are overwritten in the normal cycle, but they must remain inaccessible to ordinary users and may not be actively invoked to restore daily business.\\\", \\\"relevance\\\": \\\"This article sets a retention exception for automatically generated backup copies distinct from ordinary working copies and provides access and invocation restrictions.\\\"}, {\\\"clause_label\\\": \\\"Article 12.3 Confidentiality Obligations\\\", \\\"quoted_text\\\": \\\"Confidentiality obligations concerning the Licensed Software and its technical materials shall survive termination of the Agreement for five years.\\\", \\\"relevance\\\": \\\"This article expressly provides the post-termination survival period for confidentiality.\\\"}, {\\\"clause_label\\\": \\\"Article 12.4 Audit Records\\\", \\\"quoted_text\\\": \\\"Records relating to license fee calculation and scope of use shall be retained for two years after termination to enable completion of audits for the period before termination.\\\", \\\"relevance\\\": \\\"This article expressly provides the post-termination audit record retention obligation and its two-year period.\\\"}]}\", \"reasoning_steps\": \"[\\\"Article 12.1 provides that after termination the Licensee must immediately cease exercising the license rights and delete all copies within its control within ten business days.\\\", \\\"The same article, by way of a proviso, provides that one archival copy may be retained, but its use is strictly limited to legal, regulatory, or internal audit compliance and it may not be used for any business purpose.\\\", \\\"Article 12.2 sets an independent retention rule for backup copies created in the usual backup cycle, with the retention period depending on the normal overwrite cycle, and requires that backups be inaccessible to ordinary users and not actively used to restore daily business.\\\", \\\"Articles 12.3 and 12.4 expressly provide, respectively, that confidentiality obligations survive for five years and that audit records be retained for two years; therefore, these obligations do not immediately terminate upon termination of the Agreement.\\\"]\", \"issue_categories\": \"[\\\"Post-Termination Surviving Obligations\\\", \\\"Licensing Exception\\\", \\\"Clause Conflict\\\"]\", \"ambiguity_analysis\": \"{\\\"is_ambiguous\\\": true, \\\"ambiguity_description\\\": \\\"Article 12.1 requires deletion of all copies but then permits retention of one archival copy, and Article 12.2 further permits backup copies to continue to exist until normally overwritten; if the deletion obligation is read in isolation, it may conflict with the two retention rules.\\\", \\\"alternative_readings\\\": [\\\"Read the deletion of all copies as not permitting retention of any form of copy after termination.\\\", \\\"Treat the archival copy and backup copy provisions as express exceptions to the general deletion obligation and permit retention within their qualifying conditions.\\\"], \\\"resolution_basis\\\": \\\"Article 12.1 uses a proviso to expressly introduce the archival copy exception, and Article 12.2 separately sets out specific retention conditions for backup copies. Therefore, the second interpretation should be adopted; however, neither archival copies nor backup copies may be used to restore or continue any licensed use activities.\\\"}\", \"structured_interpretation\": \"{\\\"conclusion\\\": \\\"After termination, one compliance archival copy and backup copies within the normal backup cycle may be retained under strict conditions, but continued use of the Licensed Software is not permitted; confidentiality and audit record obligations survive for the agreed periods.\\\", \\\"scope\\\": \\\"The deletion and cessation-of-use obligations apply to copies of the Licensed Software within the Licensee's control; the archival exception is limited to one copy, and the backup exception is limited to backup copies created in the normal cycle and not yet overwritten.\\\", \\\"conditions\\\": [\\\"Immediately cease exercising the license rights after termination.\\\", \\\"Delete ordinary copies within its control within ten business days and submit proof of deletion.\\\", \\\"The archival copy may be used only for legal, regulatory, or internal audit compliance.\\\", \\\"Backup copies must be inaccessible to ordinary users and may not be actively invoked to restore daily business.\\\"], \\\"exceptions\\\": [\\\"One archival copy may be retained solely for compliance purposes.\\\", \\\"Backup copies created in accordance with the usual backup cycle may be retained until normally overwritten.\\\"], \\\"precedence_rule\\\": \\\"The general deletion rule in Article 12.1 should be read together with the archival exception expressly provided therein; Article 12.2 is a special rule for backup copies. Neither exception can restore license rights after termination or permit continued production, development, or distribution activities.\\\", \\\"survival_obligations\\\": \\\"Confidentiality obligations survive for five years after termination; audit records relating to license fee calculation and scope of use are retained for two years. The cessation-of-use, deletion, and backup access restrictions also apply during the corresponding performance periods after termination.\\\"}\"}","文本","Yes, but only to the extent retained within the limits provided in the clauses. The Licensee must immediately cease exercising the license rights and delete all copies within its control within ten business days; the exception is that it may retain one archival copy solely for legal, regulatory, or internal audit compliance, and such copy may not be used for production, development, distribution, or other business purposes. Backup copies created in accordance with the usual backup cycle may be retained until normally overwritten, but they must be inaccessible to ordinary users, may not be actively used to restore daily business, and may not be used to restore any license rights. Obligations that survive termination include the five-year confidentiality obligation and the two-year obligation to retain audit records relating to license fees and scope of use.","After termination of the Agreement, may the Licensee continue to retain archival copies and backup copies of the Licensed Software? Which obligations survive?","Post-Termination Survival Assessment","12.1 Cessation of Use and Deletion After Termination: After termination of this Agreement or expiry of the license term, the Licensee shall immediately cease exercising the license rights granted under this Agreement, delete all copies of the Licensed Software within its control within ten business days, and submit proof of deletion to the Licensor. However, the Licensee may retain one archival copy kept solely to comply with legal, regulatory, or internal audit requirements, and such copy may not be used for production, development, distribution, or other business purposes. 12.2 Backup Copies: Backup copies created in accordance with the usual information technology backup cycle may be retained until they are overwritten in the normal cycle, but they must remain inaccessible to ordinary users and may not be actively invoked to restore daily business; if invoked for disaster recovery, no license rights may be restored. 12.3 Confidentiality Obligations: Confidentiality obligations concerning the Licensed Software and its technical materials shall survive termination of the Agreement for five years. 12.4 Audit Records: Records relating to license fee calculation and scope of use shall be retained for two years after termination to enable completion of audits for the period before termination.","{\"clauses\": [{\"clause_label\": \"Article 12.1 Cessation of Use and Deletion After Termination\", \"quoted_text\": \"After termination of this Agreement or expiry of the license term, the Licensee shall immediately cease exercising the license rights granted under this Agreement, delete all copies of the Licensed Software within its control within ten business days, and submit proof of deletion to the Licensor. However, the Licensee may retain one archival copy kept solely to comply with legal, regulatory, or internal audit requirements.\", \"relevance\": \"This article establishes the post-termination cessation of use and deletion obligations and expressly permits retention of one archival copy subject to strict purpose limitations.\"}, {\"clause_label\": \"Article 12.2 Backup Copies\", \"quoted_text\": \"Backup copies created in accordance with the usual information technology backup cycle may be retained until they are overwritten in the normal cycle, but they must remain inaccessible to ordinary users and may not be actively invoked to restore daily business.\", \"relevance\": \"This article sets a retention exception for automatically generated backup copies distinct from ordinary working copies and provides access and invocation restrictions.\"}, {\"clause_label\": \"Article 12.3 Confidentiality Obligations\", \"quoted_text\": \"Confidentiality obligations concerning the Licensed Software and its technical materials shall survive termination of the Agreement for five years.\", \"relevance\": \"This article expressly provides the post-termination survival period for confidentiality.\"}, {\"clause_label\": \"Article 12.4 Audit Records\", \"quoted_text\": \"Records relating to license fee calculation and scope of use shall be retained for two years after termination to enable completion of audits for the period before termination.\", \"relevance\": \"This article expressly provides the post-termination audit record retention obligation and its two-year period.\"}]}","[\"Article 12.1 provides that after termination the Licensee must immediately cease exercising the license rights and delete all copies within its control within ten business days.\", \"The same article, by way of a proviso, provides that one archival copy may be retained, but its use is strictly limited to legal, regulatory, or internal audit compliance and it may not be used for any business purpose.\", \"Article 12.2 sets an independent retention rule for backup copies created in the usual backup cycle, with the retention period depending on the normal overwrite cycle, and requires that backups be inaccessible to ordinary users and not actively used to restore daily business.\", \"Articles 12.3 and 12.4 expressly provide, respectively, that confidentiality obligations survive for five years and that audit records be retained for two years; therefore, these obligations do not immediately terminate upon termination of the Agreement.\"]","[\"Post-Termination Surviving Obligations\", \"Licensing Exception\", \"Clause Conflict\"]","{\"is_ambiguous\": true, \"ambiguity_description\": \"Article 12.1 requires deletion of all copies but then permits retention of one archival copy, and Article 12.2 further permits backup copies to continue to exist until normally overwritten; if the deletion obligation is read in isolation, it may conflict with the two retention rules.\", \"alternative_readings\": [\"Read the deletion of all copies as not permitting retention of any form of copy after termination.\", \"Treat the archival copy and backup copy provisions as express exceptions to the general deletion obligation and permit retention within their qualifying conditions.\"], \"resolution_basis\": \"Article 12.1 uses a proviso to expressly introduce the archival copy exception, and Article 12.2 separately sets out specific retention conditions for backup copies. Therefore, the second interpretation should be adopted; however, neither archival copies nor backup copies may be used to restore or continue any licensed use activities.\"}","{\"conclusion\": \"After termination, one compliance archival copy and backup copies within the normal backup cycle may be retained under strict conditions, but continued use of the Licensed Software is not permitted; confidentiality and audit record obligations survive for the agreed periods.\", \"scope\": \"The deletion and cessation-of-use obligations apply to copies of the Licensed Software within the Licensee's control; the archival exception is limited to one copy, and the backup exception is limited to backup copies created in the normal cycle and not yet overwritten.\", \"conditions\": [\"Immediately cease exercising the license rights after termination.\", \"Delete ordinary copies within its control within ten business days and submit proof of deletion.\", \"The archival copy may be used only for legal, regulatory, or internal audit compliance.\", \"Backup copies must be inaccessible to ordinary users and may not be actively invoked to restore daily business.\"], \"exceptions\": [\"One archival copy may be retained solely for compliance purposes.\", \"Backup copies created in accordance with the usual backup cycle may be retained until normally overwritten.\"], \"precedence_rule\": \"The general deletion rule in Article 12.1 should be read together with the archival exception expressly provided therein; Article 12.2 is a special rule for backup copies. Neither exception can restore license rights after termination or permit continued production, development, or distribution activities.\", \"survival_obligations\": \"Confidentiality obligations survive for five years after termination; audit records relating to license fee calculation and scope of use are retained for two years. The cessation-of-use, deletion, and backup access restrictions also apply during the corresponding performance periods after termination.\"}",{"id":671,"relate_table":655,"relate_id":672,"file_size":572,"file_name":673,"path":8,"duration":572,"cate":483,"file_format":658,"audio_rate":8,"audio_channel":522,"audio_bit_depth":522,"quality":8,"annotation":674,"cate_name":660,"answer":675,"question":676,"answer_type":677,"source_text":678,"cited_evidence":679,"reasoning_steps":680,"issue_categories":681,"ambiguity_analysis":682,"structured_interpretation":683},15212,1123659043,"样例_2.json","{\"answer\": \"Yes, but only within the scope of Production Use. Article 3.1 permits the Licensee to use, reproduce, and modify the Licensed Software for Production Use; Schedule B further expressly permits hosting the modified software on approved cloud services and provides that it prevails in the event of a conflict with the Master Agreement. Therefore, deploying the software on cloud services listed in Schedule B for the Licensee or its authorized affiliates to conduct their own internal business is permitted. However, the license does not include the right to provide external customers with independent access, resell, or distribute the software through such cloud services.\", \"question\": \"Can the Licensee deploy and host modified Licensed Software on approved cloud services listed in Schedule B for its employees to conduct internal business through such cloud services?\", \"answer_type\": \"Conflict Resolution\", \"source_text\": \"1.1 Production Use: means the deployment or operation of the Licensed Software by the Licensee or its authorized affiliates for their own internal business operations, but excludes resale or distribution to third parties or enabling third parties to independently access the Licensed Software. 3.1 Use License: During the license term, the Licensee may use, reproduce, and modify the Licensed Software for Production Use purposes. 4.2 Third-Party Infrastructure Restriction: Except as otherwise provided in Schedule B, the Licensee may not host the Licensed Software on third-party infrastructure, nor provide access to external customers through third-party infrastructure. Schedule B Approved Cloud Services: The Licensee may use approved cloud services for Production Use, including hosting modified Licensed Software on such cloud services; if Schedule B conflicts with the Master Agreement regarding approved cloud services, Schedule B shall prevail.\", \"cited_evidence\": \"{\\\"clauses\\\": [{\\\"clause_label\\\": \\\"Article 1.1 Production Use Definition\\\", \\\"quoted_text\\\": \\\"means the deployment or operation of the Licensed Software by the Licensee or its authorized affiliates for their own internal business operations, but excludes resale or distribution to third parties or enabling third parties to independently access the Licensed Software.\\\", \\\"relevance\\\": \\\"This definition determines the purpose and boundaries of the license, supports internal business deployment, but excludes independent access, resale, and distribution to external customers.\\\"}, {\\\"clause_label\\\": \\\"Article 4.2 Third-Party Infrastructure Restriction\\\", \\\"quoted_text\\\": \\\"Except as otherwise provided in Schedule B, the Licensee may not host the Licensed Software on third-party infrastructure.\\\", \\\"relevance\\\": \\\"This article provides the general prohibition and, through the phrase 'except as otherwise provided in Schedule B,' leaves room for the specific exception in Schedule B.\\\"}, {\\\"clause_label\\\": \\\"Schedule B Approved Cloud Services\\\", \\\"quoted_text\\\": \\\"The Licensee may use approved cloud services for Production Use, including hosting modified Licensed Software on such cloud services; if Schedule B conflicts with the Master Agreement regarding approved cloud services, Schedule B shall prevail.\\\", \\\"relevance\\\": \\\"This article directly authorizes hosting modified software on approved cloud services and expressly provides that Schedule B prevails in the event of a conflict.\\\"}]}\", \"reasoning_steps\": \"[\\\"Article 1.1 limits Production Use to the Licensee's or its authorized affiliates' own internal business and excludes resale or distribution to third parties or provision of independent access.\\\", \\\"Article 3.1 limits the rights to use, reproduce, and modify to Production Use purposes.\\\", \\\"Article 4.2 establishes the general prohibition on third-party infrastructure but expressly preserves any different provisions in Schedule B.\\\", \\\"Schedule B expressly permits hosting modified software on approved cloud services and provides that it prevails in the event of a conflict with the Master Agreement, so this specific exception takes precedence over the general restriction in Article 4.2.\\\"]\", \"issue_categories\": \"[\\\"Definition Cross-Reference\\\", \\\"Priority Order\\\", \\\"Clause Conflict\\\", \\\"Conditional Rights\\\"]\", \"ambiguity_analysis\": \"{\\\"is_ambiguous\\\": true, \\\"ambiguity_description\\\": \\\"Article 4.2 in principle prohibits third-party infrastructure, while Schedule B permits hosting software on approved cloud services; there is an apparent conflict between the general rule and the specific exception.\\\", \\\"alternative_readings\\\": [\\\"Read Article 4.2 absolutely, so that any hosting on third-party infrastructure is prohibited.\\\", \\\"Treat Schedule B as a specific exception expressly preserved by Article 4.2, allowing hosting only on approved cloud services.\\\"], \\\"resolution_basis\\\": \\\"Article 4.2 expressly uses the reservation 'except as otherwise provided in Schedule B,' and Schedule B expressly provides that it prevails in the event of a conflict with the Master Agreement. Therefore, the second interpretation should be adopted, but it remains subject to the limitation on the scope of Production Use in Article 1.1.\\\"}\", \"structured_interpretation\": \"{\\\"conclusion\\\": \\\"Modified Licensed Software may be hosted on approved cloud services listed in Schedule B, but only for the internal Production Use of the Licensee or its authorized affiliates.\\\", \\\"scope\\\": \\\"The rights cover the use, reproduction, modification, and hosting on approved cloud services of the Licensed Software during the license term, with the Licensee or its authorized affiliates as the users and their own internal business as the purpose.\\\", \\\"conditions\\\": [\\\"The cloud service must be an approved cloud service listed in Schedule B.\\\", \\\"Hosting and operation must serve Production Use.\\\", \\\"The cloud service may not be used to provide external customers with independent access, resell, or distribute the Licensed Software.\\\"], \\\"exceptions\\\": [\\\"Schedule B makes an express exception to the third-party infrastructure prohibition, allowing modified software to be hosted on approved cloud services.\\\"], \\\"precedence_rule\\\": \\\"Regarding hosting on approved cloud services, Schedule B, as a specific provision, takes precedence over the general prohibition on third-party infrastructure in Article 4.2; the definition of the scope of Production Use in Article 1.1 still applies.\\\", \\\"survival_obligations\\\": \\\"The provided excerpt does not provide for survival of the hosting license or Production Use rights after termination of the Agreement, so it cannot be determined from this excerpt that operation or retention of such deployment may continue after termination.\\\"}\"}","Yes, but only within the scope of Production Use. Article 3.1 permits the Licensee to use, reproduce, and modify the Licensed Software for Production Use; Schedule B further expressly permits hosting the modified software on approved cloud services and provides that it prevails in the event of a conflict with the Master Agreement. Therefore, deploying the software on cloud services listed in Schedule B for the Licensee or its authorized affiliates to conduct their own internal business is permitted. However, the license does not include the right to provide external customers with independent access, resell, or distribute the software through such cloud services.","Can the Licensee deploy and host modified Licensed Software on approved cloud services listed in Schedule B for its employees to conduct internal business through such cloud services?","Conflict Resolution","1.1 Production Use: means the deployment or operation of the Licensed Software by the Licensee or its authorized affiliates for their own internal business operations, but excludes resale or distribution to third parties or enabling third parties to independently access the Licensed Software. 3.1 Use License: During the license term, the Licensee may use, reproduce, and modify the Licensed Software for Production Use purposes. 4.2 Third-Party Infrastructure Restriction: Except as otherwise provided in Schedule B, the Licensee may not host the Licensed Software on third-party infrastructure, nor provide access to external customers through third-party infrastructure. Schedule B Approved Cloud Services: The Licensee may use approved cloud services for Production Use, including hosting modified Licensed Software on such cloud services; if Schedule B conflicts with the Master Agreement regarding approved cloud services, Schedule B shall prevail.","{\"clauses\": [{\"clause_label\": \"Article 1.1 Production Use Definition\", \"quoted_text\": \"means the deployment or operation of the Licensed Software by the Licensee or its authorized affiliates for their own internal business operations, but excludes resale or distribution to third parties or enabling third parties to independently access the Licensed Software.\", \"relevance\": \"This definition determines the purpose and boundaries of the license, supports internal business deployment, but excludes independent access, resale, and distribution to external customers.\"}, {\"clause_label\": \"Article 4.2 Third-Party Infrastructure Restriction\", \"quoted_text\": \"Except as otherwise provided in Schedule B, the Licensee may not host the Licensed Software on third-party infrastructure.\", \"relevance\": \"This article provides the general prohibition and, through the phrase 'except as otherwise provided in Schedule B,' leaves room for the specific exception in Schedule B.\"}, {\"clause_label\": \"Schedule B Approved Cloud Services\", \"quoted_text\": \"The Licensee may use approved cloud services for Production Use, including hosting modified Licensed Software on such cloud services; if Schedule B conflicts with the Master Agreement regarding approved cloud services, Schedule B shall prevail.\", \"relevance\": \"This article directly authorizes hosting modified software on approved cloud services and expressly provides that Schedule B prevails in the event of a conflict.\"}]}","[\"Article 1.1 limits Production Use to the Licensee's or its authorized affiliates' own internal business and excludes resale or distribution to third parties or provision of independent access.\", \"Article 3.1 limits the rights to use, reproduce, and modify to Production Use purposes.\", \"Article 4.2 establishes the general prohibition on third-party infrastructure but expressly preserves any different provisions in Schedule B.\", \"Schedule B expressly permits hosting modified software on approved cloud services and provides that it prevails in the event of a conflict with the Master Agreement, so this specific exception takes precedence over the general restriction in Article 4.2.\"]","[\"Definition Cross-Reference\", \"Priority Order\", \"Clause Conflict\", \"Conditional Rights\"]","{\"is_ambiguous\": true, \"ambiguity_description\": \"Article 4.2 in principle prohibits third-party infrastructure, while Schedule B permits hosting software on approved cloud services; there is an apparent conflict between the general rule and the specific exception.\", \"alternative_readings\": [\"Read Article 4.2 absolutely, so that any hosting on third-party infrastructure is prohibited.\", \"Treat Schedule B as a specific exception expressly preserved by Article 4.2, allowing hosting only on approved cloud services.\"], \"resolution_basis\": \"Article 4.2 expressly uses the reservation 'except as otherwise provided in Schedule B,' and Schedule B expressly provides that it prevails in the event of a conflict with the Master Agreement. Therefore, the second interpretation should be adopted, but it remains subject to the limitation on the scope of Production Use in Article 1.1.\"}","{\"conclusion\": \"Modified Licensed Software may be hosted on approved cloud services listed in Schedule B, but only for the internal Production Use of the Licensee or its authorized affiliates.\", \"scope\": \"The rights cover the use, reproduction, modification, and hosting on approved cloud services of the Licensed Software during the license term, with the Licensee or its authorized affiliates as the users and their own internal business as the purpose.\", \"conditions\": [\"The cloud service must be an approved cloud service listed in Schedule B.\", \"Hosting and operation must serve Production Use.\", \"The cloud service may not be used to provide external customers with independent access, resell, or distribute the Licensed Software.\"], \"exceptions\": [\"Schedule B makes an express exception to the third-party infrastructure prohibition, allowing modified software to be hosted on approved cloud services.\"], \"precedence_rule\": \"Regarding hosting on approved cloud services, Schedule B, as a specific provision, takes precedence over the general prohibition on third-party infrastructure in Article 4.2; the definition of the scope of Production Use in Article 1.1 still applies.\", \"survival_obligations\": \"The provided excerpt does not provide for survival of the hosting license or Production Use rights after termination of the Agreement, so it cannot be determined from this excerpt that operation or retention of such deployment may continue after termination.\"}",{"id":685,"relate_table":655,"relate_id":686,"file_size":572,"file_name":687,"path":8,"duration":572,"cate":483,"file_format":658,"audio_rate":8,"audio_channel":522,"audio_bit_depth":522,"quality":8,"annotation":688,"cate_name":660,"answer":689,"question":690,"answer_type":691,"source_text":692,"cited_evidence":693,"reasoning_steps":694,"issue_categories":695,"ambiguity_analysis":696,"structured_interpretation":697},15211,1789756834,"样例_1.json","{\"answer\": \"No. Article 2.4 provides that, except for the circumstances expressly listed in the clause, the Licensee may not sublicense or grant any third party the right to use the Licensed Software. That article only permits the grant of a limited sublicense to an integration service provider approved in writing by the Licensor, and the purpose must be limited to providing integration services for the Licensee's products. A commercial distributor is neither an integration service provider referred to in that exception nor granted independent distribution rights; therefore, unless it simultaneously satisfies all conditions, including written approval, integration service use, and confidentiality obligations, it cannot obtain such sublicense rights. The evaluation and testing exception in Article 8.2 also cannot support commercial distribution.\", \"question\": \"Can the Licensee grant its commercial distributor a sublicense to the Licensed Software, enabling the distributor to independently distribute the software?\", \"answer_type\": \"Exception Application\", \"source_text\": \"2.1 License Scope: During the license term, the Licensor grants the Licensee a non-exclusive, non-transferable license, under which the Licensee may reproduce, integrate, and distribute the Licensed Software within the agreed territory, but only as a component of the Licensee's products for provision to end users. 2.2 End User: means a customer that purchases or is authorized to use the Licensee's products but does not obtain independent distribution rights to the Licensed Software. 2.4 Sublicense Restrictions: Except as expressly provided in this article, the Licensee may not sublicense, lease, lend, or otherwise grant any third party the right to use the Licensed Software. The Licensee may grant a limited sublicense to an integration service provider approved in writing by the Licensor, but such sublicense is limited to providing integration services for the Licensee's products, and the Licensor's prior written consent must be obtained and the provider must be bound by confidentiality obligations no less stringent than the standards of this Agreement. 8.2 Exception: The Licensee may provide potential customers with temporary access rights solely for evaluation and testing, but not for commercial deployment.\", \"cited_evidence\": \"{\\\"clauses\\\": [{\\\"clause_label\\\": \\\"Article 2.1 License Scope\\\", \\\"quoted_text\\\": \\\"The Licensee may reproduce, integrate, and distribute the Licensed Software within the agreed territory, but only as a component of the Licensee's products for provision to end users.\\\", \\\"relevance\\\": \\\"This article defines the purpose and object of the general license, indicating that distribution rights attach to the Licensee's products, and independent sublicense rights cannot be inferred from it for distributors.\\\"}, {\\\"clause_label\\\": \\\"Article 2.4 Sublicense Restrictions\\\", \\\"quoted_text\\\": \\\"Except as expressly provided in this article, the Licensee may not sublicense, lease, lend, or otherwise grant any third party the right to use the Licensed Software. The Licensee may grant a limited sublicense to an integration service provider approved in writing by the Licensor, but such sublicense is limited to providing integration services for the Licensee's products.\\\", \\\"relevance\\\": \\\"This article establishes the general rule prohibiting sublicensing and limits the only relevant exception to integration service providers that are approved in writing and used solely for integration services.\\\"}, {\\\"clause_label\\\": \\\"Article 8.2 Evaluation Exception\\\", \\\"quoted_text\\\": \\\"The Licensee may provide potential customers with temporary access rights solely for evaluation and testing, but not for commercial deployment.\\\", \\\"relevance\\\": \\\"This article covers only evaluation and testing access and expressly excludes commercial deployment, and cannot support granting independent distribution rights to a commercial distributor.\\\"}]}\", \"reasoning_steps\": \"[\\\"The general license in Article 2.1 only permits the Licensee to provide the Licensed Software to end users as a component of its products, and does not grant the right to distribute it independently to third parties.\\\", \\\"Article 2.4 establishes the general rule against sublicensing and limits the integration service provider exception to providers approved in writing by the Licensor, solely for integration services, and subject to corresponding confidentiality obligations.\\\", \\\"A commercial distributor's independent distribution exceeds the integration service purpose and also does not meet the limitation in the end user definition that no independent distribution rights be obtained.\\\", \\\"Article 8.2 permits only evaluation and testing access and expressly excludes commercial deployment, so it cannot serve as a basis for commercial distribution.\\\"]\", \"issue_categories\": \"[\\\"Licensing Exception\\\", \\\"Conditional Rights\\\"]\", \"ambiguity_analysis\": \"{\\\"is_ambiguous\\\": false, \\\"ambiguity_description\\\": \\\"The clause uses an express prohibition and limits the integration service provider exception to written approval, a specific purpose, and confidentiality obligations; a commercial distributor's independent distribution does not fall within that exception.\\\", \\\"alternative_readings\\\": [], \\\"resolution_basis\\\": \\\"The restrictive wording in Article 2.4, such as 'except as expressly provided in this article' and 'limited to,' together with the express exclusion of commercial deployment in Article 8.2, jointly preclude an interpretation that expands the exception to commercial distributors.\\\"}\", \"structured_interpretation\": \"{\\\"conclusion\\\": \\\"The Licensee may not grant a commercial distributor a sublicense to independently distribute the Licensed Software.\\\", \\\"scope\\\": \\\"The general license covers only the Licensee's provision of the software to end users as a component of its own products within the agreed territory and during the license term.\\\", \\\"conditions\\\": [\\\"If a sublicense is granted to a third party, that third party must be an integration service provider approved in writing by the Licensor.\\\", \\\"The sublicense purpose must be strictly limited to providing integration services for the Licensee's products.\\\", \\\"The Licensor's prior written consent must be obtained, and the third party must be bound by confidentiality obligations no less stringent than the standards of the Agreement.\\\"], \\\"exceptions\\\": [\\\"An integration service provider approved in writing may receive a limited sublicense.\\\", \\\"Potential customers may receive temporary access rights solely for evaluation and testing, but not for commercial deployment.\\\"], \\\"precedence_rule\\\": \\\"The express sublicense restrictions and exceptions in Article 2.4 take precedence over the general distribution license in Article 2.1; the general license cannot expand the covered parties or purposes of the express exceptions.\\\", \\\"survival_obligations\\\": \\\"The provided excerpt does not specify the exact survival period after termination for the sublicense restriction or related confidentiality obligations; the post-termination period cannot be determined solely from this excerpt.\\\"}\"}","No. Article 2.4 provides that, except for the circumstances expressly listed in the clause, the Licensee may not sublicense or grant any third party the right to use the Licensed Software. That article only permits the grant of a limited sublicense to an integration service provider approved in writing by the Licensor, and the purpose must be limited to providing integration services for the Licensee's products. A commercial distributor is neither an integration service provider referred to in that exception nor granted independent distribution rights; therefore, unless it simultaneously satisfies all conditions, including written approval, integration service use, and confidentiality obligations, it cannot obtain such sublicense rights. The evaluation and testing exception in Article 8.2 also cannot support commercial distribution.","Can the Licensee grant its commercial distributor a sublicense to the Licensed Software, enabling the distributor to independently distribute the software?","Exception Application","2.1 License Scope: During the license term, the Licensor grants the Licensee a non-exclusive, non-transferable license, under which the Licensee may reproduce, integrate, and distribute the Licensed Software within the agreed territory, but only as a component of the Licensee's products for provision to end users. 2.2 End User: means a customer that purchases or is authorized to use the Licensee's products but does not obtain independent distribution rights to the Licensed Software. 2.4 Sublicense Restrictions: Except as expressly provided in this article, the Licensee may not sublicense, lease, lend, or otherwise grant any third party the right to use the Licensed Software. The Licensee may grant a limited sublicense to an integration service provider approved in writing by the Licensor, but such sublicense is limited to providing integration services for the Licensee's products, and the Licensor's prior written consent must be obtained and the provider must be bound by confidentiality obligations no less stringent than the standards of this Agreement. 8.2 Exception: The Licensee may provide potential customers with temporary access rights solely for evaluation and testing, but not for commercial deployment.","{\"clauses\": [{\"clause_label\": \"Article 2.1 License Scope\", \"quoted_text\": \"The Licensee may reproduce, integrate, and distribute the Licensed Software within the agreed territory, but only as a component of the Licensee's products for provision to end users.\", \"relevance\": \"This article defines the purpose and object of the general license, indicating that distribution rights attach to the Licensee's products, and independent sublicense rights cannot be inferred from it for distributors.\"}, {\"clause_label\": \"Article 2.4 Sublicense Restrictions\", \"quoted_text\": \"Except as expressly provided in this article, the Licensee may not sublicense, lease, lend, or otherwise grant any third party the right to use the Licensed Software. The Licensee may grant a limited sublicense to an integration service provider approved in writing by the Licensor, but such sublicense is limited to providing integration services for the Licensee's products.\", \"relevance\": \"This article establishes the general rule prohibiting sublicensing and limits the only relevant exception to integration service providers that are approved in writing and used solely for integration services.\"}, {\"clause_label\": \"Article 8.2 Evaluation Exception\", \"quoted_text\": \"The Licensee may provide potential customers with temporary access rights solely for evaluation and testing, but not for commercial deployment.\", \"relevance\": \"This article covers only evaluation and testing access and expressly excludes commercial deployment, and cannot support granting independent distribution rights to a commercial distributor.\"}]}","[\"The general license in Article 2.1 only permits the Licensee to provide the Licensed Software to end users as a component of its products, and does not grant the right to distribute it independently to third parties.\", \"Article 2.4 establishes the general rule against sublicensing and limits the integration service provider exception to providers approved in writing by the Licensor, solely for integration services, and subject to corresponding confidentiality obligations.\", \"A commercial distributor's independent distribution exceeds the integration service purpose and also does not meet the limitation in the end user definition that no independent distribution rights be obtained.\", \"Article 8.2 permits only evaluation and testing access and expressly excludes commercial deployment, so it cannot serve as a basis for commercial distribution.\"]","[\"Licensing Exception\", \"Conditional Rights\"]","{\"is_ambiguous\": false, \"ambiguity_description\": \"The clause uses an express prohibition and limits the integration service provider exception to written approval, a specific purpose, and confidentiality obligations; a commercial distributor's independent distribution does not fall within that exception.\", \"alternative_readings\": [], \"resolution_basis\": \"The restrictive wording in Article 2.4, such as 'except as expressly provided in this article' and 'limited to,' together with the express exclusion of commercial deployment in Article 8.2, jointly preclude an interpretation that expands the exception to commercial distributors.\"}","{\"conclusion\": \"The Licensee may not grant a commercial distributor a sublicense to independently distribute the Licensed Software.\", \"scope\": \"The general license covers only the Licensee's provision of the software to end users as a component of its own products within the agreed territory and during the license term.\", \"conditions\": [\"If a sublicense is granted to a third party, that third party must be an integration service provider approved in writing by the Licensor.\", \"The sublicense purpose must be strictly limited to providing integration services for the Licensee's products.\", \"The Licensor's prior written consent must be obtained, and the third party must be bound by confidentiality obligations no less stringent than the standards of the Agreement.\"], \"exceptions\": [\"An integration service provider approved in writing may receive a limited sublicense.\", \"Potential customers may receive temporary access rights solely for evaluation and testing, but not for commercial deployment.\"], \"precedence_rule\": \"The express sublicense restrictions and exceptions in Article 2.4 take precedence over the general distribution license in Article 2.1; the general license cannot expand the covered parties or purposes of the express exceptions.\", \"survival_obligations\": \"The provided excerpt does not specify the exact survival period after termination for the sublicense restriction or related confidentiality obligations; the post-termination period cannot be determined solely from this excerpt.\"}","{\"answer\":\"Yes, but only to the extent retained within the limits provided in the clauses. The Licensee must immediately cease exercising the license rights and delete all copies within its control within ten business days; the exception is that it may retain one archival copy solely for legal, regulatory, or internal audit compliance, and such copy may not be used for production, development, distribution, or other business purposes. Backup copies created in accordance with the usual backup cycle may be retained until normally overwritten, but they must be inaccessible to ordinary users, may not be actively used to restore daily business, and may not be used to restore any license rights. Obligations that survive termination include the five-year confidentiality obligation and the two-year obligation to retain audit records relating to license fees and scope of use.\",\"question\":\"After termination of the Agreement, may the Licensee continue to retain archival copies and backup copies of the Licensed Software? Which obligations survive?\",\"answer_type\":\"Post-Termination Survival Assessment\",\"source_text\":\"12.1 Cessation of Use and Deletion After Termination: After termination of this Agreement or expiry of the license term, the Licensee shall immediately cease exercising the license rights granted under this Agreement, delete all copies of the Licensed Software within its control within ten business days, and submit proof of deletion to the Licensor. However, the Licensee may retain one archival copy kept solely to comply with legal, regulatory, or internal audit requirements, and such copy may not be used for production, development, distribution, or other business purposes. 12.2 Backup Copies: Backup copies created in accordance with the usual information technology backup cycle may be retained until they are overwritten in the normal cycle, but they must remain inaccessible to ordinary users and may not be actively invoked to restore daily business; if invoked for disaster recovery, no license rights may be restored. 12.3 Confidentiality Obligations: Confidentiality obligations concerning the Licensed Software and its technical materials shall survive termination of the Agreement for five years. 12.4 Audit Records: Records relating to license fee calculation and scope of use shall be retained for two years after termination to enable completion of audits for the period before termination.\",\"cited_evidence\":\"{\\\"clauses\\\": [{\\\"clause_label\\\": \\\"Article 12.1 Cessation of Use and Deletion After Termination\\\", \\\"quoted_text\\\": \\\"After termination of this Agreement or expiry of the license term, the Licensee shall immediately cease exercising the license rights granted under this Agreement, delete all copies of the Licensed Software within its control within ten business days, and submit proof of deletion to the Licensor. However, the Licensee may retain one archival copy kept solely to comply with legal, regulatory, or internal audit requirements.\\\", \\\"relevance\\\": \\\"This article establishes the post-termination cessation of use and deletion obligations and expressly permits retention of one archival copy subject to strict purpose limitations.\\\"}, {\\\"clause_label\\\": \\\"Article 12.2 Backup Copies\\\", \\\"quoted_text\\\": \\\"Backup copies created in accordance with the usual information technology backup cycle may be retained until they are overwritten in the normal cycle, but they must remain inaccessible to ordinary users and may not be actively invoked to restore daily business.\\\", \\\"relevance\\\": \\\"This article sets a retention exception for automatically generated backup copies distinct from ordinary working copies and provides access and invocation restrictions.\\\"}, {\\\"clause_label\\\": \\\"Article 12.3 Confidentiality Obligations\\\", \\\"quoted_text\\\": \\\"Confidentiality obligations concerning the Licensed Software and its technical materials shall survive termination of the Agreement for five years.\\\", \\\"relevance\\\": \\\"This article expressly provides the post-termination survival period for confidentiality.\\\"}, {\\\"clause_label\\\": \\\"Article 12.4 Audit Records\\\", \\\"quoted_text\\\": \\\"Records relating to license fee calculation and scope of use shall be retained for two years after termination to enable completion of audits for the period before termination.\\\", \\\"relevance\\\": \\\"This article expressly provides the post-termination audit record retention obligation and its two-year period.\\\"}]}\",\"reasoning_steps\":\"[\\\"Article 12.1 provides that after termination the Licensee must immediately cease exercising the license rights and delete all copies within its control within ten business days.\\\", \\\"The same article, by way of a proviso, provides that one archival copy may be retained, but its use is strictly limited to legal, regulatory, or internal audit compliance and it may not be used for any business purpose.\\\", \\\"Article 12.2 sets an independent retention rule for backup copies created in the usual backup cycle, with the retention period depending on the normal overwrite cycle, and requires that backups be inaccessible to ordinary users and not actively used to restore daily business.\\\", \\\"Articles 12.3 and 12.4 expressly provide, respectively, that confidentiality obligations survive for five years and that audit records be retained for two years; therefore, these obligations do not immediately terminate upon termination of the Agreement.\\\"]\",\"issue_categories\":\"[\\\"Post-Termination Surviving Obligations\\\", \\\"Licensing Exception\\\", \\\"Clause Conflict\\\"]\",\"ambiguity_analysis\":\"{\\\"is_ambiguous\\\": true, \\\"ambiguity_description\\\": \\\"Article 12.1 requires deletion of all copies but then permits retention of one archival copy, and Article 12.2 further permits backup copies to continue to exist until normally overwritten; if the deletion obligation is read in isolation, it may conflict with the two retention rules.\\\", \\\"alternative_readings\\\": [\\\"Read the deletion of all copies as not permitting retention of any form of copy after termination.\\\", \\\"Treat the archival copy and backup copy provisions as express exceptions to the general deletion obligation and permit retention within their qualifying conditions.\\\"], \\\"resolution_basis\\\": \\\"Article 12.1 uses a proviso to expressly introduce the archival copy exception, and Article 12.2 separately sets out specific retention conditions for backup copies. Therefore, the second interpretation should be adopted; however, neither archival copies nor backup copies may be used to restore or continue any licensed use activities.\\\"}\",\"structured_interpretation\":\"{\\\"conclusion\\\": \\\"After termination, one compliance archival copy and backup copies within the normal backup cycle may be retained under strict conditions, but continued use of the Licensed Software is not permitted; confidentiality and audit record obligations survive for the agreed periods.\\\", \\\"scope\\\": \\\"The deletion and cessation-of-use obligations apply to copies of the Licensed Software within the Licensee's control; the archival exception is limited to one copy, and the backup exception is limited to backup copies created in the normal cycle and not yet overwritten.\\\", \\\"conditions\\\": [\\\"Immediately cease exercising the license rights after termination.\\\", \\\"Delete ordinary copies within its control within ten business days and submit proof of deletion.\\\", \\\"The archival copy may be used only for legal, regulatory, or internal audit compliance.\\\", \\\"Backup copies must be inaccessible to ordinary users and may not be actively invoked to restore daily business.\\\"], \\\"exceptions\\\": [\\\"One archival copy may be retained solely for compliance purposes.\\\", \\\"Backup copies created in accordance with the usual backup cycle may be retained until normally overwritten.\\\"], \\\"precedence_rule\\\": \\\"The general deletion rule in Article 12.1 should be read together with the archival exception expressly provided therein; Article 12.2 is a special rule for backup copies. Neither exception can restore license rights after termination or permit continued production, development, or distribution activities.\\\", \\\"survival_obligations\\\": \\\"Confidentiality obligations survive for five years after termination; audit records relating to license fee calculation and scope of use are retained for two years. The cessation-of-use, deletion, and backup access restrictions also apply during the corresponding performance periods after termination.\\\"}\"}","MOBIUSI INC","https:\u002F\u002Fstatic.mobiusi.com\u002Fmobiwusi\u002F20250829\u002F7bf4ac62b4533e2b809998a6f1c5491e.png?Expires=1792463130&OSSAccessKeyId=LTAI5tH8MQqhgeiAtrzCHrxM&Signature=v6Tr8jBrdm4s5wU1SnnyGsYg%2Bhw%3D&x-oss-process=image%2Fresize%2Cm_fill%2Cw_35%2Ch_35",[702,708],{"type":703,"title":704,"count_data":705},"bar","Length distribution",[706],{"name":707,"value":483},"1k lower",{"type":709,"title":710,"count_data":711},"pie","Language distribution",[712],{"name":713,"value":483},"English"]