Jev discussion argument classifier

Identify the argument in a discussion comment

Provide a comment and its thread context. Distinguish criticism of evidence, concern about hype and an accusation of promotion without endorsing any of those claims.

discussion argument classifierLive API
Try an example

The objection identifies a comparison problem.

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.

Classify the comment in its supplied thread context: Evidence criticism questions a method, sample or inference; Hype concern questions exaggerated expectations; Marketing accusation alleges undisclosed promotion or coordinated support; Other makes a different clear point; Review applies when the main contribution is missing or two categories are equally central.

Decision rules and labels
Evidence criticismHype concernMarketing accusationOtherReview
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

The thread and parent comment can change what a short reply means. Supply them when the reply refers to an earlier claim.

Marketing accusation records what the writer alleges. It does not identify bots, prove sponsorship or evaluate the writer.

The source-linked sorter lets readers define comment buckets. This page uses an original fixed taxonomy and displays one proposed label.

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 discussion argument types.

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

    Add the information to check

    Provide a comment and its thread context.

  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 Evidence criticism, Hype concern, Marketing accusation, Other, 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
Missing controlEvidence criticism100%
Inflated promiseHype concern99.0%
Promotion allegationMarketing accusation100%
Practical questionOther99.0%
Unresolved referenceReview85.0%
Two central objectionsReview96.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

Discussion argument types: 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

  • Reviewing the kinds of objections in a product discussion.
  • Testing whether a comment taxonomy keeps accusations separate from evidence.
  • Separating methodological objections from promotional allegations in an annotation set.

Outside this demonstration

  • Determining whether an allegation is true.
  • Moderating users or inferring their motives from a label.
Example FAQ

Using this example

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

Is this a sentiment score?

No. Several categories can contain positive or negative wording. The question concerns what the argument is doing.

What if a comment makes two arguments?

Choose Review when neither is dominant. Split the comment into separate units only if your downstream task needs argument-level annotation.

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.