Triple
T30649424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | He Who Remains |
E780213
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Variant of Kang the Conqueror |
C57674
|
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: Variant of Kang the Conqueror Context triple: [He Who Remains, instanceOf, Variant of Kang the Conqueror]
-
A.
Hulk villain
A Hulk villain is a powerful adversary who challenges the Hulk physically, mentally, or morally, often embodying themes of rage, control, or the consequences of unchecked power.
-
B.
Skrull
A Skrull is a shape-shifting extraterrestrial being capable of mimicking the appearance and, often, abilities of other lifeforms, typically used in stories as infiltrators or hidden enemies.
-
C.
alternate universe version of Reed Richards
A hyper-intelligent, reality-displaced variant of Reed Richards whose divergent choices and circumstances have reshaped his scientific ethics, relationships, and use of technology in a distinct alternate universe.
-
D.
MonsterVerse character
A MonsterVerse character is a fictional being—often a giant monster, titan, or associated human figure—originating from the shared cinematic universe that includes Godzilla, Kong, and related creatures, defined by its role within that interconnected storyline.
-
E.
Hammer Bro variant
A Hammer Bro variant is an enemy type that modifies the standard Hammer Bro’s behavior, appearance, or attack pattern—such as projectile type, movement style, or defensive traits—while retaining its core role as a mobile, hammer-throwing obstacle.
- F. None of above. chosen
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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:30 p.m.