Triple
T27159537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashford Park |
E682621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neighborhood in Brookhaven, Georgia |
C52562
|
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 Brookhaven, Georgia Context triple: [Ashford Park, instanceOf, neighborhood in Brookhaven, Georgia]
-
A.
street in Alpharetta, Georgia
A street in Alpharetta, Georgia is a public roadway within the city’s limits that provides access to residential, commercial, and community areas while connecting to the broader local and regional transportation network.
-
B.
neighborhood in Brookline, Massachusetts
A neighborhood in Brookline, Massachusetts is a distinct residential and mixed-use area within the town characterized by its local architecture, community amenities, and social identity.
-
C.
district of Atlanta
A district of Atlanta is a defined geographic subdivision of the city, typically characterized by distinct administrative boundaries, land use patterns, and social, cultural, or economic identities within the broader metropolitan area.
-
D.
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.
-
E.
street in Atlanta
A street in Atlanta is a public roadway within the city’s urban grid that facilitates vehicular and pedestrian movement while reflecting the area’s distinctive Southern culture, neighborhoods, 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:18 a.m.