Triple
T2335737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highway Safety Improvement Program guidance |
E44305
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | roadway safety planning guidance |
C5736
|
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: roadway safety planning guidance Context triple: [Highway Safety Improvement Program guidance, instanceOf, roadway safety planning guidance]
-
A.
road infrastructure
Road infrastructure encompasses the physical structures, systems, and facilities—such as roads, bridges, tunnels, signage, and drainage—designed and built to support safe and efficient vehicular and pedestrian transportation.
-
B.
road network
A road network is an interconnected system of roads, intersections, and related infrastructure that enables the movement of vehicles and pedestrians between different locations.
-
C.
road segment
A road segment is a continuous portion of a roadway between two defined endpoints, such as intersections or junctions, characterized by uniform attributes like direction, number of lanes, and speed limit.
-
D.
highway law
Highway law is the body of legal rules and regulations governing the construction, maintenance, use, and safety of public roads and highways, including the rights and responsibilities of authorities and road users.
-
E.
AASHTO policy document
chosen
An AASHTO policy document is an official publication by the American Association of State Highway and Transportation Officials that establishes standards, guidelines, and best practices for the planning, design, construction, and operation of transportation infrastructure in the United States.
- 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:51 p.m.