Triple
T12038403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Hill neighborhood |
E286598
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neighborhood of Richmond, Virginia |
C30337
|
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: neighborhood of Richmond, Virginia Context triple: [Church Hill neighborhood, instanceOf, neighborhood of Richmond, Virginia]
-
A.
neighborhood in Arlington County, Virginia
A neighborhood in Arlington County, Virginia is a localized residential and mixed-use area within the county’s boundaries, typically defined by shared community identity, land-use patterns, and geographic or infrastructural features.
-
B.
municipality in Virginia
A municipality in Virginia is a legally incorporated local government entity, such as a city or town, within the Commonwealth of Virginia that provides public services and exercises governmental authority over a defined geographic area.
-
C.
county in Virginia
A county in Virginia is a primary local government and geographic subdivision of the Commonwealth of Virginia, responsible for providing regional services, administration, and governance to the communities within its boundaries.
-
D.
Greenbelt town
A greenbelt town is a planned urban settlement surrounded by protected open land to limit sprawl, preserve nature, and provide residents with accessible green space.
-
E.
neighborhood of College Park, Maryland
A neighborhood of College Park, Maryland is a localized residential and mixed-use area within the city that encompasses homes, businesses, public spaces, and community institutions sharing a common identity and infrastructure.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.