Triple
T24537521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 13 Business (Claymont, Delaware) |
E606990
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Delaware |
C48855
|
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 Delaware Context triple: [U.S. Route 13 Business (Claymont, Delaware), instanceOf, road in Delaware]
-
A.
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.
-
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 Michigan
A road in Michigan is a designated vehicular travel way within the state’s boundaries, ranging from local streets to major highways, that facilitates transportation, commerce, and connectivity among Michigan’s communities and regions.
-
D.
road in New Brunswick
A road in New Brunswick is a designated transportation corridor within the province that facilitates vehicular travel between communities, regions, and key destinations, following provincial standards for construction, maintenance, and signage.
-
E.
road in Baltimore
A road in Baltimore is a public thoroughfare within the city’s transportation network that facilitates vehicular, bicycle, and pedestrian movement while connecting neighborhoods, businesses, and regional routes.
- 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:26 a.m.