Triple
T4191430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CST |
E89044
|
entity |
| Predicate | DSTShiftFromVariant |
P8057
|
FINISHED |
| Object | -1 hour from CDT |
—
|
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: -1 hour from CDT | Statement: [CST, DSTShiftFromVariant, -1 hour from CDT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DSTShiftFromVariant Context triple: [CST, DSTShiftFromVariant, -1 hour from CDT]
-
A.
DSTType
Indicates the type or classification of daylight saving time (DST) applied to a given time zone or region.
-
B.
DSTOffsetChange
chosen
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
C.
DSTOffsetType
Indicates the relationship between a time reference and the amount of time it is shifted from standard time due to daylight saving time adjustments.
-
D.
DSTTimeZone
Indicates that a time-related entity operates under a daylight saving time rule or belongs to a time zone that observes daylight saving time adjustments.
-
E.
hasDaylightSavingVariant
Indicates that one time-related entity is the daylight saving time version or counterpart of another standard-time entity.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:46 p.m.