Triple
T34737530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Street (La Grange, Kentucky) |
E1001389
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in La Grange, Kentucky |
C27253
|
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: street in La Grange, Kentucky Context triple: [Main Street (La Grange, Kentucky), instanceOf, street in La Grange, Kentucky]
-
A.
road in Kentucky
chosen
A road in Kentucky is a designated transportation route within the state’s boundaries that facilitates vehicular travel between localities, landmarks, and regions, following Kentucky’s specific geographic, legal, and infrastructural standards.
-
B.
street in Houston
A street in Houston is a public roadway within the city’s grid that facilitates vehicular and pedestrian movement while connecting residential, commercial, and industrial areas across Houston’s diverse neighborhoods.
-
C.
street in Atlanta
A street in Atlanta is a public roadway within the city’s urban grid that facilitates vehicular and pedestrian movement while reflecting the area’s distinctive Southern culture, neighborhoods, and infrastructure.
-
D.
street in Chicago
A street in Chicago is a public urban thoroughfare within the city’s grid system that facilitates vehicular and pedestrian movement while connecting residential, commercial, and cultural areas.
-
E.
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.
- 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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.