Triple
T1497423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-355 |
E29716
|
entity |
| Predicate | tolling |
P3913
|
FINISHED |
| Object | all-electronic toll collection on some segments |
—
|
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: all-electronic toll collection on some segments | Statement: [I-355, tolling, all-electronic toll collection on some segments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tolling Context triple: [I-355, tolling, all-electronic toll collection on some segments]
-
A.
tollingType
chosen
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
-
B.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
C.
appliesTollTo
Indicates that a fee or charge is imposed on a subject for using, accessing, or passing through something.
-
D.
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.
-
E.
hasTollSegment
Indicates that a route, road, or path includes a segment where a toll must be paid.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6edca248190a90205799b270058 |
completed | March 1, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69a4c48a8cf48190a6ebf8d44a608a06 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.