Triple
T34950575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terespol–Brest |
E1007979
|
entity |
| Predicate | timezoneSideBelarus |
P107331
|
FINISHED |
| Object | Moscow Time |
—
|
NE NERFINISHED |
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: Moscow Time | Statement: [Terespol–Brest, timezoneSideBelarus, Moscow Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timezoneSideBelarus Context triple: [Terespol–Brest, timezoneSideBelarus, Moscow Time]
-
A.
timeZoneOnBelarusianSide
chosen
Indicates that the referenced time zone is the one used on the Belarusian side of a border, region, or context involving Belarus.
-
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.
timeZoneSideUkraine
Indicates that one entity is located on the Ukrainian side of a time zone boundary or within the time zone region associated with Ukraine.
-
D.
timeZoneOnPolishSide
Indicates that the referenced time zone applies to the Polish side of a border or region.
-
E.
modernBelarusianAdministrativeRegion
Indicates that an entity is an administrative region within the contemporary state structure of Belarus.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4 p.m.