Vision-Language Grounding and Spatial Hallucination Triage Checklist
Systematically debug visual question answering hallucinations, spatial misattributions, and bounding failures in multimodal LLMs.
Deploy this checklist when multimodal vision-language models fail to ground visual details, miscount objects, hallucinate spatial relations, or misinterpret interleaved image-text prompts. It creates an actionable triage procedure for prompt and visual grounding fixes.
Role: Lead Multimodal Evaluation Engineer specializing in vision-language alignment, visual grounding, and hallucination triage.
Context
- Multimodal Foundation Model: {{multimodal_model_version}}
- Visual Input Description: {{input_image_context}}
- System Prompt Architecture: {{system_prompt_scaffold}}
- Observed Grounding Failure: {{spatial_grounding_failure}}
- Interleaved Query Sequence: {{interleaved_prompt_sequence}}
- Sampling & Attention Hyperparameters: {{attention_temperature_setting}}
Task
Construct an end-to-end debugging and remediation checklist to diagnose spatial reasoning failures, eliminate hallucinations, and enforce strict visual grounding in the multimodal reasoning workflow.
Method
- Analyze {{spatial_grounding_failure}} against {{input_image_context}} to classify the error type (e.g., existence hallucination, relational misbinding, attribute misattribution, or coordinate hallucination).
- Review {{system_prompt_scaffold}} for ambiguity regarding visual verification protocols, chain-of-thought grounding mandates, or coordinate formatting.
- Dissect {{interleaved_prompt_sequence}} to determine if prompt positioning causes recency bias or visual attention degradation over long context windows.
- Assess the impact of {{attention_temperature_setting}} on token sampling divergence during visual grounding tasks.
- Devise explicit visual anchoring prompt patterns (e.g., bounding-box pre-generation, visual-crop verification, or step-back visual summarization).
- Formulate negative reasoning constraints to force the model to explicitly cite visual coordinates or state absence when confidence is low.
- Compile a structured debugging checklist covering prompt scaffolding, spatial coordinate verification, and iterative visual prompting.
- Establish deterministic evaluation metrics to benchmark hallucination rates across transformed and perturbed test images.
Constraints
- MUST format all outputs as a prioritized, operational checklist with clear completion criteria.
- MUST NOT require model fine-tuning; all solutions must rely on prompt engineering, structured reasoning, and inference parameter tuning.
- MUST include explicit chain-of-thought grounding patterns tailored to {{multimodal_model_version}}.
- Every checklist item MUST provide concrete criteria for verifying visual grounding against {{input_image_context}}.
Output format
- Hallucination Mechanism Diagnostic Summary (max 175 words)
- Checklist Tier 1: Visual Prompt Scaffolding & System Constraint Fixes (5-6 actionable items)
- Checklist Tier 2: Spatial Decomposition & Grounded Reasoning Protocols (5-7 actionable items)
- Checklist Tier 3: Inference Parameter & Context Order Tuning (4-5 actionable items)
- Quality Assurance & Perturbation Testing Suite (markdown checklist with 4 distinct verification scenarios)
Self-review
- Are the diagnostic steps specifically tailored to the grounding failure outlined in {{spatial_grounding_failure}}?
- Does the checklist include explicit spatial reasoning techniques (e.g., coordinates, region-of-interest anchoring)?
- Are all variable references syntactically matched and fully contextualized throughout the body?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.