Triple
T27374406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Meridian Street |
E691021
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Indianapolis |
C52767
|
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 Indianapolis Context triple: [North Meridian Street, instanceOf, road in Indianapolis]
-
A.
road in Pittsburgh
A road in Pittsburgh is a public vehicular thoroughfare within the city’s hilly, river-divided landscape, often featuring bridges, tunnels, and irregular intersections shaped by the region’s topography and historic development.
-
B.
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.
-
C.
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.
-
D.
road in Albany, New York
A road in Albany, New York is a public vehicular and pedestrian thoroughfare within the city’s transportation network, providing access between local destinations and connecting to regional routes.
-
E.
road in Salem, Massachusetts
A road in Salem, Massachusetts is a public thoroughfare that provides vehicular and pedestrian access through the city, connecting residential, commercial, and historic areas while integrating with local traffic regulations and infrastructure.
- 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_69ef52022538819081f873d0c84a6dd6 |
completed | April 27, 2026, 12:09 p.m. |
Created at: April 27, 2026, 12:20 p.m.