Jev discussion topic relationship

Compare the topics of two discussions

Supply summaries of both conversations. Compare the same topic, a narrower subtopic and connected or unrelated discussions before a separate summary or merge decision.

discussion topic relationshipLive API
Try an example

The second summary continues the same concrete issue.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original pair-comparison demo adapts the five relationship levels published in signal-summarizer, linked by the source post. It uses Choice labels instead of reproducing the upstream Score workflow and adds an explicit missing-summary outcome. No chat is merged.

Compare TARGET with CANDIDATE: Same for essentially the same concrete discussion or its direct continuation; Subtopic if one is a narrower example of the same concrete topic; Related for connected but distinct topics; Domain for only a broad-domain overlap; Unrelated for no meaningful subject relationship.

Decision rules and labels
SameSubtopicRelatedDomainUnrelatedUnclear
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 middle levels keep useful distinctions visible. Related discussions can inform one another without describing the same work; a subtopic is a concrete part or example of the broader conversation.

This page returns a label for one pair. It does not calculate a complete clustering solution, combine message history or write a merged summary. Those steps need application policy and additional evidence.

This original pair-comparison demo adapts the five relationship levels published in signal-summarizer, linked by the source post. It uses Choice labels instead of reproducing the upstream Score workflow and adds an explicit missing-summary outcome. No chat is merged.

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 topic relationships.

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

    Add the information to check

    Supply summaries of both conversations.

  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 Same, Subtopic, Related, Domain, Unrelated. 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 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
Direct continuationSame93.0%
Narrow exampleSubtopic99.0%
Connected but distinctRelated94.0%
Only broad domainUnrelated64.0%
No topic connectionUnrelated97.0%
Summary absentUnclear100%

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 Only broad domain, the expectation was Domain; the observed choice was Unrelated.Verified

Understand the results

Discussion topic relationships: 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 topic grouping candidates
  • Separating broad overlap from direct continuation
  • Keeping incomplete summaries unresolved

Outside this demonstration

  • Automatically merging conversations
  • Generating summaries
  • Inferring contents from short titles
Example FAQ

Using this example

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

Does Same automatically merge the threads?

No. The demo only labels a pair. A grouping application must decide how to handle message history, permissions and other related threads.

Why have both Domain and Related?

Domain captures a very broad overlap such as software development. Related requires a more specific connection while preserving distinct discussion goals.

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.