Triple

T247384
Position Surface form Disambiguated ID Type / Status
Subject Indian Standard Time E5066 entity
Predicate differenceFromUSEasternStandardTime P8740 FINISHED
Object +10:30 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: +10:30 | Statement: [Indian Standard Time, differenceFromUSEasternStandardTime, +10:30]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: differenceFromUSEasternStandardTime
Context triple: [Indian Standard Time, differenceFromUSEasternStandardTime, +10:30]
  • A. relativeToEasternTime
    Indicates that the timing or occurrence of an event is specified or interpreted with respect to the Eastern Time zone.
  • B. UTCOffsetStandardTime
    Indicates the time difference, in hours and minutes, that a location’s standard (non-daylight-saving) local time has from Coordinated Universal Time (UTC).
  • C. UTCOffsetDaylightSavingTime
    Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
  • D. offsetInSecondsFromUTC
    Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
  • E. isOneHourAheadOf
    Indicates that one entity’s local time is exactly one hour later than the other entity’s local 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_69a257c4bf688190a46ebbf411ab7473 completed Feb. 28, 2026, 2:49 a.m.
NER Named-entity recognition batch_69a25d13b8088190a3f48f0388d57496 completed Feb. 28, 2026, 3:12 a.m.
PD Predicate disambiguation batch_69a25b64ea3081908de626a0e1445bdb completed Feb. 28, 2026, 3:05 a.m.
PDg Predicate description generation batch_69a25c2ca46c81908c61696f31e59a98 completed Feb. 28, 2026, 3:08 a.m.
Created at: Feb. 28, 2026, 2:54 a.m.