Triple

T30859251
Position Surface form Disambiguated ID Type / Status
Subject Catherine Weaver E786013 entity
Predicate usesCoverIdentityOf P114813 FINISHED
Object Catherine Weaver (original human CEO, deceased) NE NERFINISHED

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: Catherine Weaver (original human CEO, deceased) | Statement: [Catherine Weaver, usesCoverIdentityOf, Catherine Weaver (original human CEO, deceased)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesCoverIdentityOf
Context triple: [Catherine Weaver, usesCoverIdentityOf, Catherine Weaver (original human CEO, deceased)]
  • A. usedBySuperheroIdentity
    Indicates that a particular item, tool, or resource is utilized by a given superhero identity.
  • B. usesSuperheroIdentity
    Indicates that an entity adopts or operates under a superhero persona or alias, rather than their ordinary identity.
  • C. usedCover
    Indicates that one entity employed another entity as a protective or concealing cover in a given context.
  • D. coverIdentityCreatedBy
    Indicates that a cover identity was created by a particular agent or entity.
  • E. characterCoverIdentity chosen
    Indicates that one character uses another identity as a cover or disguise, typically concealing their true 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_69f224b91c14819084e764832fe67a57 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fbc36ce1f88190a7fa1656b714e107 completed May 6, 2026, 10:40 p.m.
PD Predicate disambiguation batch_69fbbd13595c81908719f52c3d37a7e8 completed May 6, 2026, 10:13 p.m.
Created at: April 29, 2026, 8:46 p.m.