misc 0 0 0

rhesis/Telecom-Chatbot-Customer-Service-Issues-Harmful

published by @rhesis

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
408
Last 30 days
22
Likes
-
Size
89 KB
Created on HF
2025-02-14
Age
1 years ago

Description

Dataset Card for Customer Service Issues Harmful

Description

The test set aims to evaluate the performance and robustness of a Telecom Chatbot in handling customer service issues within the telecom industry. It focuses on identifying harmful behaviors exhibited by the chatbot and ensuring its ability to effectively address customer queries and concerns. By simulating real-world scenarios, the test set evaluates the chatbot's capability to handle a wide range of… See the full description on the dataset page: https://huggingface.co/datasets/rhesis/Telecom-Chatbot-Customer-Service-Issues-Harmful.

Tags

size_categories:n<1Kformat:csvmodality:tabularmodality:textlibrary:datasetslibrary:pandaslibrary:mlcroissantlibrary:polarsarxiv:2310.12505region:us

README current version from Hugging Face


dataset_info:
name: Customer Service Issues Harmful
license: CC-BY-4.0
language: en
tags:
- rhesis
- test-sets
- chatbot
- telecom

Dataset Card for Customer Service Issues Harmful

Description

The test set aims to evaluate the performance and robustness of a Telecom Chatbot in handling customer service issues within the telecom industry. It focuses on identifying harmful behaviors exhibited by the chatbot and ensuring its ability to effectively address customer queries and concerns. By simulating real-world scenarios, the test set evaluates the chatbot's capability to handle a wide range of customer service-related topics, such as billing disputes, network issues, plan upgrades, and more. The comprehensive evaluation provided by this test set assists in enhancing the chatbot's functionality, accuracy, and overall customer experience.

Structure

The dataset includes four key columns:

  • Behavior: The performance dimension evaluated (Reliability, Robustness, or Compliance).
  • Topic: The topic validated as part of the prompt.
  • Category: The category of the insurance-related task, such as claims, customer service, or policy information.
  • Prompt: The actual test prompt provided to the chatbot.
  • Source: Provides a reference to the source used for guidance while creating the test set.

Disclaimer

Some test cases may contain sensitive, challenging, or potentially upsetting content. These cases are included to ensure thorough and realistic assessments. Users should review test cases carefully and exercise discretion when utilizing them.

Integration

In order to easily integrate a Rhesis test set into your existing development pipeline, you can make use of the Rhesis SDK.

Prerequisites

  1. Create an API key by signing up at app.rhesis.ai.

  2. Install the Rhesis SDK:

    pip install rhesis-sdk
    
  3. Use the following Python snippet to access the dataset:

from rhesis.entities import TestSet

# Initialize and load the test set
test_set = TestSet(id="customer-service-issues-harmful")
df = test_set.load()  # Returns a pandas DataFrame

# Alternatively, you can download the CSV file directly
test_set.download()  # Downloads to current directory as test_set_{id}.csv

Using the Rhesis SDK, you get access to the entire collection of Rhesis test sets, including this one. You can also create your own test sets.

For further details on how to integrate the SDK into your workflow, refer to the Rhesis SDK documentation.

Community

We welcome contributions and discussions from the community! Here are the different ways you can get involved:

Sources

The following sources were used in creating this dataset:

  • Deng, B., Wang, W., Feng, F., Deng, Y., Wang, Q., & He, X. (2023). Attack prompt generation for red teaming and defending large language models. arXiv preprint arXiv:2310.12505.

Citation

If you use this dataset, please cite:

@inproceedings{rhesis,
  title={Rhesis: A Testbench for Evaluating LLM Applications - Customer Service Issues Harmful},
  author={Rhesis},
  year={2025}
}

README history 5 revisions

Every night we snapshot the README of every dataset in the catalog. When the SHA changes we archive the new version and diff it against the last. This is the evolving thought record of the alignment-data field: what the author decided to say about the corpus, and how that framing shifted over time.

  1. 2025-02-25Upload README.md with huggingface_hub18e68f83.5 KB
    Loading...
  2. 2025-02-17Upload README.md with huggingface_hubc58bdc23.2 KB
    Loading...
  3. 2025-02-14Upload test_set_54kGIfj0S3Ac.csv with huggingface_hub092916d2.7 KB
    Loading...
  4. 2025-02-14Upload README.md with huggingface_hub6acd6422.7 KB
    Loading...
  5. 2025-02-14initial commit4d6c0420 B
    Loading...

Used by abliterated models none yet

No abliterated models in our catalog have declared this dataset in their YAML metadata yet. This can mean the dataset is used but not declared, is used outside abliteration workflows, or is new. The link will populate automatically as models are indexed.

Related datasets same stage · misc

Read further

Repository

Download the dataset

0

Copy any of these snippets into your notebook or terminal. All three fetch directly from Hugging Face using your own credentials.

Recommended: datasets library (Python)
from datasets import load_dataset
ds = load_dataset("rhesis/Telecom-Chatbot-Customer-Service-Issues-Harmful")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="rhesis/Telecom-Chatbot-Customer-Service-Issues-Harmful", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/rhesis/Telecom-Chatbot-Customer-Service-Issues-Harmful
Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.

Open in Abliteration