Triple
T9946340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title IV—Emergency Management Performance Grants |
E195213
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | grant authorization program |
C6390
|
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 authorization program Context triple: [Title IV—Emergency Management Performance Grants, instanceOf, grant authorization program]
-
A.
grant management system
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.
-
B.
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.
-
C.
formula grant program
chosen
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.
appointing authority
An appointing authority is an individual or entity legally empowered to select, hire, promote, or otherwise make official personnel decisions for positions within an organization or governmental body.
-
E.
royal authorization
Royal authorization is the formal approval or sanction granted by a monarch that legitimizes specific actions, decisions, or privileges within a realm.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:45 p.m.