Triple
T5448995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AASHTO Highway Safety Manual |
E122321
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | roadway safety guideline |
C18225
|
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 guideline Context triple: [AASHTO Highway Safety Manual, instanceOf, roadway safety guideline]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
road designation
A road designation is a label or code assigned to a roadway (such as a route number, name, or classification) that identifies its function, hierarchy, and navigational role within a transportation network.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:07 p.m.