Triple
T18552956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jefferson Avenue (Detroit) |
E453424
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Detroit |
C1088
|
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 Detroit Context triple: [Jefferson Avenue (Detroit), instanceOf, street in Detroit]
-
A.
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.
-
B.
street in New York City
A street in New York City is a public urban thoroughfare lined with diverse buildings and infrastructure that supports vehicular, pedestrian, and commercial activity within the city's dense grid layout.
-
C.
street in Buffalo, New York
A street in Buffalo, New York is a public roadway within the city’s urban grid that facilitates vehicular and pedestrian movement while connecting residential, commercial, and civic areas characteristic of Buffalo’s regional architecture and infrastructure.
-
D.
street in Saint Petersburg
A street in Saint Petersburg is a public urban thoroughfare within the city’s historical or modern districts, typically lined with buildings and infrastructure that reflect the architectural, cultural, and social character of Russia’s northern capital.
-
E.
street
chosen
A street is a public thoroughfare in an urban or suburban area, typically bordered by buildings, that facilitates vehicular and pedestrian movement and often supports various social and commercial activities.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:38 a.m.