Triple

T17597937
Position Surface form Disambiguated ID Type / Status
Subject Omsk Time E428621 entity
Predicate changeIn2014 P48142 FINISHED
Object Russia switched to permanent standard time with UTC+06:00 for Omsk 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: Russia switched to permanent standard time with UTC+06:00 for Omsk | Statement: [Omsk Time, changeIn2014, Russia switched to permanent standard time with UTC+06:00 for Omsk]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: changeIn2014
Context triple: [Omsk Time, changeIn2014, Russia switched to permanent standard time with UTC+06:00 for Omsk]
  • A. statusAfter2014 chosen
    Indicates the condition or state of an entity as it exists from the year 2014 onward, typically in contrast to its prior status.
  • B. post2020Change
    Indicates a change, update, or event that occurred after the year 2020.
  • C. currentAsOf2024
    Indicates that the associated information is valid, accurate, or in effect up to and including the year 2024.
  • D. governanceChange
    Indicates a change in the structure, rules, or authority of how an entity, organization, or system is governed.
  • E. proposedTaxPolicyChange
    Indicates that an entity has put forward a modification or new approach to existing tax rules or structures for consideration or implementation.
  • 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_69d889e1030481909950e140c63255b9 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e469ecfb108190a9e7a5b380f8ab93 completed April 19, 2026, 5:36 a.m.
PD Predicate disambiguation batch_69e3b4fff0348190b899a32da537eaca completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:51 a.m.