Triple

T349138
Position Surface form Disambiguated ID Type / Status
Subject Pacific Time Zone E7402 entity
Predicate timeDifferenceFromCentralStandard P11086 FINISHED
Object 2 hours behind 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: 2 hours behind | Statement: [Pacific Time Zone, timeDifferenceFromCentralStandard, 2 hours behind]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeDifferenceFromCentralStandard
Context triple: [Pacific Time Zone, timeDifferenceFromCentralStandard, 2 hours behind]
  • A. differenceFromUSEasternStandardTime
    Indicates the time offset or deviation of something’s time setting relative to U.S. Eastern Standard Time.
  • B. differenceFromUSEasternDaylightTime
    Indicates that one temporal value differs by a specified amount or offset from the time expressed in US Eastern Daylight Time.
  • C. differenceFromChinaStandardTime
    Indicates the time offset or deviation of something’s time setting relative to China Standard Time.
  • D. timeDifferenceToCETWinter
    Indicates the time offset between a given time and Central European Time during the winter (standard time) period.
  • E. timeDifferenceToCETSummer
    Indicates the time offset between a given time and Central European Time during the summer (daylight saving) period.
  • 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_69a2e7e696948190bebc966535995e45 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eb1dc5f88190b54d084c6def7fc5 completed Feb. 28, 2026, 1:18 p.m.
PD Predicate disambiguation batch_69a2e955d1f88190bd687c46fa7c5469 completed Feb. 28, 2026, 1:10 p.m.
PDg Predicate description generation batch_69a2ea60e590819081779a6510918d9b completed Feb. 28, 2026, 1:15 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.