Triple

T16078781
Position Surface form Disambiguated ID Type / Status
Subject California State Route 237 E390043 entity
Predicate tollFeature P78341 FINISHED
Object high-occupancy toll lanes 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: high-occupancy toll lanes | Statement: [California State Route 237, tollFeature, high-occupancy toll lanes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tollFeature
Context triple: [California State Route 237, tollFeature, high-occupancy toll lanes]
  • A. tollRoadOf
    Indicates that a road segment is a toll road belonging to or associated with a particular roadway, route, or transportation network.
  • B. tollingType
    Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
  • C. isTollFacilityOf
    Indicates that a facility (such as a toll booth, plaza, or gantry) is part of, or used to collect tolls for, a specific toll road or toll transportation infrastructure.
  • D. tollIntroduced
    Indicates that a toll was established or put into effect for using a particular route, facility, or service.
  • E. tollComponent chosen
    Indicates a relationship where one entity functions as a toll-related part, feature, or element of another entity or system.
  • 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_69d86daf32ec8190a8c0466c8f49c3c0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1ff63edb0819092cbb671967bbdcd completed April 17, 2026, 9:37 a.m.
PD Predicate disambiguation batch_69e1827ad7c88190b867da511cbfb7fa completed April 17, 2026, 12:44 a.m.
Created at: April 10, 2026, 4:57 a.m.