Triple
T1143896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Indonesian Time |
E23518
|
entity |
| Predicate | isSameOffsetAs |
P8570
|
FINISHED |
| Object | Vietnam Standard 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: Vietnam Standard Time | Statement: [Western Indonesian Time, isSameOffsetAs, Vietnam Standard Time]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vietnam Standard Time Context triple: [Western Indonesian Time, isSameOffsetAs, Vietnam Standard 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.
Philippine Standard Time
Philippine Standard Time is the official time zone of the Philippines, observed as UTC+8 without daylight saving time.
-
C.
Korea Standard Time
Korea Standard Time is the time zone used on the Korean Peninsula, set at UTC+9 hours.
-
D.
Vladivostok Time (VLAT)
Vladivostok Time (VLAT) is a time zone used in Russia’s Far East, including the city of Vladivostok, typically set nine hours ahead of Coordinated Universal Time (UTC+9).
-
E.
Timor Leste Time
Timor Leste Time is the standard time zone used in East Timor, corresponding to UTC+9 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc5008d8819095c1ffb5db5b4911 |
completed | March 1, 2026, 10:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac5eb1f7d08190ba722dcbbc8a6799 |
completed | March 7, 2026, 5:21 p.m. |
Created at: March 1, 2026, 7:44 p.m.