Triple
T30674674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fifty-State Initiative |
E780879
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Marvel Comics storyline element |
C10897
|
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 storyline element Context triple: [Fifty-State Initiative, instanceOf, Marvel Comics storyline element]
-
A.
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.
-
B.
Marvel Comics character
A Marvel Comics character is a fictional individual within the Marvel Universe, possessing distinct abilities, personalities, and story arcs that interact with other characters and events across various comic book series and related media.
-
C.
Marvel Comics series
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.
-
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 organization
chosen
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.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:32 p.m.