Skip to main content

Pip package for Verifact

Project description

VeriScore

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

  1. prompting (Implemented)
  2. fine-tuned model (in progress)

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.

Install

  1. Make a new Python 3.6+ environment using virtualenv or conda.
  2. Install veriscore pacakge using pip
  3. Download en_core_web_sm using spacy 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}
epport 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}

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": claim_list,
  "all_claim_lst": all_claim_lst
 }

Evidence searching:

 python3 -m veriscore.retrieval_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
 }

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-1.0.3.tar.gz (14.6 kB view details)

Uploaded Source

Built Distribution

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

VeriScore-1.0.3-py3-none-any.whl (21.3 kB view details)

Uploaded Python 3

File details

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

File metadata

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

File hashes

Hashes for veriscore-1.0.3.tar.gz
Algorithm Hash digest
SHA256 f27f7f1753deaac240ba0b8cf7ac3517bed17e115db607c8cd072b352b5bb544
MD5 5c5dca194a085d9e6d5605694a660818
BLAKE2b-256 e32c4dc68b9f52d1b89316ddac067eacf9c89f92d2c9789f1d95f721d2409911

See more details on using hashes here.

File details

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

File metadata

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

File hashes

Hashes for VeriScore-1.0.3-py3-none-any.whl
Algorithm Hash digest
SHA256 955cf5e1e9ebfbb9a873e3b7426655bed0a453f7ca96aba074e9779f8386079f
MD5 a36fce3141deebd366fbf06647dd01e4
BLAKE2b-256 6f5647a14af7c38847194a2c0a199a4fcfd67d12d9632dd09937c70875998f8f

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