Triple
T17385491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of York collegiate system |
E422677
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collegiate system |
C5309
|
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: collegiate system Context triple: [University of York collegiate system, instanceOf, collegiate system]
-
A.
collegiate university system
chosen
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.
-
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.
collegiate residential system
A collegiate residential system is an organized network of on-campus living communities that integrate housing, academic support, and social programming to foster student engagement and development.
-
D.
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.
-
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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:45 a.m.