Triple
T3134030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kostroma |
E65483
|
entity |
| Predicate | timezone |
P109
|
FINISHED |
| Object | Moscow Time |
E3442
|
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: Moscow Time | Statement: [Kostroma, timezone, Moscow Time]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moscow Time Context triple: [Kostroma, timezone, Moscow Time]
-
A.
Moscow Time
chosen
Moscow Time is the standard time zone used in Moscow and much of western Russia, corresponding to UTC+3 year-round.
-
B.
Yekaterinburg Time
Yekaterinburg Time is a Russian time zone used in the Ural region, typically four hours ahead of Coordinated Universal Time (UTC+4) and one hour ahead of Moscow Time.
-
C.
Krasnoyarsk Time (standard)
Krasnoyarsk Time (standard) is a time zone used in central Siberia, Russia, corresponding to UTC+7.
-
D.
Magadan Time
Magadan Time is a time zone used in parts of Russia’s Far East, including regions such as the Sakha Republic.
-
E.
Anadyr Time
Anadyr Time is the time zone used in Russia’s far northeastern regions, including Chukotka and parts of the Russian Far East, offset well ahead of Coordinated Universal Time.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada562540081908627950dd0b56a1e |
completed | March 8, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b20f63f8f881909348d4c6eb3c7e20 |
completed | March 12, 2026, 12:57 a.m. |
Created at: March 8, 2026, 3:05 p.m.