Triple
T2213528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge Service Alliance |
E50970
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | industry–university partnership |
C343
|
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: industry–university partnership Context triple: [Cambridge Service Alliance, instanceOf, industry–university partnership]
-
A.
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.
-
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.
university institute
A university institute is an organizational unit within a university that focuses on specialized research, education, and collaboration in a particular academic or interdisciplinary field.
-
D.
research consortium
chosen
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.
public institution
A public institution is an organization established and funded by the government to provide services, regulation, or governance for the benefit of the general public.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
Created at: March 4, 2026, 7:46 p.m.