Jev comment topic relevance

Check whether a comment relates to an article

Provide the article's subject and a comment. Compare discussion of that topic with unrelated or unclear text, leaving spam and abuse to separate checks.

Does the comment belong to this topic?Live API
Try an example

The question concerns a step in the article’s task.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

The API-collected post links Jev Comment Triage. Its pinned documentation explains independent relevance, spam and abuse judgments. This page uses original synthetic comments and a bounded Choice rubric. It does not install the plugin, moderate a WordPress site or treat relevance as permission to publish.

Compare the comment with the supplied article.

Decision rules and labels
On topicOff topicUnclear relevance
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

An on-topic comment can still be spam.

The sales-pitch preset advertises a brake cable kit under a brake-adjustment article. The subject matches. A separate spam check may still flag the promotion, so On topic cannot substitute for a moderation decision.

Disagreement is another useful boundary. Suggesting a weekly inspection instead of a monthly one still addresses the article’s subject. The rule judges the relationship between texts, not whether the writer agrees with the author.

Include enough of the article to establish its topic. A bare “Amazing stuff!” does not make that relationship clear. The window returns a label and probabilities; it does not approve, hold or delete a WordPress comment.

The API-collected post links Jev Comment Triage. Its pinned documentation explains independent relevance, spam and abuse judgments. This page uses original synthetic comments and a bounded Choice rubric. It does not install the plugin, moderate a WordPress site or treat relevance as permission to publish.

Illustration of reviewing messages against supplied policy categories
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 comment topic relevance.

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

    Add the information to check

    Provide the article's subject and a comment.

  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 On topic, Off topic, Unclear relevance. 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 Unclear relevance 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
Related questionOn topic100%
Relevant sales pitchOn topic96.0%
Different subjectOff topic100%
DisagreementOn topic100%
Vague praiseUnclear relevance43.0%
No articleUnclear relevance88.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

Replay the saved synthetic requests to inspect each recorded decision

Replay the saved synthetic requests to inspect each recorded decision. Authored expectations and model disagreements remain available; these examples are not a production accuracy benchmark.

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

  • Separating topic relevance from spam risk
  • Reviewing disagreement without confusing it with irrelevance
  • Finding comments whose subject is unclear

Outside this demonstration

  • Publishing or deleting comments
  • Replacing spam and abuse checks
  • Inferring an article from a URL alone
Example FAQ

Questions about comment topic relevance.

Input scope and downstream handling determine what this judgment means.

Why is the sales pitch labeled On topic?

It concerns the same subject. This check deliberately does not decide whether the promotion is acceptable or unsolicited.

Does criticism make a comment Off topic?

No. A comment can criticize the article’s advice while directly discussing its subject.

Is the leading probability an accuracy measurement?

No. It is one value in the returned distribution over this request’s choices. The six synthetic fixtures have authored expectations; they do not measure production accuracy.

What happens on an API failure?

The window displays an error without a fresh judgment. An incomplete-input outcome describes the supplied evidence and is not used as a fallback for provider failure.

Try your own comment topic relevance input

Edit the input above, or open the Playground to explore another decision.