Jev focused field value

Choose the supplied value a form field needs

Give the focused field, user request and candidate text spans. Select the shortest complete requested value, leaving ambiguity or an absent value unmatched.

focused field valueLive API
Try an example

The field needs the place name rather than the instruction.

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 shortest complete value explicitly requested for the focused field.

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

Typing the entire user instruction into a field is a boundary error. This request selects a value already present in the candidates, using the focused field label to distinguish it from other text in the same request.

The output is a candidate label, so it cannot correct spelling or fill gaps. The application must resolve that label to the exact stored span and verify any actual input afterward. This page does neither device input nor readback.

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 checking a code change and reviewing a flagged line
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 focused field values.

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

    Add the information to check

    Give the focused field, user 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
Place searchB100%
Document titleA100%
Full search phraseC99.0%
Two values in requestB100%
Missing complete valueNone90.0%
Unknown focusA77.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. 5 of 6 results matched the authored fixture expectations. For Unknown focus, the expectation was None; the observed choice was A.Verified

Understand the results

Focused field values: 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 candidate text for a focused field
  • Separating several values in one request
  • Keeping incomplete candidate sets unresolved

Outside this demonstration

  • Generating missing field values
  • Typing into a browser or device
  • Verifying form submission
Example FAQ

Using this example

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

Can the model combine two partial candidates?

No. This contract selects one existing span. Supply a complete candidate or keep None; joining text requires a different explicit step.

Does choosing a value prove it was entered?

No. Only a later independent field readback could confirm that. This demo displays the selection.

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.