Triple
T8478873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yekaterinburg Time |
E200462
|
entity |
| Predicate | previousUTCoffsetBefore2011 |
P5577
|
FINISHED |
| Object | UTC+06:00 |
—
|
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: UTC+06:00 | Statement: [Yekaterinburg Time, previousUTCoffsetBefore2011, UTC+06:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousUTCoffsetBefore2011 Context triple: [Yekaterinburg Time, previousUTCoffsetBefore2011, UTC+06:00]
-
A.
previousUTCOffset
chosen
Indicates the UTC time offset that applied to an entity (such as a timezone or location) immediately before the current or given offset.
-
B.
previousTimeStandard
Indicates that one time standard directly preceded another in chronological use or official adoption.
-
C.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
-
D.
isAheadOfUTC
Indicates that a time, date, or timezone occurs at a later (positive offset) time than Coordinated Universal Time (UTC).
-
E.
previouslyObservedDST
Indicates that the subject has been observed in a context where daylight saving time (DST) was in effect at some point in the past.
- 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.