Triple
T23953500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South County region of San Luis Obispo County |
E603114
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subregion of San Luis Obispo County |
C48706
|
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: subregion of San Luis Obispo County Context triple: [South County region of San Luis Obispo County, instanceOf, subregion of San Luis Obispo County]
-
A.
subregion of San Diego County
A subregion of San Diego County is a geographically defined portion of the county characterized by shared physical, economic, social, or administrative features used for planning, governance, or analysis.
-
B.
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.
-
C.
subregion of the San Francisco Bay Area
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.
-
D.
region of Northern California
A region of Northern California is a geographically defined area in the northern part of the state characterized by shared environmental features, cultural identity, and economic activities.
-
E.
district of San Diego
A district of San Diego is a defined geographic subdivision of the city used for administrative, political, or community-identification purposes.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:21 p.m.