Triple
T12506462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COFUND |
E298960
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research funding programme |
C369
|
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: research funding programme Context triple: [COFUND, instanceOf, research funding programme]
-
A.
research grant program
chosen
A research grant program is a structured funding initiative that provides financial support to researchers or institutions to conduct specific scholarly, scientific, or creative projects aligned with defined goals and priorities.
-
B.
scientific research support program
A scientific research support program is an organized initiative that provides resources, funding, infrastructure, and guidance to facilitate the planning, execution, and dissemination of scientific studies.
-
C.
nuclear research funding programme
A nuclear research funding programme is an organized initiative that allocates financial and institutional resources to support scientific, technological, and safety-related research in the field of nuclear energy and radiation applications.
-
D.
research center program
A research center program is an organized initiative within a research institution that coordinates projects, resources, and collaborations to advance inquiry and innovation in a specific field or set of related disciplines.
-
E.
research funding organization
A research funding organization is an entity that allocates financial resources and support to scientific or scholarly projects, typically through competitive grants, to advance knowledge and innovation.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:57 p.m.