Triple
T8478874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yekaterinburg Time |
E200462
|
entity |
| Predicate | changedUTCoffsetInYear |
P8057
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Yekaterinburg Time, changedUTCoffsetInYear, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedUTCoffsetInYear Context triple: [Yekaterinburg Time, changedUTCoffsetInYear, 2011]
-
A.
DSTChangeYear
Indicates the specific year in which a daylight saving time (DST) change occurs or is scheduled to occur.
-
B.
DSTOffsetChange
chosen
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
C.
usesUTCOffset
Indicates that one entity applies or relies on the specified UTC time offset for timekeeping or timestamp interpretation.
-
D.
previousUTCOffset
Indicates the UTC time offset that applied to an entity (such as a timezone or location) immediately before the current or given offset.
-
E.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
- 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.