Triple

T14883214
Position Surface form Disambiguated ID Type / Status
Subject Yandabo E350051 entity
Predicate isInTimeZone P109 FINISHED
Object Myanmar Standard Time E218962 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: Myanmar Standard Time | Statement: [Yandabo, isInTimeZone, Myanmar Standard Time]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Myanmar Standard Time
Context triple: [Yandabo, isInTimeZone, Myanmar Standard Time]
  • A. Myanmar Standard Time chosen
    Myanmar Standard Time is the time zone used throughout Myanmar, set at UTC+6:30 with no daylight saving time.
  • B. Indochina Time
    Indochina Time is the standard time zone (UTC+7) used in several Southeast Asian countries, including Thailand, Vietnam, Cambodia, and Laos.
  • C. Brunei Darussalam Time
    Brunei Darussalam Time is the standard time zone used throughout Brunei, set at UTC+8 with no daylight saving time.
  • D. Singapore Standard Time
    Singapore Standard Time is the time zone used throughout Singapore, corresponding to UTC+8 with no daylight saving time.
  • E. Bangladesh Standard Time
    Bangladesh Standard Time is the time zone used in Bangladesh, corresponding to UTC+6 hours with no daylight saving 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_69d822ee4f408190b6ac3b2fa434f0df completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded5e7c0e48190af2d68a71130585c completed April 15, 2026, 12:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe6b5af8208190a35451477ea20b03 completed May 8, 2026, 11:01 p.m.
Created at: April 10, 2026, 1:56 a.m.