Triple
T29725469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UKD74 |
E752167
|
entity |
| Predicate | daylightSavingTimeZoneOfArea |
P9475
|
FINISHED |
| Object | BST |
—
|
NE NERFINISHED |
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: BST | Statement: [UKD74, daylightSavingTimeZoneOfArea, BST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: daylightSavingTimeZoneOfArea Context triple: [UKD74, daylightSavingTimeZoneOfArea, BST]
-
A.
timeZoneArea
Indicates the geographic area or region for which a particular time zone is defined or applicable.
-
B.
DSTTimeZone
chosen
Indicates that a time-related entity operates under a daylight saving time rule or belongs to a time zone that observes daylight saving time adjustments.
-
C.
DSTRegion
Indicates that a location or entity is associated with a time zone region that observes daylight saving time (DST).
-
D.
daylightSavingTimeHemisphere
Indicates the hemisphere (e.g., northern or southern) in which a location follows a particular daylight saving time pattern.
-
E.
timeZoneRegionOf
Indicates that a time zone is the official or primary time zone used within a specified geographic region.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672ff16a08190b8840351bef56f55 |
completed | May 2, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:39 p.m.