Triple
T37716171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Avengers Presents (2008) limited series |
E939457
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Marvel Comics anthology |
C10203
|
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 Comics anthology Context triple: [Young Avengers Presents (2008) limited series, instanceOf, Marvel Comics anthology]
-
A.
Marvel Comics series
chosen
A Marvel Comics series is a sequence of interconnected comic book issues published by Marvel that follows specific characters, teams, or storylines within the broader Marvel Universe continuity.
-
B.
Marvel Comics organization
A Marvel Comics organization is a fictional group, agency, or collective within the Marvel Universe that unites characters around a common purpose, ideology, or function, often influencing major storylines and events.
-
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 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.
-
E.
Marvel Comics imprint
A Marvel Comics imprint is a distinct publishing label or brand under the Marvel umbrella used to group and market specific lines of comics with shared themes, target audiences, or creative approaches.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.