Triple
T9617555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney Live Entertainment |
E232255
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | live entertainment 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: live entertainment production company Context triple: [Disney Live Entertainment, instanceOf, live entertainment 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.
television production company
A television production company is an organization that develops, finances, and produces television content such as series, specials, and documentaries for broadcast, cable, or streaming platforms.
-
D.
entertainment producer
An entertainment producer is a professional who oversees the development, financing, coordination, and execution of entertainment projects such as films, television shows, music, or live events from concept to completion.
-
E.
multimedia company
A multimedia company is an organization that creates, produces, and distributes content across multiple media formats—such as video, audio, text, and interactive platforms—to inform, entertain, or engage audiences.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:09 p.m.