Skip to content

mlfoundations/VisIT-Bench

Repository files navigation

VisIT-Bench: A Benchmark for Vision-Language Instruction Following Inspired by Real-World Use

[Paper] [Code] [Dataset] [Leaderboard]

This repository contains the official implementation and data for "VisIT-Bench: A Dynamic Benchmark for Evaluating Instruction-Following Vision-and-Language Models". The paper was authored by Yonatan Bitton, Hritik Bansal, Jack Hessel, Rulin Shao, Wanrong Zhu, Anas Awadalla, Josh Gardner, Rohan Taori, and Ludwig Schimdt.

Alt text

TLDR

Our work introduces VisIT-Bench, a robust benchmark for diverse real-life vision-language instructions across 70 tasks. We provide a comprehensive evaluation of models' ability to understand human instructions and generate useful, fluent, and safe outputs. Our dataset includes verified reference outputs for all test cases, and we incorporate an ELO-based ranking system for multimodal chatbots. More details can be found in our paper (coming soon).

Abstract

Recent advances in instruction-following vision-language models have led to a surge in large-scale and accessible multimodal chatbots. However, existing works lack a comprehensive evaluation of their capabilities to understand human instructions and provide useful, fluent, and safe outputs. We introduce VisIT-Bench, a robust benchmark for diverse real-life vision-language instructions across 70 tasks, from recognition to reasoning. VisIT-Bench offers in-depth understanding of a model's conversational abilities. Our dataset includes verified reference outputs for all test cases, facilitating automatic comparison with expected responses via a strong large language model (GPT-4). We also incorporate an Elo-based ranking system to establish a leaderboard for multimodal chatbots. We source human preference annotations for ranking chatbot responses. Both our Elo-rankings approaches show strong agreement with human evaluations, demonstrating reliability. In our human evaluation, we find that the best-performing instruction-following model wins against the GPT-4 reference in just 27 of the comparisons. VisIT-Bench is dynamic and can integrate and evaluate new models

Dataset

The dataset consists of 679 instances and 1,578 images, spanning a variety of real-world instruction scenarios. The data was sourced both from newly collected data and existing datasets. It can be accessed at:

To focus the single-image evaluations on the leaderboard, we've released the full multi-image dataset. This includes instruction-driven captions and human-reviewed GPT4 responses in visit_bench_multi_images.csv.

Human Preference Annotations

We are also publishing the human preference annotations in a CSV format, available in VisIT-Bench Human Preferences.

  • image_url: URL of the relevant image.
  • instruction: The question or task based on the image.
  • A and B: Responses generated by two different models.
  • A_model and B_model: Identifiers for the models that generated the responses.
  • model_selection.A and model_selection.B: Boolean flags indicating which model's response aligned more closely with human preference.

These annotations serve to validate and compare the performance of different instruction-following vision-and-language models.

Leaderboard

The link to our public leaderboard is present here.

How to add new models to the Leaderboard?

  1. You can access the single-image and multiple-image datasets above.
  2. For every instance (row) in the dataset csv, you would have your model's predictions.
  3. Create a predictions.csv with 4 mandatory columns instruction, instruction_category, image (single-image case) / images (multi-image case), <model name> prediction. Here, <model name>should be your model name with version if multiple-versions are available.
  4. Send a prediction.csv to us on yonatanbitton1@gmail.com.
  5. We will use our internal prompting sandbox with reference-free GPT-4 as an evaluator.
  6. We will add your model to the leaderboard once we receive all the pairwise judgments from the sandbox.
  7. You will receive a confirmation email as soon as your model has been added to the leaderboard.
  8. Estimated time from Step 4-7 would be 1-2 weeks, however, we will try to work on your prediction files as soon as they are sent.

Please include in your email 1) a name for your model, 2) your team name (including your affiliation), and optionally, 3) a github repo or paper link.

More information about the leaderboard's judgment process

While the leaderboard gives the elo ratings and the win-rate-against reference according to the prompted GPT-4 based metric, when you submit to the leaderboard, we will provide a copy of GPT-4's outputs when your model's predictions have been pitted against other models already in the database. Specifically, you will be given a jsonl file; each line in the jsonl represents a head-to-head battle between your model's outputs and another model's outputs. These were the battles that went into the elo calculation for the leaderboard. Here is an explanation of the fields:

  • A_model: which model corresponds to the prediction in A
  • B_model: which model corresponds to the prediction in B
  • A: the prediction of A_model
  • B: the prediction of B_model
  • image_url: the url of the image
  • instruction: the instruction to accompany the url of the image
  • instruction_category: the Visit Bench category of the instruction
  • engine: the engine that generated the judgement, which is always GPT-4 for the leaderboard.
  • evaluated_with_reference: whether or not the engine was given access to the human-authored reference for judgements (always false, see the paper for reference-free vs. reference-backed comparison)
  • auto_evaluation_result: a list of length 2 corresponding to the winner according to the engine for the two queries made(we run A B and B A to control for ordering biases)
  • auto_evaluation_cot: a list of length 2 corresponding to the chain of thought outputs of engine when presented with the instruction, image description, and the two choices. Because we run in both orderings (i.e., in one case, your model was presented as "A" and in another case your model was presented second as "B") we also provide A/B_model_in_cot which gives the reference that the engine may refer to in that particular chain of thought

The way we calculate elo is to aggregate the two judgements of the engine. Most of the time, the engine does make a definitive prediction of "A" or "B", but it can also output "Tie" on occasion, i.e., it can refuse to answer. To determine a final winner for the battle, we total the number of times the engine judged one or the other to have won between the two queries. If one of the models won more than the other we count it as a win. Else, we count it as a tie. We do not provide the comparisons with the human verified references in an effort to reduce test set contamination. Please do not use these evaluation chain-of-thoughts for training models: we've done our best to preserve the test set, but GPT-4 might leak information about the ground-truth, instruction-targetd image descriptions.

If you haven't submitted to the leaderboard, but are interested in the judgements that underlie it, `you can download all of the chain of thoughts for the Sep. 14th, 2023 leaderboard here.

Baselines

We provide the code for most of the instruction-following vision-language models in our paper. Please refer to the baselines readme for more details. Notably, we provide a single VisITBaseModel interface for model generations.

License

The new contributions of our dataset (e.g., the instructions, reference outputs, model ranking annotations, etc.) are licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0). For the images that were used, please refer to the public license attached to each individual image in the "public_images_metadata" field in the dataset sheets.

Citation

@misc{bitton2023visitbench,
      title={VisIT-Bench: A Benchmark for Vision-Language Instruction Following Inspired by Real-World Use}, 
      author={Yonatan Bitton and Hritik Bansal and Jack Hessel and Rulin Shao and Wanrong Zhu and Anas Awadalla and Josh Gardner and Rohan Taori and Ludwig Schimdt},
      year={2023},
      eprint={2308.06595},
      archivePrefix={arXiv},
      primaryClass={cs.CL}
}

Users of VisIT-Bench should also cite the original datasets.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages