Triple
T22964225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadway (Albany, New York) |
E570992
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Albany, New York |
C47073
|
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 Albany, New York Context triple: [Broadway (Albany, New York), instanceOf, road in Albany, New York]
-
A.
road in Queens
A road in Queens is a public thoroughfare within the Queens borough of New York City that facilitates vehicular and pedestrian movement while connecting residential, commercial, and industrial 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.
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.
-
E.
road in Portland, Oregon
A road in Portland, Oregon is a public vehicular and pedestrian thoroughfare within the city’s transportation network, defined by its physical layout, traffic regulations, and integration with local infrastructure and land use.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:47 p.m.