Triple
T26501801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sugar Hill Mixed-Use Development, Harlem |
E669442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | affordable housing complex |
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: affordable housing complex Context triple: [Sugar Hill Mixed-Use Development, Harlem, instanceOf, affordable housing complex]
-
A.
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.
-
B.
real estate complex
A real estate complex is a group of buildings and associated land, planned and developed as a unified property for residential, commercial, or mixed-use purposes.
-
C.
Section of housing complex
A Section of housing complex represents a distinct physical subdivision within a larger residential development, typically grouping multiple housing units that share common infrastructure, access, and amenities.
-
D.
industrial and residential complex
A mixed-use development that integrates industrial facilities with residential housing, designed to support both production activities and everyday living within a coordinated, shared environment.
-
E.
mixed-income housing model
A mixed-income housing model is a development approach that intentionally combines residential units for households with different income levels within the same community to promote social integration, economic diversity, and housing affordability.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:13 a.m.