Triple

T34531115
Position Surface form Disambiguated ID Type / Status
Subject Australian time zones E886537 entity
Predicate doesNotObserveDaylightSavingIn P15037 FINISHED
Object Queensland NE NERFINISHED

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: Queensland | Statement: [Australian time zones, doesNotObserveDaylightSavingIn, Queensland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: doesNotObserveDaylightSavingIn
Context triple: [Australian time zones, doesNotObserveDaylightSavingIn, Queensland]
  • A. doesNotObserveDaylightSavingTimeIn chosen
    Indicates that a place or jurisdiction does not adjust its clocks for daylight saving time in the specified region or context.
  • B. hasNoSeasonalClockChanges
    Indicates that a place or system does not adjust its clocks for seasonal time changes such as daylight saving time.
  • C. observesDaylightSavingWith
    Indicates that one entity follows the same daylight saving time rules or schedule as another entity.
  • D. observesDaylightSavingTimeFor
    Indicates that one entity follows or applies a specific daylight saving time scheme or rule for another entity (such as a place, time zone, or period).
  • E. observesDaylightSavingTime
    Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
  • 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_69f349cd7c148190aa99192b126d1527 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71fbfe61c81909bcfd3ba504769e7 completed May 3, 2026, 10:13 a.m.
PD Predicate disambiguation batch_69f71cc8074c81909ae09bea2acf1a09 completed May 3, 2026, 10 a.m.
Created at: May 1, 2026, 2:02 a.m.