Triple
T148499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GMT |
E3380
|
entity |
| Predicate | observedAsStandardTimeIn |
P6028
|
FINISHED |
| Object | United Kingdom (winter) |
—
|
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: United Kingdom (winter) | Statement: [GMT, observedAsStandardTimeIn, United Kingdom (winter)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedAsStandardTimeIn Context triple: [GMT, observedAsStandardTimeIn, United Kingdom (winter)]
-
A.
UTCOffsetStandardTime
Indicates the time difference, in hours and minutes, that a location’s standard (non-daylight-saving) local time has from Coordinated Universal Time (UTC).
-
B.
observesSameTimeAs
Indicates that two observation events occur simultaneously or during the same time interval.
-
C.
observesDaylightSavingTime
Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
-
D.
observesDaylightSavingWith
Indicates that one entity follows the same daylight saving time rules or schedule as another entity.
-
E.
timeZoneHistorical
Indicates that there is a historical time zone relationship, specifying how an entity’s time zone (including offsets, rules, or changes) applied during past periods.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a257ecb6f48190992c4c8ca908a81c |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a256599db08190a7b000b381d32ec4 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a25737f9188190b9690dce98aed83a |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.