Triple

T32482474
Position Surface form Disambiguated ID Type / Status
Subject The Night Flyer E830146 entity
Predicate antagonistNature P119796 FINISHED
Object possibly supernatural 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: possibly supernatural | Statement: [The Night Flyer, antagonistNature, possibly supernatural]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: antagonistNature
Context triple: [The Night Flyer, antagonistNature, possibly supernatural]
  • A. antagonistOf
    Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
  • B. antagonistStatus
    Indicates that an entity holds an opposing or adversarial role, often acting as the main source of conflict relative to another entity or objective.
  • C. antagonistAttribute chosen
    Indicates that an entity possesses a characteristic or role specifically associated with being an antagonist in a narrative or conflict.
  • D. hasAntagonisticProtagonist
    Indicates that the work features a main character who opposes or undermines the typical heroic or moral expectations of a traditional protagonist.
  • E. antagonistNearby
    Indicates that an opposing or hostile entity is located in close physical proximity to the reference entity.
  • 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_69f3491ff3b48190b50a7fa00bb05b1f completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c396f8b881909a940437d9c817ea completed May 3, 2026, 3:40 a.m.
PD Predicate disambiguation batch_69f6bd25bed08190befcabd3a41ffadf completed May 3, 2026, 3:12 a.m.
Created at: May 1, 2026, 12:58 a.m.