Triple

T10921408
Position Surface form Disambiguated ID Type / Status
Subject Providenciales International Airport E257954 entity
Predicate uses daylight saving time P384 FINISHED
Object no 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: no | Statement: [Providenciales International Airport, uses daylight saving time, no]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: uses daylight saving time
Context triple: [Providenciales International Airport, uses daylight saving time, no]
  • A. observesDaylightSavingTime chosen
    Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
  • B. isDaylightSavingTime
    Indicates that the specified time or date falls within a period when daylight saving time rules are in effect.
  • C. daylightSavingTimeHemisphere
    Indicates the hemisphere (e.g., northern or southern) in which a location follows a particular daylight saving time pattern.
  • D. observesDaylightSavingWith
    Indicates that one entity follows the same daylight saving time rules or schedule as another entity.
  • E. observesDaylightSavingTimeInSomeRegions
    Indicates that the entity follows daylight saving time practices, but only in certain parts or regions of its jurisdiction or coverage area.
  • 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_69d6aa864ed88190818280ab6791d065 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d77082a1488190850a4409339c3e1e completed April 9, 2026, 9:25 a.m.
PD Predicate disambiguation batch_69d72e799f808190b6ab64fc7586a303 completed April 9, 2026, 4:43 a.m.
Created at: April 8, 2026, 9:22 p.m.