Triple

T35763756
Position Surface form Disambiguated ID Type / Status
Subject Coward, South Carolina E1033950 entity
Predicate isInTimeZoneUTCOffsetStandard P68829 FINISHED
Object UTC−05:00 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: UTC−05:00 | Statement: [Coward, South Carolina, isInTimeZoneUTCOffsetStandard, UTC−05:00]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInTimeZoneUTCOffsetStandard
Context triple: [Coward, South Carolina, isInTimeZoneUTCOffsetStandard, UTC−05:00]
  • A. isInTimeZoneOffset
    Indicates that one temporal entity occurs within, or is associated with, a specific time zone offset relative to a reference time standard (such as UTC).
  • B. hasStandardTimeUTCOffset chosen
    Indicates the fixed difference in hours and minutes between an entity’s standard (non-daylight-saving) local time and Coordinated Universal Time (UTC).
  • C. isStandardTimeFor
    Indicates that a specified time zone or region is currently observing its standard (non-daylight-saving) time.
  • D. isStandardTimeIn
    Indicates that a specified time value is expressed in the standard (non-daylight-saving) time for a given region or timezone.
  • E. hasStandardTimeZone
    Indicates that an entity is associated with a particular standard time zone used to define its official local time.
  • 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_69f76e13edd081909101629aa829c4ad completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a1c61e248190ab11908163d6f26c completed May 3, 2026, 7:28 p.m.
PD Predicate disambiguation batch_69f7a070e23881909a233370acb57384 completed May 3, 2026, 7:22 p.m.
Created at: May 3, 2026, 4:06 p.m.