Triple
T31690676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Technology Transfer Program |
E808780
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technology transfer initiative |
C23225
|
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: technology transfer initiative Context triple: [Technology Transfer Program, instanceOf, technology transfer initiative]
-
A.
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.
-
B.
technology transfer mechanism
chosen
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.
-
C.
technology transfer office
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.
-
D.
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.
-
E.
transition initiative
A transition initiative is a community-led effort aimed at building local resilience and reducing dependence on fossil fuels by fostering sustainable, low-carbon lifestyles and systems.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:08 p.m.