Triple
T10665759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verny |
E251352
|
entity |
| Predicate | nowInTimeZone |
P109
|
FINISHED |
| Object | UTC+6 via Almaty |
—
|
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+6 via Almaty | Statement: [Verny, nowInTimeZone, UTC+6 via Almaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nowInTimeZone Context triple: [Verny, nowInTimeZone, UTC+6 via Almaty]
-
A.
locatedInTimeZone
chosen
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
B.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
-
C.
timeZoneContext
Indicates the time zone setting or context in which an event, action, or relationship is interpreted.
-
D.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
-
E.
locatedInTimeZoneUTCOffsetDST
Indicates that an entity exists or operates in a time zone that observes daylight saving time with a specified UTC offset during that DST period.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6f31f87748190bb44db8afa901763 |
completed | April 9, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:08 p.m.