Jev SQL question match

Check whether a SQL query matches the analytics question

Compare a SELECT with the question, schema and metric definitions. Review filters, grouping and detail level for a semantic mismatch without executing the query or certifying its result.

SQL question matchLive API
Try an example

The query counts the requested records at the requested grouping.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original SQL-reading exercise adapts the relevance review in the linked Natural Language Data Analyst Agent. Queries and schemas are synthetic. The demo does not execute SQL, validate database permissions or reproduce that application’s thresholds.

Compare the SELECT with the question, schema and metric definitions: Match if its metric, filters, grouping, entities and detail level express the requested result; Mismatch for a material difference; Unclear if required meaning, schema or query behavior is missing.

Decision rules and labels
MatchMismatchUnclear
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

Syntax, safety and meaning are separate checks. A read-only, bounded query can still use the wrong aggregation or select a different population from the one requested.

The demo reads small SELECT statements with supplied schema assumptions. Complex joins, custom functions and unstated metric policies may require more context or a different validation tool.

This original SQL-reading exercise adapts the relevance review in the linked Natural Language Data Analyst Agent. Queries and schemas are synthetic. The demo does not execute SQL, validate database permissions or reproduce that application’s thresholds.

Illustration of checking a code change and reviewing a flagged line
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 sql question matching.

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

    Add the information to check

    Compare a SELECT with the question, schema and metric definitions.

  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 Match, Mismatch, Unclear. 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
Correct grouped countMatch100%
Wrong metricMismatch100%
Wrong populationMismatch100%
Grouping lostMismatch100%
Explicit all-time scopeMatch100%
Undefined active metricUnclear93.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

SQL question matching: 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 generated SELECT meaning
  • Comparing requested and actual aggregation
  • Keeping undefined metrics unresolved

Outside this demonstration

  • Executing database queries
  • Certifying SQL safety or permissions
  • Computing result correctness from absent data
Example FAQ

Using this example

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

Does Match mean the query is safe to execute?

No. Syntax checks, permissions, resource limits and execution approval are separate. This label concerns the requested meaning only.

Can SQL fill in a missing definition of active?

It can encode an assumption, but that does not make the assumption the user’s intent. Supply the agreed definition before judging the match.

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.