Triple
T20006157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oracle Grants Accounting |
E494465
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | grants management software |
C19626
|
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: grants management software Context triple: [Oracle Grants Accounting, instanceOf, grants management software]
-
A.
library grant program
A library grant program is a structured funding initiative that provides financial support to libraries for projects, resources, services, or infrastructure that enhance community access to information, education, and cultural enrichment.
-
B.
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.
-
C.
grant management system
chosen
A grant management system is a software platform that streamlines the end-to-end lifecycle of grants, from application and review through award, monitoring, reporting, and closeout.
-
D.
management program
A management program is a structured software or organizational system designed to plan, coordinate, monitor, and optimize resources, processes, and activities to achieve specific goals efficiently.
-
E.
subaward reporting system
A subaward reporting system is a centralized platform that collects, validates, and manages detailed information about subawards to ensure compliance, transparency, and accurate tracking of funds across prime and sub-recipient organizations.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:33 p.m.