Triple
T2787031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Russian time zone reform |
E61835
|
entity |
| Predicate | changedUTCOffsetOf |
P5578
|
FINISHED |
| Object | Moscow Time |
E3442
|
NE FINISHED |
How this triple was built (3 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: [2014 Russian time zone reform, changedUTCOffsetOf, Moscow Time]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moscow Time Context triple: [2014 Russian time zone reform, changedUTCOffsetOf, 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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedUTCOffsetOf Context triple: [2014 Russian time zone reform, changedUTCOffsetOf, Moscow Time]
-
A.
usesUTCOffset
Indicates that one entity applies or relies on the specified UTC time offset for timekeeping or timestamp interpretation.
-
B.
DSTOffsetChange
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
C.
changedToUTCPlus3
chosen
Indicates that something has been converted or adjusted to use the UTC+3 time zone.
-
D.
previousUTCOffset
Indicates the UTC time offset that applied to an entity (such as a timezone or location) immediately before the current or given offset.
-
E.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
- F. None of above.
Provenance (4 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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdeea881481908d759c72798a50fb |
completed | March 7, 2026, 8:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afce8e2c488190a63332f36803c295 |
completed | March 10, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abdd025c948190a97dd961a9592bac |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.