Triple
T20885848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Route 3 |
E514277
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | numbered highway in Alaska |
C43881
|
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 Alaska Context triple: [Alaska Route 3, instanceOf, numbered highway in Alaska]
-
A.
numbered highway in Maine
A numbered highway in Maine is a designated state, U.S., or interstate route identified by a unique number that provides organized, signed road connections between cities, towns, and regions within and beyond the state.
-
B.
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.
-
C.
U.S. Numbered Highway
A U.S. Numbered Highway is a nationally coordinated, signed roadway within the United States that is part of the United States Numbered Highway System, providing intercity and interstate connections but distinct from the Interstate Highway System.
-
D.
numbered highway in New Hampshire
A numbered highway in New Hampshire is a designated state, U.S., or interstate route within New Hampshire’s road network, identified by a unique number and maintained by the appropriate transportation authority.
-
E.
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.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:46 p.m.