Triple
T34802718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan emergency manager system |
E1003261
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state governance framework |
C27337
|
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: state governance framework Context triple: [Michigan emergency manager system, instanceOf, state governance framework]
-
A.
state administration
State administration is the organized system of public institutions and officials responsible for implementing government policies, managing public services, and enforcing laws within a state's territory.
-
B.
federal government framework
A federal government framework is a structural system that defines how power, responsibilities, and relationships are distributed and coordinated between a central authority and its constituent regional or state governments.
-
C.
provincial policy framework
A provincial policy framework is a structured set of guiding principles, objectives, and regulations developed at the provincial level to coordinate and direct public policies, programs, and resource allocation across sectors within that jurisdiction.
-
D.
state government
A state government is the political organization and administrative apparatus that exercises authority, creates and enforces laws, and provides public services within a specific subnational region of a country.
-
E.
legal-political framework
chosen
A legal-political framework is the structured system of laws, institutions, and governing principles that defines how power is distributed, exercised, and constrained within a society.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.