Triple
T22849187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia/Ulaanbaatar |
E566310
|
entity |
| Predicate | standardTimeName |
P6292
|
FINISHED |
| Object | Ulaanbaatar Time |
—
|
NE NERFINISHED |
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: Ulaanbaatar Time | Statement: [Asia/Ulaanbaatar, standardTimeName, Ulaanbaatar Time]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ulaanbaatar Time Context triple: [Asia/Ulaanbaatar, standardTimeName, Ulaanbaatar Time]
-
A.
Asia/Ulaanbaatar
chosen
Asia/Ulaanbaatar is the primary time zone used in Mongolia’s capital city, Ulaanbaatar, and much of the surrounding region.
-
B.
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).
-
C.
Magadan Time
Magadan Time is a time zone used in parts of Russia’s Far East, including regions such as the Sakha Republic.
-
D.
Irkutsk Time
Irkutsk Time is a time zone in eastern Siberia, Russia, set eight hours ahead of Coordinated Universal Time (UTC+8).
-
E.
Kyrgyzstan Time
Kyrgyzstan Time is the standard time zone used throughout Kyrgyzstan, corresponding to UTC+6 with no daylight saving time.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e8aceb88190b137d17a7510fee4 |
completed | April 29, 2026, 3:44 a.m. |
Created at: April 17, 2026, 3:36 p.m.