Triple
T38656959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West 72nd Street and Central Park West |
E939917
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street intersection in Manhattan |
C14784
|
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 intersection in Manhattan Context triple: [West 72nd Street and Central Park West, instanceOf, street intersection in Manhattan]
-
A.
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.
-
B.
street in Staten Island
A street in Staten Island is a public roadway within the borough’s urban and suburban neighborhoods that facilitates local and through traffic, connects residential, commercial, and recreational areas, and integrates with New York City’s broader transportation network.
-
C.
location in Manhattan
chosen
A location in Manhattan represents a specific, identifiable place within the borough’s geographic boundaries, such as an address, landmark, intersection, or point of interest.
-
D.
road in the Bronx
A road in the Bronx is a public thoroughfare within the Bronx borough of New York City that facilitates vehicular and pedestrian movement while connecting residential, commercial, and institutional areas.
-
E.
region of Manhattan
A region of Manhattan is a contiguous geographic area within the borough, defined by boundaries such as streets, avenues, or natural features, that shares common characteristics like land use, demographics, or cultural identity.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:33 p.m.