Deque uses Labelbox Model Diagnostics and Catalog to improve ML model performance 5%+ and cut labeling spend by over 50%
Deque's ML team spent about 10 minutes annotating each webpage screen and relied on disparate open-source annotation tools hacked together with Jupyter Notebooks and Google Sheets to manually calculate model metrics, making dataset curation and error diagnosis a disjointed, labor-intensive process.
Before Labelbox, the team had to manually visualize model predictions and calculate metrics themselves, and data selection for poorly-performing classes required tedious, untargeted collection.
Using Labelbox Model Diagnostics and Catalog, Deque filtered out about one-third of less trustworthy data points, raised model performance by 5%+, and reduced annual labeling spend and needs by over 50%.
Show all 8 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
Using Labelbox Model Diagnostics and Catalog, Deque filtered out about one-third of less trustworthy data points, raised model performance by 5%+, and reduced annual labeling spend and needs by over 50%.
What tools did this team use?
Labelbox, Model Diagnostics, Catalog, Jupyter Notebooks, Google Sheets.
What results were reported?
Annotation time per screen: about 10 minutes; Data points filtered out as less trustworthy: about one-third; Model performance improvement: 5%+; Annual labeling spend and needs reduction: over 50% (source-reported, not independently verified).
What failed first in this deployment?
Before Labelbox, the team had to manually visualize model predictions and calculate metrics themselves, and data selection for poorly-performing classes required tedious, untargeted collection.
How is this data entry ops AI workflow structured?
Webpage screen annotation → Model Diagnostics noise detection → Low-trust data filtering → Catalog targeted data prioritization → Re-labeling and model iteration.