Triple
T31019240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Region 3 (UDOT) |
E790407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Utah Department of Transportation region |
C57381
|
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: Utah Department of Transportation region Context triple: [Region 3 (UDOT), instanceOf, Utah Department of Transportation region]
-
A.
numbered highway in Utah
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.
Colorado State Highway
A Colorado State Highway is a numbered public roadway maintained by the state of Colorado that facilitates regional and intrastate transportation between cities, towns, and key destinations within the state.
-
C.
county of Utah
A county of Utah is an administrative subdivision of the state of Utah that functions as a local government unit responsible for regional services, governance, and regulation within its defined geographic boundaries.
-
D.
Utah State University campus
Utah State University campus is a scenic, mountain-framed academic environment in Logan, Utah, featuring historic and modern facilities that support education, research, and student life.
-
E.
Utah Valley University campus
Utah Valley University campus is a modern, commuter-friendly university environment in Orem, Utah, featuring interconnected academic buildings, student services, and community-focused spaces designed to support a large, diverse student body.
- F. None of above. chosen
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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:58 p.m.