Triple
T4933529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park Hill |
E110753
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic residential neighborhood |
C11817
|
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 residential neighborhood Context triple: [Park Hill, instanceOf, historic residential neighborhood]
-
A.
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.
-
B.
residential historic district
chosen
A residential historic district is a geographically defined neighborhood composed primarily of homes that collectively reflect significant historical, architectural, or cultural characteristics from a particular period or periods.
-
C.
historic suburb
A historic suburb is a residential area on the outskirts of a city characterized by long-established neighborhoods, preserved architecture, and cultural or historical significance.
-
D.
historic African American neighborhood
A historic African American neighborhood is a culturally rich, predominantly Black community whose physical spaces, institutions, and traditions reflect the social, political, and economic experiences of African Americans over time.
-
E.
historic township
A historic township is a former or long-established local administrative or geographic subdivision, often with distinct historical boundaries, governance, and community identity that may differ from modern municipal structures.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:30 p.m.