Triple
T34850917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 1 in South Carolina |
E1004597
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | segment of U.S. Route 1 |
C1129
|
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: segment of U.S. Route 1 Context triple: [U.S. Route 1 in South Carolina, instanceOf, segment of U.S. Route 1]
-
A.
segment of U.S. Route 220
A segment of U.S. Route 220 is a specific, continuous portion of the U.S. Route 220 highway defined by its start and end points, physical characteristics, and associated transportation attributes.
-
B.
highway segment
chosen
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.
-
C.
United States federal road
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.
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.
-
E.
road segment
A road segment is a continuous portion of a roadway between two defined endpoints, such as intersections or junctions, characterized by uniform attributes like direction, number of lanes, and speed limit.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.