Triple
T34569059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacksonville riverfront estates |
E887570
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | residential community type |
C5974
|
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: residential community type Context triple: [Jacksonville riverfront estates, instanceOf, residential community type]
-
A.
planned residential community
chosen
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.
residential building type
A residential building type is a category of structures designed primarily for people to live in, characterized by specific forms, layouts, and occupancy patterns such as single-family homes, apartments, or townhouses.
-
C.
communal residence
A communal residence is a shared living arrangement where multiple unrelated individuals or families cohabit a single property, pooling certain resources, spaces, and responsibilities while maintaining varying degrees of personal privacy.
-
D.
Residential district
A residential district is an area of a city or town primarily designated for housing, where people live in various types of dwellings and are supported by local amenities and services.
-
E.
residential cooperative
A residential cooperative is a housing arrangement where residents collectively own and manage the property through a cooperative corporation, holding shares that entitle them to occupy specific units.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.