Triple
T3923948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Matamoros |
E93226
|
entity |
| Predicate | offsetDSTApprox |
P51698
|
FINISHED |
| Object | UTC−05:00 |
—
|
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: UTC−05:00 | Statement: [America/Matamoros, offsetDSTApprox, UTC−05:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offsetDSTApprox Context triple: [America/Matamoros, offsetDSTApprox, UTC−05:00]
-
A.
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.
-
B.
offsetDSTDifferenceHours
Indicates the difference in time zone offsets, measured in hours, that results specifically from the application of daylight saving time.
-
C.
observesDSTOffset
Indicates that one entity follows or applies a specific daylight saving time (DST) offset in its timekeeping or scheduling.
-
D.
DSTOffsetChange
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
E.
DSTIsAheadOfUTC
Indicates that the time in a region observing Daylight Saving Time is ahead of Coordinated Universal Time (UTC) by a specified offset.
- F. None of above. chosen
Provenance (4 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeed7dacdc8190854ebc13db2d24bc |
completed | March 9, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69aee7609c4081908000ce12ae827c3f |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb5f859c819095b61f5ba8eace4f |
completed | March 9, 2026, 3:46 p.m. |
Created at: March 9, 2026, 3:23 p.m.