Triple
T12231044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Nicholas Historic District |
E291476
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic district in New York City |
C6736
|
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: historic district in New York City Context triple: [St. Nicholas Historic District, instanceOf, historic district in New York City]
-
A.
New York City cultural site
A New York City cultural site is a location within the city—such as a museum, theater, gallery, landmark, or performance space—dedicated to preserving, presenting, or fostering artistic, historical, or community-based cultural expression.
-
B.
New York City designated landmark
chosen
A New York City designated landmark is a building, site, object, or district officially recognized and protected by the New York City Landmarks Preservation Commission for its special historical, cultural, or architectural significance.
-
C.
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.
-
D.
landmark in New York City
A landmark in New York City is a notable, often historically or culturally significant site, building, or structure officially recognized for its importance to the city’s heritage and identity.
-
E.
location in Manhattan
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.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:51 p.m.