Triple
T4828995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claremont Colleges |
E107896
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college consortium |
C9354
|
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: college consortium Context triple: [Claremont Colleges, instanceOf, college consortium]
-
A.
consortium of colleges
chosen
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.
-
B.
university association
A university association is an organized group within a higher education institution that brings together students, staff, or alumni around shared academic, professional, cultural, or social interests to provide support, activities, and representation.
-
C.
group of institutions
A group of institutions is a collection of formally organized entities, such as schools, hospitals, or government bodies, that are associated or coordinated for a common purpose or function.
-
D.
research consortium
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
-
E.
university collaboration
University collaboration is the structured partnership between universities and external entities (such as other academic institutions, industry, government, or communities) to jointly pursue research, education, innovation, and resource sharing.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:24 p.m.