Triple
T31480040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 89 (Utah) |
E803113
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Utah |
C48390
|
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: road in Utah Context triple: [U.S. Route 89 (Utah), instanceOf, road in Utah]
-
A.
numbered highway in Utah
chosen
A numbered highway in Utah is a designated road within the state’s transportation network, identified by a unique route number and maintained by state or federal agencies to facilitate regional and interstate travel.
-
B.
Utah Department of Transportation region
A Utah Department of Transportation region is a geographically defined administrative division of the state’s transportation agency responsible for planning, constructing, operating, and maintaining transportation infrastructure within its boundaries.
-
C.
road in North Dakota
A road in North Dakota is a transportation route, often long and sparsely traveled, that connects rural communities, agricultural areas, and towns across the state’s predominantly flat and open landscape.
-
D.
road in South Dakota
A road in South Dakota is a constructed transportation route within the state that facilitates vehicular travel between locations, often traversing rural landscapes, prairies, and small towns.
-
E.
Nevada State Route
A Nevada State Route is a numbered highway within the state of Nevada that is part of the state-maintained road network, facilitating regional and local 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:31 p.m.