Triple
T13324072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgetown Park shopping complex |
E317390
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mixed-use retail center |
C24772
|
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: mixed-use retail center Context triple: [Georgetown Park shopping complex, instanceOf, mixed-use retail center]
-
A.
mixed-use lifestyle center
A mixed-use lifestyle center is a planned development that combines retail, dining, entertainment, residential, and often office spaces in a walkable, open-air environment designed to create a vibrant, community-oriented destination.
-
B.
mixed-use development district
A mixed-use development district is a designated urban area that intentionally combines residential, commercial, recreational, and sometimes industrial uses within a walkable, integrated environment to promote vibrant, efficient, and sustainable community life.
-
C.
mixed-use skyscraper complex
A mixed-use skyscraper complex is a vertically integrated high-rise development that combines residential, commercial, office, and often recreational or civic functions within a unified architectural and infrastructural framework.
-
D.
shopping centre
A shopping centre is a large complex of retail stores, services, and often entertainment facilities planned and managed as a single commercial property.
-
E.
commercial and residential complex
chosen
A commercial and residential complex is a mixed-use development that integrates living spaces with retail, office, and service facilities within a unified property or group of buildings.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:30 p.m.