Triple
T378586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Society Industry Fellowships |
E8625
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collaborative funding scheme |
C365
|
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 funding scheme Context triple: [Royal Society Industry Fellowships, instanceOf, collaborative funding scheme]
-
A.
competitive funding program
A competitive funding program is a structured process in which individuals or organizations submit proposals to vie for limited financial resources, with awards granted based on predefined criteria and comparative merit.
-
B.
fellowship program
chosen
A fellowship program is a structured, time-bound opportunity that provides individuals with financial support, mentorship, and professional development to advance their skills, research, or leadership in a specific field.
-
C.
philanthropic campaign
A philanthropic campaign is a coordinated effort designed to raise awareness, funds, or resources to support charitable causes and drive positive social impact.
-
D.
research grant program
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.
-
E.
university collaboration
University collaboration is the structured partnership between universities and external entities (such as other academic institutions, industry, government, or communities) to jointly pursue research, education, innovation, and resource sharing.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.