Triple
T26545929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idaho state higher education system |
E671531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | statewide postsecondary education system |
C435
|
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: statewide postsecondary education system Context triple: [Idaho state higher education system, instanceOf, statewide postsecondary education system]
-
A.
state system
A state system is a structured framework in which distinct political entities (states) interact under shared norms, rules, and institutions that regulate their behavior and relationships.
-
B.
statewide school system
A statewide school system is a coordinated network of public educational institutions, policies, and administrative bodies that operate under a unified state authority to provide standardized education across all regions within the state.
-
C.
state university system
chosen
A state university system is a coordinated network of public higher education institutions within a state, governed by a central authority to manage funding, policy, and academic standards.
-
D.
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.
-
E.
community college system
A community college system is a coordinated network of publicly funded two-year colleges that collectively provide accessible, affordable postsecondary education, vocational training, and transfer pathways within a defined region or state.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:44 a.m.