Triple
T14508230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FilmRise |
E340323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | independent entertainment company |
C18735
|
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: independent entertainment company Context triple: [FilmRise, instanceOf, independent entertainment company]
-
A.
entertainment holding company
An entertainment holding company is a parent corporation that owns and manages controlling interests in multiple entertainment-related businesses, such as film studios, music labels, streaming platforms, and live event producers, to coordinate strategy and maximize overall value.
-
B.
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.
-
C.
multimedia company
chosen
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.
-
D.
production company
A production company is a business entity that develops, finances, and manages the creation of media content such as films, television shows, music, or digital productions.
-
E.
commercial production company
A commercial production company is a business entity that specializes in planning, filming, and producing video advertisements and branded content for clients across various media platforms.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:21 a.m.