BioKGBench-Dataset / README.md
alexander2618's picture
update metadata
09b4620
|
raw
history blame
5.08 kB
metadata
language:
  - en
license: mit
task_categories:
  - question-answering
  - text-retrieval
  - other
pretty_name: BioKGBench
size_categories: 10K<n<100K
annotations_creators:
  - expert-generated
  - machine-generated
task_ids:
  - fact-checking
  - closed-domain-qa
  - fact-checking-retrieval
dataset_info:
  features:
    - name: kgcheck
      dtype: string
    - name: kgqa
      dtype: string
    - name: scv
      dtype: string
    - name: bioKG
      dtype: string
configs:
  - config_name: kgcheck
    data_files:
      - split: dev
        path: kgcheck/dev.json
      - split: test
        path: kgcheck/test.json
  - config_name: kgqa
    data_files:
      - split: dev
        path: kgqa/dev.json
      - split: test
        path: kgqa/test.json
  - config_name: scv-corpus
    data_files:
      - split: corpus
        path: scv/merged_corpus.jsonl
  - config_name: scv
    data_files:
      - split: dev
        path: scv/dev.jsonl
      - split: test
        path: scv/test.jsonl
  - config_name: biokg
    data_files:
      - split: datasets
        path: bioKG/datasets/*.tsv
      - split: ontologies
        path: bioKG/ontologies/*.tsv
tags:
  - agent
  - medical
arxiv: 2407.00466

Agent4S-BioKG

A Knowledge Graph Checking Benchmark of AI Agent for Biomedical Science.

Github

Introduction

Pursuing artificial intelligence for biomedical science, a.k.a. AI Scientist, draws increasing attention, where one common approach is to build a copilot agent driven by Large Language Models(LLMs).
However, to evaluate such systems, people either rely on direct Question-Answering
(QA) to the LLM itself, or in a biomedical experimental manner. How to precisely benchmark biomedical agents from an AI Scientist perspective remains largely unexplored. To this end, we draw inspiration from one most important abilities of scientists, understanding the literature, and introduce BioKGBench.
In contrast to traditional evaluation benchmark that only focuses on factual QA, where the LLMs are known to have hallucination issues, we first disentangle Understanding Literature into two atomic abilities, i) Understanding the unstructured text from research papers by performing scientific claim verification, and ii) Ability to interact with structured Knowledge-Graph Question-Answering~(KGQA) as a form of Literature grounding. We then formulate a novel agent task, dubbed KGCheck, using KGQA and domain-based Retrieval-Augmented Generation (RAG) to identify the factual errors of existing large-scale knowledge graph databases. We collect over two thousand data for two atomic tasks and 225 high-quality annotated data for the agent task. Surprisingly, we discover that state-of-the-art agents, both daily scenarios and biomedical ones, have either failed or inferior performance on our benchmark. We then introduce a simple yet effective baseline, dubbed BKGAgent. On the widely used popular dataset, we discover over 90 factual errors which yield the effectiveness of our approach, yields substantial value for both the research community or practitioners in the biomedical domain.

Overview

Dataset(Need to download from huggingface)
  • bioKG: The knowledge graph used in the dataset.
  • KGCheck: Given a knowledge graph and a scientific claim, the agent needs to check whether the claim is supported by the knowledge graph. The agent can interact with the knowledge graph by asking questions and receiving answers.
    • Dev: 20 samples
    • Test: 205 samples
    • corpus: 51 samples
  • KGQA: Given a knowledge graph and a question, the agent needs to answer the question based on the knowledge graph.
    • Dev: 60 samples
    • Test: 638 samples
  • SCV: Given a scientific claim and a research paper, the agent needs to check whether the claim is supported by the research paper.
    • Dev: 120 samples
    • Test: 1265 samples
    • corpus: 5664 samples

Citation

Contact

For adding new features, looking for helps, or reporting bugs associated with BioKGBench, please open a GitHub issue and pull request with the tag new features, help wanted, or enhancement. Feel free to contact us through email if you have any questions.