Triple

T30517466
Position Surface form Disambiguated ID Type / Status
Subject Russian military police E776603 entity
Predicate notableRoleAfter2019 P207281 FINISHED
Object securing Russian bases in Syria 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: securing Russian bases in Syria | Statement: [Russian military police, notableRoleAfter2019, securing Russian bases in Syria]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableRoleAfter2019
Context triple: [Russian military police, notableRoleAfter2019, securing Russian bases in Syria]
  • A. notableBearerOfRole
    Indicates that an entity is a particularly prominent or well-known holder or performer of a specified role.
  • B. notableFormerHolderRole
    Indicates that an entity previously held a particular notable role or position.
  • C. notableHolderRole
    Indicates that an entity is recognized for holding a particular role, office, or position in a notable or distinguished capacity.
  • D. notableMemberFutureAct
    Indicates that an entity is expected or planned to become a notable member of a group, organization, or activity in the future.
  • E. notablePersonnel
    Indicates that the subject has associated individuals who are particularly important, distinguished, or prominent in relation to it.
  • 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_69f2249b23c4819087fa85496d92f43f completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_6a037c9141dc819098d7fcc36e69882c completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379e2fac0819089b522db3260028c completed May 12, 2026, 7:05 p.m.
PDg Predicate description generation batch_6a037c7ee0388190a29faeb5cdb0950a completed May 12, 2026, 7:16 p.m.
Created at: April 29, 2026, 8:16 p.m.