Triple
T25619132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 101 Collins Street, Melbourne (fit‑outs and refurbishments) |
E642243
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commercial interior fit‑out program |
C42523
|
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: commercial interior fit‑out program Context triple: [101 Collins Street, Melbourne (fit‑outs and refurbishments), instanceOf, commercial interior fit‑out program]
-
A.
commercial building projects
chosen
Commercial building projects are organized efforts to plan, design, finance, construct, and deliver structures intended primarily for business, retail, office, or other non-residential commercial uses.
-
B.
commercial park
A commercial park is a planned area of land developed with multiple business facilities—such as offices, retail spaces, and light industrial units—designed to support commercial activities within a cohesive, often landscaped environment.
-
C.
commercial façade
A commercial façade is the outward-facing exterior of a commercial building, designed to present a visual identity, attract customers, and often comply with branding and regulatory requirements.
-
D.
commercial real estate
Commercial real estate encompasses properties used primarily for business activities, such as offices, retail spaces, industrial facilities, and multifamily housing, that generate income through leasing, operations, or capital appreciation.
-
E.
Commercial unit
A Commercial unit represents a standardized quantity, package, or configuration of a product defined for sale, pricing, and transaction purposes in a commercial context.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 5:02 p.m.