Triple
T2335687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manual on Uniform Traffic Control Devices |
E44304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traffic control standard |
C5735
|
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 control standard Context triple: [Manual on Uniform Traffic Control Devices, instanceOf, traffic control standard]
-
A.
transportation standard
chosen
A transportation standard is an agreed-upon set of rules, specifications, and protocols that ensure compatibility, safety, and efficiency across transportation systems, vehicles, and infrastructure.
-
B.
controlled-access highway
A controlled-access highway is a high-speed road designed for uninterrupted traffic flow, featuring limited entry and exit points via ramps, no at-grade intersections, and restrictions on pedestrian and non-motorized access.
-
C.
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.
-
D.
traffic circle
A traffic circle is a circular intersection where vehicles travel counterclockwise around a central island, yielding to circulating traffic to manage flow and reduce conflict points.
-
E.
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.
- 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.