Triple
T12946926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyaukphyu |
E309793
|
entity |
| Predicate | timezone |
P109
|
FINISHED |
| Object | Myanmar 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 Time | Statement: [Kyaukphyu, timezone, Myanmar Time]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Myanmar Time Context triple: [Kyaukphyu, timezone, Myanmar 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.
Malaysia Time
Malaysia Time is the standard time zone used throughout Malaysia, set eight hours ahead of Coordinated Universal Time (UTC+8).
-
C.
Indochina Time
Indochina Time is the standard time zone (UTC+7) used in several Southeast Asian countries, including Thailand, Vietnam, Cambodia, and Laos.
-
D.
Brunei Darussalam Time
Brunei Darussalam Time is the standard time zone used throughout Brunei, set at UTC+8 with no daylight saving time.
-
E.
Bhutan Time
Bhutan Time is the standard time zone of Bhutan, set at UTC+6 and used nationwide including in the capital, Thimphu.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e1c67b8819094e5243267f93ce2 |
completed | April 10, 2026, 10:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6af75bc04819098d98c47fca48ac9 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 9, 2026, 5:43 p.m.