Triple
T2787035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Russian time zone reform |
E61835
|
entity |
| Predicate | restoredTimeZones |
P43575
|
FINISHED |
| Object | some previously abolished Russian time zones |
—
|
LITERAL 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: some previously abolished Russian time zones | Statement: [2014 Russian time zone reform, restoredTimeZones, some previously abolished Russian time zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restoredTimeZones Context triple: [2014 Russian time zone reform, restoredTimeZones, some previously abolished Russian time zones]
-
A.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
B.
timeZoneDatabase
Indicates that there is an association between something (such as a system, service, or region) and a specific time zone database it uses or is defined by.
-
C.
relatedTimeZone
Indicates that two entities are associated with or operate within the same or corresponding time zone(s).
-
D.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
-
E.
timeZoneHistorical
Indicates that there is a historical time zone relationship, specifying how an entity’s time zone (including offsets, rules, or changes) applied during past periods.
- F. None of above. chosen
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. |
| PD | Predicate disambiguation | batch_69abdd025c948190a97dd961a9592bac |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdee94c2081908e5075e87e70780a |
completed | March 7, 2026, 8:16 a.m. |
Created at: March 6, 2026, 9:57 p.m.