Triple
T3151464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge University colleges |
E65886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | constituent college 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: constituent college system Context triple: [Cambridge University colleges, instanceOf, constituent college system]
-
A.
constituent college
A constituent college is an institution that forms an integral part of a larger university or educational system, operating under its governance while providing specific academic programs or services.
-
B.
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.
-
C.
consortium of colleges
A consortium of colleges is a collaborative association of independent higher education institutions that coordinate resources, programs, and services to enhance academic offerings and operational efficiency for their students and faculty.
-
D.
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.
-
E.
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.
- 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_69ad8584485081909ed529e890cadc4a |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:05 p.m.