Triple
T30597462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Runs Out |
E778825
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Avengers storyline |
C25620
|
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: Avengers storyline Context triple: [Time Runs Out, instanceOf, Avengers storyline]
-
A.
Avengers branch
An Avengers branch is a regional or specialized subdivision of the Avengers organization, formed to address localized threats and missions while operating under the broader Avengers framework.
-
B.
Marvel Comics storyline
chosen
A Marvel Comics storyline is a connected sequence of comic book issues that together tell a cohesive narrative within the Marvel Universe, often featuring recurring characters, overarching plots, and sometimes crossing multiple titles.
-
C.
narrative status within the Avengers
Narrative status within the Avengers is the degree of plot importance, focus, and influence a character holds in Avengers stories, shaping how central they are to the team’s overarching narrative.
-
D.
Marvel Comics continuity
Marvel Comics continuity is the interconnected, evolving narrative universe that encompasses the shared history, events, and character developments across Marvel’s comic book titles.
-
E.
Marvel Cinematic Universe phase
A Marvel Cinematic Universe phase is a curated grouping of interconnected films and series released within a specific timeframe that collectively advance overarching story arcs and character developments in the MCU.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:24 p.m.