Triple
T34549106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Западный административный округ города Москвы |
E887011
|
entity |
| Predicate | часовойПояс |
P179309
|
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: [Западный административный округ города Москвы, часовойПояс, UTC+3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: часовойПояс Context triple: [Западный административный округ города Москвы, часовойПояс, UTC+3]
-
A.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
-
B.
isThreeQuartersOfAnHourAheadOf
Indicates that one entity’s time occurs exactly 45 minutes later than the other entity’s time.
-
C.
countryMainlandTimeDifference
Indicates the time difference between a country’s mainland and another referenced region or standard time.
-
D.
capitalTimeZoneOf
Indicates that a specified time zone is the primary or official time zone in which a given capital city is located or operates.
-
E.
timeZoneOnRussianSide
Indicates that the referenced time zone is the one used on the Russian side of a border, region, or cross-border context.
- F. None of above. chosen
Provenance (4 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720239d9881909ded0a06477fd9b8 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: May 1, 2026, 2:02 a.m.