Triple
T30687770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American television franchises |
E781233
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | television franchise category |
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: television franchise category Context triple: [American television franchises, instanceOf, television franchise category]
-
A.
television series
A television series is a serialized audiovisual narrative or program produced for broadcast or streaming, released in multiple episodes often organized into seasons.
-
B.
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.
-
C.
television franchise race
A television franchise race is a recurring competitive event or series within a TV franchise where participants vie for victory across multiple episodes or seasons, often sharing themes, rules, and branding under the same overarching show universe.
-
D.
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.
-
E.
television programming category
A television programming category is a conceptual classification that groups TV shows and content based on shared characteristics such as genre, format, target audience, or thematic elements.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:33 p.m.