Triple
T8235830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tengboche |
E192401
|
entity |
| Predicate | timeZone |
P109
|
FINISHED |
| Object | Nepal Time |
E173520
|
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: Nepal Time | Statement: [Tengboche, timeZone, Nepal Time]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nepal Time Context triple: [Tengboche, timeZone, Nepal Time]
-
A.
Nepal Time
chosen
Nepal Time is the standard time zone of Nepal, set at UTC+5:45 and used nationwide including in the capital, Kathmandu.
-
B.
Bhutan Time
Bhutan Time is the standard time zone of Bhutan, set at UTC+6 and used nationwide including in the capital, Thimphu.
-
C.
Afghanistan Time
Afghanistan Time is the standard time zone used throughout Afghanistan, set at UTC+4:30.
-
D.
Myanmar Standard Time
Myanmar Standard Time is the time zone used throughout Myanmar, set at UTC+6:30 with no daylight saving time.
-
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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb782a5e18819096235679f5a644a8 |
completed | March 31, 2026, 7:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd34fb069c8190965d69fae908482e |
completed | April 1, 2026, 3:08 p.m. |
Created at: March 30, 2026, 5:47 p.m.