Jev event location attribution

Find the place attached to a reported event

Provide the passage, specified event and candidate places. Separate where the event occurred from printing and archive locations, preserving multiple sites or an unresolved reference.

event location attributionLive API
Try an example

The passage attaches the sighting to Reed Marsh; Northport identifies the newspaper's printing place.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original text exercise adapts the narrow location-screening question described in the cited author account. The English passages, candidate names and fallback rules are ours. It does not reproduce the upstream research pipeline, geocode places or verify historical events.

Identify consistent locations of the specified event from the passage.

Decision rules and labels
ABCMultipleOutsideUnresolved
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 passage can name the place where an event occurred, where a report was printed and where a copy was filed. The input names one event and three candidate places. This decision follows the relationship in the text instead of choosing the first place name.

Multiple preserves an event that actually spans several places, even if some are absent from the candidates. Two incompatible accounts of a single location instead need Unresolved. Outside means that the text gives one clear place but the supplied choices omit it. A reference such as here needs an explicit anchor in the original account.

The cited author describes asking Jev where archival animal mentions are located before a later reading stage. This text-only exercise supplies its own English passages, choices and fallback rules. It does not reproduce that pipeline, inspect original scans or confirm historical findings.

This original text exercise adapts the narrow location-screening question described in the cited author account. The English passages, candidate names and fallback rules are ours. It does not reproduce the upstream research pipeline, geocode places or verify historical events.

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 event location in text.

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

    Add the information to check

    Provide the passage, specified event and candidate places.

  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 A, B, C, Multiple, Outside. 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
Event and printing location differA100%
Archive label differs from the eventB100%
A supplied anchor for hereC100%
One survey spans two sitesMultiple93.0%
Explicit place absent from the candidatesOutside100%
Here without an original reference pointUnresolved91.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

Event location in text: 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

  • Separating an event location from publication metadata
  • Screening place attribution before a human reviews an archive record
  • Keeping missing reference points and incomplete candidate lists visible

Outside this demonstration

  • Generating coordinates or resolving historical place-name aliases
  • Confirming whether an event or transcription is true
  • Searching an archive or extracting every location from a document
Example FAQ

Using this example

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

Does the first place name identify where the event occurred?

No. A dateline, printer's address or archive folder can name another place. Supply the event and the full passage so the decision can follow the stated relationship.

When is here enough to choose a place?

Only when the supplied text anchors it to the original speaker or writer's location. A later reprint's location does not supply that missing reference point.

How are Multiple and Unresolved different?

Multiple is the expected label when one event explicitly spans several places. Unresolved preserves conflicting alternatives or missing context. The rule does not turn disagreement into evidence that the event happened in both places.

Can this geocode the result?

No. It selects from the place candidates you supply. A separate georeferencing process must resolve real-world identity, coordinates and uncertainty.

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.