Triple
T2692430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exhibition Place |
E58433
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-purpose event complex |
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 event complex Context triple: [Exhibition Place, instanceOf, multi-purpose event complex]
-
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.
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.
-
C.
entertainment complex
An entertainment complex is a large, multi-purpose facility that combines various leisure, recreational, and cultural attractions—such as cinemas, theaters, restaurants, gaming areas, and event spaces—within a single integrated venue.
-
D.
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.
-
E.
conference center
A conference center is a large, purpose-built facility designed to host meetings, conventions, exhibitions, and other events, providing flexible spaces and supporting services for groups of various sizes.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
Created at: March 6, 2026, 9:54 p.m.