Triple

T1252010
Position Surface form Disambiguated ID Type / Status
Subject Africa/Bujumbura E26895 entity
Predicate offsetDoesNotVarySeasonally P13686 FINISHED
Object true 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: true | Statement: [Africa/Bujumbura, offsetDoesNotVarySeasonally, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: offsetDoesNotVarySeasonally
Context triple: [Africa/Bujumbura, offsetDoesNotVarySeasonally, true]
  • A. hasNoSeasonalClockChanges chosen
    Indicates that a place or system does not adjust its clocks for seasonal time changes such as daylight saving time.
  • B. hasSeasonalPattern
    Indicates that the occurrence, intensity, or characteristics of something regularly vary according to a recurring seasonal cycle.
  • C. doesNotObserveDaylightSavingTimeIn
    Indicates that a place or jurisdiction does not adjust its clocks for daylight saving time in the specified region or context.
  • D. hasSeasonalStatus
    Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
  • E. nonTraditionalSeason
    Indicates that an event, activity, or occurrence takes place outside the customary or standard season in which it is typically expected.
  • 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_69a49487a9c48190ba9b05348fd1b53f completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4bf85e1e08190ba6aac3fcd8bb3e7 completed March 1, 2026, 10:36 p.m.
PD Predicate disambiguation batch_69a4bb6c977c8190a2bf3e8b67a59beb completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:47 p.m.