Triple

T30378979
Position Surface form Disambiguated ID Type / Status
Subject ExpressLanes on I-10 and I-110 E772768 entity
Predicate tollVariationFactor P161320 FINISHED
Object real-time traffic conditions 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: real-time traffic conditions | Statement: [ExpressLanes on I-10 and I-110, tollVariationFactor, real-time traffic conditions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tollVariationFactor
Context triple: [ExpressLanes on I-10 and I-110, tollVariationFactor, real-time traffic conditions]
  • A. tollVariesBy chosen
    Indicates that the amount of a toll changes depending on a specified factor or condition (such as time, vehicle type, or route).
  • B. hasTollVariant
    Indicates that an entity has a version or instance that requires paying a toll or fee for use or access.
  • C. tollRoadOf
    Indicates that a road segment is a toll road belonging to or associated with a particular roadway, route, or transportation network.
  • D. tollingType
    Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
  • E. tollRoadFunction
    Indicates that a road segment operates as a toll facility, requiring payment from users for access or passage.
  • 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_69f2248e3444819081b05712dc6873de completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f68516d72c8190a86c755b5907f5c4 completed May 2, 2026, 11:13 p.m.
PD Predicate disambiguation batch_69f678d019fc8190913662cd2f87b857 completed May 2, 2026, 10:21 p.m.
Created at: April 29, 2026, 8 p.m.