Triple
T16662153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trongsa District |
E404884
|
entity |
| Predicate | timeZone |
P109
|
FINISHED |
| Object | Bhutan 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: Bhutan Time | Statement: [Trongsa District, timeZone, Bhutan Time]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhutan Time Context triple: [Trongsa District, timeZone, Bhutan Time]
-
A.
Bhutan Time
chosen
Bhutan Time is the standard time zone of Bhutan, set at UTC+6 and used nationwide including in the capital, Thimphu.
-
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.
Kyrgyzstan Time
Kyrgyzstan Time is the standard time zone used throughout Kyrgyzstan, corresponding to UTC+6 with no daylight saving time.
-
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
Bhutan is a small, landlocked Himalayan kingdom in South Asia known for its Buddhist culture, mountainous landscapes, and emphasis on Gross National Happiness.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c99efa8819096c6325ff4898bd7 |
completed | April 18, 2026, 12:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0084d091e0819088a98ef4aa775d07 |
completed | May 10, 2026, 1:14 p.m. |
Created at: April 10, 2026, 5:18 a.m.