Triple

T28825151
Position Surface form Disambiguated ID Type / Status
Subject Brian Lumley E727879 entity
Predicate literaryUniverseCreated P115764 FINISHED
Object Necroscope universe NE NERFINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Necroscope universe | Statement: [Brian Lumley, literaryUniverseCreated, Necroscope universe]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: literaryUniverseCreated
Context triple: [Brian Lumley, literaryUniverseCreated, Necroscope universe]
  • A. literaryUniverse
    Indicates that two or more works of literature exist within the same fictional universe or continuity, sharing settings, characters, or canonical events.
  • B. fictionalUniverseCreated
    Indicates that one entity is the creator or originator of a particular fictional universe or setting in which stories or works take place.
  • C. fictionalUniverseAuthor chosen
    Indicates that an author is the creator or primary writer responsible for a given fictional universe.
  • D. fictionalUniverseOwner
    Indicates that one entity is the creator, rights holder, or controlling owner of a particular fictional universe or setting.
  • E. fictionalUniverseDebut
    Indicates the first appearance of an entity within a particular fictional universe or continuity.
  • F. None of above.

Provenance (3 batches)

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_69f0319d09088190bbf14cdf1987792a completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f6bbf6e33c819086e5176d64e7a614 completed May 3, 2026, 3:07 a.m.
PD Predicate disambiguation batch_69f6ba6b1e6c8190adf9d6a257e0b744 completed May 3, 2026, 3 a.m.
Created at: April 28, 2026, 6:35 a.m.