Triple
T16623380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Invasion! (Arrowverse) |
E403885
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | television crossover event |
C4879
|
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 crossover event Context triple: [Invasion! (Arrowverse), instanceOf, television crossover event]
-
A.
television event
chosen
A television event is a scheduled broadcast program or special presentation designed for viewing on television, often characterized by its significance, live nature, or anticipated large audience.
-
B.
comic book crossover event
A comic book crossover event is a large-scale storyline that spans multiple series or titles, bringing together characters and plots from different books into a single, interconnected narrative.
-
C.
televisionPlotEvent
A televisionPlotEvent represents a discrete narrative occurrence or turning point within a television episode or series that advances the storyline, develops characters, or alters the dramatic situation.
-
D.
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.
-
E.
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.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:17 a.m.