Triple
T31456078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connecticut parkways |
E802453
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | limited-access highway network |
C3821
|
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: limited-access highway network Context triple: [Connecticut parkways, instanceOf, limited-access highway network]
-
A.
controlled-access highway
A controlled-access highway is a high-speed road designed for uninterrupted traffic flow, featuring limited entry and exit points via ramps, no at-grade intersections, and restrictions on pedestrian and non-motorized access.
-
B.
Interstate business loop
An Interstate business loop is a special route that departs from an Interstate Highway to pass through the downtown or commercial center of a nearby city before reconnecting with the same Interstate.
-
C.
highway connection
A highway connection is a road segment or interchange that links two or more highways or major roads, enabling continuous vehicular travel between them.
-
D.
highway system
chosen
A highway system is an interconnected network of major roads and supporting infrastructure designed to enable efficient, high-capacity vehicular travel between cities and regions.
-
E.
highway segment
A highway segment is a continuous portion of a highway between two defined endpoints, such as interchanges, intersections, or mile markers, characterized by consistent physical and operational attributes.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:16 p.m.