Skip to main content

Pip package for VeriScore

Project description

VeriScore

This is introduction for pip package of VeriScore. It have two type of method to extract claims by

  1. Prompting
  2. Fine-tuned model

We have a preliminary Colab notebook for demo

VeriScore consists of three parts 1) claim extraction 2) evidence searching and 3) claim verification. We provide an end-to-end pipeline to obtain the VeriScore, along with each of its components individually.

You can choose between a prompting-based approach and a fine-tuned model-based approach using the model_name option. If you specify the path to the checkpoint of a fine-tuned model, it will automatically access the local model to perform inference. If the model name is not in a directory format, it will use an API call instead.

Install

  1. Make a new Python 3.9+ environment using virtualenv or conda.
  2. Install veriscore pacakge using pip
  3. Download en_core_web_sm using spacy library
  4. Our code supports inference using fine-tuned models based on the Unsloth library. To use this feature, you need to install the Unsloth library.
pip install --upgrade veriscore
python -m spacy download en_core_web_sm

Setup environment before running code

  1. Download prompt folder that have txt file of prompt template (you can see prompt folder VeriScore's repository)
  2. Set OpenAI or Claude API key to environment variable of bash for prompting approach
export OPENAI_API_KEY_PERSONAL={your_openai_api_key}
export CLAUDE_API_KEY={your_claude_api_key}
  1. Set SERPER API key to environment variable of bash for searching evidence
export SERPER_KEY_PRIVATE={your_serper_api_key}
  1. For the prompt-based approach, you need to set data_dir/demos/ with few-shot examples.

Running VeriScore using a command line

This is an end-to-end pipeline for running VeriScore.

 python3 -m veriscore.veriscore --data_dir {data_dir} --input_file {input_file} --model_name_extraction {model_name_extraction} --model_name_verification {model_name_verification}
  • data_dir: Directory containing input data. ./data by default.
  • input_file: Name of input data file. It should be jsonl format where each line contains
    • question: query to ask
    • response: generated response from of question
    • model: name of model generate response
    • prompt_source: name of dataset provide question like FreshQA
  • model_name_extraction: Name of model used for claim extraction. gpt-4-0125-preview by default.
  • model_name_verification: Name of model used for claim verification. gpt-4o by default.

Other optional flags:

  • output_dir: Directory for saving ouptut data. ./data by default.
  • cache_dir: Directory for saving cache data. ./data/cache by default.
  • label_n: This is type of label for claim verification. It could be 2 (binary) ro 3 (trinary)
    • 2: query to ask binary supported and unsupported
    • 3: query to ask trinay labels—supported, contradicted, and inconclusive
  • search_res_num: A Hyperparameter for number of search result. 5 by default.

Saving output: input_file_name is file name removed jsonl from —-input_file

  • extracted claims will be saved to output_dir/claims_{input_file_name}.jsonl.
  • searched evidence will be saved to output_dir/evidence_{input_file_name}.jsonl.
  • verified claims will be saved to output_dir/model_output/verification_{input_file_name}.jsonl.

Running individual part using a command line

Claim extraction:

 python3 -m veriscore.extract_claims --data_dir {data_dir} --input_file {input_file} --model_name {model_name} 
  • input_file: Name of input data file. It should be jsonl format where each line contains
    • question: query to ask
    • response: generated response from of question
    • model: name of model generate response
    • prompt_source: name of dataset provide question like FreshQA
  • model_name: Name of model used for claim extraction. gpt-4-0125-preview by default. output:
 {
  "question": question.strip(),
  "prompt_source": prompt_source,
  "response": response.strip(),
  "prompt_tok_cnt": prompt_tok_cnt,
  "response_tok_cnt": response_tok_cnt,
  "model": model,
  "abstained": False,  
  "claim_list": list of claims for each snippet,
  "all_claims": list of all claims
 }

Evidence searching:

 python3 -m veriscore.retrieve_evidence --data_dir {data_dir} --input_file {input_file}
  • input_file: Name of input data file. It should be jsonl format where each line contains the keys of the output dictionary from the Claim extraction. output:
 {
  ...
  "claim_snippets_dict": dictionary for claim and list of searched evidence. each evidence have dictionary of {"title": title, "snippet": snippet, "link": link}
 }

Claim verification:

 python3 -m veriscore.verify_claims --data_dir {data_dir} --input_file {input_file} --model_name {model_name}
  • input_file: Name of input data file. It should be jsonl format where each line contains the keys of the output dictionary from the Evidence searching. output:
 {
  ...
  "response": result of claim verification
  "clean_output": post-processed label
 }

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

veriscore-2.0.1.tar.gz (16.0 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

VeriScore-2.0.1-py3-none-any.whl (21.1 kB view details)

Uploaded Python 3

File details

Details for the file veriscore-2.0.1.tar.gz.

File metadata

  • Download URL: veriscore-2.0.1.tar.gz
  • Upload date:
  • Size: 16.0 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.1.0 CPython/3.10.14

File hashes

Hashes for veriscore-2.0.1.tar.gz
Algorithm Hash digest
SHA256 606a5cd5b0a9f3afc226a39b350ec69c221bb51d60413434049223d6463e8fef
MD5 fb53c6a7218bb51a75f062469738f086
BLAKE2b-256 2adc8161895545c88c8174b2f996360f88b85d40d113f3d3d09fddc59f604e6d

See more details on using hashes here.

File details

Details for the file VeriScore-2.0.1-py3-none-any.whl.

File metadata

  • Download URL: VeriScore-2.0.1-py3-none-any.whl
  • Upload date:
  • Size: 21.1 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.1.0 CPython/3.10.14

File hashes

Hashes for VeriScore-2.0.1-py3-none-any.whl
Algorithm Hash digest
SHA256 575ed8af25f307c601567b0f058cca51c47b51e83cfaee6242fd568595e03834
MD5 ba4e99676f6048d212140761a7c03df1
BLAKE2b-256 5c06cf1480a0314a90b818615dc2b75350b8c266c947ce653d2e684a86fbfb39

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page