Jev data answer gap

Explain why a data question has no usable answer yet

Provide the question, catalog notes and query report. Distinguish a missing field, ambiguous request and empty row list from a valid answer such as a count of zero.

data answer gapLive API
Try an example

The requested fact is absent from the declared data scope, not absent only from a filtered result.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original report-reading exercise is inspired by the cited CSV-ontology video. The video shows interface messages, not verified database behavior. These synthetic inputs do not reproduce its implementation, authenticate its results or connect to a database.

Use the question, catalog notes and query report.

Decision rules and labels
Missing fieldNo matchesAmbiguous requestAvailableUnclear
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 input is a report about a data question, not a live database connection. A missing field may require a new data source, an ambiguous request needs a clearer definition, and a completed empty list may simply mean the filters matched nothing.

The result must be read in the context of the question. A count query returning zero has supplied an answer. This check does not verify that the SQL was correct or that the database contains every real-world record; the stated catalog and query status are evidence supplied by the caller.

This original report-reading exercise is inspired by the cited CSV-ontology video. The video shows interface messages, not verified database behavior. These synthetic inputs do not reproduce its implementation, authenticate its results or connect to a database.

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 data answer gaps.

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

    Add the information to check

    Provide the question, catalog notes and query report.

  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 Missing field, No matches, Ambiguous request, Available, 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 Missing field, No matches, Ambiguous request 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
The required fact is not storedMissing field100%
A supported query returns no vehiclesNo matches98.0%
Best has no agreed measureAmbiguous request100%
An answer is presentAvailable100%
Zero is the requested countAvailable95.0%
Execution outcome is unknownUnclear88.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

Data answer gaps: 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

  • Explaining distinct reasons an analytics question was not answered
  • Keeping an empty list separate from an unavailable metric
  • Recognizing zero counts as valid reported answers

Outside this demonstration

  • Executing or validating SQL
  • Certifying database completeness or result accuracy
  • Creating missing fields or collecting new data
Example FAQ

Using this example

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

Does No matches mean the data does not exist?

It means the supplied completed row-list query returned no qualifying records. The underlying fields may be available and other records may exist. Do not describe that outcome as a missing column or unavailable metric.

Why is a count of zero Available?

The question asks how many, and the report supplies that count. A zero value is different from having no report, an unavailable field or a request whose meaning has not been defined.

Does the source video prove the query results are correct?

No. It shows interface text describing a known data gap and a separate no-matching-records outcome. These original examples explain that distinction without verifying the source application or its data.

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.