Triple

T4909244
Position Surface form Disambiguated ID Type / Status
Subject Mountain Daylight Time E110191 entity
Predicate hoursBehindCentralDaylightTime P59377 FINISHED
Object 1 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: 1 | Statement: [Mountain Daylight Time, hoursBehindCentralDaylightTime, 1]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hoursBehindCentralDaylightTime
Context triple: [Mountain Daylight Time, hoursBehindCentralDaylightTime, 1]
  • A. hoursAheadOfUTC
    Indicates the number of hours by which a given time or timezone is offset ahead of Coordinated Universal Time (UTC).
  • B. hoursAheadOf
    Indicates that one entity’s time is a specified number of hours ahead of another entity’s time.
  • C. differenceFromUSEasternDaylightTime
    Indicates that one temporal value differs by a specified amount or offset from the time expressed in US Eastern Daylight Time.
  • D. timeDifferenceFromCentralStandard
    Indicates the time offset between a given time reference and Central Standard Time (CST), typically expressed as the difference in hours or minutes.
  • E. differenceFromUSEasternStandardTime
    Indicates the time offset or deviation of something’s time setting relative to U.S. Eastern Standard Time.
  • F. None of above. chosen

Provenance (4 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_69bd44132b94819088522d92beaadc78 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6e99414081908c3d3283f563bba4 completed March 20, 2026, 3:58 p.m.
PD Predicate disambiguation batch_69bd6c325e188190823836d79934e9bc completed March 20, 2026, 3:48 p.m.
PDg Predicate description generation batch_69bd6cc228088190849f23b7bd4cf549 completed March 20, 2026, 3:50 p.m.
Created at: March 20, 2026, 1:29 p.m.