Triple
T2787014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Russian time zone reform |
E61835
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Russia |
C1824
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: event in Russia Context triple: [2014 Russian time zone reform, instanceOf, event in Russia]
-
A.
event in the Russo-Ukrainian War
An event in the Russo-Ukrainian War is a specific, temporally and geographically bounded occurrence—such as a battle, diplomatic action, territorial change, or significant incident—that affects the course, perception, or outcomes of the conflict.
-
B.
event in the Russian Revolution
An event in the Russian Revolution is a significant historical occurrence—such as a protest, decree, battle, or political change—that contributed to the overthrow of the tsarist regime and the subsequent rise of Soviet power.
-
C.
oblast of Russia
An oblast of Russia is a primary administrative division comparable to a province, governed by regional authorities under the federal structure of the Russian Federation.
-
D.
event
chosen
An event is a distinct occurrence or happening, often bounded in time and space, that involves one or more participants and may trigger changes in state or behavior within a system.
-
E.
military event
A military event is an occurrence involving organized armed forces engaging in actions such as combat, maneuvers, operations, or strategic activities within a specific time and place.
- F. None of above.
Provenance (1 batch)
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. |
Created at: March 6, 2026, 9:57 p.m.