Triple
T14732852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFK Bridge |
E346119
|
entity |
| Predicate | replacedTollBoothsWith |
P24137
|
FINISHED |
| Object | open road cashless tolling |
—
|
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: open road cashless tolling | Statement: [RFK Bridge, replacedTollBoothsWith, open road cashless tolling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedTollBoothsWith Context triple: [RFK Bridge, replacedTollBoothsWith, open road cashless tolling]
-
A.
tollIntroduced
Indicates that a toll was established or put into effect for using a particular route, facility, or service.
-
B.
hasTollBoothsAt
Indicates that toll booths are present at or associated with a particular location or segment of infrastructure.
-
C.
hasTollPlazaRemoved
chosen
Indicates that a previously existing toll plaza associated with an entity has been removed or decommissioned.
-
D.
replacedStation
Indicates that one station has taken the place of another station, typically succeeding it in function, service, or location.
-
E.
formerTollRoad
Indicates that a road previously operated as a toll road but is no longer tolled.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec72ea9348190817efcdaa973d7f7 |
completed | April 14, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:29 a.m.