Triple
T19616537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europe/Minsk |
E470874
|
entity |
| Predicate | standardOffsetLabel |
P34679
|
FINISHED |
| Object | UTC+3 |
—
|
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+3 | Statement: [Europe/Minsk, standardOffsetLabel, UTC+3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardOffsetLabel Context triple: [Europe/Minsk, standardOffsetLabel, UTC+3]
-
A.
standardTimeDesignation
Indicates that one entity designates or specifies the standard (non-daylight-saving) time applicable to another entity.
-
B.
standardTimeName
Indicates the official name assigned to a particular standard time used in a region or context.
-
C.
standardTimeType
Indicates that a time value is expressed using a particular standard or conventional time format or classification.
-
D.
standardTimeCounterpart
Indicates that one time representation is the corresponding value expressed in a standard or canonical time format for the other.
-
E.
utcOffsetDescription
chosen
Indicates the textual description of how far a time zone’s local time differs from Coordinated Universal Time (UTC), often including details like hours, minutes, and daylight saving adjustments.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e272808190800c5bccccd64753 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.