Triple
T6044277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hannibal (TV series) – referenced/alternate continuity |
E134626
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | television series continuity |
C19816
|
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 series continuity Context triple: [Hannibal (TV series) – referenced/alternate continuity, instanceOf, television series continuity]
-
A.
Star Trek continuity
Star Trek continuity is the cohesive, evolving narrative framework that connects the events, characters, timelines, and canon across all Star Trek series and films into a shared fictional universe.
-
B.
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.
-
C.
television series organization
A television series organization is an entity responsible for the planning, production, coordination, and management of all creative, technical, and logistical aspects involved in creating and distributing a TV series.
-
D.
television episode
A television episode is a single, self-contained installment of a television series that contributes to an ongoing narrative or theme and is typically broadcast or streamed as part of a scheduled sequence.
-
E.
television season
A television season is a collection of episodes of a TV series that are produced and broadcast as a cohesive unit within a specific time frame, often following a continuous storyline or thematic arc.
- 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:09 p.m.