Triple
T30355779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knowledge Transfer Partnerships |
E772139
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | knowledge transfer scheme |
C27200
|
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: knowledge transfer scheme Context triple: [Knowledge Transfer Partnerships, instanceOf, knowledge transfer scheme]
-
A.
technology transfer mechanism
A technology transfer mechanism is a structured process or tool that facilitates the movement of knowledge, inventions, or innovations from their creators to external parties for practical application and commercialization.
-
B.
technology transfer mission
A technology transfer mission is a coordinated effort to share, adapt, and implement knowledge, tools, or innovations from one organization or context to another to enhance capabilities and outcomes.
-
C.
academic–industry collaboration scheme
chosen
An academic–industry collaboration scheme is a structured framework that facilitates joint research, knowledge transfer, and innovation between universities and commercial organizations through coordinated projects, funding mechanisms, and shared resources.
-
D.
standardization scheme
A standardization scheme is a structured framework of rules, formats, and procedures designed to ensure consistency, compatibility, and interoperability across systems, processes, or data.
-
E.
knowledge society initiative
A knowledge society initiative is a coordinated program or policy framework aimed at fostering the creation, sharing, and effective use of knowledge across society to drive innovation, inclusion, and sustainable development.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:57 p.m.