Jev sarcasm cue classification

Read a sarcastic cue in its event context

Provide the remark and the event it describes. Compare ironic praise of a negative event with literal praise or criticism, preserving ambiguous intent rather than claiming to know the speaker's thoughts.

Is the praise literal or ironic?Live API
Try an example

Original input for the Sarcasm cue 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 remark in its stated event.

Decision rules and labels
Sarcasm cueLiteral praiseLiteral criticismAmbiguousNeed 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

A positive word can describe a negative experience.

The word wonderful does not settle the label. The first example supplies a failed operation alongside apparent praise, so the contradiction becomes evidence for an ironic reading. The successful export supplies the opposite context.

Literal criticism is a separate outcome. Calling a failure frustrating does not require an ironic interpretation. The ambiguous example preserves uncertainty rather than attributing an intention that the text never establishes.

The source post reports difficulty with sarcasm classification. These authored cases make that limitation testable; they do not claim to reproduce its dataset or improve its accuracy.

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 sarcasm context check.

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

    Add the information to check

    Provide the remark and the event it describes.

  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 Sarcasm cue, Literal praise, Literal criticism, Ambiguous, 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 Ambiguous, 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
Crash called wonderfulSarcasm cue100%
Fast exportLiteral praise100%
Direct complaintLiteral criticism100%
No stated intentAmbiguous76.0%
Quoted praise used ironicallySarcasm cue100%
Missing remarkNeed 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

  • Reviewing literal and ironic feedback in a stated context
  • Finding examples for a human annotation session
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Inferring someone’s private intention from a detached sentence
  • Estimating sentiment accuracy from six fixtures
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about sarcasm cue classification.

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

Is sarcasm the same as negative sentiment?

No. A direct negative complaint belongs under Literal criticism. Sarcasm cue requires apparent praise that conflicts with a supplied negative event.

Can the same remark change labels?

Yes. Great, another update may be sincere after a useful release or ironic after a repeated disruption. Keep the event in the input and preserve ambiguous wording.

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 sarcasm cue classification input

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