Detecting Issues in a Text Dataset with Datalab#
In this 5-minute quickstart tutorial, we use Datalab to detect various issues in an intent classification dataset composed of (text) customer service requests at an online bank. We consider a subset of the Banking77-OOS Dataset containing 1,000 customer service requests which are classified into 10 categories based on their intent (you can run this same code on any text classification dataset). Cleanlab automatically identifies bad examples in our dataset, including mislabeled data, out-of-scope examples (outliers), or otherwise ambiguous examples. Consider filtering or correcting such bad examples before you dive deep into modeling your data!
Overview of what we’ll do in this tutorial:
Use a pretrained transformer model to extract the text embeddings from the customer service requests
Train a simple Logistic Regression model on the text embeddings to compute out-of-sample predicted probabilities
Run cleanlab’s
Datalabaudit with these predictions and embeddings in order to identify problems like: label issues, outliers, and near duplicates in the dataset.
Quickstart
Already have (out-of-sample) pred_probs from a model trained on an existing set of labels? Maybe you have some numeric features as well? Run the code below to find any potential label errors in your dataset.
from cleanlab import Datalab
lab = Datalab(data=your_dataset, label_name="column_name_of_labels")
lab.find_issues(pred_probs=your_pred_probs, features=your_features)
lab.report()
lab.get_issues()
1. Install required dependencies#
You can use pip to install all packages required for this tutorial as follows:
!pip install sklearn sentence-transformers
!pip install "cleanlab[datalab]"
# Make sure to install the version corresponding to this tutorial
# E.g. if viewing master branch documentation:
# !pip install git+https://github.com/cleanlab/cleanlab.git
[2]:
import re
import string
import pandas as pd
from sklearn.metrics import accuracy_score, log_loss
from sklearn.model_selection import cross_val_predict
from sklearn.linear_model import LogisticRegression
from sentence_transformers import SentenceTransformer
from cleanlab import Datalab
2. Load and format the text dataset#
[4]:
data = pd.read_csv("https://s.cleanlab.ai/banking-intent-classification.csv")
data.head()
[4]:
| text | label | |
|---|---|---|
| 0 | i accidentally made a payment to a wrong account. what should i do? | cancel_transfer |
| 1 | i no longer want to transfer funds, can we cancel that transaction? | cancel_transfer |
| 2 | cancel my transfer, please. | cancel_transfer |
| 3 | i want to revert this mornings transaction. | cancel_transfer |
| 4 | i just realised i made the wrong payment yesterday. can you please change it to the right account? it's my rent payment and really really needs to be in the right account by tomorrow | cancel_transfer |
[5]:
raw_texts, labels = data["text"].values, data["label"].values
num_classes = len(set(labels))
print(f"This dataset has {num_classes} classes.")
print(f"Classes: {set(labels)}")
This dataset has 10 classes.
Classes: {'getting_spare_card', 'cancel_transfer', 'beneficiary_not_allowed', 'supported_cards_and_currencies', 'card_about_to_expire', 'change_pin', 'lost_or_stolen_phone', 'apple_pay_or_google_pay', 'visa_or_mastercard', 'card_payment_fee_charged'}
Let’s view the i-th example in the dataset:
[6]:
i = 1 # change this to view other examples from the dataset
print(f"Example Label: {labels[i]}")
print(f"Example Text: {raw_texts[i]}")
Example Label: cancel_transfer
Example Text: i no longer want to transfer funds, can we cancel that transaction?
The data is stored as two numpy arrays:
raw_textsstores the customer service requests utterances in text formatlabelsstores the intent categories (labels) for each example
Bringing Your Own Data (BYOD)?
You can easily replace the above with your own text dataset, and continue with the rest of the tutorial.
Next we convert the text strings into vectors better suited as inputs for our ML models.
We will use numeric representations from a pretrained Transformer model as embeddings of our text. The Sentence Transformers library offers simple methods to compute these embeddings for text data. Here, we load the pretrained electra-small-discriminator model, and then run our data through network to extract a vector embedding of each example.
[7]:
transformer = SentenceTransformer('google/electra-small-discriminator')
text_embeddings = transformer.encode(raw_texts)
No sentence-transformers model found with name /home/runner/.cache/torch/sentence_transformers/google_electra-small-discriminator. Creating a new one with MEAN pooling.
/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/torch/_utils.py:831: UserWarning: TypedStorage is deprecated. It will be removed in the future and UntypedStorage will be the only storage class. This should only matter to you if you are using storages directly. To access UntypedStorage directly, use tensor.untyped_storage() instead of tensor.storage()
return self.fget.__get__(instance, owner)()
Our subsequent ML model will directly operate on elements of text_embeddings in order to classify the customer service requests.
3. Define a classification model and compute out-of-sample predicted probabilities#
A typical way to leverage pretrained networks for a particular classification task is to add a linear output layer and fine-tune the network parameters on the new data. However this can be computationally intensive. Alternatively, we can freeze the pretrained weights of the network and only train the output layer without having to rely on GPU(s). Here we do this conveniently by fitting a scikit-learn linear model on top of the extracted embeddings.
To identify label issues, cleanlab requires a probabilistic prediction from your model for each datapoint. However these predictions will be overfit (and thus unreliable) for datapoints the model was previously trained on. cleanlab is intended to only be used with out-of-sample predicted class probabilities, i.e. on datapoints held-out from the model during the training.
Here we obtain out-of-sample predicted class probabilities for every example in our dataset using a Logistic Regression model with cross-validation. Make sure that the columns of your pred_probs are properly ordered with respect to the ordering of classes, which for Datalab is: lexicographically sorted by class name.
[8]:
model = LogisticRegression(max_iter=400)
pred_probs = cross_val_predict(model, text_embeddings, labels, method="predict_proba")
4. Use cleanlab to find issues in your dataset#
Given feature embeddings and the (out-of-sample) predicted class probabilities obtained from any model you have, cleanlab can quickly help you identify low-quality examples in your dataset.
Here, we use cleanlab’s Datalab to find issues in our data. Datalab offers several ways of loading the data; we’ll simply wrap the training features and noisy labels in a dictionary.
[9]:
data_dict = {"texts": raw_texts, "labels": labels}
All that is need to audit your data is to call find_issues(). We pass in the predicted probabilities and the feature embeddings obtained above, but you do not necessarily need to provide all of this information depending on which types of issues you are interested in. The more inputs you provide, the more types of issues Datalab can detect in your data. Using a better model to produce these inputs will ensure cleanlab more accurately estimates issues.
[10]:
lab = Datalab(data_dict, label_name="labels")
lab.find_issues(pred_probs=pred_probs, features=text_embeddings)
Finding null issues ...
Finding label issues ...
Finding outlier issues ...
Fitting OOD estimator based on provided features ...
Finding near_duplicate issues ...
Finding non_iid issues ...
Finding class_imbalance issues ...
Finding underperforming_group issues ...
Audit complete. 85 issues found in the dataset.
After the audit is complete, review the findings using the report method:
[11]:
lab.report()
Here is a summary of the different kinds of issues found in the data:
issue_type num_issues
label 42
outlier 38
near_duplicate 4
non_iid 1
Dataset Information: num_examples: 1000, num_classes: 10
----------------------- label issues -----------------------
About this issue:
Examples whose given label is estimated to be potentially incorrect
(e.g. due to annotation error) are flagged as having label issues.
Number of examples with this issue: 42
Overall dataset quality in terms of this issue: 0.9710
Examples representing most severe instances of this issue:
is_label_issue label_score given_label predicted_label
981 True 0.000005 card_about_to_expire card_payment_fee_charged
974 True 0.000146 beneficiary_not_allowed change_pin
982 True 0.000224 apple_pay_or_google_pay card_about_to_expire
971 True 0.000507 beneficiary_not_allowed change_pin
980 True 0.000960 card_about_to_expire card_payment_fee_charged
---------------------- outlier issues ----------------------
About this issue:
Examples that are very different from the rest of the dataset
(i.e. potentially out-of-distribution or rare/anomalous instances).
Number of examples with this issue: 38
Overall dataset quality in terms of this issue: 0.3584
Examples representing most severe instances of this issue:
is_outlier_issue outlier_score
994 True 0.009642
999 True 0.013067
81 True 0.013841
433 True 0.014722
989 True 0.018224
------------------ near_duplicate issues -------------------
About this issue:
A (near) duplicate issue refers to two or more examples in
a dataset that are extremely similar to each other, relative
to the rest of the dataset. The examples flagged with this issue
may be exactly duplicated, or lie atypically close together when
represented as vectors (i.e. feature embeddings).
Number of examples with this issue: 4
Overall dataset quality in terms of this issue: 0.6070
Examples representing most severe instances of this issue:
is_near_duplicate_issue near_duplicate_score near_duplicate_sets distance_to_nearest_neighbor
160 True 0.095724 [148] 0.006237
148 True 0.095724 [160] 0.006237
546 True 0.099341 [514] 0.006485
514 True 0.099341 [546] 0.006485
481 False 0.123418 [] 0.008165
---------------------- non_iid issues ----------------------
About this issue:
Whether the dataset exhibits statistically significant
violations of the IID assumption like:
changepoints or shift, drift, autocorrelation, etc.
The specific violation considered is whether the
examples are ordered such that almost adjacent examples
tend to have more similar feature values.
Number of examples with this issue: 1
Overall dataset quality in terms of this issue: 0.0000
Examples representing most severe instances of this issue:
is_non_iid_issue non_iid_score
313 True 0.564102
13 False 0.572258
28 False 0.574915
31 False 0.575507
40 False 0.575874
Additional Information:
p-value: 0.0
Label issues#
The report indicates that cleanlab identified many label issues in our dataset. We can see which examples are flagged as likely mislabeled and the label quality score for each example using the get_issues method, specifying label as an argument to focus on label issues in the data.
[12]:
label_issues = lab.get_issues("label")
label_issues.head()
[12]:
| is_label_issue | label_score | given_label | predicted_label | |
|---|---|---|---|---|
| 0 | False | 0.792090 | cancel_transfer | cancel_transfer |
| 1 | False | 0.257611 | cancel_transfer | cancel_transfer |
| 2 | False | 0.698710 | cancel_transfer | cancel_transfer |
| 3 | False | 0.182121 | cancel_transfer | apple_pay_or_google_pay |
| 4 | False | 0.771619 | cancel_transfer | cancel_transfer |
This method returns a dataframe containing a label quality score for each example. These numeric scores lie between 0 and 1, where lower scores indicate examples more likely to be mislabeled. The dataframe also contains a boolean column specifying whether or not each example is identified to have a label issue (indicating it is likely mislabeled).
We can get the subset of examples flagged with label issues, and also sort by label quality score to find the indices of the 5 most likely mislabeled examples in our dataset.
[13]:
identified_label_issues = label_issues[label_issues["is_label_issue"] == True]
lowest_quality_labels = label_issues["label_score"].argsort()[:5].to_numpy()
print(
f"cleanlab found {len(identified_label_issues)} potential label errors in the dataset.\n"
f"Here are indices of the top 5 most likely errors: \n {lowest_quality_labels}"
)
cleanlab found 42 potential label errors in the dataset.
Here are indices of the top 5 most likely errors:
[981 974 982 971 980]
Let’s review some of the most likely label errors.
Here we display the top 5 examples identified as the most likely label errors in the dataset, together with their given (original) label and a suggested alternative label from cleanlab.
[14]:
data_with_suggested_labels = pd.DataFrame(
{"text": raw_texts, "given_label": labels, "suggested_label": label_issues["predicted_label"]}
)
data_with_suggested_labels.iloc[lowest_quality_labels]
[14]:
| text | given_label | suggested_label | |
|---|---|---|---|
| 981 | i was charged for getting cash. | card_about_to_expire | card_payment_fee_charged |
| 974 | can i change my pin on holiday? | beneficiary_not_allowed | change_pin |
| 982 | will i be sent a new card before mine expires? | apple_pay_or_google_pay | card_about_to_expire |
| 971 | please tell me how to change my pin. | beneficiary_not_allowed | change_pin |
| 980 | why do i see extra charges for withdrawing my money? | card_about_to_expire | card_payment_fee_charged |
These are very clear label errors that cleanlab has identified in this data! Note that the given_label does not correctly reflect the intent of these requests, whoever produced this dataset made many mistakes that are important to address before modeling the data.
Outlier issues#
According to the report, our dataset contains some outliers. We can see which examples are outliers (and a numeric quality score quantifying how typical each example appears to be) via get_issues. We sort the resulting DataFrame by cleanlab’s outlier quality score to see the most severe outliers in our dataset.
[15]:
outlier_issues = lab.get_issues("outlier")
outlier_issues.sort_values("outlier_score").head()
[15]:
| is_outlier_issue | outlier_score | |
|---|---|---|
| 994 | True | 0.009642 |
| 999 | True | 0.013067 |
| 81 | True | 0.013841 |
| 433 | True | 0.014722 |
| 989 | True | 0.018224 |
[16]:
lowest_quality_outliers = outlier_issues["outlier_score"].argsort()[:5]
data.iloc[lowest_quality_outliers]
[16]:
| text | label | |
|---|---|---|
| 994 | (A AND NOT B) OR (C AND NOT D) OR (B AND NOT C AND D) | change_pin |
| 999 | 636C65616E6C616220697320617765736F6D6521 | cancel_transfer |
| 81 | cancel transaction | cancel_transfer |
| 433 | phone is gone | lost_or_stolen_phone |
| 989 | <p><samp>File not found.<br>Press F1 to continue</samp></p> | supported_cards_and_currencies |
We see that cleanlab has identified entries in this dataset that do not appear to be proper customer requests. Outliers in this dataset appear to be out-of-scope customer requests and other nonsensical text which does not make sense for intent classification. Carefully consider whether such outliers may detrimentally affect your data modeling, and consider removing them from the dataset if so.
Near-duplicate issues#
According to the report, our dataset contains some sets of nearly duplicated examples. We can see which examples are (nearly) duplicated (and a numeric quality score quantifying how dissimilar each example is from its nearest neighbor in the dataset) via get_issues. We sort the resulting DataFrame by cleanlab’s near-duplicate quality score to see the text examples in our dataset that are most nearly duplicated.
[17]:
duplicate_issues = lab.get_issues("near_duplicate")
duplicate_issues.sort_values("near_duplicate_score").head()
[17]:
| is_near_duplicate_issue | near_duplicate_score | near_duplicate_sets | distance_to_nearest_neighbor | |
|---|---|---|---|---|
| 160 | True | 0.095724 | [148] | 0.006237 |
| 148 | True | 0.095724 | [160] | 0.006237 |
| 546 | True | 0.099341 | [514] | 0.006485 |
| 514 | True | 0.099341 | [546] | 0.006485 |
| 481 | False | 0.123418 | [] | 0.008165 |
The results above show which examples cleanlab considers nearly duplicated (rows where is_near_duplicate_issue == True). Here, we see that example 160 and 148 are nearly duplicated, as are example 546 and 514.
Let’s view these examples to see how similar they are.
[18]:
data.iloc[[160, 148]]
[18]:
| text | label | |
|---|---|---|
| 160 | why was i charged an additional fee when paying with card? | card_payment_fee_charged |
| 148 | why was i charged an extra fee when paying with card? | card_payment_fee_charged |
[19]:
data.iloc[[546, 514]]
[19]:
| text | label | |
|---|---|---|
| 546 | do i have to go to the bank to change my pin? | change_pin |
| 514 | do i have to go into the bank to change my pin? | change_pin |
We see that these two sets of request are indeed very similar to one another! Including near duplicates in a dataset may have unintended effects on models, and be wary about splitting them across training/test sets. Learn more about handling near duplicates in a dataset from the FAQ.
Non-IID issues (data drift)#
According to the report, our dataset does not appear to be Independent and Identically Distributed (IID). The overall non-iid score for the dataset (displayed below) corresponds to the p-value of a statistical test for whether the ordering of samples in the dataset appears related to the similarity between their feature values. A low p-value strongly suggests that the dataset violates the IID assumption, which is a key assumption required for conclusions (models) produced from the
dataset to generalize to a larger population.
[20]:
p_value = lab.get_info('non_iid')['p-value']
p_value
[20]:
0.0
Here, our dataset was flagged as non-IID because the rows happened to be sorted by class label in the original data. This may be benign if we remember to shuffle rows before model training and data splitting. But if you don’t know why your data was flagged as non-IID, then you should be worried about potential data drift or unexpected interactions between data points (their values may not be statistically independent). Think carefully about what future test data may look like (and whether your data is representative of the population you care about). You should not shuffle your data before the non-IID test runs (will invalidate its conclusions).
As demonstrated above, cleanlab can automatically shortlist the most likely issues in your dataset to help you better curate your dataset for subsequent modeling. With this shortlist, you can decide whether to fix these label issues or remove nonsensical or duplicated examples from your dataset to obtain a higher-quality dataset for training your next ML model. cleanlab’s issue detection can be run with outputs from any type of model you initially trained.
Easy Mode#
Cleanlab is most effective when you run this code with a good ML model. Try to produce the best ML model you can for your data (instead of the basic model from this tutorial). If you don’t know the best ML model for your data, try Cleanlab Studio which will automatically produce one for you. Super easy to use, Cleanlab Studio is no-code platform for data-centric AI that automatically: detects data issues (more types of issues than this cleanlab package), helps you quickly correct these data issues, confidently labels large subsets of an unlabeled dataset, and provides other smart metadata about each of your data points – all powered by a system that automatically trains/deploys the best ML model for your data. Try it for free!