Triple

T8981798
Position Surface form Disambiguated ID Type / Status
Subject Rock Sound International Airport E214547 entity
Predicate usesSummerTimeZone P5550 FINISHED
Object Eastern Daylight Time 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: Eastern Daylight Time | Statement: [Rock Sound International Airport, usesSummerTimeZone, Eastern Daylight Time]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesSummerTimeZone
Context triple: [Rock Sound International Airport, usesSummerTimeZone, Eastern Daylight Time]
  • A. summerTimeZone chosen
    Indicates that a specified region or entity uses a particular time zone during the summer or daylight-saving period.
  • B. isSummerTimeVariantOf
    Indicates that one temporal or time-related entity is the daylight-saving (summer time) version of another standard-time entity.
  • C. isSummerMonthInRegion
    Indicates that a given month falls within the summer season for a specified geographic region.
  • D. summerUtcOffset
    Indicates the difference in hours or minutes between local time and Coordinated Universal Time (UTC) during the summer or daylight saving period.
  • E. isDaylightSavingTime
    Indicates that the specified time or date falls within a period when daylight saving time rules are in effect.
  • 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_69ca839ea8b88190922c6a326ffcc0d3 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc67a76f748190a4abad5d53d58fa8 completed April 1, 2026, 12:32 a.m.
PD Predicate disambiguation batch_69cc5edba0f88190b97401636a076d7a completed March 31, 2026, 11:55 p.m.
Created at: March 30, 2026, 7:03 p.m.