Triple

T38481832
Position Surface form Disambiguated ID Type / Status
Subject Operation Witchcraft E915697 entity
Predicate hasFictionalAdversaryOrganization P17627 FINISHED
Object Soviet intelligence 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: Soviet intelligence | Statement: [Operation Witchcraft, hasFictionalAdversaryOrganization, Soviet intelligence]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFictionalAdversaryOrganization
Context triple: [Operation Witchcraft, hasFictionalAdversaryOrganization, Soviet intelligence]
  • A. hasFictionalGovernmentAgency
    Indicates that an entity includes, features, or is associated with a government agency that is fictional rather than real.
  • B. rivalFictionalAgency
    Indicates that one fictional agency stands in opposition or competition to another fictional agency.
  • C. villainOrganization
    Indicates that an entity is an organization characterized as antagonistic, criminal, or evil within a given context or narrative.
  • D. isFictionalAgentOf
    Indicates that one entity is a fictional character or agent that acts on behalf of, or represents, another entity.
  • E. hasAntagonistGroup chosen
    Indicates that an entity is opposed or challenged by a specific group acting as its antagonist.
  • 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_69f76e8ff5cc8190a88803369183845e completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a008e29f76881908e656dbbd7fceea3 completed May 10, 2026, 1:54 p.m.
PD Predicate disambiguation batch_6a008dc01b308190bc26e69814692f82 completed May 10, 2026, 1:53 p.m.
Created at: May 3, 2026, 4:31 p.m.