Triple

T3922479
Position Surface form Disambiguated ID Type / Status
Subject Pacific/Chatham E93192 entity
Predicate timeOffsetMinutesStandard P712 FINISHED
Object 765 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: 765 | Statement: [Pacific/Chatham, timeOffsetMinutesStandard, 765]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeOffsetMinutesStandard
Context triple: [Pacific/Chatham, timeOffsetMinutesStandard, 765]
  • A. UTCOffsetStandardTime chosen
    Indicates the time difference, in hours and minutes, that a location’s standard (non-daylight-saving) local time has from Coordinated Universal Time (UTC).
  • B. timeOffsetType
    Indicates the type or category of temporal offset that specifies how one time point is shifted relative to another.
  • C. timeDifferenceFromCentralStandard
    Indicates the time offset between a given time reference and Central Standard Time (CST), typically expressed as the difference in hours or minutes.
  • D. timeOffsetReference
    Indicates that a temporal value is specified relative to a particular reference time or event, defining the offset between them.
  • E. typicalOffsetFromCentralTime
    Indicates the usual time difference between a given time zone and Central Time (CT), expressed as an offset in hours or minutes.
  • 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_69aed96bfa1081908f7b30f2c647dee6 completed March 9, 2026, 2:30 p.m.
NER Named-entity recognition batch_69aef188b474819087680db42b04ecdd completed March 9, 2026, 4:12 p.m.
PD Predicate disambiguation batch_69aee75eedcc81908088ff4dbb8be56b completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:22 p.m.