Triple

T6352267
Position Surface form Disambiguated ID Type / Status
Subject Laclede, Missouri E142900 entity
Predicate hasTimezoneAbbreviation P67797 FINISHED
Object 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: CST | Statement: [Laclede, Missouri, hasTimezoneAbbreviation, CST]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTimezoneAbbreviation
Context triple: [Laclede, Missouri, hasTimezoneAbbreviation, CST]
  • A. includesTimeZoneAbbreviation chosen
    Indicates that something explicitly contains or specifies a time zone abbreviation as part of its representation or data.
  • B. hasTimeZones
    Indicates that an entity is associated with one or more time zones in which it is valid or operates.
  • C. hasStandardTimeUTCOffset
    Indicates the fixed difference in hours and minutes between an entity’s standard (non-daylight-saving) local time and Coordinated Universal Time (UTC).
  • D. DSTAbbreviation
    Indicates that one entity is the standard abbreviated form used to represent another entity related to daylight saving time.
  • E. 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).
  • 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_69c008d6dcbc8190aa1c2f1fd8916b42 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c067dd3c74819085a164b750094c46 completed March 22, 2026, 10:06 p.m.
PD Predicate disambiguation batch_69c060ec091c8190912aac44e1b8b1c9 completed March 22, 2026, 9:36 p.m.
Created at: March 22, 2026, 4:31 p.m.