Triple
T29956189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lafayette City-Parish Consolidated Government |
E760906
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | consolidated city-parish government |
C14162
|
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: consolidated city-parish government Context triple: [Lafayette City-Parish Consolidated Government, instanceOf, consolidated city-parish government]
-
A.
consolidated city and county
chosen
A consolidated city and county is a single unified jurisdiction formed when a city and its surrounding county merge their governmental functions into one combined entity.
-
B.
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.
-
C.
centrally governed city
A centrally governed city is an urban area whose key administrative, economic, and policy decisions are directed and controlled by a single, central authority rather than by multiple local or decentralized bodies.
-
D.
former municipal government
A former municipal government is a previously existing local governing body or administrative authority that has been dissolved, merged, or replaced and no longer exercises official jurisdiction over its former municipality.
-
E.
autonomous city government
An autonomous city government is a self-governing municipal authority that exercises significant political, administrative, and fiscal control over local affairs independent of higher levels of government.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:27 p.m.