Triple
T8291694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Entertainment & Convention Authority |
E193912
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | venue management authority |
C1115
|
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: venue management authority Context triple: [Metropolitan Entertainment & Convention Authority, instanceOf, venue management authority]
-
A.
venue management company
A venue management company is an organization that oversees the operation, booking, maintenance, and commercial performance of event spaces on behalf of their owners.
-
B.
festival venue
A festival venue is a designated location equipped with the infrastructure, amenities, and spatial layout necessary to host large-scale, often multi-day cultural, musical, or artistic events for public audiences.
-
C.
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.
-
D.
hospitality venue
A hospitality venue is a place that provides guests with lodging, food, beverages, and/or entertainment services in a welcoming, service-oriented environment.
-
E.
stadium authority
chosen
A stadium authority is an organization, typically public or quasi-public, responsible for owning, managing, financing, and overseeing the operation and development of a sports or entertainment stadium and its surrounding facilities.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:52 p.m.