Jev book subject tagging

Check whether a book supports a subject tag

Give a proposed tag, its rule and a book description or excerpt. Compare substantive support with excluded content and a suggestive title that needs review.

book subject taggingLive API
Try an example

Both description and excerpt concern writing programs.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Evaluate the candidate book tag using its supplied inclusion and exclusion rule and the description or excerpt.

Decision rules and labels
SupportedExcludedReview
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

What the decision checks

A tag is a rule, not just a word. Include exclusions when a name has common metaphorical or adjacent meanings.

This one-tag Choice demo adapts a library-tagging pattern. It does not implement the source plugin’s multiple independent tag questions, thresholds or calibre integration.

Use original or permitted excerpts and review suggestions before updating a catalog. A short excerpt may not represent the entire book.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

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 book subject tagging.

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

    Add the information to check

    Give a proposed tag, its rule and a book description or excerpt.

  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 Supported, Excluded, Review. 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 Review 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
Practical programmingSupported100%
Career memoirExcluded100%
Ambiguous titleReview100%
Fictional mysterySupported99.0%
Different meaningExcluded100%
Conflicting metadataReview56.0%

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

Book subject tagging: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

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.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Testing a library tag definition against metadata.
  • Finding when a title-only record needs a description before tagging.
  • Separating literal subjects from metaphorical uses of a tag name.

Outside this demonstration

  • Automatically tagging a whole book from its title.
  • Replacing catalog review or claiming the original plugin’s results.
Example FAQ

Using this example

The input contract and these limits define what the result means.

Can several tags be supported?

Yes. This exercise checks one tag at a time. Separate subject and genre tags may both fit; a complete application needs its own multi-tag selection policy.

Are existing tags used as evidence?

Not in these samples. Reusing unverified tags can simply repeat an earlier classification mistake.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.