Triple
T30056839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superman villains |
E763755
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | DC Comics character category |
C4314
|
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: DC Comics character category Context triple: [Superman villains, instanceOf, DC Comics character category]
-
A.
comic book character
chosen
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.
-
B.
DC Comics species
A DC Comics species is a fictional group of beings within the DC Universe that share common biological traits, origins, or cultural characteristics, often including unique powers or advanced technologies.
-
C.
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.
-
D.
DC Comics superhero
A DC Comics superhero is a fictional character, often possessing extraordinary abilities or advanced technology, who fights evil and protects the innocent within the shared DC Universe.
-
E.
DC Comics object
A DC Comics object is any in-universe item, artifact, device, or construct—mundane or supernatural—that exists within DC’s fictional continuity and can influence characters, events, or settings.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 6:56 p.m.