Triple
T151621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Time |
E3442
|
entity |
| Predicate | changedToUTCPlus3 |
P5578
|
FINISHED |
| Object | 2014-10-26 |
—
|
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: 2014-10-26 | Statement: [Moscow Time, changedToUTCPlus3, 2014-10-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedToUTCPlus3 Context triple: [Moscow Time, changedToUTCPlus3, 2014-10-26]
-
A.
isOneHourAheadOf
Indicates that one entity’s local time is exactly one hour later than the other entity’s local time.
-
B.
UTCOffsetDaylightSavingTime
Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
-
C.
relativeToEasternTime
Indicates that the timing or occurrence of an event is specified or interpreted with respect to the Eastern Time zone.
-
D.
UTCOffsetStandardTime
Indicates the time difference, in hours and minutes, that a location’s standard (non-daylight-saving) local time has from Coordinated Universal Time (UTC).
-
E.
locatedInTimeZone
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580f55a88190b37b54ee0ed5ac7c |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565adaf48190b68ae4444ff83ccd |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a256eb46ec81909c730000e5041d0d |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.