Triple

T34281775
Position Surface form Disambiguated ID Type / Status
Subject I-394 (Minnesota) E879608 entity
Predicate hasHighOccupancyVehicleLanes P104384 FINISHED
Object yes 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: yes | Statement: [I-394 (Minnesota), hasHighOccupancyVehicleLanes, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHighOccupancyVehicleLanes
Context triple: [I-394 (Minnesota), hasHighOccupancyVehicleLanes, yes]
  • A. hasHighOccupancyTollLanes
    Indicates that a roadway or highway segment includes high-occupancy toll (HOT) lanes where vehicles meeting certain occupancy or payment conditions are allowed to travel.
  • B. hasCarpoolLanes chosen
    Indicates that a road, route, or transportation facility includes designated carpool (high-occupancy vehicle) lanes available for use.
  • C. hasDedicatedLanes
    Indicates that specific lanes within a route or roadway are reserved exclusively for a particular type of traffic or use.
  • D. hasExpressLanes
    Indicates that a roadway or transportation facility includes designated express lanes for faster or prioritized travel.
  • E. hasLanes
    Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
  • 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_69f349b5f6648190b9420d94a4cd16e0 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ff0b6bc4a88190bf1d38c6ea26bcdc completed May 9, 2026, 10:24 a.m.
PD Predicate disambiguation batch_69ff082a22f4819095ded971dbd8ea7b completed May 9, 2026, 10:10 a.m.
Created at: May 1, 2026, 1:57 a.m.