Triple

T26088940
Position Surface form Disambiguated ID Type / Status
Subject Ajax E658062 entity
Predicate hasNemesisRelationshipWith P172646 FINISHED
Object Deadpool 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: Deadpool | Statement: [Ajax, hasNemesisRelationshipWith, Deadpool]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNemesisRelationshipWith
Context triple: [Ajax, hasNemesisRelationshipWith, Deadpool]
  • A. hasFriendEnemyRelationshipWith
    Indicates a relationship where two entities are simultaneously connected as both friends and enemies, reflecting a mixed or ambivalent association between them.
  • B. wasEnemyOf chosen
    Indicates that one entity regarded or interacted with another as an adversary or opponent, typically in a hostile or conflicting relationship.
  • C. relationshipWithAntagonist
    Indicates a relationship or connection that an entity has with an opposing or adversarial figure in a narrative or context.
  • D. laterEnemyOf
    Indicates that one entity becomes an enemy of another at a later time, after not initially being in an antagonistic relationship.
  • E. hasAntagonisticProtagonist
    Indicates that the work features a main character who opposes or undermines the typical heroic or moral expectations of a traditional protagonist.
  • 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_69ee5bbfc4d08190a1b206d0ac3a1e8d completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f7117e55908190a67105e92bc4830f completed May 3, 2026, 9:12 a.m.
PD Predicate disambiguation batch_69f70f380690819090cc34763ba460ed completed May 3, 2026, 9:02 a.m.
Created at: April 26, 2026, 7:45 p.m.