Triple
T8464640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Board of Regents system |
E200129
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | higher education governance system |
C2463
|
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: higher education governance system Context triple: [Iowa Board of Regents system, instanceOf, higher education governance system]
-
A.
higher education system segment
A higher education system segment is a distinct subset of institutions, programs, or stakeholders within the broader higher education landscape that share common characteristics, functions, or target populations.
-
B.
university system
A university system is an integrated organizational framework that manages academic programs, students, faculty, resources, and administrative processes across one or more higher education institutions.
-
C.
university governing body
A university governing body is a formal group of appointed or elected individuals responsible for setting the institution’s strategic direction, overseeing its policies and finances, and ensuring accountability and compliance with legal and educational standards.
-
D.
higher education agency
chosen
A higher education agency is an organization responsible for overseeing, coordinating, regulating, or supporting postsecondary institutions and policies within a specific jurisdiction or sector.
-
E.
higher education organization
A higher education organization is an institution that provides post-secondary academic or professional education, conducts research, and grants recognized degrees or certifications.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:11 p.m.