Triple

T38378636
Position Surface form Disambiguated ID Type / Status
Subject Kyrgyzstan Time E893694 entity
Predicate DSTStatusSince1990s P85540 FINISHED
Object permanent standard time 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: permanent standard time | Statement: [Kyrgyzstan Time, DSTStatusSince1990s, permanent standard time]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: DSTStatusSince1990s
Context triple: [Kyrgyzstan Time, DSTStatusSince1990s, permanent standard time]
  • A. historicalDSTUsage
    Indicates that there was a period in the past when the entity or location observed daylight saving time, even if it may not do so currently.
  • B. DSTseason
    Indicates that the relationship specifies the daylight saving time (DST) period or season during which a time-related event or setting is in effect.
  • C. DSTNotRegularSince chosen
    Indicates that daylight saving time has not been regularly observed in the specified location since a given point in time.
  • D. DSTobserved
    Indicates that daylight saving time is in effect or being observed for a given time, date, or location.
  • E. DSTPolicy
    Indicates a relationship where a timekeeping system follows a specific daylight saving time policy, defining how and when clocks are adjusted seasonally.
  • 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_69f76e4b1f748190a380696a16eae4a2 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fcd1499e2c81909bafd84dc4810f45 completed May 7, 2026, 5:52 p.m.
PD Predicate disambiguation batch_69fcccf024ec819086383ffbb6cfc036 completed May 7, 2026, 5:33 p.m.
Created at: May 3, 2026, 4:31 p.m.