Triple
T25834232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-4 Ultimate reconstruction project |
E650751
|
entity |
| Predicate | usesTolling |
P3913
|
FINISHED |
| Object | dynamic pricing on express 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: dynamic pricing on express lanes | Statement: [I-4 Ultimate reconstruction project, usesTolling, dynamic pricing on express lanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTolling Context triple: [I-4 Ultimate reconstruction project, usesTolling, dynamic pricing on express lanes]
-
A.
appliesTollTo
Indicates that a fee or charge is imposed on a subject for using, accessing, or passing through something.
-
B.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
C.
tollingType
chosen
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
-
D.
hasTollBoothsAt
Indicates that toll booths are present at or associated with a particular location or segment of infrastructure.
-
E.
operatesTollSystem
Indicates that an entity is responsible for running and managing a toll collection 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f601f485c48190bdbeb260653d9849 |
completed | May 2, 2026, 1:53 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 7:40 a.m.