Triple
T248568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Society University Research Fellowships |
E5091
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research fellowship program |
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: research fellowship program Context triple: [Royal Society University Research Fellowships, instanceOf, research fellowship program]
-
A.
research fellowship
A research fellowship is a funded, time-limited academic or professional position that supports an individual in conducting specialized research, often under the mentorship of senior experts.
-
B.
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.
-
C.
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.
-
D.
graduate fellowship
A graduate fellowship is a competitive funding award that supports a graduate student's education and research, typically covering tuition and providing a stipend without requiring equivalent work duties.
-
E.
research project
A research project is a structured, systematic investigation designed to answer specific questions or test hypotheses by collecting, analyzing, and interpreting data within a defined scope and timeframe.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.