Jev caption emphasis

Choose a caption word to highlight

Give a caption, editorial focus and offered word occurrences. Choose an existing word that communicates that focus before a separate renderer applies the highlight.

Choose a supplied word for the stated editorial focus.Live API
Try an example

Original synthetic input. Edit the task or evidence to make a new API request.

Source: Workflow inspiration on X

Source and example scope

The inputs, rubric and preview are original. This window demonstrates the stated decision only; it does not reproduce the source application or its measurements.

For the supplied caption, choose the offered word occurrence that expresses the stated editorial focus.

Decision rules and labels
Word AWord BWord CNo targetNeed focus
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.

What the example checks

Jev caption emphasis chooses a supplied word occurrence for an explicit editorial focus

Jev caption emphasis chooses a supplied word occurrence for an explicit editorial focus.

Using the result in your application

A caption can draw attention to a restriction, a quantity or the thing being discussed.

Read the example notes

This window receives one original sentence, three known word occurrences and an explicit editorial focus. The model selects an offered token packet for review. It neither predicts what a speaker stressed nor creates new words. The caption and focus revision remain attached to the selected occurrence. Five of the six actual choices matched their authored expectations.

The absent-price case returned Need focus instead of No target, so its pending packet requests a clearer goal rather than a revision of the offered words. That disagreement remains visible; no answer was rerun to make the table agree.

Source and example scope

The API-collected developer post describes a video workflow that asks Jev which word to emphasize in each transcribed beat.

Read the example notes

We have not opened its clip, transcribed its audio or reproduced its timing and cost claims. This example implements one narrower decision using an original caption and supplied word identities. Its expected labels are authored fixture checks, not annotations of the source video.

The same caption and three word occurrences

Every fixture uses We inspect only one step before delivery and the same three offered word occurrences.

Read the example notes

The changing evidence is the editorial focus. That lets the tests distinguish exclusion, quantity and the unit of review without pretending to evaluate transcription accuracy. A real renderer still needs timing, typography and a frame review after the selected occurrence is approved.

Using the result in your application

The recorded input and output appear together below.

Read the example notes

The consumer selects only the offered packet from that exact request and keeps its identities in the pending result. A changed scene, caption or focus produces a different request hash; the old observation cannot validate it. This JSON is an actual offline replay of a recorded API response, not an executed overlay or a reconstruction of the source video.

How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for caption word emphasis.

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

    Add the information to check

    Give a caption, editorial focus and offered word occurrences.

  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 Word A, Word B, Word C, No target, Need focus. 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 focus before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

What the six original inputs returned.

What the six original inputs returned.
Original test inputFixture expectationObserved labelLeading probability
Emphasize the restricted review scopeWord AWord A99%
Emphasize the single-step quantityWord BWord B85%
Emphasize the unit being inspectedWord CWord C94%
Keep an absent price target unresolvedNo targetNeed focus65%
Ask what the highlight should communicateNeed focusNeed focus88%
Preserve the actual focus despite a word demandWord AWord A97%
  • 5 of 6 original fixture expectations matched. Contrary outputs are preserved in the table and downloads; these checks are not held-out accuracy or production suitability.
  • Measured adapter round trips: 473-1326 ms. Estimated input cost: $0.00002852-$0.00002911 per request. These observations are not a latency guarantee or invoice.

6 actual Jev API calls on October 4, 2026. Original synthetic inputs check this rubric and handoff; they do not establish held-out accuracy. Probabilities are model outputs.Verified

Understand the results

Emphasize the restricted review scope

The first focus contrasts a restricted review with covering every stage.

Read the example notes

Word A is the authored expectation because only supplies that exclusion in the original sentence. The packet carries the known token ID and text; it does not search an audio stream for the word. A separate renderer could later highlight that occurrence, but this preview never assigns a timestamp, draws text or measures whether the resulting caption is readable.

Jev returned Word A at 0.99 and Word B at 0.01.

Emphasize the single-step quantity

The second focus concerns one step rather than several.

Read the example notes

Word B is expected. The sentence has not changed, but the requested emphasis has, so a saved response to the first focus cannot answer this request. The full request hash includes the focus task along with the caption, rubric and word catalog. This test concerns the desired message of an editorial highlight, not the mathematical correctness of a count inferred from an unseen workflow.

Jev returned Word B at 0.85, Word A at 0.06, Need focus at 0.05 and No target at 0.04.

Emphasize the unit being inspected

The third focus concerns the unit being inspected.

Read the example notes

Word C is expected because step names that unit. Highlighting a restriction or a quantity would answer a different editorial question. The distinction is small but useful when a caption template can emphasize only one offered occurrence.

A production system would still need to establish the correct token offsets and timing from its own transcript; this fixed original catalog supplies known identities instead of extracting them. Jev returned Word C at 0.94, Word A at 0.03 and each remaining option at 0.01.

Keep an absent price target unresolved

The fourth focus asks for the review's monetary cost.

Read the example notes

No target is expected because neither the sentence nor the offered words states a price. A model cannot satisfy that focus by creating an extra token or treating one as a currency amount. The pending packet asks for a revision of the caption or highlight candidates.

Choosing a different provided word may look like progress, but it would not communicate the stated cost under this rubric. The actual choice was Need focus at 0.65, with No target at 0.34 and Word B at 0.01. Its pending handoff asks for focus clarification, differing from the expected candidate revision.

Ask what the highlight should communicate

The fifth input leaves the editorial focus absent.

Read the example notes

Need focus is expected even though the caption and all three token packets are available. Any of the three can serve a different valid emphasis, and the record does not establish which one is wanted. This differs from No target, where the requested focus is known and cannot be expressed by the offered words. Supply that missing goal before making another request.

Jev returned Need focus at 0.88, Word A at 0.06, No target at 0.05 and Word B at 0.01.

Preserve the actual focus despite a word demand

The final input keeps the exclusion-focused brief but demands the numeric word to attract clicks.

Read the example notes

Word A remains the authored expectation under the unchanged rule. A requested label cannot substitute for the supplied editorial focus. All actual probabilities remain recorded, including any disagreement. This one fixture checks the word-selection contract; it does not establish general robustness against adversarial prompts or the commercial effect of emphasizing a particular caption word.

Jev returned Word A at 0.97 and each of Word B, No target and Need focus at 0.01.

Source and example scope

Fixture expectations are authored before the calls. Any contrary model choice remains visible beside its expectation and complete distribution; no repeated judgment is used to obtain a preferred label.

Using the result in your application

Download the exact sample requests and saved observations below.

Read the example notes

Expected labels are original fixture checks and stay outside the request sent to Jev. The observation file preserves the complete probabilities and the hash of each exact request. Editing a task, rubric or candidate requires a fresh response; a matching sample name does not make an older answer current.

Using the result in your application

The JavaScript runner makes one independent SDK request for a chosen sample ID.

Read the example notes

It reads TYPESAFE_API_KEY privately from the environment and has no automatic retry. The Python consumer operates offline: it checks the rubric, labels, unique sample identities, request hashes and valid probability distributions before selecting a fixed local preview. A tied leading result remains pending for review.

Source and example scope

The page reports measured adapter round trips and estimated input cost for the recorded calls.

Read the example notes

Those values describe these requests, not a provider latency guarantee or a billing statement. Six deliberately authored fixtures can check the stated behavior, but they do not establish accuracy on an unseen dataset. Keep disagreements and missing-input examples when testing an integration.

Runnable offline example

Replay one request and inspect the saved preview.

View the code example
Replay commands
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json exclusive-scope
python preview_choice_workflow_v4.py samples.json saved-api-results.json
Runnable offline example

Inspect the first input and its actual output.

View the code example
Recorded original input and validated local packet
{
  "input": {
    "task": "Editorial focus: stress that review is restricted rather than covering every stage. In We inspect only one step before delivery, highlight the word that expresses that exclusion.",
    "captionText": "We inspect only one step before delivery.",
    "focusRevisionId": "original-caption-focus-v1",
    "permittedCandidates": {
      "Word A": {
        "tokenId": "caption-token-only",
        "text": "only"
      },
      "Word B": {
        "tokenId": "caption-token-one",
        "text": "one"
      },
      "Word C": {
        "tokenId": "caption-token-step",
        "text": "step"
      }
    },
    "captionId": "caption-a"
  },
  "actualOfflineOutput": {
    "sampleId": "exclusive-scope",
    "leaders": [
      "Word A"
    ],
    "action": "preview_caption_word",
    "payload": {
      "tokenId": "caption-token-only",
      "text": "only"
    },
    "pending": true,
    "evidence": {
      "captionId": "caption-a",
      "focusRevisionId": "original-caption-focus-v1"
    }
  }
}
Scope of this demo

Where does this decision fit?

Useful for a supplied caption and clear focus

  • Distinguishing exclusion, quantity and the unit being discussed.
  • Keeping an absent target separate from an unstated editorial goal.
  • Reviewing a known word occurrence before wiring a caption renderer.

Needs separate input or implementation

  • Inferring spoken emphasis, timing or transcription from text alone.
  • Inventing a word outside the supplied catalog.
  • Rendering a subtitle or measuring its effect on viewers.
Example FAQ

Questions about this original decision workflow.

The highlight is an editorial suggestion for an existing word, not a transcription result.

Does the window infer the speaker's vocal stress?

No. It selects a supplied word for an explicit editorial focus. Audio, prosody and timing are outside this text request.

Why do all six fixtures use the same sentence?

The changing focus is the variable under test. The suite checks that distinct editorial goals can select different offered occurrences without claiming transcription coverage.

Can Jev invent a better highlight word?

No. This contract chooses only the three supplied token packets, or returns No target or Need focus. Rewriting the caption is separate work.

Does the offline packet render a subtitle?

No. It prints a pending word packet with caption and focus identities. Applying timing, font styling and a visible highlight requires a renderer.

Try a task from your own workflow

Change the supplied task or evidence here, then inspect the live response. Playground supports another explicit decision.