Triple
T38390545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Universe |
E899704
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Universal Classic Monsters reboot |
C66463
|
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: Universal Classic Monsters reboot Context triple: [Dark Universe, instanceOf, Universal Classic Monsters reboot]
-
A.
Universal Classic Monster
A Universal Classic Monster is a legendary cinematic creature from Universal Pictures’ early horror films, characterized by iconic, archetypal designs and enduring influence on popular culture’s vision of monsters.
-
B.
Universal Classic Monsters film
A Universal Classic Monsters film is a horror movie produced by Universal Pictures during the early-to-mid 20th century that features iconic supernatural or monstrous characters such as Dracula, Frankenstein’s Monster, the Mummy, or the Wolf Man.
-
C.
film monster
A film monster is a fictional creature or entity in movies designed to evoke fear, awe, or suspense, often serving as a central antagonist or symbolic representation of human anxieties.
-
D.
organization in the MonsterVerse
An organization in the MonsterVerse is a structured group of humans or entities, such as Monarch or Apex, that operates with specific goals related to the study, control, exploitation, or defense against Titans and other colossal creatures within the shared cinematic universe.
-
E.
Monsters
Monsters are fantastical or supernatural beings, often embodying fear, danger, or the unknown, that challenge heroes and societies within myths, stories, and games.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.