Triple

T16570540
Position Surface form Disambiguated ID Type / Status
Subject Khrabrovo Airport E402571 entity
Predicate timezone P109 FINISHED
Object Kaliningrad Time E383380 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: Kaliningrad Time | Statement: [Khrabrovo Airport, timezone, Kaliningrad Time]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kaliningrad Time
Context triple: [Khrabrovo Airport, timezone, Kaliningrad Time]
  • A. Kaliningrad Time chosen
    Kaliningrad Time is the time standard used in Russia’s Kaliningrad Oblast, corresponding to UTC+2 and aligning with Eastern European Time without daylight saving changes.
  • B. 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.
  • C. Samara Time
    Samara Time is a time zone used in parts of Russia, including the Samara region, that is three hours ahead of Coordinated Universal Time (UTC+3).
  • D. Yakutsk Time
    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).
  • E. Irkutsk Time
    Irkutsk Time is a time zone in eastern Siberia, Russia, set eight hours ahead of Coordinated Universal Time (UTC+8).
  • 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_69d8838648088190acf97ef11fc3f61b completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e359580f548190a21afd148bc22d8d completed April 18, 2026, 10:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a006ee8812c81908ef74636bf39d44a completed May 10, 2026, 11:41 a.m.
Created at: April 10, 2026, 5:16 a.m.