Triple
T22079840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan Historical Commission |
E545619
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state historical commission |
C3980
|
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 historical commission Context triple: [Michigan Historical Commission, instanceOf, state historical commission]
-
A.
historic preservation commission
A historic preservation commission is a governing body that identifies, protects, and regulates historically significant buildings, sites, and districts within a community.
-
B.
state government commission
chosen
A state government commission is an officially authorized body established by a state to investigate, regulate, advise on, or administer specific public policy areas or functions within its jurisdiction.
-
C.
heritage committee
A heritage committee is a group of appointed or elected individuals responsible for identifying, preserving, and advising on the protection and promotion of cultural, historical, or natural heritage resources within a community or organization.
-
D.
California state historic preservation program
The California state historic preservation program is a government-led initiative that identifies, protects, and promotes the state’s historically and culturally significant buildings, sites, and landscapes through designation, regulation, and public support.
-
E.
historic state
A historic state is a former political entity or government that once exercised sovereignty over a defined territory and population but has since ceased to exist in its original form.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:28 p.m.