Triple
T37015006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeast Los Angeles |
E916052
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of Los Angeles County |
C13574
|
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 Los Angeles County Context triple: [Southeast Los Angeles, instanceOf, region of Los Angeles County]
-
A.
subregion of Los Angeles County
chosen
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.
-
B.
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.
-
C.
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.
-
D.
Los Angeles community plan area
A Los Angeles community plan area is a defined geographic subdivision of the City of Los Angeles used in the General Plan to guide and regulate land use, development, and community-specific planning policies.
-
E.
subregion of Santa Barbara County
A subregion of Santa Barbara County is a geographically defined portion of the county characterized by shared physical, cultural, economic, or administrative features that distinguish it from other areas within the county.
- 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.