Triple
T1625221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CST (China Standard Time) |
E35124
|
entity |
| Predicate | IANAZoneIdentifier |
P719
|
FINISHED |
| Object | Asia/Harbin |
E5773
|
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: Asia/Harbin | Statement: [CST (China Standard Time), IANAZoneIdentifier, Asia/Harbin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asia/Harbin Context triple: [CST (China Standard Time), IANAZoneIdentifier, Asia/Harbin]
-
A.
Asia/Yakutsk
Asia/Yakutsk is the IANA time zone identifier representing Yakutsk Time, used in the Yakutsk region of Russia.
-
B.
Magadan Time
Magadan Time is a time zone used in parts of Russia’s Far East, including regions such as the Sakha Republic.
-
C.
China Standard Time
chosen
China Standard Time is the single official time zone used throughout mainland China, corresponding to UTC+8.
-
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.
Indochina Time
Indochina Time is the standard time zone (UTC+7) used in several Southeast Asian countries, including Thailand, Vietnam, Cambodia, and Laos.
- 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a909d19b008190b2224717b2909a78 |
completed | March 5, 2026, 4:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad6810e09c81909a214d16d865646a |
completed | March 8, 2026, 12:14 p.m. |
Created at: March 4, 2026, 7:28 p.m.