Triple

T32171848
Position Surface form Disambiguated ID Type / Status
Subject Impastor E821728 entity
Predicate protagonistAssumedIdentity P86336 FINISHED
Object gay Lutheran pastor 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: gay Lutheran pastor | Statement: [Impastor, protagonistAssumedIdentity, gay Lutheran pastor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: protagonistAssumedIdentity
Context triple: [Impastor, protagonistAssumedIdentity, gay Lutheran pastor]
  • A. protagonistAlterEgoOf
    Indicates that one entity is the alternate identity or secret persona of the main character (protagonist) in a narrative.
  • B. hasFictionalAlterEgoOf chosen
    Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
  • C. actsInSteadOf
    Indicates that one entity performs an action or fulfills a role as a substitute or proxy for another entity.
  • D. usedBySuperheroIdentity
    Indicates that a particular item, tool, or resource is utilized by a given superhero identity.
  • E. usesSuperheroIdentity
    Indicates that an entity adopts or operates under a superhero persona or alias, rather than their ordinary identity.
  • 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_69f3490699a48190bbef96b198e8fade completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f7221dc9a88190bb8194fcc29c42bc completed May 3, 2026, 10:23 a.m.
PD Predicate disambiguation batch_69f72153a9188190b02adc84e1be4af8 completed May 3, 2026, 10:20 a.m.
Created at: May 1, 2026, 12:33 a.m.