Triple
T2446160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BST |
E53598
|
entity |
| Predicate | startLocalTimeEffect |
P28440
|
FINISHED |
| Object | clocks move forward from 01:00 to 02:00 local time |
—
|
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: clocks move forward from 01:00 to 02:00 local time | Statement: [BST, startLocalTimeEffect, clocks move forward from 01:00 to 02:00 local time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startLocalTimeEffect Context triple: [BST, startLocalTimeEffect, clocks move forward from 01:00 to 02:00 local time]
-
A.
impactTimeLocal
Indicates the specific local time at which an impact event occurs or is expected to occur.
-
B.
localTime
Indicates that a specific time value is expressed relative to a particular local time zone or locale, rather than in a universal or standardized time reference.
-
C.
endTimeLocal
Indicates the local date and time at which an event, activity, or state concludes.
-
D.
placeOfEffect
Indicates the location or setting where an action, event, or effect takes place or is realized.
-
E.
activationTime
chosen
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.