Triple
T21091991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VA Home Loan Guaranty Program |
E519659
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal home loan guaranty program |
C357
|
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: federal home loan guaranty program Context triple: [VA Home Loan Guaranty Program, instanceOf, federal home loan guaranty program]
-
A.
Federal Home Loan Bank System program
A Federal Home Loan Bank System program is a government-sponsored initiative that provides low-cost funding and liquidity to member financial institutions to support housing finance and community development.
-
B.
housing agency
A housing agency is an organization that helps people find, secure, and maintain suitable housing by providing listings, guidance, and related support services.
-
C.
federal government program
chosen
A federal government program is an organized set of activities, services, or regulations funded and administered by the national government to achieve specific public policy goals.
-
D.
public housing subsidy program
A public housing subsidy program is a government initiative that provides financial assistance or reduced-cost housing to eligible low-income individuals and families to ensure access to safe, stable, and affordable homes.
-
E.
reverse mortgage program
A reverse mortgage program is a financial arrangement that allows homeowners, typically seniors, to convert part of their home equity into cash payments or a line of credit, which generally does not require repayment until the home is sold, the borrower moves out, or the borrower dies.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:51 p.m.