Triple
T21170715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highway Capacity Manual |
E521683
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation engineering reference |
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: transportation engineering reference Context triple: [Highway Capacity Manual, instanceOf, transportation engineering reference]
-
A.
transportation research program
A transportation research program is an organized initiative that systematically studies and develops knowledge, technologies, and policies to improve the safety, efficiency, sustainability, and equity of transportation systems.
-
B.
AASHTO policy document
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.
-
C.
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.
-
D.
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.
-
E.
engineering treatise
An engineering treatise is a comprehensive, systematically organized written work that rigorously analyzes, explains, and documents engineering principles, methods, designs, or systems.
- 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3 p.m.