Triple
T3327675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakubva |
E69955
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-density residential area |
C5457
|
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: high-density residential area Context triple: [Sakubva, instanceOf, high-density residential area]
-
A.
planned residential community
A planned residential community is a deliberately designed neighborhood or development where housing, infrastructure, amenities, and land use are pre-organized to create a cohesive living environment.
-
B.
inner-city area
chosen
An inner-city area is a densely populated, centrally located urban district typically characterized by older infrastructure, mixed residential and commercial land use, and often higher levels of socioeconomic challenges.
-
C.
multi-family residential property
A multi-family residential property is a single real estate asset containing multiple separate housing units, such as duplexes, townhomes, or apartment buildings, designed to accommodate more than one household.
-
D.
former residential neighborhood
A former residential neighborhood is an area that once contained homes and community life but has since been depopulated, demolished, repurposed, or otherwise ceased to function as a residential district.
-
E.
urban-type settlement
An urban-type settlement is a semi-urban locality that exhibits some characteristics of a town or small city—such as concentrated housing, infrastructure, and non-agricultural employment—without meeting all the criteria for full city status.
- 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_69ad85a1829881908942c14075644d0d |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:12 p.m.