Triple
T33914303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuclear Man |
E869408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Superman antagonist |
C24394
|
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: Superman antagonist Context triple: [Nuclear Man, instanceOf, Superman antagonist]
-
A.
Superman character
chosen
A Superman character is a fictional superhero archetype possessing extraordinary powers, a strong moral code, and a dual identity used to protect others and fight injustice.
-
B.
Green Lantern villain
A Green Lantern villain is an adversary who opposes members of the Green Lantern Corps, often wielding their own powerful energy sources, emotional spectrum rings, or cosmic forces to challenge the will-powered protectors of the universe.
-
C.
Aquaman villain
An Aquaman villain is an adversary who opposes Aquaman, often seeking power over the seas or Atlantis through schemes that exploit marine environments, mystical artifacts, or political conflict beneath the ocean.
-
D.
DC Extended Universe character
A DC Extended Universe character is a fictional persona appearing within the interconnected films and related media of the DC Extended Universe franchise, often adapted from DC Comics and sharing a common continuity with other characters and storylines.
-
E.
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.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.