Triple
T10767026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VA 243 |
E253979
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Virginia state highway |
C264
|
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: Virginia state highway Context triple: [VA 243, instanceOf, Virginia state highway]
-
A.
road in Virginia
A road in Virginia is a designated vehicular travelway within the Commonwealth of Virginia that facilitates transportation, access, and connectivity between locations while adhering to state and local regulations and infrastructure standards.
-
B.
United States federal road
A United States federal road is a roadway that is part of the national highway system and is funded, regulated, or maintained in whole or in part by the federal government to support interstate travel, commerce, and defense.
-
C.
state highway
chosen
A state highway is a public road maintained and administered by a state government, forming part of a regional or statewide transportation network that connects cities, towns, and other major routes.
-
D.
Florida State Road
A Florida State Road is a numbered highway within the state of Florida that is planned, constructed, and maintained by the Florida Department of Transportation as part of the state’s primary roadway network.
-
E.
numbered highway in Maryland
A numbered highway in Maryland is a designated roadway within the state’s transportation network, identified by a unique route number and maintained by the appropriate state or federal agency to facilitate regional and interstate travel.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:16 p.m.