Triple

T13928716
Position Surface form Disambiguated ID Type / Status
Subject IST E334928 entity
Predicate usesDaylightSavingTransitionRules P54666 FINISHED
Object defined by Israeli law 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: defined by Israeli law | Statement: [IST, usesDaylightSavingTransitionRules, defined by Israeli law]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesDaylightSavingTransitionRules
Context triple: [IST, usesDaylightSavingTransitionRules, defined by Israeli law]
  • A. hasDaylightSavingVariant
    Indicates that one time-related entity is the daylight saving time version or counterpart of another standard-time entity.
  • B. observesDaylightSavingWith
    Indicates that one entity follows the same daylight saving time rules or schedule as another entity.
  • C. daylightSavingRule chosen
    Indicates the rule or policy that defines when and how daylight saving time is applied or adjusted for a given context.
  • D. observesDaylightSavingTimeInSomeRegions
    Indicates that the entity follows daylight saving time practices, but only in certain parts or regions of its jurisdiction or coverage area.
  • E. isDaylightSavingShift
    Indicates that a change in local clock time occurs due to the start or end of daylight saving time.
  • 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_69d81c5f739081908bc05b2461f54828 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2aa900a0819095eeb1bc46b0336e completed April 14, 2026, 11:53 a.m.
PD Predicate disambiguation batch_69de059e4ba881908554f72e889719fa completed April 14, 2026, 9:15 a.m.
Created at: April 9, 2026, 10:16 p.m.