Triple
T11669693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Rebirth |
E277345
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Marvel Comics concept |
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 concept Context triple: [Project Rebirth, instanceOf, Marvel Comics concept]
-
A.
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.
-
B.
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.
-
C.
Marvel Comics object
A Marvel Comics object is any tangible or intangible item, artifact, device, or construct that exists within the Marvel universe and plays a role in its stories, such as weapons, costumes, technology, or mystical relics.
-
D.
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.
-
E.
Marvel Comics objects
Marvel Comics objects are tangible or intangible items within the Marvel universe—such as weapons, artifacts, technologies, or mystical relics—that possess distinctive properties, origins, and narrative significance.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.