Triple
T8298826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Oakland |
E194293
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of Oakland, California |
C5141
|
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: region of Oakland, California Context triple: [East Oakland, instanceOf, region of Oakland, California]
-
A.
subregion of the San Francisco Bay Area
chosen
A subregion of the San Francisco Bay Area is a geographically and/or culturally distinct part of the larger Bay Area, typically defined by shared economic, social, environmental, or infrastructural characteristics.
-
B.
district of San Francisco
A district of San Francisco is a geographically defined area within the city that groups neighborhoods sharing common administrative boundaries, local services, and community characteristics.
-
C.
subregion of Los Angeles County
A subregion of Los Angeles County is a geographically defined portion of the county characterized by shared social, economic, cultural, or environmental features used for planning, governance, and analysis.
-
D.
district of Los Angeles
A district of Los Angeles is a defined geographic subdivision of the city characterized by distinct administrative boundaries, local governance functions, and unique cultural, economic, or residential features.
-
E.
East Bay Regional Park District park
An East Bay Regional Park District park is a publicly accessible natural or recreational area in California’s East Bay region that is managed by the East Bay Regional Park District to provide open space, conservation, and outdoor activities for the community.
- 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:53 p.m.