Who it is forA data analyst with a spreadsheet or DataFrame of tickets, records, or messages that need consistent labels.
The problemLabeling rows by hand takes time, and rule-based labels miss meaning in free text.
The outcomeA table with a new label column, plus cached answers that can be reused on later runs.
What you need first
- Access to Jev through the TypeSafe early-access entry point at typesafe.ai
- A small labeled sample of your own data to check Jev answers before relying on them
Steps
- Open the hunch repository at github.com/steven-shoemaker/hunch and follow its installation section.
- Define the closed set of labels your rows should receive.
- Run the classify or score verb over each row of your DataFrame.
- Join the cached answers back to the table and keep the thresholds and actions in your own code.
- Review a random sample of about twenty labeled rows by hand.
Prompt for your agent
Using the steven-shoemaker/hunch Python library, classify each row of <dataset path> into the closed-set labels <label list>. Return the labeled table and a count per label. Verify twenty random rows by hand before reporting results.
Caveat. Jev returns schema-valid answers, which are not guaranteed correct, so calibrate on a hand-labeled sample first.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page