Triple
T24654743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festival Productions, Inc. |
E610355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | music and events production company |
C19240
|
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: music and events production company Context triple: [Festival Productions, Inc., instanceOf, music and events production company]
-
A.
live event production company
chosen
A live event production company plans, coordinates, and executes all technical and creative aspects of concerts, conferences, festivals, and other in-person experiences to deliver seamless, engaging events.
-
B.
management and production company
A management and production company is a business entity that represents and guides talent or projects while overseeing the development, financing, and execution of creative or commercial productions.
-
C.
audiovisual production company
An audiovisual production company is a business that specializes in creating, managing, and delivering multimedia content—such as video, audio, and digital media—for clients across entertainment, advertising, corporate, and educational sectors.
-
D.
leisure and entertainment company
A leisure and entertainment company is an organization that creates, manages, and delivers recreational, cultural, and amusement experiences to consumers through venues, events, media, or activities designed for enjoyment and relaxation.
-
E.
media and hospitality company
A media and hospitality company is an organization that creates, distributes, and monetizes content while simultaneously providing lodging, dining, and experiential services to consumers.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:34 a.m.