Triple
T36697344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bullseye |
E906127
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Daredevil character |
C57804
|
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: Daredevil character Context triple: [Bullseye, instanceOf, Daredevil character]
-
A.
Daredevil antagonist
chosen
A Daredevil antagonist is a morally complex foe who challenges Daredevil both physically and psychologically, exploiting his heightened senses, legal career, and Catholic guilt to push him to his ethical and emotional limits.
-
B.
comic book character
A comic book character is a fictional persona, often possessing distinctive abilities, traits, or backstory, that appears in sequential art narratives and drives the plot through their actions and development.
-
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.
Marvel Comics person
A Marvel Comics person is an individual character—human, superhuman, alien, or otherwise—who exists within the Marvel universe and participates in its stories, events, and relationships.
-
E.
Hulk supporting character
A Hulk supporting character is an individual, ally, or occasional adversary whose actions, relationships, or conflicts significantly influence the Hulk’s story, development, and the outcomes of his adventures.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.