Triple
T30053821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CU |
E763672
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university system in the United States |
C8236
|
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: university system in the United States Context triple: [CU, instanceOf, university system in the United States]
-
A.
university system
chosen
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.
-
B.
collegiate university system
A collegiate university system is a higher education structure in which a central university is composed of semi-autonomous constituent colleges that share academic standards and degrees while maintaining their own governance, finances, and community life.
-
C.
state university system
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.
public state university
A public state university is a higher education institution primarily funded and overseen by a state government, offering undergraduate and graduate programs to a broad population, often at reduced tuition for in-state residents.
-
E.
university system headquarters
The university system headquarters is the central administrative entity that oversees, coordinates, and supports the policies, operations, and strategic direction of all institutions within a multi-campus university system.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 6:56 p.m.