Triple
T2080008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korea Standard Time |
E45216
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | KST |
E45216
|
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: KST | Statement: [Korea Standard Time, abbreviation, KST]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KST Context triple: [Korea Standard Time, abbreviation, KST]
-
A.
Korea Standard Time
chosen
Korea Standard Time is the time zone used on the Korean Peninsula, set at UTC+9 hours.
-
B.
Anadyr Time
Anadyr Time is the time zone used in Russia’s far northeastern regions, including Chukotka and parts of the Russian Far East, offset well ahead of Coordinated Universal Time.
-
C.
Hawaii–Aleutian Standard Time
Hawaii–Aleutian Standard Time is the time zone used by Hawaii and part of the Aleutian Islands, typically 10 hours behind Coordinated Universal Time (UTC−10:00).
-
D.
Magadan Time
Magadan Time is a time zone used in parts of Russia’s Far East, including regions such as the Sakha Republic.
-
E.
Nepal Time
Nepal Time is the standard time zone of Nepal, set at UTC+5:45 and used nationwide including in the capital, Kathmandu.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba345be48190a1895f388e7749e5 |
completed | March 7, 2026, 5:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae273ad87c8190a7b1407868692202 |
completed | March 9, 2026, 1:49 a.m. |
Created at: March 4, 2026, 7:41 p.m.