Triple
T16872892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parkchester |
E421218
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planned residential neighborhood |
C5974
|
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: planned residential neighborhood Context triple: [Parkchester, instanceOf, planned residential neighborhood]
-
A.
planned residential community
chosen
A planned residential community is a deliberately designed neighborhood or development where housing, infrastructure, amenities, and land use are pre-organized to create a cohesive living environment.
-
B.
Residential district
A residential district is an area of a city or town primarily designated for housing, where people live in various types of dwellings and are supported by local amenities and services.
-
C.
residential quadrangle
A residential quadrangle is a four-sided courtyard or open space enclosed or bordered by housing buildings, typically used for communal living, circulation, and social interaction.
-
D.
neighborhood
A neighborhood is a geographically localized community within a larger city or town, characterized by shared residential spaces, social interactions, and common amenities.
-
E.
former residential neighborhood
A former residential neighborhood is an area that once contained homes and community life but has since been depopulated, demolished, repurposed, or otherwise ceased to function as a residential district.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:29 a.m.