Triple
T23735801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FEMA Public Assistance Program and Policy Guide |
E586537
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public assistance policy manual |
C34448
|
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 assistance policy manual Context triple: [FEMA Public Assistance Program and Policy Guide, instanceOf, public assistance policy manual]
-
A.
public policy document
chosen
A public policy document is an official written statement issued by a government or public institution that outlines decisions, rules, or strategies intended to address societal issues and guide future actions.
-
B.
public policy office
A public policy office is an organizational unit within a government or institution responsible for researching, developing, analyzing, and coordinating policies to address public issues and guide decision-making.
-
C.
FHA policy manual
The FHA policy manual is an authoritative reference document that consolidates and explains the Federal Housing Administration’s rules, procedures, and eligibility requirements for insured mortgage lending programs.
-
D.
public policy book
A public policy book is a written work that analyzes, explains, or critiques government policies and policymaking processes, often offering frameworks, evidence, and recommendations for addressing societal issues.
-
E.
public policy advisory council
A public policy advisory council is a formal group of experts, stakeholders, and community representatives that provides informed recommendations and analysis to government bodies on policy development and decision-making.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:10 p.m.