Triple
T37815063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primary State Highway 1J (part, historical) |
E942751
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Washington state highway designation |
C10921
|
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: Washington state highway designation Context triple: [Primary State Highway 1J (part, historical), instanceOf, Washington state highway designation]
-
A.
road in Washington State
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.
state highway system
A state highway system is a network of roads and highways maintained and regulated by a state government to facilitate regional transportation and connectivity.
-
C.
highway numbering policy
Highway numbering policy is the set of rules and conventions that govern how route numbers are assigned, organized, and displayed across a road network to convey location, hierarchy, and direction.
-
D.
former state highway designation
chosen
A former state highway designation is an official route number or name that was once assigned to a state-maintained roadway but has since been removed, reassigned, or decommissioned from the state highway system.
-
E.
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.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.