Triple
T16623329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elseworlds (Arrowverse) |
E403884
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arrowverse crossover event |
C38138
|
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: Arrowverse crossover event Context triple: [Elseworlds (Arrowverse), instanceOf, Arrowverse crossover event]
-
A.
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.
-
B.
Marvel Comics crossover event
A Marvel Comics crossover event is a large-scale storyline that spans multiple comic book series, bringing together various characters and plotlines into a single, interconnected narrative.
-
C.
superhero series
A superhero series is a narrative work, often episodic, that follows characters with extraordinary abilities as they confront threats, explore moral dilemmas, and protect their world or community.
-
D.
DC Comics superhero franchise
A DC Comics superhero franchise is a multimedia entertainment property centered on one or more DC superheroes, spanning comic books, films, television, games, and related merchandise within a shared fictional universe.
-
E.
Marvel Cinematic Universe organization
A Marvel Cinematic Universe organization is a structured group or agency within the MCU, composed of characters united by a common purpose, hierarchy, and resources that influence the franchise’s overarching narrative and events.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:17 a.m.