Triple

T20506912
Position Surface form Disambiguated ID Type / Status
Subject Daylight saving time (United States) E503457 entity
Predicate previousEndRule P100162 FINISHED
Object last Sunday in October (before 2007) 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: last Sunday in October (before 2007) | Statement: [Daylight saving time (United States), previousEndRule, last Sunday in October (before 2007)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: previousEndRule
Context triple: [Daylight saving time (United States), previousEndRule, last Sunday in October (before 2007)]
  • A. previousRule chosen
    Indicates that one rule directly precedes another rule in an ordered sequence or hierarchy.
  • B. endRule
    Indicates that a previously active rule, regulation, or governing condition is terminated or ceases to apply.
  • C. typicalEndRule
    Indicates the rule or condition that normally determines how or when a process, event, or relationship comes to an end.
  • D. endOfRuleContext
    Indicates that a particular parsing or evaluation rule has reached its terminating boundary within the current context.
  • E. reasonForEndOfRule
    Indicates the cause, circumstance, or event that led to the termination or conclusion of a particular rule or period of rule.
  • 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_69e0b4b1e52c8190894281cf7e3283ab completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69dc82dd0819085d64d65a1e72c70 completed April 20, 2026, 9:42 p.m.
PD Predicate disambiguation batch_69e59fcdf6e08190a604204615dc56e6 completed April 20, 2026, 3:38 a.m.
Created at: April 16, 2026, 11:36 a.m.