Triple
T20681313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Poppins franchise |
E508299
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | children's media franchise |
C4316
|
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: children's media franchise Context triple: [Mary Poppins franchise, instanceOf, children's media franchise]
-
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.
media franchise
chosen
A media franchise is a collection of related creative works and products—such as films, TV shows, books, games, and merchandise—built around shared characters, settings, or storylines and managed as a unified commercial property.
-
C.
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.
-
D.
media franchise tie-in
A media franchise tie-in is a product, work, or piece of content created to promote, expand, or capitalize on an existing franchise across different media formats.
-
E.
Power franchise television series
A Power franchise television series is a serialized drama set within the shared Power universe that expands its crime-driven narrative through interconnected characters, timelines, and storylines across multiple spin-off shows.
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:45 a.m.