Triple

T2786890
Position Surface form Disambiguated ID Type / Status
Subject YAKT E61830 entity
Predicate ianaTimeZoneExample P719 FINISHED
Object Asia/Yakutsk E61836 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: Asia/Yakutsk | Statement: [YAKT, ianaTimeZoneExample, Asia/Yakutsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Asia/Yakutsk
Context triple: [YAKT, ianaTimeZoneExample, Asia/Yakutsk]
  • A. Asia/Yakutsk chosen
    Asia/Yakutsk is the IANA time zone identifier representing Yakutsk Time, used in the Yakutsk region of Russia.
  • 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. 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.
  • 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.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ianaTimeZoneExample
Context triple: [YAKT, ianaTimeZoneExample, Asia/Yakutsk]
  • A. ianaTimeZoneId
    Indicates the association between an entity and its time zone as identified by a standard IANA time zone identifier (e.g., "America/New_York").
  • B. timeZonePractice
    Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
  • C. IANATimeZoneIdentifierExample chosen
    Indicates that the relationship provides an example of an IANA time zone identifier corresponding to a given time zone or context.
  • D. relatedTimeZone
    Indicates that two entities are associated with or operate within the same or corresponding time zone(s).
  • E. timeZoneDependence
    Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
  • F. None of above.

Provenance (4 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_69abdeea881481908d759c72798a50fb completed March 7, 2026, 8:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69afc6555ee08190b1ddd5446818f74e completed March 10, 2026, 7:20 a.m.
PD Predicate disambiguation batch_69abdd025c948190a97dd961a9592bac completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 9:57 p.m.