Jev product description category

Assign a product description to a supplied category

Read an original product description using a small catalog taxonomy. Distinguish hand tools, storage and stationery by stated purpose, preserving equally central mixed uses or missing details.

Which catalog category fits this description?Live API
Try an example

Original input for the Hand tool outcome. Edit the evidence to send a new request.

Source: Background discussion on X

Source and example scope

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

Classify the product’s described primary purpose.

Decision rules and labels
Hand toolStorageStationeryMixed productNeed evidence
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

Classify the product, not the nouns it contains.

Tool organizer contains tool, but its purpose is storage. The screwdriver and notebook supply clearer category boundaries, while the equal bundle shows why a mixed outcome is useful.

This task derives a category from a description. It differs from mapping an existing legacy label to a canonical ID: a legacy label may be absent, incorrect or too coarse.

The example is inspired by using Jev in a spreadsheet. It does not connect to Excel, inspect a real shop or overwrite catalog rows. The application should review uncertain items before persisting labels.

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

Illustration of one spreadsheet row producing two separate classification results
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for product category classification.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Read an original product description using a small catalog taxonomy.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Hand tool, Storage, Stationery, Mixed product, Need evidence. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Need evidence before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Small screwdriverHand tool100%
Parts organizerStorage100%
Paper notebookStationery100%
Equal bundleMixed product100%
Tool word in storage copyStorage100%
No product descriptionNeed evidence100%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Source and example scope

Compare each saved result with its authored expectation. A disagreement remains in the fixture review; the call is not repeated to obtain a preferred label.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Testing a small description-based catalog classifier
  • Reviewing misleading category keywords in product copy
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Inferring unavailable product specifications
  • Overwriting a catalog from six synthetic checks
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about product description category.

The rubric explains the decision; the application owns the next step.

Can a product belong to more than one category?

Yes. This rubric preserves an equally central combination as Mixed product. A real multi-label taxonomy needs a different contract instead of forcing every bundle into one category.

What if the catalog uses different categories?

Edit both the decision rule and the choice labels, then test representative rows from that taxonomy. The three authored categories are only a bounded example.

Does the leading probability measure production accuracy?

No. It is the model distribution for this one request. The six examples are functional checks with authored expectations, not a representative benchmark. Inspect disagreements and evaluate your own examples before using the label.

What happens when the API fails?

The window shows an error and supplies no fresh judgment. The downloadable runner sends one request without retries. Need evidence is a valid outcome about incomplete input; it does not stand in for a network or provider failure.

Try your own product description category input

Edit the evidence above or use the Playground to test another bounded question.