Triple
T17861774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamaica Standard Time |
E446088
|
entity |
| Predicate | usesDSTCurrently |
P8084
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Jamaica Standard Time, usesDSTCurrently, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDSTCurrently Context triple: [Jamaica Standard Time, usesDSTCurrently, no]
-
A.
DSTobserved
chosen
Indicates that daylight saving time is in effect or being observed for a given time, date, or location.
-
B.
DSTObservedInCountry
Indicates that daylight saving time (DST) is implemented or observed within a given country.
-
C.
DSTseason
Indicates that the relationship specifies the daylight saving time (DST) period or season during which a time-related event or setting is in effect.
-
D.
DSTPolicy
Indicates a relationship where a timekeeping system follows a specific daylight saving time policy, defining how and when clocks are adjusted seasonally.
-
E.
DSTRegion
Indicates that a location or entity is associated with a time zone region that observes daylight saving time (DST).
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e49790ea148190b7a966812d44f430 |
completed | April 19, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.