Triple
T27499933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington State Route 101 |
E694124
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | numbered highway in Washington |
C51657
|
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 Washington Context triple: [Washington State Route 101, instanceOf, numbered highway in Washington]
-
A.
road in Washington State
chosen
A road in Washington State is a constructed transportation route within the state's boundaries that facilitates vehicular travel between locations, adhering to state and local regulations and infrastructure standards.
-
B.
numbered highway in Alaska
A numbered highway in Alaska is a designated state or federal roadway identified by a specific route number that facilitates vehicular travel across Alaska’s diverse and often remote regions.
-
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 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.
-
E.
numbered highway in Wisconsin
A numbered highway in Wisconsin is a designated state, U.S., or Interstate route within Wisconsin’s borders that provides organized, signed corridors for vehicular travel and connectivity between cities, towns, and regions.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:10 p.m.