Apply to my task
arXiv:2605.04131 ★ 74 May 5, 2026

Structured Multimodal Dialogue: a three-step method for fixing errors when working with images

Key result

From 96% to 64% — one screenshot. The model hasn't forgotten the subject: it's trying to parse the image and solve the problem at the same time — and breaks at the seam. Structured Multimodal Dialogue lets you get an accurate analysis of any image — a chart, a funnel, a diagram — even when the model misreads it the first time. The trick: the method splits the two processes — first the model only describes the image, you correct its perception, and only then does it solve the problem. 82% of errors fixed. Visual ones — 100% of them.

01

TL;DR

Models lose up to 30% accuracy when a problem comes with an image. The cause isn't a lack of subject knowledge — it's an inability to first parse the image and then think about the problem. Structured Multimodal Dialogue is a method that splits those two steps apart: first the model describes the visual content, then it solves the problem.

Main finding: on text-only problems, models answer correctly 96% of the time. Add an image and accuracy drops to 64–89% depending on the model. The authors call this the Multimodal Interference Effect: visual processing "overloads" the model, and it starts confusing even the basic meaning of the problem — even though its subject knowledge hasn't gone anywhere. It's like a smart person who knows physics inside out but is reading the problem sheet upside down.

The method fixes this with a three-step dialogue. Step 1: ask the model to describe the image. Step 2: correct only factual perception errors (don't hint at the solution). Step 3: ask it to solve the problem. This sequence fixed 82% of errors. Visual errors — 100% of them.

Want this for your own case? Apply this study to your task: AI adapts its method to what you are working on and writes the prompt.

02

Method Blueprint

All three steps happen in one conversation (separate messages in the same chat)

STEP 1 → First message:
Attach the image + ask for a description:
"Describe what you see in this image/graph"
→ You get: a text description of the visual

STEP 2 → Your reply:
Check the description. If something is wrong, correct 
only the visual facts (numbers, directions, labels).
Don't hint at the solution.
→ You get: corrected perception

STEP 3 → Next message:
"Now solve the problem: {problem}"
or: "Read the question again and solve the problem"
→ You get: a solution based on correct perception
03

Example in Action

Task: You're looking at a screenshot of a sales funnel from HubSpot and want to find where the biggest drop-offs are. The numbers on the screenshot are tiny, the conversion rates are jumbled, and the model is clearly misreading something on the first try.

Prompt (Step 1):

[Attach the funnel screenshot]

Look carefully at this image. 
Describe exactly what it shows: 
which stages, which numbers, which conversion rates between them. 
List everything you see — in order, from top to bottom.

Your response (Step 2):

You read the description and spot a mistake — say, the model mixed up the "Lead" and "Qualified Lead" stages or misread 1,200 as 1,20.

You write: "Not quite: the 'Qualification' stage has 3,400 leads, not 340. And that stage comes after 'Lead,' not before it."

Prompt (Step 3):

Now, based on this data:
find the stage with the biggest customer loss in percentage terms 
and suggest 2-3 hypotheses for why conversion dropped right there.

Result: The model will deliver an analysis based on the correct data — it will find the funnel's bottleneck, name the specific loss figure and propose hypotheses. Without steps 1-2, it would be analyzing a distorted picture and drawing wrong conclusions.

04

Why It Works

The LLM's weakness: the model processes text and image at the same time, "in one pass." That's an overload. The visual part needs its own attention — reading axes, parsing labels, remembering numbers. That "takes up space" and throws the model off when it frames the problem. As a result, errors appear not because the model doesn't know physics or marketing, but because it misread the source data.

The LLM's strength: when the data is given as text, the model reasons excellently. That's exactly why accuracy on text problems is 96%. The knowledge is there. The problem is reading, not thinking.

How the method uses this: the method splits the two processes. First — only perceiving the image (step 1). Then — a human corrects the perception (step 2). And only then — working with the data (step 3). In essence, you turn the image into verified text, and from there the model works in its strong zone.

Prompt control levers:

  • Level of detail in step 1 → ask it to "name all numbers and labels" for complex charts, or to "describe the overall structure" for diagrams
  • Scope of correction in step 2 → fix only facts, give no hints about the solution (this is essential — otherwise you're solving the problem yourself)
  • Wording of step 3 → if the description was long, add "reread the question" before "solve" so the model doesn't lose sight of the goal
  • Multiple images → run each one separately through steps 1-2, then launch step 3 with all the descriptions
05

Prompt Template

Step 1 — Description:

[Attach the image]

Describe in detail what you see in this image.
{Task-specific note: "List all numbers and labels" / 
"Describe the structure and connections" / "Name all elements from top to bottom"}

Step 2 — Your correction (if needed):

Correction: {fix only the visual fact — a number, a direction, an order}.
{Other details} are correct.

Step 3 — The problem:

Now, based on this data, {problem}.

What to fill in: - {Task-specific note} — depends on the image type: charts → numbers and axes; diagrams → connections and order; tables → headers and values - {fix only the visual fact} — don't explain the problem, only correct the perception - {problem} — your question, unchanged from the very beginning


🚀 Quick start — paste into the chat:

Here is a three-step method for working with images (Structured Multimodal Dialogue). 
Adapt it to my task: {describe your task}. 
Ask me questions to fill in the fields.

[paste the template above]

The LLM will ask what kind of image it is and what the end goal is — because that determines what to ask it to describe in step 1 and how to phrase step 3.

06

Limitations

⚠️ Context errors are hard to fix: If the model misunderstood the gist of the problem from the start (rather than just a visual fact), the method helps only 44% of the time. Describing the image doesn't always cure flawed reasoning about the setup.

⚠️ Requires human checking: Step 2 is you. You need to know what's correct in the image yourself. If you're not sure either, the method won't help.

⚠️ Not for drawing tasks: If you need the model to create or edit an image, this doesn't apply. Analysis of existing images only.

⚠️ Small sample: 44 problems isn't many. Fixing 100% of visual errors is impressive, but the lower bound of the confidence interval is 81%. Larger studies are needed for confidence.

07

How They Studied It

The team took 100 text problems and 44 problems with images from OpenStax — an open university physics textbook. Three models (Claude, Gemini, ChatGPT) solved the problems under identical conditions. First pure text, then problems with graphs, diagrams and tables. Correctness was checked by a separate multi-model LLM system.

An interesting detail: on text problems the models were practically indistinguishable — 96% for all three. But as soon as images appeared, the gap became statistically significant. That means a model's "smarts" with text don't predict its ability to handle visuals.

The errors were sorted into four types, and the team found something important: computational errors appeared only in text problems, while visual errors appeared only in multimodal ones. This suggests an image doesn't just add difficulty — it creates a different kind of error. So different correction strategies are needed.

Then they applied the three-step dialogue to all the wrong answers. They fixed 28 of 34 errors. Visual ones — 100%. Contextual ones — 44%. The difference turned out to be the key insight: if the model sees wrong, that's fixable. If it misunderstands the meaning of the problem, that's harder.

08

Original from the Paper

The intervention followed a three-step dialogue: 

(i) "Describe what you observe in the figure/graph,"

(ii) researcher correction of any misidentified visual elements 
[corrections were restricted to observable visual properties 
in order to align the model's perception with the source image. 
Researcher input was limited to clarifying the direction of a force vector, 
or the numerical value of a graph's intercept 
without providing any hints regarding the underlying physics principles or formulas.]

(iii) "Solve the problem" 
(or "Read the question again and solve the problem" 
when the description was lengthy)

Context: This is the exact intervention protocol from the Methods section. Note the remark on step (ii): correct only visual facts, no hints about the physics or the solution method — otherwise you're solving the problem yourself.

09

Adaptations and Extrapolations

💡 Adaptation for medicine and health

The same protocol works for analyzing scans, lab results and medical charts.

[Attach the scan/result]

Describe what you see in this image: 
all visible structures, markings, numbers, anomalies.
Be as specific as possible.

→ You check for obvious perception errors.

Now explain to me in plain words 
what these values mean for my health.

⚠️ Not for diagnosis. For understanding and preparing questions for your doctor.


💡 Adaptation for design reviews and UX

[Attach the UI screenshot]

Describe the structure of this screen: 
what elements there are, where they're placed, 
what the text says, what the hierarchy is.

→ If something is wrong, you correct it.

Now find 3 UX problems 
and suggest how to fix them.

🔧 Technique: remove the human from step 2 → automatic mode

If you can't check the description yourself (say, you're working fast), replace step 2 with a model self-check:

[Step 1 — description]

Now reread your description and check: 
did you read everything correctly? 
Is there anything in the image you're unsure about?

[Step 3 — the problem]

The effect is weaker (no external check), but better than going straight to "solve the problem." Fine for low-stakes tasks where accuracy isn't critical.

10

Resources

Paper title: A Dialogue-Based Framework for Correcting Multimodal Errors in AI-Assisted STEM Education

Authors: Akshay Syal, Lawrence Swaminathan Xavier Prince, Evin Gultepe, Nik Bear Brown, Srinivas Sridhar

Textbook base: OpenStax Physics — openstax.org

Affiliation: Northeastern University (based on Nik Bear Brown's author profile)

Research digest

Key result

From 96% to 64% — one screenshot. The model hasn't forgotten the subject: it's trying to parse the image and solve the problem at the same time — and breaks at the seam. Structured Multimodal Dialogue lets you get an accurate analysis of any image — a chart, a funnel, a diagram — even when the model misreads it the first time. The trick: the method splits the two processes — first the model only describes the image, you correct its perception, and only then does it solve the problem. 82% of errors fixed. Visual ones — 100% of them.

Principle

Don't mix reading the image and solving the problem in one request — they're two different processes, and there isn't enough brainpower for both at once. The twist: the problem isn't knowledge, it's multitasking. Reading an image and thinking about a problem at the same time is, for a model, like reading the problem upside down. The knowledge is there. The reading lets it down. Three steps in one chat: description → correction → solution. In essence, you translate the image into verified text — and from there the model works where it has 96% accuracy.

Why it works

On pure text problems, models answer correctly 96% of the time. Add an image and accuracy drops to 64–89%. The authors call this the Multimodal Interference Effect: visual processing takes up room in the model's head, and it starts confusing the basic meaning of the problem — even though its subject knowledge hasn't gone anywhere. The key insight: the problem is reading, not thinking. The method removes this bottleneck: first you extract a text description of the image, check it yourself — and only then kick off the thinking. The model works in its strong zone.

When to apply

Any task with an image → especially charts, screenshots with numbers, technical diagrams, tables in small print. Works best when: the image contains specific numbers or labels that are easy to misread; the task is sensitive to data accuracy — financial analysis, engineering diagrams, medical scans. NOT a fit for: cases where you yourself don't know what's correct in the image (step 2 requires your check); image generation or editing tasks; situations where the model misunderstood the whole gist of the problem — here the method helps only 44% of the time.

Mini recipe

1. Send the image with a request to describe it: attach the picture and write: `Describe in detail what you see — all numbers, labels, structure, order of elements`. For charts add: `Name the axes and all values`. For diagrams: `Describe the connections and order from top to bottom`. 2. Check the description yourself: read what the model wrote. Found an error — a wrong number, a jumbled order, an incorrect label? Write only the factual correction: `Correction: the Y axis shows 10,000, not 1,000. The rest is correct`. No hints about the solution — perception only. 3. Pose the problem: `Now solve: {your question}`. If the description was long, add before the question: `Reread the problem and solve it`, so the model doesn't lose sight of the goal.

Examples

[BAD]: `[attach the funnel screenshot] Where are the biggest drop-offs in this funnel and why?` [GOOD]: Step 1: `[attach the funnel screenshot] Describe exactly what you see: which stages, which numbers at each, which conversion rates between them — in order from top to bottom` Step 2 (if the model got it wrong): `Correction: the "Qualification" stage has 3,400 leads, not 340. And it comes after "Lead," not before it. The rest is correct` Step 3: `Now find the stage with the biggest customer loss in percentage terms and suggest 2–3 hypotheses for why conversion dropped right there`

In plain words

AI assistants stumble on problems with images not because they're dumb, but because they're trying to do two things at once: examine the details and solve the equation. That's the fundamental mistake: the model processes visuals and logic in a single pass, which turns its brain to mush. It simply mixes up numbers on the axes or misses a small label, and then builds "brilliant" conclusions on top of that garbage. To fix this, you bring in Structured Multimodal Dialogue — a method that makes the AI rub its eyes first and only then open its mouth.

It's like assembling an IKEA wardrobe while reading the manual and screwing in a shelf at the same time, without looking at the parts. You end up driving a screw into the wrong spot because it looked like the right board. The method suggests laying out all the parts on the floor first and saying out loud: "Okay, I've got three long panels and a bag of bolts," and only once the inventory is done do you pick up the drill. Without that stage, the model acts like an overconfident intern who screws up 30% of the time just from carelessness.

Technically, it works through a three-step dialogue in a single chat. First you ask the model for a visual description: just list what it sees on the chart or diagram, without trying to solve anything. Then comes the correction stage, where you (or the system itself) check whether it hallucinated pink elephants instead of numbers. And only at the end, once the data in the chat is locked in as text, do you give the command to solve the problem. Splitting these processes into separate messages lets the model focus all its "attention" on vision first and logic second.

Although the study was run on STEM problems (physics, chemistry, math), the principle is completely universal. It's vital for any business that deals with charts: from a sales funnel in HubSpot to complex dashboards in Tableau. If you just drop in a screenshot and ask "Where are we losing money?", the model may spit out total garbage, mixing up the conversion rates. But if you make it digitize the screenshot into text first, accuracy shoots up, because a text context is an LLM's home turf, while an image is always a risk zone.

Bottom line: stop expecting "one-click" magic from AI models on complex data. The main takeaway: description first, solution second. If the model hasn't spelled out what exactly it sees in the image, there's a one-in-three chance it'll get the conclusions wrong. Use a structured dialogue, make the AI pin down the inputs as text, and only then demand the analysis. Ignore this rule and you get hallucinations out of nowhere and blown budgets.

AI lab assistant

Apply this study to your task

Describe what you're working on. AI takes the method and the measured results from this paper and adapts them to your case, or writes a ready prompt built on them.

Based on Structured Multimodal Dialogue: a three-step method for fixing errors when working with images arXiv:2605.04131

Sign in to apply this study New accounts get 50 free credits.