Triple

T7681088
Position Surface form Disambiguated ID Type / Status
Subject Mogilyovsky Bridge E173993 entity
Predicate locatedInTimeZone P109 FINISHED
Object Moscow Time Zone 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 Zone | Statement: [Mogilyovsky Bridge, locatedInTimeZone, Moscow Time Zone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moscow Time Zone
Context triple: [Mogilyovsky Bridge, locatedInTimeZone, Moscow Time Zone]
  • 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. Russian Empire standard time
    Russian Empire standard time was the official time standard used across the territories of the Russian Empire before the adoption of modern time zones.
  • D. Kaliningrad Time
    Kaliningrad Time is the time standard used in Russia’s Kaliningrad Oblast, corresponding to UTC+2 and aligning with Eastern European Time without daylight saving changes.
  • E. Irkutsk Time
    Irkutsk Time is a time zone in eastern Siberia, Russia, set eight hours ahead of Coordinated Universal Time (UTC+8).
  • 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_69c6995840408190a19de6c51090f46f completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c701ffc1fc8190bc9c2b1f3bb37f0d completed March 27, 2026, 10:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8a24de3a48190a92009b6092b09d0 completed March 29, 2026, 3:53 a.m.
Created at: March 27, 2026, 4:01 p.m.