Triple
T29996437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belarus–Ukraine border |
E762036
|
entity |
| Predicate | timeZoneSideUkraineDST |
P168731
|
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: [Belarus–Ukraine border, timeZoneSideUkraineDST, UTC+3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneSideUkraineDST Context triple: [Belarus–Ukraine border, timeZoneSideUkraineDST, UTC+3]
-
A.
timeZoneSideUkraine
chosen
Indicates that one entity is located on the Ukrainian side of a time zone boundary or within the time zone region associated with Ukraine.
-
B.
timeZoneOnRussianSide
Indicates that the referenced time zone is the one used on the Russian side of a border, region, or cross-border context.
-
C.
timeZoneOnBelarusianSide
Indicates that the referenced time zone is the one used on the Belarusian side of a border, region, or context involving Belarus.
-
D.
timeZoneOnPolishSide
Indicates that the referenced time zone applies to the Polish side of a border or region.
-
E.
timeZoneOnKazakhSide
Indicates that the referenced time zone is the one used on the Kazakh side of a border, region, or shared area.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6791f059481908ae818256390255c |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:40 p.m.