Papers › Answer Mining from a Pool of Images: Towards Retrieval-Based Visual Question Answering

Answer Mining from a Pool of Images: Towards Retrieval-Based Visual Question Answering

29 Jun 2023arXiv:2306.16713archive 2025-07-28

Abhirama Subramanyam Penamakuri, Manish Gupta, Mithun Das Gupta, Anand Mishra

We study visual question answering in a setting where the answer has to be mined from a pool of relevant and irrelevant images given as a context. For such a setting, a model must first retrieve relevant images from the pool and answer the question from these retrieved images. We refer to this problem as retrieval-based visual question answering (or RETVQA in short). The RETVQA is distinctively different and more challenging than the traditionally-studied Visual Question Answering (VQA), where a given question has to be answered with a single relevant image in context. Towards solving the RETVQA task, we propose a unified Multi Image BART (MI-BART) that takes a question and retrieved images using our relevance encoder for free-form fluent answer generation. Further, we introduce the largest dataset in this space, namely RETVQA, which has the following salient features: multi-image and retrieval requirement for VQA, metadata-independent questions over a pool of heterogeneous images, expecting a mix of classification-oriented and open-ended generative answers. Our proposed framework achieves an accuracy of 76.5% and a fluency of 79.3% on the proposed dataset, namely RETVQA and also outperforms state-of-the-art methods by 4.9% and 11.8% on the image segment of the publicly available WebQA dataset on the accuracy and fluency metrics, respectively.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 7 code samples harvested from 1 repository linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 4 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 7 samples from 1 repository, 7 ran (3 with no instrument failure; 4 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-24 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

Abhiram4572/mi_bart officialmentioned on GitHubpytorchMITSyntology: 7 samples, 7 ran (4 instrument-failed) · 0 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

7 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 4 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

3ran · our draft was wrong
1ran; the contract check could not run
3ran

Licence: 6 of the 7 samples are pointer only, meaning Syntology does not serve that copy's text. For 6 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from Abhiram4572/mi_bart. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

Abhiram4572/mi_bart official repository 7 samples, 7 ran (4 instrument-failed) · 0 unverified
all_gather in 119 papers mi_bart/src/dist_utils.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 41c46b0d5713eb14 · report fixture: signature data:dict/0/?, group:NoneType/0/? · returned list · level recorded 2026-09-24
do_nms in 12 papers mi_bart/inference/modeling_frcnn.py ran MIT (permissive) here; the stored copy is pointer only · e21bb85b8e1b4836 · report fixture: signature boxes:Tensor/2/float, scores:Tensor/2/float, image_shape:tuple/1/int, score_thresh:float/0/float, nms_thresh:float/0/float, mind:int/0/int, maxd:int/0/int · returned tuple · level recorded 2026-09-24
gather in 75 papers mi_bart/src/dist_utils.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 00a9f7918ac39329 · report fixture: signature data:dict/0/?, dst:int/0/int, group:NoneType/0/? · returned list · level recorded 2026-09-24
norm_box in 12 papers mi_bart/inference/modeling_frcnn.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) here; the stored copy is pointer only · 16c0e181ff805fb7 · report fixture: signature boxes:Tensor/3/float, raw_sizes:Tensor/2/float · returned Tensor · level recorded 2026-09-24
normalize_text_for_bart mi_bart/src/eval_retvqa.py ran fingerprinted MIT (permissive) · c1fdfb1330fa24b1 · report fixture: signature x:str/0/str · returned str · level recorded 2026-09-26
pad_list_tensors in 12 papers mi_bart/inference/modeling_frcnn.py ran MIT (permissive) here; the stored copy is pointer only · 54a2fff601881b32 · report fixture: signature list_tensors:list/1/Tensor, preds_per_image:list/1/int, max_detections:int/0/int, return_tensors:str/0/str, padding:str/0/str, pad_value:int/0/int, location:str/0/str · returned Tensor · level recorded 2026-09-24
reduce_dict in 73 papers mi_bart/src/dist_utils.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 44f4152cc7eb1ddd · report fixture: signature input_dict:dict/0/?, average:bool/0/bool · returned dict · level recorded 2026-09-24

Tasks

Answer GenerationQuestion AnsweringRetrievalVisual Question AnsweringVisual Question Answering (VQA)

Datasets

Introduced by this paper, per the archive.

RetVQA

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Visual Question Answering (VQA) RetVQA MI-BART Accuarcy 76.5 #1 of 1 Archive leaderboard report
Visual Question Answering (VQA) RetVQA MI-BART Accuracy * Fluency 70.9 #1 of 1 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

AdamAttentionBARTBPEDense ConnectionsDropoutLayer NormalizationLinear LayerMulti-Head AttentionResidual ConnectionSoftmax

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections