Triple
T8478359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Brock |
E200451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traffic management scheme |
C24472
|
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: traffic management scheme Context triple: [Operation Brock, instanceOf, traffic management scheme]
-
A.
traffic authority
A traffic authority is an organization or governmental body responsible for planning, regulating, and managing road use, traffic flow, and transportation safety within a specific jurisdiction.
-
B.
road pricing scheme
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.
-
C.
road traffic agreement
A road traffic agreement is a formal arrangement between parties—such as governments, municipalities, or private entities—that defines rights, responsibilities, and rules for the use, management, and regulation of road traffic within a specified area or network.
-
D.
transport policy framework
A transport policy framework is a structured set of principles, goals, and regulatory tools that guide the planning, funding, operation, and governance of transportation systems to achieve economic, social, and environmental objectives.
-
E.
transport model
A transport model is a conceptual or mathematical representation used to simulate and analyze the movement of people, goods, or resources across a network or spatial system under various conditions and constraints.
- F. None of above. chosen
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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:12 p.m.