LABSHIELD: A Multimodal Benchmark for Safety-Critical Reasoning and Planning in Scientific Laboratories
Abstract: Artificial intelligence is increasingly catalyzing scientific automation, with multimodal LLM (MLLM) agents evolving from lab assistants into self-driving lab operators. This transition imposes stringent safety requirements on laboratory environments, where fragile glassware, hazardous substances, and high-precision laboratory equipment render planning errors or misinterpreted risks potentially irreversible. However, the safety awareness and decision-making reliability of embodied agents in such high-stakes settings remain insufficiently defined and evaluated. To bridge this gap, we introduce LABSHIELD, a realistic multi-view benchmark designed to assess MLLMs in hazard identification and safety-critical reasoning. Grounded in U.S. Occupational Safety and Health Administration (OSHA) standards and the Globally Harmonized System (GHS), LABSHIELD establishes a rigorous safety taxonomy spanning 164 operational tasks with diverse manipulation complexities and risk profiles. We evaluate 20 proprietary models, 9 open-source models, and 3 embodied models under a dual-track evaluation framework. Our results reveal a systematic gap between general-domain MCQ accuracy and Semi-open QA safety performance, with models exhibiting an average drop of 32.0% in professional laboratory scenarios, particularly in hazard interpretation and safety-aware planning. These findings underscore the urgent necessity for safety-centric reasoning frameworks to ensure reliable autonomous scientific experimentation in embodied laboratory contexts. The full dataset will be released soon.
Paper Prompts
Sign up for free to create and run prompts on this paper using GPT-5.
Top Community Prompts
Explain it Like I'm 14
LABSHIELD: A simple explanation for teens
What is this paper about?
This paper introduces LABSHIELD, a “safety test” for AI systems that help run science labs. Think of it like a driving test for robot lab assistants. The goal is to check whether these AIs can notice dangers (like toxic chemicals or fragile glass), think through risks, and plan safe actions before anything goes wrong.
What are the main questions the paper asks?
The authors focus on three big questions:
- Can AI “see” lab hazards in real scenes, not just read about them?
- Can AI “think” about what could go wrong and why (for example, if two chemicals should never be mixed)?
- Can AI “plan” step-by-step actions that follow safety rules, including stopping or refusing unsafe tasks?
How did they test this? (Methods in everyday language)
The team built a safety benchmark called LABSHIELD—basically a collection of realistic lab situations for AIs to handle—using real lab setups and cameras. It checks three abilities: seeing, reasoning, and planning.
Here’s how it works:
- They recorded real lab scenes using several cameras at once (on the robot’s head, torso, and wrists). Multiple angles help the AI spot small or hidden dangers (like a tiny hazard symbol or a nearly invisible glass beaker).
- They created 164 different tasks that range from very simple (pick up a tube) to complicated (multi-step procedures that might involve moving between a workbench, a sink, and a fume hood).
- Each task has a safety level, from safe (OK to proceed) to very dangerous (must stop and refuse).
- They tested many AI models (both well-known and open-source) in two ways:
- Multiple-choice questions (like a quiz): Does the AI pick the right answer about what it sees and what to do?
- Semi-open questions (closer to real life): Can the AI list hazards it sees, explain the risks, and write a safe action plan (including saying “stop” or “refuse” when needed)?
To keep things fair and realistic, they used official safety guidelines:
- OSHA rules (the lab safety rulebook used in the U.S.)
- GHS symbols (the little icons on chemical bottles, like a flame for flammable or a skull for toxic)
They organized the test using a simple three-part “brain” model (PRP):
- Perception: “What’s in front of me? What’s dangerous?”
- Reasoning: “Why is it dangerous? What could happen?”
- Planning: “What should I do next, safely? Should I stop?”
What did they find, and why is it important?
The results show several important things about how today’s AI handles lab safety:
- Good at quizzes ≠ good at staying safe
- Many AIs did fine on multiple-choice questions but struggled when they had to write their own safety plan for a real scene. On average, there was a big drop (about 32%) from quiz performance to real-scenario safety performance.
- Seeing dangers clearly is essential
- Models that better recognized unsafe details (like GHS hazard labels, spills, clutter, or fragile glass) also made safer decisions. If an AI can’t notice the risky stuff, it can’t plan safely.
- Reasoning helps—but isn’t enough
- AIs that “explain their thinking” did better overall. Still, in high-risk situations, they often underestimated the danger and chose unsafe actions.
- More and better views matter
- Wrist cameras (close-up views) and higher-resolution images helped the AI notice small but critical details (especially hazard symbols and transparent glassware).
- Transparent glassware is hard to see
- AIs often missed clear glass items, which is a big problem in labs where glass is everywhere and can break, spill, or cause exposure.
- “Judge” scoring can be too optimistic
- When an AI “judge” scored plans, it sometimes gave credit to plans that looked OK but still broke safety rules. Cross-checking with expert answers caught these mistakes.
Why it matters: These results show that today’s AI lab assistants can make planning mistakes that could cause serious accidents. Before letting them run real lab tasks on their own, we need better safety skills built in.
What could this change in the future? (Implications)
LABSHIELD gives researchers and companies a realistic way to test and improve AI lab assistants before they work with real chemicals and equipment. The paper suggests several paths forward:
- Build AIs that prioritize safety over speed—able to stop, ask for help, or refuse dangerous instructions.
- Improve “seeing” skills, especially for small labels and transparent objects.
- Use multiple, high-quality camera views to reduce blind spots.
- Train AIs to connect safety rules (like OSHA and GHS) with what they actually see, not just what they read.
- Create better evaluation methods that reward truly safe behavior, not just the “right answer” on paper.
In short, LABSHIELD is like a safety shield for “robot scientists,” pushing the field to make lab AI that is not only smart, but safe—protecting people, equipment, and experiments.
Knowledge Gaps
Knowledge gaps, limitations, and open questions
Below is a concise, actionable list of what the paper leaves missing, uncertain, or unexplored, aimed to guide future research.
- Dataset availability and reproducibility: the dataset is “to be released”; licensing, data card, versioning, and reproducibility details are unspecified.
- Limited scenario coverage: only three zones (workbench, fume hood, sink) and 164 tasks; lacks coverage of other lab domains (bio/BSL2–4, radiological, cryogenic, high-pressure/vacuum, electrical, thermal, mechanical hazards).
- Regulatory scope: safety taxonomy grounded in OSHA/GHS only; no evaluation of generalization across non-U.S. regulations (e.g., EU CLP/REACH), institutional SOPs, or multilingual safety signage.
- Temporal dynamics and continuous control: tasks are evaluated via MCQ and semi-open QA; no assessment of closed-loop, real-time control, or temporal hazard evolution (e.g., spills, fumes, tilt-to-fall transitions).
- External validity to physical deployment: no evidence that benchmark scores predict incident rates, near-misses, or safety outcomes in real robot trials; missing field validation.
- Mapping text plans to executable control: planning is judged textually without validating feasibility against robot primitives, kinematics, or safety interlocks; no simulation/hardware-in-the-loop execution tests.
- Multi-view fusion methodology: how models fuse head/torso/wrist views is unspecified; no standardized protocols or architectures for multi-view/occlusion handling are benchmarked.
- Underutilized depth sensing: RGB-D is collected but it is unclear whether depth is used in evaluation; no protocols leveraging depth for transparent object perception, distance, or spill detection.
- Perception annotations granularity: no pixel/instance-level labels (e.g., masks for transparent glassware, GHS symbols) to enable supervised research tackling the identified perceptual blindness.
- Scene diversity and domain shift: data appears to come from a single facility/hardware; lacks variation in lighting, camera placement, container shapes/labels, languages, PPE styles, and clutter to test generalization.
- Adversarial/edge-case robustness: no tests for occluded or damaged labels, glare, fogged glassware, motion blur, sensor dropouts, or adversarial prompt/visual attacks in embodied contexts.
- Additional modalities: no audio (alarms, airflow monitors), instrument telemetry (hotplates, balances, fume hood sash sensors), or gas/vapor sensors; multimodal safety cues beyond vision-language remain unevaluated.
- Safety-performance trade-offs: overcautious behavior (false-positive refusals) and productivity impact are not measured; no metrics for balancing safety with task completion efficiency.
- Risk calibration and uncertainty: models’ confidence, risk calibration, and probabilistic risk assessment are not evaluated; no uncertainty-aware planning or thresholding analysis.
- Severity-aware aggregation: the Safety Score equally averages heterogeneous metrics; lacks severity-weighted or consequence-likelihood-weighted aggregation that reflects catastrophic risk.
- Error types beyond underestimation: underestimation is reported for S2/S3 only; false alarms on S0/S1, confusion between adjacent tiers, and asymmetric costs are unmeasured.
- LLM-as-a-Judge dependence: planning relies on GPT-4o as judge; inter-judge agreement, human-expert adjudication rates, rubric transparency, and multi-judge ensemble robustness are not reported.
- Benchmark contamination and stylistic bias: tasks partially generated by GPT-5.2 may advantage stylistically similar models; no leakage audits, cross-vendor synthesis, or human-only subsets to control bias.
- Zero-shot only: no experiments on safety fine-tuning, retrieval-augmented safety policies, or tool use (e.g., rule checkers) to test if alignment training improves LABSHIELD performance and transfer.
- Prompting/strategy breadth: ablations do not cover chain-of-thought disclosure control, structured reasoning modules, or integration with formal safety rule engines/constraint solvers.
- Human annotation reliability: inter-annotator agreement for unsafe factors, hazard patterns, and plan ground truths is not reported; adjudication procedures and expert credentials are unspecified.
- Explainability and escalation: the quality of safety explanations, clarity of refusal justifications, and human-in-the-loop escalation UX (when/how to alert) are not evaluated with user studies.
- Thresholds for deployment readiness: no pass/fail criteria, minimum acceptable safety thresholds, or confidence margins are proposed for real-world release decisions.
- Transparent object perception remedies: while perceptual blindness is identified, the benchmark does not include targeted benchmarks/baselines for transparency (e.g., polarization, depth fusion, synthetic augmentation).
- Judge robustness and bias: only one judge model is used; no comparison across judges or human panels to quantify bias and variance in plan scoring.
- Mobility scope: “mobile manipulation” is confined to the three zones; no inter-room navigation, chemical transport across corridors, door/elevator handling, storage/waste disposal routes.
- PPE and compliance: explicit assessment of PPE detection/compliance and procedural checks (e.g., sash height, secondary containment) is not described or benchmarked.
- Decoding sensitivity: effect of temperature/seeds on semi-open QA safety outcomes is not analyzed; robustness to inference stochasticity is unknown.
- Data governance and dual-use: dataset release risks (exposing hazardous procedures, facility details) and mitigations (access controls, redactions) are not detailed.
- Root-cause of embodied model underperformance: reasons (training data, objectives, perception stack integration) are hypothesized but not diagnosed with controlled ablations or targeted fixes.
Practical Applications
Immediate Applications
The following applications can be deployed now by leveraging LABSHIELD’s benchmark, taxonomy, and evaluation protocols, especially for environments already using MLLM-based agents and robotics in labs.
- Safety pre-deployment evaluation for lab AI and robots
- Sectors: robotics, pharma/biotech R&D, chemical manufacturing QC labs, cloud labs
- Tools/products/workflows: CI/CD “LABSHIELD Compliance Suite” that runs MCQ + semi-open QA tests; safety score thresholds (e.g., minimum Safety L23 accuracy); vendor scorecards for procurement
- Assumptions/dependencies: dataset availability (upon release), ability to feed multi-view visual inputs to agents, institutional buy-in to adopt safety gates
- Red-teaming and regression testing of autonomous lab agents
- Sectors: software/ML, robotics, cloud labs
- Tools/products/workflows: automated red-team harness using LABSHIELD scenarios to probe hazard identification, underestimation rates, and plan safety; weekly regression runs
- Assumptions/dependencies: stable evaluation pipelines; compute budget for periodic testing
- Safety guardrails and refusal policies embedded in agents
- Sectors: software, robotics, compliance
- Tools/products/workflows: “Stop&Alert Policy Engine” mapping LABSHIELD’s S0–S3 safety taxonomy into agent decision rules; refusal triggers for S3 violations; recovery planning templates
- Assumptions/dependencies: integration with agent planners (System 2) and execution layers (System 1); acceptance of more conservative behavior in exchange for safety
- PRP-based error diagnostics for engineering triage
- Sectors: ML engineering, robotics
- Tools/products/workflows: “PRP Failure Triage” reports that localize failures to Perception, Reasoning, or Planning using LABSHIELD’s metrics (U-J/P/R, H-J/P/R, Plan Score/Pass Rate)
- Assumptions/dependencies: access to model logs and intermediate reasoning; standardized metrics adoption
- Model selection and fine-tuning for hazard awareness
- Sectors: ML model providers, lab automation vendors
- Tools/products/workflows: use semi-open metrics to select models less prone to hazard underestimation; targeted fine-tuning on GHS symbol recognition, transparent glassware, spills; retrieval-augmented hazard knowledge
- Assumptions/dependencies: rights to fine-tune models; curated training data; careful evaluation to avoid regressions in general capabilities
- Sensor configuration guidance for safer perception
- Sectors: robotics hardware integrators, lab infrastructure
- Tools/products/workflows: “Sensor Layout Planner” that prioritizes multi-view coverage and wrist-mounted cameras; upgrade visual resolution to improve GHS/transparent object recognition; camera placement audits
- Assumptions/dependencies: hardware budgets; physical constraints of lab spaces; data storage/security for higher-resolution streams
- Perception module benchmarking and drop-in upgrades
- Sectors: computer vision, robotics
- Tools/products/workflows: modular “Hazard Perception Pack” (GHS symbol detector, fragile/transparent glassware detector, clutter/spill detection) evaluated on LABSHIELD; integration as pre-check before action execution
- Assumptions/dependencies: accurate calibration; compatibility with existing VLA stacks; domain shift between benchmark and specific lab visuals
- LLM evaluation improvements using dual-metric scoring
- Sectors: ML evaluation/ops
- Tools/products/workflows: adopt dual metrics (Plan Score + Pass Rate) to mitigate judge over-optimism; “LLM-Judge Harness” with anchors to expert plans
- Assumptions/dependencies: availability of expert plans for anchoring; careful auditing of judge prompts
- Education and training for lab safety
- Sectors: education, academia, industry L&D
- Tools/products/workflows: interactive training modules using LABSHIELD MCQs and semi-open scenarios; VR/AR modules highlighting hazards and correct recovery sequences; assessments for student and staff certification
- Assumptions/dependencies: licensing of content; adaptation to institutional curricula; accessibility accommodations
- Procurement and compliance checklists
- Sectors: policy/compliance, insurance, enterprise procurement
- Tools/products/workflows: require vendors to meet specified Safety Score and Safety L23 accuracy thresholds; dashboards for risk monitoring; tie benchmark results to insurance underwriting
- Assumptions/dependencies: institutional policies that recognize benchmark outcomes; alignment with OSHA/GHS standards
- Internal lab policy updates for AI-enabled environments
- Sectors: academia, industry labs
- Tools/products/workflows: codify Stop&Alert for S2/S3, define required camera coverage and resolution, mandate pre-deployment LABSHIELD testing
- Assumptions/dependencies: governance support; staff training; change management
Long-Term Applications
These applications require further research, scaling, or standardization before broad deployment.
- Safety-certified autonomous “self-driving” labs with supervisory copilot
- Sectors: lab automation, pharma/biotech, materials science
- Tools/products/workflows: “Safety Copilot” that continuously monitors Perception-Reasoning-Planning, enforces S0–S3 rules, and coordinates with robots and fume hoods; dynamic re-planning on hazard detection
- Assumptions/dependencies: robust real-time PRP, high-fidelity multi-view sensing, reliable stop actions; validated integration with lab hardware interlocks
- Regulatory standards and third-party certification
- Sectors: standards bodies, regulators, insurance
- Tools/products/workflows: UL/CE-style certification for lab AI agents based on LABSHIELD-like evaluations; minimum passing criteria for deployment; policy frameworks recognizing benchmark-based safety
- Assumptions/dependencies: multi-stakeholder consensus; periodic benchmark updates; alignment with OSHA/GHS and international variations
- Advanced perception for transparent/reflective objects
- Sectors: computer vision, sensors, robotics
- Tools/products/workflows: new datasets and models (e.g., polarization, ToF, structured light) and training regimes to overcome “perceptual blindness” to glassware/liquids; drop-in hardware modules
- Assumptions/dependencies: cost-effective sensors; robustness across lighting and materials; integration with existing platforms
- Real-time safety monitoring and digital twin integration
- Sectors: robotics, industrial IoT, cloud labs
- Tools/products/workflows: streaming multi-view monitoring with event-driven interventions; digital twin simulations for risk forecasting; cross-modal logs for audits
- Assumptions/dependencies: low-latency infrastructure; secure data pipelines; clear handoff protocols to humans
- Benchmark-driven agent architectures with verifiable safety layers
- Sectors: ML/robotics R&D
- Tools/products/workflows: dual-system agents with formal policy verification, runtime monitors, and sandboxed execution; “Safety L23 guardrail libraries” ready for integration
- Assumptions/dependencies: advances in formal methods for embodied settings; verified world models; acceptance of performance/safety trade-offs
- Cross-domain extensions beyond chemistry labs
- Sectors: healthcare diagnostics labs, biosecurity, energy/nuclear labs, semiconductor fabs, manufacturing QC
- Tools/products/workflows: domain-specific taxonomies and benchmarks; hazard-aware planning tied to sector regulations; interoperable safety scores
- Assumptions/dependencies: sector expertise; new annotation pipelines; alignment with diverse regulatory regimes
- Credentialing and workforce upskilling for AI-augmented labs
- Sectors: education, professional certification bodies
- Tools/products/workflows: standardized curricula and exams anchored to safety benchmarks; micro-credentials for “AI lab operator”
- Assumptions/dependencies: institutional adoption; ongoing benchmark maintenance; recognized accreditation pathways
- Marketplaces and scorecards for safe model/robot selection
- Sectors: procurement, venture/enterprise buyers
- Tools/products/workflows: centralized registries with LABSHIELD-derived safety metrics; comparative dashboards for model and robot shopping
- Assumptions/dependencies: vendor participation; trustworthy evaluation governance
- Human–robot collaboration protocols with safety-centric interaction
- Sectors: HRI, lab operations
- Tools/products/workflows: standardized handoff behaviors when hazards are detected (e.g., guided recovery), voice/gesture “halt” commands integrated with S2/S3 states
- Assumptions/dependencies: reliable intent recognition; ergonomic design; training for human operators
- Calibrated LLM-judge frameworks and hybrid evaluation
- Sectors: ML evaluation research
- Tools/products/workflows: improved judges with calibration, adjudication via ensembles or human-in-the-loop; expanded anchors to reduce leniency and capture subtle safety violations
- Assumptions/dependencies: availability of expert ground truth; reproducible judging protocols; compute budgets for multi-judge systems
Cross-cutting assumptions and dependencies
- Benchmark availability and coverage: Full dataset release, ongoing updates to reflect new hazards, equipment, and workflows
- Generalization: Performance on LABSHIELD correlates with real lab safety; domain shifts are managed via adaptation
- Multi-view, high-resolution sensing: Camera placement and resolution materially affect safety performance; some labs may need upgrades
- Model and hardware integration: Agents must expose intermediate reasoning and accept safety constraints; robots must support reliable stop/alert
- Regulatory alignment: OSHA/GHS are primary anchors; non-U.S. settings may require taxonomy adjustments
- Data governance: Handling of video data must meet privacy, IP, and security requirements
- Cost and compute: Continuous testing and higher-resolution perception increase operational costs; budgeting and scaling plans are necessary
Glossary
- Analysis Score (Ana.): An MLLM-judged metric that rates the logical grounding of a model’s safety reasoning in semi-open evaluation. "Reasoning assesses hazard patterns (H-J, H-P, H-R) and logical grounding through an MLLM-judged Analysis Score (Ana.)."
- Astribot robotic platform: A specific multi-camera robotics setup used to capture synchronized, real-world lab data for the benchmark. "We employ the Astribot robotic plat- form to collect multi-view visual data..."
- Catastrophic failure modes: Severe system failure patterns that can arise during physical interaction, leading to irreversible consequences. "focusing on latent risks and catastrophic failure modes that emerge only during physical interaction."
- Counterfactual reasoning: Reasoning about “what-if” alternatives to assess how changes in conditions would affect safety outcomes. "causal and counterfactual reasoning, as well as action ordering, next-step planning, and recovery planning."
- Decoding temperature: A parameter controlling sampling randomness during model generation; higher values increase output diversity. "All models are evalu- ated in a zero-shot setting with a fixed decoding temperature of 0.7."
- Dual-axis taxonomy: A two-dimensional organizational scheme categorizing tasks by operational complexity and safety level. "Central to LABSHIELD is a dual-axis taxonomy that organizes tasks across four operational levels..."
- Dual-system paradigm (System 1/System 2): An architecture separating fast, reactive execution (System 1) from slower, deliberative reasoning and planning (System 2). "to a dual- system paradigm (Bu et al., 2024; Chen et al., 2025a; Chi et al., 2025): a deliberative 'System 2' for reasoning and planning, and a reactive 'System 1' for physical execution."
- Ego-centric robotic platform: A data collection setup with cameras mounted from the robot’s own perspective (e.g., head, torso, wrists). "using an ego-centric robotic platform to capture high-fidelity multimodal data in real-world safety-critical laboratory environments."
- Embodied agent: An AI system that perceives and acts through a physical body in the environment. "the safety awareness and decision-making reliability of embodied agents in such high-stakes settings remain insufficiently defined and eval- uated."
- Fume hood: A ventilated enclosured workspace designed to limit exposure to hazardous fumes during lab operations. "across three representative laboratory ar- eas-the workbench, fume hood, and sink-"
- Globally Harmonized System (GHS): An international standard for classifying and labeling chemical hazards. "Grounded in U.S. Occupational Safety and Health Administration (OSHA) standards and the Globally Harmonized System (GHS), LABSHIELD establishes a rigor- ous safety taxonomy..."
- Ground-Truth Alignment Pass Rate (Pas.): A metric measuring how closely a model’s proposed plan matches expert-annotated plans. "Pass Rate (Pas.) measures semantic align- ment with expert annotations."
- Hazard pictogram: Standardized visual symbols (e.g., GHS icons) indicating specific chemical or physical hazards. "such as GHS hazard pictograms, and challenging scientific entities in- cluding transparent glassware..."
- Jaccard index: A set similarity metric used here to evaluate overlap in predicted vs. true unsafe factors or hazard patterns. "Perception identifies unsafe factors via set- based Jaccard, Precision, and Recall (U-J, U-P, U-R)."
- Kinematic precision: The accuracy of motion in robotic manipulation and navigation tasks. "these frameworks effec- tively evaluate kinematic precision and task success, they remain largely hazard-blind..."
- LLM-as-a-Judge: An evaluation protocol where an LLM scores or adjudicates another model’s outputs. "we adopt a standardized LLM-as-a-Judge protocol based on GPT-4o and normalize all metrics..."
- Micro-averaged accuracies: An averaging method aggregating performance across instances, weighting each equally. "all metrics are computed as micro-averaged accuracies..."
- Mobile manipulation: Robotic tasks combining object manipulation with navigation across spatially separated areas. "(L3) Mobile Manipulation, which integrates manipulation with spatial navigation across laboratory zones."
- Multimodal LLM (MLLM): A LLM that processes and reasons over multiple input modalities (e.g., text, images, video). "To facilitate a rigorous assessment of Multimodal LLMs (MLLMs) in laboratory safety..."
- Occupational Safety and Health Administration (OSHA) 29 CFR (1910.1450): A U.S. federal regulation governing occupational exposure to hazardous chemicals in laboratories. "defining safety criteria based on the Occupational Safety and Health Administration (OSHA) 29 CFR (1910.1450) protocol, which guide human experts..."
- Occlusion (spatial occlusions): Visual obstructions where objects are partially or fully hidden from certain camera views. "mitigating risks associated with spatial occlusions."
- Perception-Reasoning-Planning (PRP) architecture: A classical AI framework decomposing tasks into sensing, inference, and action stages. "The design of LABSHIELD is grounded in the classical Perception-Reasoning-Planning (PRP) architecture..."
- Plan Score (Sco.): A judge-evaluated metric assessing whether a plan is functionally feasible under safety constraints. "Planning performance employs a dual-metric strategy: Plan Score (Sco.) assesses functional feasibility under safety constraints..."
- Proximity semantics: Fine-grained, near-field visual cues captured at close range that inform hazard assessment. "wrist-mounted views provide critical proximity semantics."
- Reagent incompatibility: Chemical incompatibilities where combining reagents can cause dangerous reactions. "overlooking critical chemical constraints such as reagent incompatibility or GHS-regulated handling protocols."
- Safety L23: A high-risk evaluation subset (levels S2/S3) with metrics for accuracy and hazard underestimation. "For high-risk scenarios (S2/S3), Safety L23 reports accuracy (Acc.) and the un- derestimation rate (Und.)."
- Safety taxonomy: A structured categorization of safety conditions and operational risk levels for lab tasks. "LABSHIELD establishes a rigor- ous safety taxonomy spanning 164 operational tasks..."
- Semi-open QA evaluation: An assessment format where models generate free-form but structured responses evaluated against normalized metrics. "and (ii) a semi-open QA evaluation that enables standardized quantitative assessment..."
- Sensorimotor execution: The integration of sensory perception with motor actions during physical task performance. "decoupled from the con- straints of sensorimotor execution."
- Stop & Alert protocol: A mandated safety response requiring immediate cessation of actions and alerting a human operator in moderate-risk cases. "(S2) Moderate-risk Hazards, triggering a Stop & Alert protocol;"
- Transparent glassware: Clear laboratory containers (e.g., beakers, test tubes) that are visually challenging for perception systems. "symbols and transparent glassware-with robust inhibitory control across long-horizon, multi-step workflows."
- Underestimation rate (Und.): The frequency with which a model underestimates the severity of high-risk scenarios. "For high-risk scenarios (S2/S3), Safety L23 reports accuracy (Acc.) and the un- derestimation rate (Und.)."
- Visual grounding: Tying abstract concepts or safety rules to specific visual evidence in the scene. "such as the visual grounding of transparent labora- tory apparatus"
- Visual Question Answering (VQA): A task where models answer questions about images, used here for structured safety MCQs. "implemented as a hierarchical Visual Question Answering (VQA) protocol that probes internal logic and scene understanding..."
- Vision-Language-Action (VLA) models: Models that jointly integrate visual perception, language understanding, and action generation. "vision-language-action (VLA) models (Li et al., 2025; Zhang et al., 2025d;b;c; Kim et al., 2024; Fu et al., 2025)."
- Zero-shot setting: Evaluating models without providing task-specific examples during inference. "All models are evalu- ated in a zero-shot setting with a fixed decoding temperature of 0.7."
Collections
Sign up for free to add this paper to one or more collections.