- Rating
- 3
- Confidence
- 1
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
The paper introduces RuleSafe-VL, a benchmark for evaluating how vision-language models apply explicit content-moderation policies when rules interact and relevant context may be missing. Its main contributions are a rule-conditioned task formulation and an annotated benchmark covering four capabilities: identifying satisfied policy conditions, recovering relationships between rules, determining whether evidence supports a unique decision, and adapting decisions when additional context is supplied.
The benchmark contains 2,166 image-text cases, linked to 93 atomic rules and 92 relations derived from public platform policies, across nudity/sexualized content, dangerous/harmful behavior, and graphic/injury-related content. Labels are established through independent human annotation and expert adjudication.
The study provides extensive experiments to evaluate 10 existing VLMs under zero-shot prompting.
Critical strengths
The benchmark links 2,166 image-text cases to explicit policy rules and relations, supported by independent annotation and expert adjudication. Reported agreement k=0.91, 0.82, and 0.86 across the case-level annotation tasks-provides evidence that annotators apply the guidelines consistently. Holding image-text content fixed while varying supplied context also creates a useful setting for testing whether decisions change appropriately. This combination gives the benchmark potential value for developing and comparing moderation systems, beyond documenting low performance on a collection of difficult examples.
Critical weaknesses
1, The study is lacking an overview figure to help readers can capture the overview of the work and pipeline.
- There are several internal inconsistencies in the benchmark reported results. a) Table 1 reports 918 decidable cases out of 2,166 (42.4%), whereas the categories with decidable paired evidence in Table 12 sum to 49.0%. (b) LLaVAGuard’s T2 score is 4.7 in Table 2, but 6.7 in Table 10
Questions for authors
-
Could you provide an overview figure to help readers capture the workflow and pipeline easier?
-
I would like recommend you to review and correct all the inconsistencies in the benchmark.
2 comments
Thank you very much for your additional information. They address all my concerns.
Author Response to Weakness 1, Weakness 2
W1 & Q1. Overview of the Benchmark Construction and Evaluation Pipeline
Thank you for this suggestion. We have added Figure 2 in Page 3 to the revised manuscript to show the benchmark construction pipeline and the inputs and outputs of all four tasks.
Benchmark construction. The left panel presents policy construction and case construction. We collect 186 policies from Meta, YouTube, Reddit, and TikTok, filter them for conditions assessable from observable evidence or explicit context, and remove duplicates to obtain 24 policies. Expert annotation and adjudication establish 93 atomic rules and 92 typed relations. These policies guide the selection of 2,320 candidate image–text pairs, from which validation and annotation yield 2,166 cases. Experts annotate rule activation and decision states, then provide contextual completions and compliance labels for underdetermined cases. The left panel makes explicit that every gold label is traceable to specific policy requirements and case evidence through documented human annotation and adjudication.
Evaluation framework. The right panel illustrates four complementary tasks: Task 1 identifies evidence-supported atomic rules; Task 2 recovers relationships among policy rules; Task 3 assesses whether the available evidence determines a unique outcome; and Task 4 determines the appropriate outcome under supplied context. Each task includes a representative input, a guiding question, and its expected output, making the evaluation procedure directly accessible. Together, the panels show how RuleSafe-VL formalizes moderation as rule-conditioned reasoning under the joint constraints of policy, content, and context, and translates its requirements into independently annotated evaluation targets. Evaluating these targets alongside end-to-end predictions distinguishes final-outcome correctness from correctness on the associated diagnostic judgments—a distinction supported by §5.3. Figure 2 thus connects the formulation, benchmark construction, and evaluation objectives.
W2 & Q2. Numerical inconsistencies: LLaVAGuard’s Task 2 score (4.7 vs. 6.7) and decidable-case proportions (42.4% vs. 49.0%)
Thank you for identifying these discrepancies. The Task 2 score difference is a transcription error in Table 2. The decidable-case proportions use different denominators: the full benchmark in Table 1 and a modality-sufficiency diagnostic subset in Table 12.
Task 2 score: correction of Table 2. Regarding “4.7 in Table 2, but 6.7 in Table 10,” the correct Task 2 Macro-F1 for LLaVAGuard-7B is 6.7, consistent with the per-family results and their average in Appendix Table 10. We will correct the transcription error in Table 2 from 4.7 to 6.7. This changes its relative ordering with GuardReasoner-VL-3B, which scores 6.6, but preserves the conclusion that both safety-oriented models score substantially below the evaluated general-purpose VLMs on rule-relation recovery under our structured evaluation protocol.
Decidable proportions: full benchmark versus diagnostic subset. Regarding “42.4%” in Table 1 versus “49.0%” in Table 12, Table 1 reports 918 decidable cases out of 2,166, giving 918/2,166×100=42.38%, or 42.4% rounded to one decimal place. Table 12 alone uses a separately selected subset for modality-sufficiency analysis. We retained all 918 decidable cases and selected 956 of the 1,248 underdetermined cases through stratified random sampling by policy category, independently of model predictions. The resulting subset contains 1,874 cases, giving 918/1,874×100=48.99%. This matches the rounded sum of the four categories with decidable paired evidence: 38.9+4.9+2.7+2.5=49.0%. The original image–text decision-state labels remain unchanged; text-only and image-only sufficiency were additionally annotated for this subset. Both the proportions and model accuracies in Table 12 refer to these 1,874 cases. We will document the subset construction and denominator explicitly and rename “Dataset Share” to “Share within the diagnostic subset (%)”.