Triple
T5325208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project-Based Voucher Program |
E121768
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rental subsidy program |
C17919
|
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: rental subsidy program Context triple: [Project-Based Voucher Program, instanceOf, rental subsidy program]
-
A.
hospitality housing program
A hospitality housing program is an organized initiative that provides temporary, welcoming accommodations—often at low or no cost—to guests such as travelers, patients, or families in need, typically through partnerships with hosts, institutions, or community organizations.
-
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.
loan program
A loan program is a structured financial offering that provides borrowers with funds under defined terms, such as interest rates, repayment schedules, and eligibility criteria, to support specific purposes like education, housing, or business development.
-
D.
public employment program
A public employment program is a government-initiated scheme that directly creates temporary or permanent jobs, typically in public works or community services, to reduce unemployment and support income for targeted populations.
-
E.
municipal program
A municipal program is an organized set of services, initiatives, or activities implemented and managed by a local government to address community needs and improve public welfare within its jurisdiction.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 1:59 p.m.