Triple
T34510491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 101 in Mountain View |
E886004
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | part of U.S. Route 101 |
C9637
|
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: part of U.S. Route 101 Context triple: [U.S. Route 101 in Mountain View, instanceOf, part of U.S. Route 101]
-
A.
part of California State Route 125
A part of California State Route 125 represents a specific contiguous segment of this state highway, characterized by its defined geographic extent, roadway features, and functional role within the overall SR 125 transportation corridor.
-
B.
segment of Washington State Route 99
A segment of Washington State Route 99 represents a continuous portion of the state highway between two defined endpoints, characterized by its specific location, roadway features, and role in regional transportation.
-
C.
United States federal road
chosen
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.
-
D.
Alaska Marine Highway route
An Alaska Marine Highway route is a designated ferry corridor within the Alaska Marine Highway System that connects specific coastal communities and ports according to a defined schedule and service pattern.
-
E.
Farm to Market Road
A Farm to Market Road is a rural roadway designed to connect agricultural areas and farms with nearby towns, markets, and major transportation routes to facilitate the movement of goods and people.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.