Triple
T5950806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Integrated Disbursement and Information System |
E132392
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | grant management system |
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: grant management system Context triple: [Integrated Disbursement and Information System, instanceOf, grant management system]
-
A.
grant administration guide
A grant administration guide is a comprehensive reference that outlines the policies, procedures, and best practices for managing grants throughout their lifecycle, from application and award through implementation, reporting, and closeout.
-
B.
package management system
A package management system is a tool that automates the processes of finding, installing, upgrading, configuring, and removing software packages and their dependencies in a consistent and reliable way.
-
C.
management system structure
A management system structure is the organized framework of roles, processes, and relationships that coordinate resources and activities to achieve an organization’s objectives efficiently and consistently.
-
D.
administrative authority
An administrative authority is an organization or body empowered by law or policy to implement, manage, and enforce rules, regulations, and public administration decisions within a defined jurisdiction.
-
E.
authorization framework
An authorization framework is a structured system of rules, components, and processes that determines and enforces what actions users or services are permitted to perform on protected resources.
- F. None of above. chosen
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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:02 p.m.