Triple
T14320080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Performances Birmingham Limited |
E355060
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | arts and events management company |
C20259
|
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: arts and events management company Context triple: [Performances Birmingham Limited, instanceOf, arts and events management company]
-
A.
hybrid event management platform
A hybrid event management platform is a unified system that enables planning, hosting, and analyzing events that combine in-person and virtual experiences, including registration, engagement tools, content delivery, and post-event analytics.
-
B.
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.
-
C.
event management app
An event management app is a software application that helps users plan, organize, promote, and track events by managing tasks such as scheduling, registrations, ticketing, communication, and attendee engagement.
-
D.
arts organisation
chosen
An arts organisation is an entity that supports, produces, presents, or promotes artistic and cultural activities, often serving as a hub connecting artists, audiences, and communities.
-
E.
virtual event management platform
A virtual event management platform is a software system that enables organizations to plan, host, manage, and analyze online events by integrating registration, content delivery, engagement tools, and post-event analytics in a unified digital environment.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:13 a.m.