Triple
T31692128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhode Island Turnpike and Bridge Authority |
E808819
|
entity |
| Predicate | typeOfTolling |
P3913
|
FINISHED |
| Object | user-fee based financing |
—
|
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: user-fee based financing | Statement: [Rhode Island Turnpike and Bridge Authority, typeOfTolling, user-fee based financing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTolling Context triple: [Rhode Island Turnpike and Bridge Authority, typeOfTolling, user-fee based financing]
-
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.
typeOfTollSystem
Indicates the specific kind or category of toll collection system used in a given context.
-
C.
tollRoadClass
Indicates the classification or category assigned to a toll road based on its type, characteristics, or tolling scheme.
-
D.
tollingAuthority
Indicates the entity that has the authority to impose, collect, or manage a toll on a given route, facility, or service.
-
E.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a000014497c819088d5cda3977522dd |
completed | May 10, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69ffff9a52b08190be1024e0fb6fe661 |
completed | May 10, 2026, 3:46 a.m. |
Created at: April 30, 2026, 11:09 p.m.