Triple
T27467248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilversum public housing projects |
E693209
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public housing development program |
C41059
|
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 housing development program Context triple: [Hilversum public housing projects, instanceOf, public housing development program]
-
A.
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.
-
B.
affordable housing project
chosen
An affordable housing project is a planned development that provides safe, decent, and financially accessible homes to low- and moderate-income individuals or families, often supported by public subsidies or incentives.
-
C.
housing plan
A housing plan is a detailed architectural and spatial blueprint outlining the design, layout, and organization of residential living spaces within a building or development.
-
D.
rental subsidy program
A rental subsidy program is a structured initiative that provides financial assistance to eligible individuals or households to help cover a portion of their housing costs and make rental housing more affordable.
-
E.
social housing ensemble
A social housing ensemble is a cohesive group of residential buildings and shared spaces designed to provide affordable, community-oriented living for diverse populations within an integrated urban or suburban setting.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 12:52 p.m.