Triple
T15858977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 경기도 화성시 |
E384531
|
entity |
| Predicate | timeZone |
P109
|
FINISHED |
| Object | 한국 표준시 |
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: 한국 표준시 | Statement: [경기도 화성시, timeZone, 한국 표준시]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 한국 표준시 Context triple: [경기도 화성시, timeZone, 한국 표준시]
-
A.
Korea Standard Time
chosen
Korea Standard Time is the time zone used on the Korean Peninsula, set at UTC+9 hours.
-
B.
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).
-
C.
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.
-
D.
Sakhalin Time
Sakhalin Time is the time zone used on Russia’s Sakhalin Island, corresponding to UTC+11 hours.
-
E.
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).
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1555956ec8190b13602a177e7a2bb |
completed | April 16, 2026, 9:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa14da7ac8190bbef49a1602a76fe |
completed | May 9, 2026, 9:04 p.m. |
Created at: April 10, 2026, 4:50 a.m.