Triple
T30051530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Jetsons Meet the Flintstones |
E763614
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | animated crossover television film |
C56674
|
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: animated crossover television film Context triple: [The Jetsons Meet the Flintstones, instanceOf, animated crossover television film]
-
A.
monster crossover film
A monster crossover film is a movie that brings together two or more established monster characters or franchises into a single shared narrative, often pitting them against each other or uniting them against a common threat.
-
B.
animated superhero film
An animated superhero film is a motion picture that uses animation to depict characters with extraordinary abilities engaging in heroic adventures, often blending action, fantasy, and comic-book-inspired storytelling.
-
C.
animated television franchise
An animated television franchise is a series of related animated TV shows, often spanning multiple seasons, spin-offs, and media tie-ins, that share common characters, settings, or storylines under a unified brand.
-
D.
animated television special
An animated television special is a standalone, longer-than-standard TV program that uses animation to tell a self-contained story, often produced for a specific event, holiday, or promotional occasion.
-
E.
animated film series
An animated film series is a collection of related animated movies that share common characters, settings, or storylines, released over time as a continuing franchise.
- F. None of above. chosen
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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 6:55 p.m.