Triple
T11747820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BST Act 1972 |
E279328
|
entity |
| Predicate | timeZoneDuringBST |
P8739
|
FINISHED |
| Object | GMT+1 |
—
|
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: GMT+1 | Statement: [BST Act 1972, timeZoneDuringBST, GMT+1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneDuringBST Context triple: [BST Act 1972, timeZoneDuringBST, GMT+1]
-
A.
differenceFromLondonTimeInSummer
chosen
Indicates the time difference between a given location and London during the summer (daylight saving) period.
-
B.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
-
C.
DSTTimeZone
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.
-
D.
typicalDSTChangeHour
Indicates the usual clock time at which a daylight saving time change (such as shifting clocks forward or backward) is applied.
-
E.
DSTobserved
Indicates that daylight saving time is in effect or being observed for a given time, date, or location.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50763a081908597da118bd0a64e |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.