Triple
T11378397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Pictures Home Entertainment |
E269528
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | home entertainment company |
C10376
|
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: home entertainment company Context triple: [Universal Pictures Home Entertainment, instanceOf, home entertainment company]
-
A.
home entertainment division
chosen
The home entertainment division is the organizational unit responsible for producing, acquiring, and distributing entertainment content and related products for in-home consumption across physical and digital platforms.
-
B.
television company
A television company is an organization that produces, acquires, schedules, and broadcasts television content to audiences through various distribution channels such as terrestrial, cable, satellite, or streaming platforms.
-
C.
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.
-
D.
television distribution company
A television distribution company is an organization that acquires, packages, and delivers TV content to broadcasters, streaming platforms, and other outlets across various regions and markets.
-
E.
media franchise company
A media franchise company is an organization that creates, owns, manages, and licenses interconnected entertainment properties (such as films, TV shows, games, and merchandise) under shared brands, characters, or story universes.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:33 p.m.