Triple
T1298707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenwich Village Historic District |
E27712
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New York City designated landmark |
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: New York City designated landmark Context triple: [Greenwich Village Historic District, instanceOf, New York City designated landmark]
-
A.
New York City community board
A New York City community board is a local advisory group of appointed residents that consults on land use, budget, and service delivery issues within a specific community district.
-
B.
borough of New York City
A borough of New York City is one of the five primary administrative and geographic divisions of the city, each coextensive with a county and possessing its own local identity, governance structures, and community characteristics within the larger metropolis.
-
C.
Chinatown landmark
A Chinatown landmark is a notable physical site, structure, or feature within a Chinatown neighborhood that holds cultural, historical, or social significance for the local Chinese community and its visitors.
-
D.
bridge in New York City
A bridge in New York City is a large-scale transportation structure spanning waterways or land to connect boroughs and neighborhoods, supporting vehicular, rail, bicycle, and pedestrian traffic within the city’s dense urban environment.
-
E.
Chicago landmark
A Chicago landmark is a notable building, structure, or site in Chicago officially recognized or widely regarded for its historical, architectural, cultural, or social significance.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
Created at: March 1, 2026, 7:51 p.m.