Triple
T20691267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FJT |
E508555
|
entity |
| Predicate | UTCOffsetDuringDaylightSaving |
P713
|
FINISHED |
| Object | +13: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: +13:00 | Statement: [FJT, UTCOffsetDuringDaylightSaving, +13:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UTCOffsetDuringDaylightSaving Context triple: [FJT, UTCOffsetDuringDaylightSaving, +13:00]
-
A.
UTCOffsetDaylightSavingTime
chosen
Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
-
B.
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.
-
C.
timeOffsetInHours
Indicates the temporal difference between two time points or events, measured in hours.
-
D.
daylightSavingTimeHemisphere
Indicates the hemisphere (e.g., northern or southern) in which a location follows a particular daylight saving time pattern.
-
E.
offsetDSTApprox
Indicates an approximate time offset between entities that accounts for daylight saving time adjustments.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c10d83548190a52b9ef84c8f9205 |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:08 p.m.