Triple
T9994647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinity Saga |
E197173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Marvel Cinematic Universe storyline |
C24361
|
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: Marvel Cinematic Universe storyline Context triple: [Infinity Saga, instanceOf, Marvel Cinematic Universe storyline]
-
A.
Marvel Cinematic Universe phase
chosen
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.
-
B.
Marvel Cinematic Universe film
A Marvel Cinematic Universe film is a feature-length motion picture produced by Marvel Studios that takes place within a shared continuity of interconnected superhero stories, characters, and events based on Marvel Comics.
-
C.
Marvel Comics storyline
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.
-
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.
location in the Marvel Cinematic Universe
A location in the Marvel Cinematic Universe is any distinct place—real or fictional—where events, characters, or organizations appear or operate within the interconnected MCU narrative.
- 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:50 p.m.