Triple
T14840908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DreamWorks Animation Home Entertainment |
E348960
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | home entertainment label |
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 label Context triple: [DreamWorks Animation Home Entertainment, instanceOf, home entertainment label]
-
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.
film label
A film label is a brand or imprint under which movies are produced, marketed, and distributed, often reflecting a specific style, genre focus, or target audience.
-
C.
entertainment market segment
An entertainment market segment is a distinct group of consumers within the broader entertainment industry who share similar preferences, behaviors, and demographic or psychographic characteristics, allowing for targeted content, marketing, and distribution strategies.
-
D.
entertainment media brand
An entertainment media brand is an identity that creates, curates, and distributes engaging content across platforms to attract, retain, and monetize an audience through distinctive storytelling and experiences.
-
E.
entertainment media
Entertainment media encompasses various forms of content—such as film, television, music, games, and digital platforms—created and distributed to engage, amuse, and emotionally or intellectually stimulate 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:53 a.m.