Triple
T18426792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayward Area Recreation and Park District |
E450160
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special district in California |
C2259
|
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: special district in California Context triple: [Hayward Area Recreation and Park District, instanceOf, special district in California]
-
A.
special-purpose district
chosen
A special-purpose district is a limited-purpose local government entity created to perform a specific public function or set of functions—such as water supply, transportation, or education—within a defined geographic area.
-
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.
district of San Jose, California
A district of San Jose, California is an administrative or commonly recognized geographic subdivision of the city, typically characterized by distinct residential, commercial, cultural, or historical features.
-
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.
Los Angeles City Council district
A Los Angeles City Council district is a geographically defined electoral area within the City of Los Angeles, each represented by a single councilmember responsible for local legislation, constituent services, and community advocacy.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:24 a.m.