Triple
T4234747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishkek |
E94665
|
entity |
| Predicate | timeZone |
P109
|
FINISHED |
| Object | Kyrgyzstan Time |
E384875
|
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: Kyrgyzstan Time | Statement: [Bishkek, timeZone, Kyrgyzstan Time]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kyrgyzstan Time Context triple: [Bishkek, timeZone, Kyrgyzstan Time]
-
A.
Turkmenistan Time
Turkmenistan Time is the standard time zone used throughout Turkmenistan, corresponding to UTC+5 hours.
-
B.
Nepal Time
Nepal Time is the standard time zone of Nepal, set at UTC+5:45 and used nationwide including in the capital, Kathmandu.
-
C.
Bhutan Time
chosen
Bhutan Time is the standard time zone of Bhutan, set at UTC+6 and used nationwide including in the capital, Thimphu.
-
D.
Afghanistan Time
Afghanistan Time is the standard time zone used throughout Afghanistan, set at UTC+4:30.
-
E.
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).
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e6705548190b695b3789d713b4a |
completed | March 12, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5a8630a4481909b9835aad51614b2 |
completed | March 14, 2026, 6:26 p.m. |
Created at: March 12, 2026, 11:05 p.m.