Jev catalog entity name

Select a complete entity name for a catalog lookup

Give a lookup request and candidate text spans. Select the shortest complete work or person name, leaving ambiguous or incomplete candidates unmatched.

catalog entity nameLive API
Try an example

The complete supplied title is shorter than the command.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original text demonstration adapts a decision in a repository linked by the cited X post. The examples and explicit uncertainty outcomes are ours. The post is a directory reference, not proof that its author built every linked project. No third-party benchmark, business outcome or external action is reproduced.

Choose A, B or C containing the complete work or person name requested for catalog lookup, without surrounding search commands or unrelated qualifiers.

Decision rules and labels
ABCNone
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 search phrase and a catalog key serve different purposes. Director interviews belongs in a research query, but a film catalog may need only the film’s complete title. The requested lookup target must be explicit.

The model chooses from supplied strings. It does not check a catalog, disambiguate real people using hidden information or guarantee a match. Return None when the candidates omit the complete name.

This original text demonstration adapts a decision in a repository linked by the cited X post. The examples and explicit uncertainty outcomes are ours. The post is a directory reference, not proof that its author built every linked project. No third-party benchmark, business outcome or external action is reproduced.

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 catalog lookup names.

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

    Add the information to check

    Give a lookup request and candidate text spans.

  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 A, B, C, None. 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 uncertain or unexpected results 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
Film titleA100%
Person nameB100%
Title contains common wordsC100%
Broader questionB100%
Only fragmentsNone95.0%
Ambiguous targetNone79.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

Catalog lookup names: 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

  • Selecting known title candidates for a catalog
  • Preserving complete multiword names
  • Separating lookup keys from research phrases

Outside this demonstration

  • External identity resolution
  • Creating missing names
  • Guaranteeing a catalog match
Example FAQ

Using this example

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

How is this different from query selection?

Query selection retains topic relationships for a search. This task produces the complete entity-name candidate for a catalog that expects a name or title.

Should articles such as The be removed?

Not automatically. Preserve them when the input identifies them as part of the full title.

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.