Triple

T5937763
Position Surface form Disambiguated ID Type / Status
Subject Yakutsk Airport E132084 entity
Predicate operatedInTimeZone P109 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 Airport, operatedInTimeZone, Yakutsk Time]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yakutsk Time
Context triple: [Yakutsk Airport, operatedInTimeZone, 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: operatedInTimeZone
Context triple: [Yakutsk Airport, operatedInTimeZone, Yakutsk Time]
  • A. locatedInTimeZone chosen
    Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
  • B. timeZoneDependence
    Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
  • C. timeZoneOnUSSide
    Indicates that the referenced time zone is the one used on the United States side of a border, region, or cross-national context.
  • D. relatedTimeZone
    Indicates that two entities are associated with or operate within the same or corresponding time zone(s).
  • E. partlyLocatedInTimeZone
    Indicates that an entity’s extent overlaps multiple time zones, with at least part of it falling within the specified time zone.
  • 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_69c0085c55dc8190aa90e242c956e2fa completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c03f26f51881908cc253fe5775a1fc completed March 22, 2026, 7:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0c06f979881908d7e98ee674f1ff2 completed March 23, 2026, 4:24 a.m.
PD Predicate disambiguation batch_69c03355caf08190b960563a1aed23f9 completed March 22, 2026, 6:22 p.m.
Created at: March 22, 2026, 4:01 p.m.