Triple
T12665028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skydance Animation |
E302527
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of Skydance Media |
C9104
|
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: division of Skydance Media Context triple: [Skydance Animation, instanceOf, division of Skydance Media]
-
A.
division of The Walt Disney Company
A division of The Walt Disney Company is an organizational unit within the corporation responsible for managing a specific line of business, brand portfolio, or operational function under Disney’s overall corporate structure.
-
B.
film production company division
chosen
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.
division of Warner Bros.
A division of Warner Bros. is a distinct organizational unit within the company responsible for specific entertainment functions such as film production, television, animation, or interactive media.
-
D.
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.
-
E.
streaming media division
A streaming media division is an organizational unit within a company responsible for acquiring, producing, managing, and distributing digital audio and video content over internet-based streaming 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:19 p.m.