Triple
T27030893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Virginia Route 39 |
E680913
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | numbered highway in West Virginia |
C42613
|
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: numbered highway in West Virginia Context triple: [West Virginia Route 39, instanceOf, numbered highway in West Virginia]
-
A.
road in West Virginia
chosen
A road in West Virginia is a transportation route, ranging from winding rural byways to major highways, that traverses the state's mountainous terrain to connect its towns, cities, and natural landmarks.
-
B.
numbered highway in Pennsylvania
A numbered highway in Pennsylvania is a designated roadway within the state’s transportation network identified by a unique route number and maintained by state or federal authorities for regional and interstate travel.
-
C.
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.
-
D.
numbered highway in Vermont
A numbered highway in Vermont is a designated state or federal roadway identified by a unique route number that facilitates regional and interstate travel within and through the state.
-
E.
numbered highway in New Hampshire
A numbered highway in New Hampshire is a designated state, U.S., or interstate route within New Hampshire’s road network, identified by a unique number and maintained by the appropriate transportation authority.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 7:13 a.m.