Triple
T7935494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRADA |
E184278
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collaborative research and development agreement |
C23224
|
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: collaborative research and development agreement Context triple: [CRADA, instanceOf, collaborative research and development agreement]
-
A.
partnership agreement
A partnership agreement is a legally binding contract between two or more parties that defines their business relationship, including ownership shares, roles, responsibilities, profit and loss distribution, and procedures for decision-making and dispute resolution.
-
B.
research and development organization
A research and development organization is an entity dedicated to systematically investigating ideas and technologies to create new knowledge, products, or processes and improve existing ones.
-
C.
scientific collaboration board
A scientific collaboration board is a shared digital or physical workspace where researchers coordinate projects, exchange data and ideas, track progress, and manage collaborative tasks across institutions and disciplines.
-
D.
innovation partnership
An innovation partnership is a collaborative relationship between organizations or individuals formed to co-create, develop, and implement new ideas, technologies, or solutions that deliver mutual value.
-
E.
research consortium
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
- 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.