Triple
T323256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow City Duma |
E6460
|
entity |
| Predicate | locatedInTimeZone |
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: [Moscow City Duma, locatedInTimeZone, Moscow Time]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moscow Time Context triple: [Moscow City Duma, locatedInTimeZone, 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.
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).
-
C.
Moscow
Moscow is the capital and largest city of Russia, serving as its political, economic, and cultural center.
-
D.
Yakutsk Time (seasonally, depending on Russian DST history)
Yakutsk Time is a time zone used in eastern Russia that has seasonally aligned with Japan Standard Time at various points depending on Russia’s daylight saving time policies.
-
E.
Madras Time
Madras Time was a former local time standard used in the Madras (now Chennai) region of India before the adoption of a unified national time zone.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea82ba748190bae651f5de908617 |
completed | Feb. 28, 2026, 1:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3d240b0d881908611456ba7b29fce |
completed | March 1, 2026, 5:44 a.m. |
Created at: Feb. 28, 2026, 1:08 p.m.