Triple

T229437
Position Surface form Disambiguated ID Type / Status
Subject Eastern European Time E4377 entity
Predicate typicalOffsetFromUTC P4413 FINISHED
Object two hours ahead 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: two hours ahead | Statement: [Eastern European Time, typicalOffsetFromUTC, two hours ahead]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalOffsetFromUTC
Context triple: [Eastern European Time, typicalOffsetFromUTC, two hours ahead]
  • A. typicalOffsetFromCentralTime
    Indicates the usual time difference between a given time zone and Central Time (CT), expressed as an offset in hours or minutes.
  • B. typicalOffsetFromPacificTime
    Indicates the usual time difference between a given time zone and Pacific Time (PT), without accounting for temporary variations like daylight saving changes.
  • 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. offsetFromUTCInHours chosen
    Indicates the number of hours a time value is offset from Coordinated Universal Time (UTC), positive for time zones ahead and negative for those behind.
  • 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_69a257363ffc81909757bde7ab3404da completed Feb. 28, 2026, 2:47 a.m.
NER Named-entity recognition batch_69a25e0868708190ad551ca06cc57f4a completed Feb. 28, 2026, 3:16 a.m.
PD Predicate disambiguation batch_69a25b5a075081909b0e9b88c1492d5a completed Feb. 28, 2026, 3:04 a.m.
Created at: Feb. 28, 2026, 2:53 a.m.