Triple
T8478852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yekaterinburg Time |
E200462
|
entity |
| Predicate | offsetInHoursFromMoscowTime |
P29831
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Yekaterinburg Time, offsetInHoursFromMoscowTime, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offsetInHoursFromMoscowTime Context triple: [Yekaterinburg Time, offsetInHoursFromMoscowTime, 2]
-
A.
offsetFromMoscowTimeHours
chosen
Indicates the time difference, in whole or fractional hours, between a given time reference and Moscow’s local time.
-
B.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
-
C.
offsetFromUTCInHours
Indicates the number of hours a time value is offset from Coordinated Universal Time (UTC), positive for time zones ahead and negative for those behind.
-
D.
offsetFromEasternEuropeanTime
Indicates that one time value is a specified offset relative to Eastern European Time (EET).
-
E.
offsetDSTDifferenceHours
Indicates the difference in time zone offsets, measured in hours, that results specifically from the application of daylight saving time.
- F. None of above.
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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5216d6481908e25a49bcc2e00cc |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.