Triple

T15283046
Position Surface form Disambiguated ID Type / Status
Subject Yen Bai Province E365318 entity
Predicate timeZone P109 FINISHED
Object Indochina Time E61477 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: Indochina Time | Statement: [Yen Bai Province, timeZone, Indochina Time]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Indochina Time
Context triple: [Yen Bai Province, timeZone, Indochina Time]
  • A. Indochina Time chosen
    Indochina Time is the standard time zone (UTC+7) used in several Southeast Asian countries, including Thailand, Vietnam, Cambodia, and Laos.
  • B. Myanmar Standard Time
    Myanmar Standard Time is the time zone used throughout Myanmar, set at UTC+6:30 with no daylight saving time.
  • C. Brunei Darussalam Time
    Brunei Darussalam Time is the standard time zone used throughout Brunei, set at UTC+8 with no daylight saving time.
  • D. Philippine Standard Time
    Philippine Standard Time is the official time zone of the Philippines, observed as UTC+8 without daylight saving time.
  • E. Central Indonesia Time
    Central Indonesia Time is one of Indonesia’s standard time zones, set at UTC+8 and used by regions including Sulawesi, Bali, and parts of Kalimantan and Nusa Tenggara.
  • 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_69d85a103d9081908c1ea6c4c73ac8e3 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e00e51f82081909f63d14b589d5587 completed April 15, 2026, 10:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69feef773bc4819083c9a86543659aa9 completed May 9, 2026, 8:25 a.m.
Created at: April 10, 2026, 3:15 a.m.