Triple
T38369098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yahoo! Studios |
E892529
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital media production company division |
C53533
|
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: digital media production company division Context triple: [Yahoo! Studios, instanceOf, digital media production company division]
-
A.
media production company division
chosen
A media production company division is an organizational unit within a media company responsible for planning, creating, and managing specific types of content or production activities, such as film, television, digital media, or advertising.
-
B.
film production company division
A film production company division is a specialized organizational unit within a larger film company responsible for developing, producing, and sometimes distributing specific types or slates of film projects.
-
C.
cultural and entertainment company division
A cultural and entertainment company division is an organizational unit within a larger enterprise that develops, manages, and delivers cultural, artistic, and entertainment products or services to targeted audiences.
-
D.
online advertising company division
A specialized unit within an online advertising company responsible for planning, executing, optimizing, and analyzing digital ad campaigns for specific markets, products, or client segments.
-
E.
video production company
A video production company is a business that specializes in planning, filming, and editing video content for clients such as businesses, organizations, and individuals.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.