Triple
T17377512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge Enterprise |
E422478
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commercialisation arm of a university |
C2453
|
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: commercialisation arm of a university Context triple: [Cambridge Enterprise, instanceOf, commercialisation arm of a university]
-
A.
commercialization initiative
A commercialization initiative is a coordinated effort or program designed to transform ideas, research, or prototypes into market-ready products or services that generate sustainable economic value.
-
B.
technology transfer office
chosen
A technology transfer office is an organizational unit, typically within a university or research institution, that manages the identification, protection, and commercialization of intellectual property arising from research activities.
-
C.
commercialization program
A commercialization program is a structured initiative that helps transform ideas, research, or prototypes into market-ready products or services through validation, development support, and go-to-market guidance.
-
D.
science and technology university
A science and technology university is a higher education institution focused on advancing knowledge and innovation in scientific, engineering, and technological fields through specialized teaching and research.
-
E.
innovation and knowledge centre
An innovation and knowledge centre is a collaborative hub that integrates research, expertise, and resources to develop, share, and apply new ideas, technologies, and best practices.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:45 a.m.