Triple

T29126245
Position Surface form Disambiguated ID Type / Status
Subject Patrick Danville E738236 entity
Predicate hasPropheticRole P121680 FINISHED
Object savior figure in the Dark Tower mythos 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: savior figure in the Dark Tower mythos | Statement: [Patrick Danville, hasPropheticRole, savior figure in the Dark Tower mythos]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPropheticRole
Context triple: [Patrick Danville, hasPropheticRole, savior figure in the Dark Tower mythos]
  • A. roleInTheProphecy chosen
    Indicates that an entity holds a specific function, status, or significance within the context of a particular prophecy.
  • B. symbolicRoleInProphecy
    Indicates that an entity serves as a symbolic figure or sign within a prophecy, representing or foreshadowing specific events, themes, or outcomes.
  • C. prophecyKnownAs
    Indicates that a particular prophecy is referred to or recognized by a specific name or title.
  • D. prophecyHeldBy
    Indicates that a particular prophecy is possessed, guarded, or maintained by a specific holder.
  • E. subjectOfProphecy
    Indicates that the subject is foretold or predicted to play a significant role or experience a specific event according to a prophecy.
  • 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_69f07cb29cdc8190afa55444553de60c completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69ff409ff5548190849c2d50e99bd807 completed May 9, 2026, 2:11 p.m.
PD Predicate disambiguation batch_69ff401a5e188190a72f945e910b4a6c completed May 9, 2026, 2:09 p.m.
Created at: April 28, 2026, 11:28 a.m.