Triple

T2786886
Position Surface form Disambiguated ID Type / Status
Subject YAKT E61830 entity
Predicate timeZoneName P11952 FINISHED
Object Yakutsk Time
Yakutsk Time is a time zone used in eastern Russia, typically nine hours ahead of Coordinated Universal Time (UTC+9).
 E32360 NE FINISHED

How this triple was built (4 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: Yakutsk Time | Statement: [YAKT, timeZoneName, Yakutsk Time]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Yakutsk Time
Context triple: [YAKT, timeZoneName, Yakutsk Time]
  • A. Anadyr Time
    Anadyr Time is the time zone used in Russia’s far northeastern regions, including Chukotka and parts of the Russian Far East, offset well ahead of Coordinated Universal Time.
  • B. Magadan Time
    Magadan Time is a time zone used in parts of Russia’s Far East, including regions such as the Sakha Republic.
  • C. Krasnoyarsk Time (standard)
    Krasnoyarsk Time (standard) is a time zone used in central Siberia, Russia, corresponding to UTC+7.
  • 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. Vladivostok Time (VLAT)
    Vladivostok Time (VLAT) is a time zone used in Russia’s Far East, including the city of Vladivostok, typically set nine hours ahead of Coordinated Universal Time (UTC+9).
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Yakutsk Time
Triple: [YAKT, timeZoneName, Yakutsk Time]
Generated description
Yakutsk Time is a time zone used in eastern Russia, typically nine hours ahead of Coordinated Universal Time (UTC+9).
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Yakutsk Time
Target entity description: Yakutsk Time is a time zone used in eastern Russia, typically nine hours ahead of Coordinated Universal Time (UTC+9).
  • A. Anadyr Time
    Anadyr Time is the time zone used in Russia’s far northeastern regions, including Chukotka and parts of the Russian Far East, offset well ahead of Coordinated Universal Time.
  • B. Magadan Time
    Magadan Time is a time zone used in parts of Russia’s Far East, including regions such as the Sakha Republic.
  • C. Krasnoyarsk Time (standard)
    Krasnoyarsk Time (standard) is a time zone used in central Siberia, Russia, corresponding to UTC+7.
  • 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. Vladivostok Time (VLAT) chosen
    Vladivostok Time (VLAT) is a time zone used in Russia’s Far East, including the city of Vladivostok, typically set nine hours ahead of Coordinated Universal Time (UTC+9).
  • F. None of above.

Provenance (5 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_69ab4b7f51d881908768300ebd2fbdae completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abddb0d3488190a3f2bf47ebb35802 completed March 7, 2026, 8:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69afce8e2c488190a63332f36803c295 completed March 10, 2026, 7:55 a.m.
NEDg Description generation batch_69afcf6ded208190a9315d1130dd0cbe completed March 10, 2026, 7:59 a.m.
NED2 Entity disambiguation (via description) batch_69afd0219b34819095bc98ba28ca97f5 completed March 10, 2026, 8:02 a.m.
Created at: March 6, 2026, 9:57 p.m.