Triple
T36591057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marius de Romanus |
E902670
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in The Vampire Chronicles |
C65439
|
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: character in The Vampire Chronicles Context triple: [Marius de Romanus, instanceOf, character in The Vampire Chronicles]
-
A.
character in the Twilight series
A character in the Twilight series is an individual—human, vampire, or werewolf—whose personal history, supernatural traits, and relationships drive the romantic and dramatic conflicts within Stephenie Meyer’s Twilight universe.
-
B.
character in the Shannara series
A character in the Shannara series is an individual—human or otherwise—who inhabits the Four Lands and participates in its unfolding history of magic, conflict, and destiny.
-
C.
character in the His Dark Materials trilogy
A character in the His Dark Materials trilogy is an individual—human or otherwise—who exists within Philip Pullman’s multiverse, defined by their relationship with a dæmon, their role in the struggle over Dust, and their influence on the intertwined fates of multiple worlds.
-
D.
Vampire Slayer
A Vampire Slayer is a skilled and often supernaturally empowered hunter dedicated to tracking, combating, and destroying vampires and related undead threats.
-
E.
character in the Majipoor series
A character in the Majipoor series is an inhabitant of the vast, multi-species world of Majipoor whose personal story intersects with the planet’s intricate political, social, and often mystical events.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.