Triple
T2752846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ORTA |
E61027
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technology transfer statute |
C251
|
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 statute Context triple: [ORTA, instanceOf, technology transfer statute]
-
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.
science and technology policy instrument
A science and technology policy instrument is a deliberate governmental or institutional tool—such as funding programs, regulations, tax incentives, or public–private partnerships—used to influence the direction, pace, and societal impact of scientific research and technological innovation.
-
C.
trade law
Trade law is the body of rules and principles governing the exchange of goods, services, and capital across borders, including treaties, regulations, and dispute resolution mechanisms between nations and commercial entities.
-
D.
statute
chosen
A statute is a formal written law enacted by a legislative body that establishes rules, obligations, or prohibitions within a governing jurisdiction.
-
E.
intelligence law
Intelligence law is the body of legal rules, principles, and oversight mechanisms that govern the collection, analysis, sharing, and use of intelligence by state and related actors to protect national security while safeguarding rights and liberties.
- 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:56 p.m.