Triple

T23374505
Position Surface form Disambiguated ID Type / Status
Subject Willis Davidge E593568 entity
Predicate initiallyEnemyOf P152485 FINISHED
Object Jeriba Shigan 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: Jeriba Shigan | Statement: [Willis Davidge, initiallyEnemyOf, Jeriba Shigan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: initiallyEnemyOf
Context triple: [Willis Davidge, initiallyEnemyOf, Jeriba Shigan]
  • A. formerEnemyOf
    Indicates that one entity was previously an enemy of another entity, but that adversarial relationship no longer holds.
  • B. temporarilyEnemyOf
    Indicates a relationship where two entities are in a state of enmity or opposition for a limited, non-permanent period of time.
  • C. laterEnemyOf
    Indicates that one entity becomes an enemy of another at a later time, after not initially being in an antagonistic relationship.
  • D. archenemyOf
    Indicates a relationship in which one entity is the principal or most important enemy of another, often characterized by deep, ongoing opposition or rivalry.
  • E. hasFriendEnemyRelationshipWith
    Indicates a relationship where two entities are simultaneously connected as both friends and enemies, reflecting a mixed or ambivalent association between them.
  • F. None of above. chosen

Provenance (4 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_69e25d268a50819095f2fd479da8ef3f completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a3b1d24881909945936cbf00876e completed April 29, 2026, 6:22 a.m.
PD Predicate disambiguation batch_69f061c7aaa48190a58ce93f87155ffc completed April 28, 2026, 7:29 a.m.
PDg Predicate description generation batch_69f0bd4a0e408190ad8916faf23562d9 completed April 28, 2026, 1:59 p.m.
Created at: April 17, 2026, 5:33 p.m.