Triple
T38214873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 278 in South Carolina |
E1010657
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in South Carolina |
C65293
|
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: road in South Carolina Context triple: [U.S. Route 278 in South Carolina, instanceOf, road in South Carolina]
-
A.
road in Charleston, South Carolina
A road in Charleston, South Carolina is a public thoroughfare within the city’s historic and coastal environment that supports vehicular, pedestrian, and related transportation activities while connecting local residences, businesses, and landmarks.
-
B.
road in West Virginia
A road in West Virginia is a transportation route, ranging from winding rural byways to major highways, that traverses the state's mountainous terrain to connect its towns, cities, and natural landmarks.
-
C.
road in South Dakota
A road in South Dakota is a constructed transportation route within the state that facilitates vehicular travel between locations, often traversing rural landscapes, prairies, and small towns.
-
D.
road in Virginia
A road in Virginia is a designated vehicular travelway within the Commonwealth of Virginia that facilitates transportation, access, and connectivity between locations while adhering to state and local regulations and infrastructure standards.
-
E.
road in Delaware
A road in Delaware is a paved or unpaved public or private thoroughfare within the state’s boundaries that facilitates vehicular and pedestrian travel between locations.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.