Triple
T17242581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kim Chaek City |
E418537
|
entity |
| Predicate | timeZone |
P109
|
FINISHED |
| Object | Korea Standard Time |
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: Korea Standard Time | Statement: [Kim Chaek City, timeZone, Korea Standard Time]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Korea Standard Time Context triple: [Kim Chaek City, timeZone, Korea Standard Time]
-
A.
Korea Standard Time
chosen
Korea Standard Time is the time zone used on the Korean Peninsula, set at UTC+9 hours.
-
B.
Japan Standard Time
Japan Standard Time is the standard time zone used throughout Japan, set at nine hours ahead of Coordinated Universal Time (UTC+9) without daylight saving time.
-
C.
Sakhalin Time
Sakhalin Time is the time zone used on Russia’s Sakhalin Island, corresponding to UTC+11 hours.
-
D.
KST
KST is the standard time zone used in South Korea (and formerly North Korea), set nine hours ahead of Coordinated Universal Time (UTC+9).
-
E.
Myanmar Standard Time
Myanmar Standard Time is the time zone used throughout Myanmar, set at UTC+6:30 with no daylight saving time.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e21003c81908c884a3c8712676a |
completed | April 19, 2026, 1:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0170f388608190b709b1c228a7ba29 |
completed | May 11, 2026, 6:02 a.m. |
Created at: April 10, 2026, 5:39 a.m.