Triple

T17861763
Position Surface form Disambiguated ID Type / Status
Subject Jamaica Standard Time E446088 entity
Predicate isFixedOffsetYearRound P4886 FINISHED
Object yes 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: yes | Statement: [Jamaica Standard Time, isFixedOffsetYearRound, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isFixedOffsetYearRound
Context triple: [Jamaica Standard Time, isFixedOffsetYearRound, yes]
  • A. isFixedOffsetFromUTC chosen
    Indicates that one time-related entity consistently differs from Coordinated Universal Time (UTC) by a specific, unchanging offset.
  • B. isFixedOffsetSince
    Indicates that one entity consistently occurs or is positioned at a constant, unchanging offset in time or value relative to another reference entity.
  • C. hasNonIntegerHourOffset
    Indicates that the time-related value or time zone differs from a reference time by an offset that is not a whole number of hours (e.g., includes 30- or 45-minute increments).
  • D. hasStandardTimeUTCOffset
    Indicates the fixed difference in hours and minutes between an entity’s standard (non-daylight-saving) local time and Coordinated Universal Time (UTC).
  • E. hasTimeOffset
    Indicates that one temporal value is shifted or displaced from another by a specified amount of 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_69d8b9f26f18819089c9e43250bee6ae completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e49790ea148190b7a966812d44f430 completed April 19, 2026, 8:51 a.m.
PD Predicate disambiguation batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 completed April 18, 2026, 7:17 p.m.
Created at: April 10, 2026, 10:17 a.m.