Triple
T19451011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MFi |
E486613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technology licensing program |
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 licensing program Context triple: [MFi, instanceOf, technology licensing program]
-
A.
Microsoft licensing program
A Microsoft licensing program is a structured framework through which Microsoft offers, manages, and enforces the terms, pricing, and distribution of its software and cloud service licenses to organizations and individuals.
-
B.
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.
-
C.
conference licensing program
A conference licensing program is a structured framework that grants organizations or individuals the rights to host, brand, or replicate an established conference format under specified terms and conditions.
-
D.
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.
-
E.
proprietary license
A proprietary license is a legal agreement that grants users limited rights to use, but not freely modify or redistribute, software or other intellectual property owned and controlled by a specific individual or organization.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:38 p.m.