Jev analytics concept route

Match an analytics question to the right business concept

Provide a question and the complete field definitions for your concept catalog. See which concept covers it, whether several are needed, or which meaning needs clarification.

analytics concept routeLive API
Try an example

The grouping field and requested tire-width measure both belong to Rear.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original text exercise adapts the visible concept-routing task in the cited CSV-ontology video. Its small catalog, field assignments, examples and fallback policy are ours. The video shows UI routes, not the exact prompt, schema, database truth or this implementation.

Use question meaning and the complete concept catalog.

Decision rules and labels
RearOffroadElectricMultiple conceptsNo conceptClarify
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

A concept here is a named group of fields in the supplied catalog. Read the requested measure, grouping and filters, then check which group defines all of them. A concept name by itself is not evidence that it contains a needed field.

The proposed route can narrow the schema context passed to a later SQL stage. It does not establish that records exist, that two concepts can be joined or that a query is authorized. Multiple concepts preserves a request that no single group covers; it does not design the join.

The source video visibly routes questions through named concepts such as Offroad, Rear and Electric. These examples use an original, smaller catalog. Its field assignments and fallback labels are authored rules, not a reconstruction of the source application.

This original text exercise adapts the visible concept-routing task in the cited CSV-ontology video. Its small catalog, field assignments, examples and fallback policy are ours. The video shows UI routes, not the exact prompt, schema, database truth or this implementation.

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 analytics concept routing.

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

    Add the information to check

    Provide a question and the complete field definitions for your concept catalog.

  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 Rear, Offroad, Electric, Multiple concepts, No concept. 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 uncertain or unexpected results 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
Rear-wheel groupingRear100%
Off-road use by terrainOffroad99.0%
Battery-charging fieldsElectric90.0%
Fields from two conceptsMultiple concepts100%
A field outside the catalogNo concept99.0%
An undefined comparisonClarify98.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

Analytics concept routing: 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

  • Selecting relevant schema context for an analytics question
  • Spotting requests that need fields from more than one concept
  • Keeping an undefined business term out of a forced route

Outside this demonstration

  • Discovering a schema or building a business ontology
  • Generating joins, writing SQL or executing a query
  • Confirming that data or query results are correct
Example FAQ

Using this example

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

Does a concept route mean the question can be answered?

It means the supplied field definitions cover the request under this rule. Values may still be absent, permissions may prevent access, or a later query may return no records. Those outcomes need separate evidence.

Why not choose whichever concept covers the most fields?

A partial route can lose a filter or measure. The contract expects Multiple concepts when the catalog covers everything only across groups. It expects No concept when a required field is outside the complete catalog.

What does the source video establish?

It shows named routes beside questions and result tables. It does not expose the exact routing prompt or prove database correctness. Our catalog, six inputs and single-concept coverage policy are independent examples.

Is this choosing a database engine?

No. Rear and Electric name business-field groups in the input. This decision does not select a database product, estimate query cost or compare execution engines.

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.