Triple

T15561192
Position Surface form Disambiguated ID Type / Status
Subject Yakutsk Time E371000 entity
Predicate standardTimeDesignation P119186 FINISHED
Object Yakutsk Time E371000 NE FINISHED

How this triple was built (3 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: [Yakutsk Time, standardTimeDesignation, Yakutsk Time]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yakutsk Time
Context triple: [Yakutsk Time, standardTimeDesignation, Yakutsk Time]
  • A. Yakutsk Time chosen
    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).
  • B. Irkutsk Time
    Irkutsk Time is a time zone in eastern Siberia, Russia, set eight hours ahead of Coordinated Universal Time (UTC+8).
  • C. 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.
  • D. Magadan Time
    Magadan Time is a time zone used in parts of Russia’s Far East, including regions such as the Sakha Republic.
  • E. Omsk Time
    Omsk Time is a time zone used in parts of Russia, including the city of Omsk, that is offset from Coordinated Universal Time by several hours.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: standardTimeDesignation
Context triple: [Yakutsk Time, standardTimeDesignation, Yakutsk Time]
  • A. standardTimeName
    Indicates the official name assigned to a particular standard time used in a region or context.
  • B. standardTimeType
    Indicates that a time value is expressed using a particular standard or conventional time format or classification.
  • C. standardTimeCounterpart
    Indicates that one time representation is the corresponding value expressed in a standard or canonical time format for the other.
  • D. isStandardTime
    Indicates that a given time value is expressed in standard (non-daylight-saving) time for its associated time zone.
  • E. standardTimeAllYear
    Indicates that a location or entity observes standard time throughout the entire year without switching to daylight saving time.
  • F. None of above. chosen

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_69d85cc6cf40819091f4a5facee1ebe6 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04ddb4c0c81909b3f4c75c91f7f3f completed April 16, 2026, 2:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff56bf8cac81909886de5b82849cb2 completed May 9, 2026, 3:46 p.m.
PD Predicate disambiguation batch_69deda7e6e748190b29ccce23298afef completed April 15, 2026, 12:23 a.m.
PDg Predicate description generation batch_69dff7f05f708190850f1d8782e132b0 completed April 15, 2026, 8:41 p.m.
Created at: April 10, 2026, 4:09 a.m.