Triple
T15641741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TMU Recreation and Athletic Centre |
E376083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-purpose recreation centre |
C242
|
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: multi-purpose recreation centre Context triple: [TMU Recreation and Athletic Centre, instanceOf, multi-purpose recreation centre]
-
A.
multi-purpose facility
A multi-purpose facility is a versatile building or space designed to support a wide range of activities, events, and functions through adaptable layouts and shared resources.
-
B.
sports and recreation facility
chosen
A sports and recreation facility is a place designed and equipped for individuals or groups to engage in physical activities, sports, exercise, and leisure pursuits.
-
C.
multi-purpose event venue
A multi-purpose event venue is a flexible space designed to accommodate a wide range of gatherings—such as conferences, concerts, weddings, and exhibitions—by offering adaptable layouts, technical infrastructure, and support services.
-
D.
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.
-
E.
convention center
A convention center is a large, purpose-built facility designed to host conferences, trade shows, exhibitions, and other large-scale events, providing flexible meeting spaces and supporting 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:15 a.m.