Triple
T4027238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champlain Towers South condominium |
E83619
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | residential condominium building |
C9953
|
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 condominium building Context triple: [Champlain Towers South condominium, instanceOf, residential condominium building]
-
A.
luxury condominium tower
A luxury condominium tower is a high-rise residential building offering upscale, privately owned units with premium amenities, services, and finishes in a prestigious urban location.
-
B.
multi-family residential property
chosen
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.
-
C.
residential palace building
A residential palace building is a grand, often historically or culturally significant dwelling designed to house royalty, nobility, or other high-status residents, featuring luxurious architecture, expansive interiors, and formal reception spaces.
-
D.
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.
-
E.
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.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:36 p.m.