Jev entity attribute attribution

Check which entity a stated attribute belongs to

Provide the note, target entity and proposed attribute. Compare supported ownership with a nearby entity's value, an unstated property or an ambiguous reference.

entity attribute attributionLive API
Try an example

The explicit assignment points to Birch.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the source application, verify reported outcomes, or perform an external action.

Does the proposed attribute belong to the named target according to the note?

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

This example tests attribution rather than word matching. The same input can mention several devices or plans, and each attribute must stay attached to the correct entity.

The source post reports one contextual classification failure in a model comparison. This page uses new fictional device and subscription examples; it does not reproduce that comparison or rank models. Explicit relationship chains are allowed, while missing links stay Unstated.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the source application, verify reported outcomes, or perform an external action.

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 entity attribute ownership.

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

    Add the information to check

    Provide the note, target entity and proposed attribute.

  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 Supported, Contradicted, Unstated, Ambiguous. 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 Ambiguous 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
Assigned deviceSupported100%
Nearby attributeContradicted100%
No assignmentUnstated97.0%
Unresolved personAmbiguous78.0%
Direct propertySupported100%
Different propertyUnstated98.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

Entity attribute ownership: 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 entity-property labels before adding them to a search index
  • Checking whether neighboring records contaminated an extraction
  • Testing explicit relationship chains with fictional records

Outside this demonstration

  • Resolving real identities without supplied evidence
  • Completing a knowledge graph from outside knowledge
  • Benchmarking one model against another
Example FAQ

Using this example

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

Is a related word enough to mark Supported?

No. The note must connect the property to the named target. A display type mentioned for another laptop does not establish the target laptop's display.

How does Unstated differ from Contradicted?

Unstated means the required relationship or property is missing. Contradicted requires an explicit incompatible value for that same property.

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.