Triple
T15150907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Academy of Engineering Enterprise Hub partners |
E361937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | innovation support network |
C36035
|
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: innovation support network Context triple: [Royal Academy of Engineering Enterprise Hub partners, instanceOf, innovation support network]
-
A.
innovation agency
An innovation agency is an organization that helps businesses or institutions identify opportunities, develop new ideas, and implement creative solutions to drive growth and transformation.
-
B.
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.
-
C.
innovation partnership
An innovation partnership is a collaborative relationship between organizations or individuals formed to co-create, develop, and implement new ideas, technologies, or solutions that deliver mutual value.
-
D.
innovation and entrepreneurship space
A dynamic, collaborative environment that provides resources, mentorship, and networking opportunities to help individuals and teams develop, test, and launch innovative ideas and entrepreneurial ventures.
-
E.
Knowledge and Innovation Community
A Knowledge and Innovation Community is an ecosystem that brings together academic, industrial, and entrepreneurial actors to collaboratively generate, share, and apply knowledge for innovative solutions and sustainable economic and social impact.
- F. None of above. chosen
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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:07 a.m.