Triple

T29638026
Position Surface form Disambiguated ID Type / Status
Subject The Nostradamus Traitor E755775 entity
Predicate literaryGenreFusion P178055 FINISHED
Object espionage and prophetic mystery LITERAL FINISHED

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: espionage and prophetic mystery | Statement: [The Nostradamus Traitor, literaryGenreFusion, espionage and prophetic mystery]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: literaryGenreFusion
Context triple: [The Nostradamus Traitor, literaryGenreFusion, espionage and prophetic mystery]
  • A. literaryGenreOfWork
    Indicates that a work belongs to or is classified under a particular literary genre.
  • B. fictionalGenre
    Indicates that a work of fiction belongs to or is categorized under a particular narrative genre or style.
  • C. literaryGenreAssociated
    Indicates that there is an association between an entity and a particular literary genre with which it is related or classified.
  • D. literaryUniverse
    Indicates that two or more works of literature exist within the same fictional universe or continuity, sharing settings, characters, or canonical events.
  • E. literaryGenreOfSourceWork
    Indicates that a work belongs to, or is characterized by, a particular literary genre.
  • F. None of above. chosen

Provenance (4 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_69f0ef88fbe081908f0ad90c1c413f1c completed April 28, 2026, 5:34 p.m.
NER Named-entity recognition batch_69f707f7959881908f037f0d6b1d0c36 completed May 3, 2026, 8:31 a.m.
PD Predicate disambiguation batch_69f700fc274c8190a128593dc7c7abd0 completed May 3, 2026, 8:02 a.m.
PDg Predicate description generation batch_69f707f380388190954b79d52a321921 completed May 3, 2026, 8:31 a.m.
Created at: April 28, 2026, 6:45 p.m.