Triple
T2590893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Summer Time Act 1972 |
E58117
|
entity |
| Predicate | timeOffsetDuringSummer |
P5550
|
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: [British Summer Time Act 1972, timeOffsetDuringSummer, GMT+1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOffsetDuringSummer Context triple: [British Summer Time Act 1972, timeOffsetDuringSummer, GMT+1]
-
A.
differenceFromLondonTimeInSummer
Indicates the time difference between a given location and London during the summer (daylight saving) period.
-
B.
summerTimeZone
chosen
Indicates that a specified region or entity uses a particular time zone during the summer or daylight-saving period.
-
C.
timeOffsetType
Indicates the type or category of temporal offset that specifies how one time point is shifted relative to another.
-
D.
timeDifferenceToCETSummer
Indicates the time offset between a given time and Central European Time during the summer (daylight saving) period.
-
E.
isSummerTimeVariantOf
Indicates that one temporal or time-related entity is the daylight-saving (summer time) version of another standard-time entity.
- 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd40075f08190b760cb41c1417169 |
completed | March 7, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.