Triple
T29018288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard Material Transfer Agreement |
E737378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | material transfer agreement |
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: material transfer agreement Context triple: [Standard Material Transfer Agreement, instanceOf, material transfer agreement]
-
A.
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.
-
B.
collaborative research and development agreement
A collaborative research and development agreement is a contract between two or more parties that defines how they will jointly conduct R&D activities, share resources, allocate intellectual property rights, and manage risks and responsibilities.
-
C.
shipping safety agreement
A shipping safety agreement is a formal contract between parties in the supply chain that defines responsibilities, standards, and procedures to prevent accidents, protect cargo, and ensure compliance with safety regulations during transportation.
-
D.
shipping safety agreement
A shipping safety agreement is a formal contract between parties in the supply chain that defines responsibilities, standards, and procedures to ensure the safe handling, transport, and delivery of goods.
-
E.
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.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 9:47 a.m.