Triple
T26907573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 15 express lanes |
E677296
|
entity |
| Predicate | tollVariesBy |
P161320
|
FINISHED |
| Object | vehicle occupancy |
—
|
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: vehicle occupancy | Statement: [Interstate 15 express lanes, tollVariesBy, vehicle occupancy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tollVariesBy Context triple: [Interstate 15 express lanes, tollVariesBy, vehicle occupancy]
-
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.
tollRoadOf
Indicates that a road segment is a toll road belonging to or associated with a particular roadway, route, or transportation network.
-
C.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
D.
tollRoadFunction
Indicates that a road segment operates as a toll facility, requiring payment from users for access or passage.
-
E.
hasTollBoothsAt
Indicates that toll booths are present at or associated with a particular location or segment of infrastructure.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 6 a.m.