Triple
T26525058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney direct-to-video films |
E670665
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disney media franchise segment |
C35252
|
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: Disney media franchise segment Context triple: [Disney direct-to-video films, instanceOf, Disney media franchise segment]
-
A.
Disney media franchise setting
A Disney media franchise setting is a cohesive fictional world or universe, originating from Disney properties, that provides the shared backdrop, rules, and locations for interconnected stories, characters, and media products.
-
B.
Disney film series
chosen
A Disney film series is a collection of related movies produced or distributed by The Walt Disney Company that share common characters, settings, or narrative continuity.
-
C.
Disney entertainment production
Disney entertainment production is the process by which The Walt Disney Company develops, finances, and creates films, television shows, stage productions, and related media content under its various brands and studios.
-
D.
Disney brand
The Disney brand is a globally recognized entertainment and media identity that represents family-friendly storytelling, beloved characters, immersive experiences, and nostalgic magic across films, television, theme parks, merchandise, and digital platforms.
-
E.
Disney film category
A Disney film category is a classification grouping Disney-produced or Disney-distributed movies based on shared characteristics such as genre, era, franchise, target audience, or thematic content.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:31 a.m.