Triple

T15476644
Position Surface form Disambiguated ID Type / Status
Subject Hsinchu–Taipei–Keelung corridor E376795 entity
Predicate timeZone P109 FINISHED
Object National Standard Time of Taiwan E423825 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: National Standard Time of Taiwan | Statement: [Hsinchu–Taipei–Keelung corridor, timeZone, National Standard Time of Taiwan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: National Standard Time of Taiwan
Context triple: [Hsinchu–Taipei–Keelung corridor, timeZone, National Standard Time of Taiwan]
  • A. Taipei Time chosen
    Taipei Time is the time zone used in Taiwan, corresponding to National Standard Time at UTC+8 without daylight saving time.
  • B. China Standard Time
    China Standard Time is the single official time zone used throughout mainland China, corresponding to UTC+8.
  • C. Singapore Standard Time
    Singapore Standard Time is the time zone used throughout Singapore, corresponding to UTC+8 with no daylight saving time.
  • 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. Hong Kong Time
    Hong Kong Time is the standard time zone used in Hong Kong, set at UTC+8 without 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_69d85cd21dcc81908646251b1c26ea00 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03f88a5dc8190a2d7830748e29180 completed April 16, 2026, 1:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff2d093ccc8190aefc355a837c83f4 completed May 9, 2026, 12:48 p.m.
Created at: April 10, 2026, 3:34 a.m.