Triple
T12993153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kohalpur |
E321965
|
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: [Kohalpur, timeZone, Nepal Time]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nepal Time Context triple: [Kohalpur, 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.
Kyrgyzstan Time
Kyrgyzstan Time is the standard time zone used throughout Kyrgyzstan, corresponding to UTC+6 with no daylight saving time.
-
D.
Nepal Sambat
Nepal Sambat is a traditional lunar-solar calendar of the Newar people of Nepal, historically used for cultural, religious, and ceremonial purposes.
-
E.
Afghanistan Time
Afghanistan Time is the standard time zone used throughout Afghanistan, set at UTC+4:30.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e7765788190a9503ef055bc30ca |
completed | April 10, 2026, 10:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6e266000c8190b0ba4c9e63ba0542 |
completed | May 3, 2026, 5:51 a.m. |
Created at: April 9, 2026, 8:44 p.m.