Triple
T23995844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan municipalities |
E605187
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government unit category |
C15097
|
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 unit category Context triple: [Michigan municipalities, instanceOf, local government unit category]
-
A.
local governmental entity
chosen
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.
local government association
A local government association is an organization that represents and supports the collective interests, coordination, and capacity-building of local authorities within a specific region or country.
-
C.
system of local government
A system of local government is an organized framework of institutions, powers, and processes through which local authorities manage public services, enforce regulations, and represent community interests within a defined geographic area.
-
D.
local government service
A local government service is a public function or resource provided by municipal or regional authorities to meet community needs such as safety, infrastructure, health, and social support.
-
E.
municipal organization
A municipal organization is a local government entity responsible for providing public services, managing community resources, and implementing policies within a city, town, or other local jurisdiction.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:38 p.m.