Triple
T1330553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marion County–Indianapolis consolidated city-county |
E28633
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | unified local government |
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: unified local government Context triple: [Marion County–Indianapolis consolidated city-county, instanceOf, unified local government]
-
A.
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.
-
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.
county government
A county government is a local administrative body responsible for providing regional services, enforcing laws, managing public resources, and implementing policies within a defined county jurisdiction.
-
D.
municipal agency
A municipal agency is a local government organization responsible for delivering specific public services, enforcing local regulations, and managing community programs within a city or town.
-
E.
District
A District is a defined geographic or administrative area within a larger region, established for governance, organization, or service delivery purposes.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:55 p.m.