Triple
T33021212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herman Munster |
E844916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Frankenstein’s-monster-like character |
C5616
|
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: Frankenstein’s-monster-like character Context triple: [Herman Munster, instanceOf, Frankenstein’s-monster-like character]
-
A.
adaptation of Victor Frankenstein
An adaptation of Victor Frankenstein is a reimagined portrayal of Mary Shelley’s ambitious scientist, reshaped through new settings, themes, or character perspectives while preserving his core role as a creator who confronts the consequences of defying natural limits.
-
B.
Homunculus
A homunculus is a small, artificially created human-like being, often used in philosophy, alchemy, and psychology to represent a miniature person controlling or embodying aspects of the mind or body.
-
C.
Maiar-corrupted creature
A Maiar-corrupted creature is a once-mundane being twisted and empowered by the influence of a fallen Maia, bearing unnatural abilities, warped form, and a will partially or wholly subjugated to its corrupter’s purpose.
-
D.
undead character
An undead character is a once-living being reanimated through supernatural or necromantic forces, often retaining fragmented memories, altered physical form, and a tenuous connection to life and death.
-
E.
monster archetype
chosen
A monster archetype is a conceptual template that defines the core traits, behaviors, and narrative role of a type of creature used to evoke specific fears, challenges, or themes in stories and games.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:23 a.m.