Triple
T19057789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irkutsk Time |
E466443
|
entity |
| Predicate | timeZoneDatabaseIdentifier |
P719
|
FINISHED |
| Object |
Asia/Irkutsk
Asia/Irkutsk is the IANA time zone identifier representing the standard time observed in the Irkutsk region of Russia.
|
E1356262
|
NE FINISHED |
How this triple was built (4 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/Irkutsk | Statement: [Irkutsk Time, timeZoneDatabaseIdentifier, Asia/Irkutsk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asia/Irkutsk Context triple: [Irkutsk Time, timeZoneDatabaseIdentifier, Asia/Irkutsk]
-
A.
Asia/Tomsk
Asia/Tomsk is an IANA time zone identifier representing the local time observed in the Tomsk region of Russia, aligned with Krasnoyarsk Time.
-
B.
Asia/Omsk
Asia/Omsk is the IANA time zone identifier representing the standard time observed in the Omsk region of Russia.
-
C.
Asia/Barnaul
Asia/Barnaul is an IANA time zone identifier used for the Barnaul region of Russia, corresponding to Krasnoyarsk Time (UTC+7).
-
D.
Asia/Yakutsk
Asia/Yakutsk is the IANA time zone identifier representing Yakutsk Time, used in the Yakutsk region of Russia.
-
E.
Asia/Vladivostok
Asia/Vladivostok is the time zone covering Russia’s Far Eastern city of Vladivostok and surrounding Primorsky Krai, typically observed as UTC+10.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Asia/Irkutsk Triple: [Irkutsk Time, timeZoneDatabaseIdentifier, Asia/Irkutsk]
Generated description
Asia/Irkutsk is the IANA time zone identifier representing the standard time observed in the Irkutsk region of Russia.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Asia/Irkutsk Target entity description: Asia/Irkutsk is the IANA time zone identifier representing the standard time observed in the Irkutsk region of Russia.
-
A.
Asia/Tomsk
Asia/Tomsk is an IANA time zone identifier representing the local time observed in the Tomsk region of Russia, aligned with Krasnoyarsk Time.
-
B.
Asia/Omsk
Asia/Omsk is the IANA time zone identifier representing the standard time observed in the Omsk region of Russia.
-
C.
Asia/Barnaul
Asia/Barnaul is an IANA time zone identifier used for the Barnaul region of Russia, corresponding to Krasnoyarsk Time (UTC+7).
-
D.
Asia/Yakutsk
Asia/Yakutsk is the IANA time zone identifier representing Yakutsk Time, used in the Yakutsk region of Russia.
-
E.
Asia/Vladivostok
Asia/Vladivostok is the time zone covering Russia’s Far Eastern city of Vladivostok and surrounding Primorsky Krai, typically observed as UTC+10.
- F. None of above. chosen
Provenance (5 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc0742288190a594be859184841a |
completed | April 20, 2026, 7:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a05c55bceb081908f7d8a74dd01dc32 |
completed | May 14, 2026, 12:51 p.m. |
| NEDg | Description generation | batch_6a05c93eb7b881909bf53002224ea86e |
completed | May 14, 2026, 1:08 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a05ca4de6448190aca4c8b4a5af9416 |
completed | May 14, 2026, 1:12 p.m. |
Created at: April 10, 2026, 12:03 p.m.