Triple
T6647851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binh Thuy District |
E150746
|
entity |
| Predicate | hasTimezone |
P3413
|
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: [Binh Thuy District, hasTimezone, Indochina Time]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Indochina Time Context triple: [Binh Thuy District, hasTimezone, 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.
Philippine Standard Time
Philippine Standard Time is the official time zone of the Philippines, observed as UTC+8 without daylight saving time.
-
D.
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.
-
E.
Sakhalin Time
Sakhalin Time is the time zone used on Russia’s Sakhalin Island, corresponding to UTC+11 hours.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6b01eb9148190a3f462e57c7556c2 |
completed | March 27, 2026, 4:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6eef6def8819084bccdf6f11e63da |
completed | March 27, 2026, 8:56 p.m. |
Created at: March 27, 2026, 2 p.m.