Jev date role classification

Identify the role of a date in a document

Show the marked date and surrounding text. Distinguish a creation or issue date from a covered period and an explicit revision date.

Label the date's role before storing it.Live API
Try an example

Original synthetic input. Edit the task or evidence to make a new API request.

Source: Workflow inspiration on X

Source and example scope

The inputs, rubric and preview are original. This window demonstrates the stated decision only; it does not reproduce the source application or its measurements.

Classify the marked date from its surrounding document text.

Decision rules and labels
Creation or issuePeriod coveredRevisionNeed more context
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.

What the example checks

Creation date versus the period described

Jev date role classification distinguishes when a document was produced from the period its contents describe.

Coverage year differs from the creation header

A budget can mention its coverage year on every page while its creation header names the previous year.

Read the example notes

A classifier that treats the most prominent year as the creation date loses that distinction. This example asks Jev to label the role of one marked date using the supplied surrounding text. It offers Creation or issue, Period covered, Revision and Need more context. The marked value is already provided; the model is not asked to find every date in a file.

Source and example scope

The attributed source describes this distinction in a document-classification workflow and reports a comparison between models.

Read the example notes

Our original demonstration tests the date-role question with six synthetic excerpts. It does not reproduce that comparison, process the author's files or decide whether any real document should be public. W3C DCAT separates issuance and modification metadata; those distinct fields informed the cases where a creation header and a later update both appear.

Using the result in your application

Role classification belongs before a downstream metadata assignment.

Read the example notes

A document parser still needs to locate the correct field, preserve its evidence and validate the extracted date format. Code should own date parsing and calendar comparisons. The local output here records a pending role label only. It writes no metadata, uploads no document and changes no sharing permission. When the supplied text conflicts, the unresolved label keeps the uncertainty attached to the input.

Using the result in your application

Each saved output includes the marked occurrence ID and value from its exact request, so two dates in one document cannot silently share a result.

Read the example notes

The title-only case also shows why that trace matters: its returned label disagreed with our expectation, and the pending packet preserves both the specific occurrence and the recorded distribution for review.

How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for document date roles.

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

    Add the information to check

    Show the marked date and surrounding text.

  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 Creation or issue, Period covered, Revision, Need more context. 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 Need more context before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

What the six original inputs returned.

What the six original inputs returned.
Original test inputFixture expectationObserved labelLeading probability
Created before the budget yearCreation or issueCreation or issue100%
Budget coverage yearPeriod coveredPeriod covered100%
Updated headerRevisionRevision100%
Title without a date roleNeed more contextPeriod covered84%
Conflicting captionNeed more contextNeed more context100%
Instruction inside the documentCreation or issueCreation or issue97%
  • 5 of 6 original fixture expectations matched. Contrary outputs are preserved in the table and downloads; these checks are not held-out accuracy or production suitability.
  • Measured adapter round trips: 487-1209 ms. Estimated input cost: $0.00002419-$0.00002512 per request. These observations are not a latency guarantee or invoice.

6 actual Jev API calls on October 3, 2026. Original synthetic inputs check this rubric and handoff; they do not establish held-out accuracy. Probabilities are model outputs.Verified

Understand the results

Created before the budget year

The first budget excerpt states a creation date in December 2025 and names Budget 2026 as its title.

Read the example notes

The marked value comes from the creation header. This fixture tests whether the model follows the stated role rather than the repeated coverage year. It does not claim that every budget was created in the preceding year. The result concerns the exact supplied header; a real file needs its own recorded evidence.

Budget coverage year

The second budget case keeps the same creation header but marks the year inside an explicit coverage sentence.

Read the example notes

Changing the marked occurrence changes the question even when the document title is unchanged. Period covered is an authored expectation about that occurrence. The demo does not calculate the length of the reporting period or infer accounting dates. The full request preserves which words were marked so the output can be reproduced.

Source and example scope

The handbook contains both a creation header and a change log.

Read the example notes

Its marked September value belongs to the update entry. A Revision label is a semantic role, not proof that the handbook is current or that the change was approved. A downstream metadata tool could attach that label to an extracted field after validating the source. This demonstration stops at a local preview and keeps the earlier creation value in the supplied evidence.

Using the result in your application

The title-only case supplies Planning 2026 without a creation header, coverage statement or change log.

Read the example notes

We expected Need more context. The recorded API response instead selected Period covered with probability 0.84; Need more context received 0.16. That is a disagreement with this rubric, not a verified coverage field. The pending output retains title-year as the occurrence ID and 2026 as its value. Add an explicit statement to make a new request, or ask a reviewer before assigning this field.

Source and example scope

The conflicting captions deliberately assign two roles to the same marked value.

Read the example notes

Neither caption is prioritized, and no separate header resolves their disagreement. The Need more context outcome preserves that conflict. It does not mark the whole document false or reject every date in it. A useful integration would ask for the relevant header or an authoritative metadata record before storing a creation or revision value.

Instruction inside the document

The final excerpt pairs an issuance header with an instruction-looking sentence in its body.

Read the example notes

Jev returned Creation or issue at 0.97 for this exact request, which matched the authored expectation. The consumer retained issuance-header and October 2, 2025 from the same request alongside that label. This observation concerns one supplied sentence; it does not establish resistance to other prompt injections. The local packet remains pending and performs no metadata write.

Source and example scope

Fixture expectations are authored before the calls. Any contrary model choice remains visible beside its expectation and complete distribution; no repeated judgment is used to obtain a preferred label.

Using the result in your application

Download the exact sample requests and saved observations below.

Read the example notes

Expected labels are original fixture checks and stay outside the request sent to Jev. The observation file preserves the complete probabilities and the hash of each exact request. Editing a task, rubric or candidate requires a fresh response; a matching sample name does not make an older answer current.

Using the result in your application

The JavaScript runner makes one independent SDK request for a chosen sample ID.

Read the example notes

It reads TYPESAFE_API_KEY privately from the environment and has no automatic retry. The Python consumer operates offline: it checks the rubric, labels, unique sample identities, request hashes and valid probability distributions before selecting a fixed local preview. A tied leading result remains pending for review.

Source and example scope

The page reports measured adapter round trips and estimated input cost for the recorded calls.

Read the example notes

Those values describe these requests, not a provider latency guarantee or a billing statement. Six deliberately authored fixtures can check the stated behavior, but they do not establish accuracy on an unseen dataset. Keep disagreements and missing-input examples when testing an integration.

Runnable offline example

Replay one request and inspect the saved preview.

View the code example
Replay commands
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json created-before-budget
python preview_choice_workflow_v4.py samples.json saved-api-results.json
Scope of this demo

Where does this decision fit?

Useful before metadata assignment

  • Distinguishing a budget coverage year from an explicit creation header.
  • Recognizing a marked date in a change-log entry.
  • Keeping absent or conflicting date-role evidence unresolved.

Needs another implementation

  • Extracting every date from a PDF or scanning an original file.
  • Calculating periods or comparing timestamps.
  • Changing document sharing or deciding legal validity.
Example FAQ

Questions about document date roles.

Keep the marked occurrence, its role and the source text together.

Does this extract dates from a PDF?

No. Each input supplies a marked date and its surrounding text. A parser or extraction step must provide that evidence before this role classification runs.

Are issuance and creation always the same field?

No. This deliberately broad output groups creation, preparation and issuance for a local preview. A system that needs separate fields should define separate outcomes and test the changed rubric.

Can a year in the title become a creation date?

The title alone does not establish that role under this rubric. Add an explicit creation header or other relevant evidence before assigning the value.

Does the output decide whether a document is public?

No. A date role carries no permission or legal-validity decision. Sharing and metadata writes need separate authenticated checks.

Try a task from your own workflow

Change the supplied task or evidence here, then inspect the live response. Playground supports another explicit decision.