Triple

T856931
Position Surface form Disambiguated ID Type / Status
Subject Amur Oblast E18512 entity
Predicate timeZone P109 FINISHED
Object Yakutsk Time E10242 NE 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: Yakutsk Time | Statement: [Amur Oblast, timeZone, Yakutsk Time]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yakutsk Time
Context triple: [Amur Oblast, timeZone, 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. 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).
  • C. Moscow Time
    Moscow Time is the standard time zone used in Moscow and much of western Russia, corresponding to UTC+3 year-round.
  • D. Yakutsk Time (seasonally, depending on Russian DST history) chosen
    Yakutsk Time is a time zone used in eastern Russia that has seasonally aligned with Japan Standard Time at various points depending on Russia’s daylight saving time policies.
  • E. Yukon Time Zone
    The Yukon Time Zone is a North American time zone used primarily in Canada's Yukon territory, aligning year-round with Pacific Daylight Time.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a4938bdd3c8190a954a3c11844d9cf completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac4d47508190b48d944aa2d881bf completed March 1, 2026, 9:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69a7a3c1ee4481909d5713122e5ad856 completed March 4, 2026, 3:15 a.m.
Created at: March 1, 2026, 7:39 p.m.