Triple

T37775755
Position Surface form Disambiguated ID Type / Status
Subject Europe/Helsinki E941682 entity
Predicate typicalStandardOffsetHours P204382 FINISHED
Object 2 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: 2 | Statement: [Europe/Helsinki, typicalStandardOffsetHours, 2]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalStandardOffsetHours
Context triple: [Europe/Helsinki, typicalStandardOffsetHours, 2]
  • A. typicalOffsetFromCentralTime
    Indicates the usual time difference between a given time zone and Central Time (CT), expressed as an offset in hours or minutes.
  • B. typicalOffsetFromPacificTime
    Indicates the usual time difference between a given time zone and Pacific Time (PT), without accounting for temporary variations like daylight saving changes.
  • C. typicalOffsetWinter
    Indicates the usual temporal or spatial offset associated with winter in relation to a reference point or period.
  • D. typicalDSTChangeHour
    Indicates the usual clock time at which a daylight saving time change (such as shifting clocks forward or backward) is applied.
  • E. typicalUtcOffsetRange
    Indicates the usual range of UTC time offsets during which an entity (such as a place or time zone) normally operates, accounting for standard and daylight saving variations.
  • 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_69f76ee4431881908f87e8892a9f39f3 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a037cae084081909004d77514c5f286 completed May 12, 2026, 7:17 p.m.
PD Predicate disambiguation batch_6a037a1772e48190ba738c6d11b321e2 completed May 12, 2026, 7:05 p.m.
PDg Predicate description generation batch_6a037c84ecbc81908232e5215355f43b completed May 12, 2026, 7:16 p.m.
Created at: May 3, 2026, 4:19 p.m.