JevMade

Sign in
← Back to guides

JevMade field notes / Written guide

Aman Kumar: When Jev Works as a Filter

Aman Kumar compares Jev with language models on public text datasets and private workflows, recommending a filter for the clearest cases.

Original by Aman KumarEvaluation

Listen to this guide

JevMade’s plain-English explanation

0:00 /

Our summary

About 16,000 calls underpin Aman Kumar's comparison of Jev with small language models on public text datasets and private business workflows. He asks whether Jev should replace a whole classifier or filter just the cases that look clearly positive or clearly negative.

His proposed filter takes cases from both ends of the probability scale. Very high and very low scores can use a cheaper route, while the uncertain middle goes to another model. Test the cutoffs on your own examples; a score that worked elsewhere is not a ready-made cutoff.

Results differ across tasks. Short text and clear labels fare better than long documents or decisions requiring detailed business context. Kumar shares code and public cases, but reports the production results himself. This supports a selective filter, not a promise that a confident answer is correct.

Key takeaways

  1. Try the comparison on your own task before replacing the classifier you already use.
  2. Possible filter cutoffs sit at both ends: test very low scores as well as very high ones.
  3. Leave the uncertain cases on the more capable route rather than sending every decision through Jev.

Kumar reports the pipeline numbers himself. Code and public cases are available, while private production examples cannot be independently checked from that repository.

amankumar.ai · Original published

Read the original guide Opens the author’s site in a new tab.

Keep this for later

Sign in to bookmark experiments, guides and videos, and keep notes only you can see.

Continue to sign in

We’ll bring you back to this listing.