Triple
T5476096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Berkeley |
E122957
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Berkeley, 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: district of Berkeley, California Context triple: [South Berkeley, instanceOf, district of Berkeley, California]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
college of the University of California, Berkeley
A college of the University of California, Berkeley is an academic division within the university that organizes related departments and programs to offer undergraduate and graduate degrees in specific fields of study.
-
E.
district of Portland, Oregon
A district of Portland, Oregon is a defined geographic area within the city that groups together neighborhoods sharing common administrative, cultural, or commercial characteristics.
- 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:09 p.m.