Triple
T24296695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MECCA complex |
E605976
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-purpose convention and entertainment facility |
C8055
|
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 convention and entertainment facility Context triple: [MECCA complex, instanceOf, multi-purpose convention and entertainment facility]
-
A.
multi-purpose event venue
chosen
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.
-
B.
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.
-
C.
entertainment facility
An entertainment facility is a venue designed and equipped to provide recreational, cultural, or leisure activities to individuals or groups, such as theaters, amusement parks, sports arenas, or gaming centers.
-
D.
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.
-
E.
multi-purpose stadium
A multi-purpose stadium is a large, versatile venue designed to host a variety of events, such as sports games, concerts, and community gatherings, by accommodating different configurations and audiences.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:09 a.m.