Triple
T38267008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockholm congestion tax |
E1021091
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | congestion pricing scheme |
C18840
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: congestion pricing scheme Context triple: [Stockholm congestion tax, instanceOf, congestion pricing scheme]
-
A.
road pricing scheme
chosen
A road pricing scheme is a system for charging drivers fees to use specific roads or areas, typically to manage congestion, reduce environmental impacts, or fund transportation infrastructure.
-
B.
traffic management scheme
A traffic management scheme is a coordinated set of policies, controls, and infrastructure measures designed to regulate and optimize the movement of vehicles, pedestrians, and goods within a transportation network.
-
C.
public transport pricing scheme
A public transport pricing scheme is a structured set of rules and fares that determines how passengers are charged for using public transit services based on factors such as distance, time, mode, and user category.
-
D.
high-occupancy toll lanes
High-occupancy toll lanes are special highway lanes that allow vehicles with multiple occupants to travel for free or at reduced cost while single-occupant vehicles can use them by paying a variable toll designed to manage congestion and maintain faster traffic flow.
-
E.
transponder-based toll system
A transponder-based toll system is an automated electronic toll collection method where vehicles equipped with small radio-frequency devices are detected and charged as they pass through toll points without stopping.
- F. None of above.
Provenance (1 batch)
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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.