Triple

T622577
Position Surface form Disambiguated ID Type / Status
Subject Toronto Pearson International Airport E14544 entity
Predicate timezoneDaylightSaving P713 FINISHED
Object UTC−04:00 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−04:00 | Statement: [Toronto Pearson International Airport, timezoneDaylightSaving, UTC−04:00]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timezoneDaylightSaving
Context triple: [Toronto Pearson International Airport, timezoneDaylightSaving, UTC−04:00]
  • A. daylightSavingTimeHemisphere
    Indicates the hemisphere (e.g., northern or southern) in which a location follows a particular daylight saving time pattern.
  • B. isDaylightSavingShift
    Indicates that a change in local clock time occurs due to the start or end of daylight saving time.
  • C. UTCOffsetDaylightSavingTime chosen
    Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
  • D. observesDaylightSavingTime
    Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
  • E. hasDaylightSavingVariant
    Indicates that one time-related entity is the daylight saving time version or counterpart of another standard-time entity.
  • 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_69a4934b17c881909ace8270e8ddd202 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49e402d9c8190936896e3ebb6edc5 completed March 1, 2026, 8:14 p.m.
PD Predicate disambiguation batch_69a49d0069d0819087c83b608f6fc053 completed March 1, 2026, 8:09 p.m.
Created at: March 1, 2026, 7:35 p.m.