Triple
T35429925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Cancun |
E1024027
|
entity |
| Predicate | changeToUtcMinusFiveEffectiveDate |
P182969
|
FINISHED |
| Object | 2015-02-01 |
—
|
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: 2015-02-01 | Statement: [America/Cancun, changeToUtcMinusFiveEffectiveDate, 2015-02-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changeToUtcMinusFiveEffectiveDate Context triple: [America/Cancun, changeToUtcMinusFiveEffectiveDate, 2015-02-01]
-
A.
offsetChangeToUTCMinus4Implemented
Indicates that a change in time zone offset has been applied so that the affected time is now set to UTC−4.
-
B.
relativeToEasternTime
Indicates that the timing or occurrence of an event is specified or interpreted with respect to the Eastern Time zone.
-
C.
timeZoneAtUSEnd
Indicates the time zone that applies at the end point of a U.S.-based event, interval, or usage period.
-
D.
differenceFromUSEasternStandardTime
Indicates the time offset or deviation of something’s time setting relative to U.S. Eastern Standard Time.
-
E.
differenceFromUSEasternDaylightTime
Indicates that one temporal value differs by a specified amount or offset from the time expressed in US Eastern Daylight Time.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.