Triple

T12998298
Position Surface form Disambiguated ID Type / Status
Subject Birth E322099 entity
Predicate mainAntagonisticForce P81119 FINISHED
Object Murder House spirits 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: Murder House spirits | Statement: [Birth, mainAntagonisticForce, Murder House spirits]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mainAntagonisticForce
Context triple: [Birth, mainAntagonisticForce, Murder House spirits]
  • A. antagonistOf
    Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
  • B. primaryAntagonistType
    Indicates the role or category of the main opposing force or adversary that serves as the central source of conflict.
  • C. hasAntagonisticProtagonist
    Indicates that the work features a main character who opposes or undermines the typical heroic or moral expectations of a traditional protagonist.
  • D. primaryAntagonists chosen
    Indicates that the referenced entities serve as the main opposing or adversarial forces in relation to a specified subject or narrative.
  • E. 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.
  • 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_69d8076479b8819090afce3591939cdf completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97e7b268c8190b8bb855e9de23c3b completed April 10, 2026, 10:49 p.m.
PD Predicate disambiguation batch_69d97dc153a081909d13a694993f074a completed April 10, 2026, 10:46 p.m.
Created at: April 9, 2026, 8:46 p.m.