Triple
T5230831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Cooperative Highway Research Program |
E118105
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | highway research program |
C10079
|
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: highway research program Context triple: [National Cooperative Highway Research Program, instanceOf, highway research program]
-
A.
highway funding program
chosen
A highway funding program is a structured governmental initiative that allocates financial resources for the planning, construction, maintenance, and improvement of highway infrastructure.
-
B.
public transit and highway improvement program
A public transit and highway improvement program is a coordinated set of projects and policies designed to enhance the capacity, safety, efficiency, and accessibility of transportation networks through upgrades to roads, highways, and mass transit systems.
-
C.
highway system
A highway system is an interconnected network of major roads and supporting infrastructure designed to enable efficient, high-capacity vehicular travel between cities and regions.
-
D.
division of the Federal Highway Administration
A division of the Federal Highway Administration is a regional or state-level office responsible for implementing FHWA policies, overseeing federal-aid highway programs, and coordinating with state and local transportation agencies within its jurisdiction.
-
E.
highway
A highway is a major public road designed for high-speed, long-distance vehicular travel, typically featuring multiple lanes, limited access points, and safety infrastructure.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:48 p.m.