Triple

T20522085
Position Surface form Disambiguated ID Type / Status
Subject October Revolution Island E503834 entity
Predicate timeZone P109 FINISHED
Object Krasnoyarsk Time 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: Krasnoyarsk Time | Statement: [October Revolution Island, timeZone, Krasnoyarsk Time]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Krasnoyarsk Time
Context triple: [October Revolution Island, timeZone, Krasnoyarsk Time]
  • A. Krasnoyarsk Time (standard) chosen
    Krasnoyarsk Time (standard) is a time zone used in central Siberia, Russia, corresponding to UTC+7.
  • B. Irkutsk Time
    Irkutsk Time is a time zone in eastern Siberia, Russia, set eight hours ahead of Coordinated Universal Time (UTC+8).
  • C. Yakutsk Time
    Yakutsk Time is a time zone used in eastern Russia, including parts of the Sakha Republic, that is typically nine hours ahead of Coordinated Universal Time (UTC+9).
  • D. Yekaterinburg Time
    Yekaterinburg Time is a Russian time zone used in the Ural region, typically four hours ahead of Coordinated Universal Time (UTC+4) and one hour ahead of Moscow Time.
  • E. Magadan Time
    Magadan Time is a time zone used in parts of Russia’s Far East, including regions such as the Sakha Republic.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4b3a6e08190ae663701f50fab8e completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69f46488c819093687b4e07837793 completed April 20, 2026, 9:48 p.m.
Created at: April 16, 2026, 11:36 a.m.