Triple

T33335004
Position Surface form Disambiguated ID Type / Status
Subject 2022 Russian offensive on Sumy Oblast E853509 entity
Predicate outcomeForUkraine P176507 FINISHED
Object restoration of control over Sumy Oblast 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: restoration of control over Sumy Oblast | Statement: [2022 Russian offensive on Sumy Oblast, outcomeForUkraine, restoration of control over Sumy Oblast]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: outcomeForUkraine
Context triple: [2022 Russian offensive on Sumy Oblast, outcomeForUkraine, restoration of control over Sumy Oblast]
  • A. UkraineResponse
    Indicates a response, action, or policy taken by Ukraine in reaction to a specific event, situation, or external stimulus.
  • B. objectiveOfUkraine
    Indicates that a particular goal, aim, or purpose is held or pursued by Ukraine.
  • C. outcomeForUnitedKingdom
    Indicates the result, consequence, or impact that something has specifically for the United Kingdom.
  • D. statusAfter2022Invasion
    Indicates the condition or classification of an entity following the 2022 invasion event.
  • E. outcomeForJapan
    Indicates the result, consequence, or impact that an event, action, or situation has specifically for Japan.
  • 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_69f34969614c81909cd99661b0902533 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e3156ea48190b604e414665ef351 completed May 3, 2026, 5:54 a.m.
PD Predicate disambiguation batch_69f6de0b9ba48190887c9eb5d06a2e94 completed May 3, 2026, 5:32 a.m.
PDg Predicate description generation batch_69f6e312d7fc819094dec41810f2585d completed May 3, 2026, 5:54 a.m.
Created at: May 1, 2026, 1:34 a.m.