Triple
T24839485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan State Administrative Board |
E621576
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state administrative board |
C49626
|
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 administrative board Context triple: [Michigan State Administrative Board, instanceOf, state administrative board]
-
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.
state transportation board
A state transportation board is a governing body that oversees planning, funding, and policy decisions for a state’s transportation systems and infrastructure.
-
C.
state regulatory agency
A state regulatory agency is a government body at the state level responsible for creating, implementing, and enforcing rules and standards within specific sectors (such as utilities, health, or finance) to protect the public interest and ensure legal compliance.
-
D.
California state board
A California state board is an official governing or advisory body established by state law to oversee, regulate, or provide guidance on specific public policy areas, professions, or services within California.
-
E.
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.
- F. None of above. chosen
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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:18 a.m.