Triple

T13612244
Position Surface form Disambiguated ID Type / Status
Subject U.S. Routes in Ventura County E325218 entity
Predicate primaryCorridorFor P46518 FINISHED
Object regional travel in Ventura County LITERAL FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: regional travel in Ventura County | Statement: [U.S. Routes in Ventura County, primaryCorridorFor, regional travel in Ventura County]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryCorridorFor
Context triple: [U.S. Routes in Ventura County, primaryCorridorFor, regional travel in Ventura County]
  • A. primaryCorridorServed chosen
    Indicates that a corridor is the main route or pathway served by a given service, facility, or entity.
  • B. primaryRoute
    Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
  • C. primaryHubFor
    Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
  • D. primaryDirection
    Indicates the main or dominant directional orientation associated with an entity or relation.
  • E. primaryFor
    Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
  • F. None of above.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69d8076aae28819092cf636190ee5529 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbbb9ee3f081909056dc1a92c40b7a completed April 12, 2026, 3:34 p.m.
PD Predicate disambiguation batch_69dbae1b3ee481909bd43ded6227a3e5 completed April 12, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:50 p.m.