Triple
T7935495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRADA |
E184278
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technology transfer mechanism |
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 mechanism Context triple: [CRADA, instanceOf, technology transfer mechanism]
-
A.
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.
-
B.
data transfer mechanism
A data transfer mechanism is a method or system that enables the movement of data between components, systems, or locations while preserving its integrity and intended structure.
-
C.
arms transfer mechanism
An arms transfer mechanism is a system or process that facilitates the legal or illegal movement, sale, or provision of weapons and related military equipment between parties, such as states, organizations, or individuals.
-
D.
trade policy mechanism
A trade policy mechanism is a structured tool or set of rules—such as tariffs, quotas, subsidies, or trade agreements—used by governments to influence international trade flows, prices, and economic outcomes.
-
E.
technical advisory mechanism
A technical advisory mechanism is a structured process or body that provides expert, evidence-based guidance to inform decision-making, policy development, or implementation in a specific technical domain.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:08 p.m.