Triple

T3965191
Position Surface form Disambiguated ID Type / Status
Subject America/El_Salvador E92199 entity
Predicate observesStandardTimeName P6028 FINISHED
Object Central Standard Time (CST) 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: Central Standard Time (CST) | Statement: [America/El_Salvador, observesStandardTimeName, Central Standard Time (CST)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: observesStandardTimeName
Context triple: [America/El_Salvador, observesStandardTimeName, Central Standard Time (CST)]
  • A. observedAsStandardTimeIn chosen
    Indicates that a particular time standard is used as the official or standard time within a specified place or region.
  • B. standardTimeName
    Indicates the official name assigned to a particular standard time used in a region or context.
  • C. daylightSavingTimeName
    Indicates the specific name or label used for the time zone during daylight saving time.
  • D. observesDaylightSavingTimeFor
    Indicates that one entity follows or applies a specific daylight saving time scheme or rule for another entity (such as a place, time zone, or period).
  • E. DSTobserved
    Indicates that daylight saving time is in effect or being observed for a given time, date, or location.
  • 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_69aed96624188190ac8c45bb57ab72b5 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefba878a48190a2e234d775215938 completed March 9, 2026, 4:56 p.m.
PD Predicate disambiguation batch_69aef8efcf3c81908ccf61d9ce26b0c0 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:31 p.m.