Triple
T21219755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berkeley City Council District 2 |
E522932
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local political subdivision |
C39
|
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: local political subdivision Context triple: [Berkeley City Council District 2, instanceOf, local political subdivision]
-
A.
local governmental entity
A local governmental entity is an administrative organization, such as a city, county, or district, that exercises governmental authority and provides public services within a specific geographic area below the level of the central or national government.
-
B.
sub‑national government
A sub-national government is a governing authority below the national level—such as a state, province, region, or municipality—that exercises political, administrative, and often fiscal powers within a defined territorial jurisdiction.
-
C.
local council
A local council is a governing body elected or appointed to make decisions, set policies, and manage public services for a specific municipality or local area.
-
D.
local government politics
Local government politics encompasses the processes, power dynamics, and decision-making activities through which local officials, institutions, and community stakeholders shape policies and allocate resources within municipalities or regions.
-
E.
municipality
chosen
A municipality is a local administrative unit, such as a city, town, or district, governed by elected officials and responsible for providing public services and regulations within its defined geographic area.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:43 p.m.