Triple
T30597365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Brevoort |
E778823
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Marvel Comics executive |
C54416
|
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 executive Context triple: [Tom Brevoort, instanceOf, Marvel Comics executive]
-
A.
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.
-
B.
Marvel Studios executive
A Marvel Studios executive is a high-level decision-maker responsible for overseeing the development, production, and strategic direction of Marvel’s film and television projects within the broader Marvel Cinematic Universe and corporate objectives.
-
C.
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.
-
D.
comic book editor
A comic book editor oversees the development, coherence, and quality of comic book stories and artwork, coordinating writers, artists, and production to ensure timely, polished publications that align with the publisher’s vision.
-
E.
comics professional
chosen
A comics professional is an individual who earns a living by creating, editing, publishing, or otherwise working in the production and distribution of comic books, graphic novels, or related sequential art media.
- 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.