Triple
T13874110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potomac Greens |
E333533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neighborhood in Alexandria, Virginia |
C34289
|
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 in Alexandria, Virginia Context triple: [Potomac Greens, instanceOf, neighborhood in Alexandria, 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.
neighborhood of Richmond, Virginia
A neighborhood of Richmond, Virginia is a distinct residential or mixed-use area within the city characterized by its own local identity, history, demographics, and community amenities.
-
C.
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.
-
D.
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.
-
E.
neighborhood in Washington, D.C.
A neighborhood in Washington, D.C. is a distinct, localized community within the city characterized by its own residential patterns, cultural identity, land use, and social, economic, and historical features.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:14 p.m.