Triple
T4242698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Investigator Program awards |
E95451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | competitive grant |
C370
|
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: competitive grant Context triple: [Young Investigator Program awards, instanceOf, competitive grant]
-
A.
competitive funding program
chosen
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.
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.
formula grant program
A formula grant program is a funding mechanism in which money is distributed to eligible recipients based on a predetermined, objective formula (such as population, need, or performance indicators) rather than through a competitive application process.
-
D.
competition policy
Competition policy is the set of laws, regulations, and enforcement practices designed to promote fair market competition, prevent anti-competitive behavior, and protect consumer welfare.
-
E.
competition section
A competition section is a designated part of an event, document, or platform that organizes, presents, and manages information, rules, and results related to specific contests or competitive activities.
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:05 p.m.