Triple
T29655911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DreamHack |
E750262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital festival organizer |
C56036
|
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: digital festival organizer Context triple: [DreamHack, instanceOf, digital festival organizer]
-
A.
festival organization
Festival organization is the coordinated planning, management, and execution of all logistical, financial, promotional, and experiential aspects required to design and deliver a successful festival event.
-
B.
virtual event management platform
A virtual event management platform is a digital system that enables organizations to plan, host, manage, and analyze online events such as conferences, webinars, and trade shows through integrated tools for registration, content delivery, engagement, and reporting.
-
C.
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.
-
D.
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.
-
E.
music festival association
A music festival association is an organized entity that plans, coordinates, and promotes music festivals, often representing the interests of artists, venues, sponsors, and attendees.
- F. None of above. chosen
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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 6:55 p.m.