Triple

T32143285
Position Surface form Disambiguated ID Type / Status
Subject Wagner PMC E820961 entity
Predicate hasAllegedTiesTo P120587 FINISHED
Object Russian government 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: Russian government | Statement: [Wagner PMC, hasAllegedTiesTo, Russian government]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAllegedTiesTo
Context triple: [Wagner PMC, hasAllegedTiesTo, Russian government]
  • A. hasAllegedRelationshipWith chosen
    Indicates a claimed or suspected relationship between two entities that is not confirmed as factual.
  • B. hasIndustryTies
    Indicates that an entity maintains professional, financial, or organizational connections with a particular industry or sector.
  • C. allegesCollaborationWith
    Indicates that one party claims or asserts that another party has worked together or cooperated with a specified entity.
  • D. isLinkedPoliticallyTo
    Indicates that there exists a political connection, alliance, or association between the entities, such that their political actions, interests, or affiliations are related or coordinated.
  • E. allegedAgentOf
    Indicates that one entity is claimed or suspected, but not confirmed, to be the agent responsible for an action or event involving another entity.
  • 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_69f3490520d081909b2f1271dab75faa completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fcda3699948190adb57625bae08091 completed May 7, 2026, 6:30 p.m.
PD Predicate disambiguation batch_69fcd8fd16d08190b0aca6e19a632e99 completed May 7, 2026, 6:25 p.m.
Created at: May 1, 2026, 12:31 a.m.