Triple
T26201553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basic Democrats |
E655242
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government representatives |
C38758
|
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 government representatives Context triple: [Basic Democrats, instanceOf, local government representatives]
-
A.
municipal government officeholders
chosen
Individuals elected or appointed to positions of authority within a city or local government, responsible for creating, implementing, and overseeing municipal policies, services, and regulations.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
local government meeting
A local government meeting is a formal gathering where elected officials, staff, and sometimes community members convene to discuss, deliberate, and make decisions on public policies, services, and issues affecting a specific municipality or region.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:48 p.m.