Triple
T38452631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. federal government appropriations via NIH |
E912214
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public research funding mechanism |
C20722
|
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: public research funding mechanism Context triple: [U.S. federal government appropriations via NIH, instanceOf, public research funding mechanism]
-
A.
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.
-
B.
arts funding mechanism
An arts funding mechanism is a structured method or system through which financial resources are allocated to support the creation, presentation, and preservation of artistic work.
-
C.
public funding body
chosen
A public funding body is a government or publicly mandated organization that allocates financial resources to support projects, institutions, or activities in line with public policy goals and societal needs.
-
D.
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.
-
E.
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.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:31 p.m.