Triple
T180881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europe/London |
E3872
|
entity |
| Predicate | daylightSavingTimeAbbreviation |
P2161
|
FINISHED |
| Object | BST |
—
|
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: BST | Statement: [Europe/London, daylightSavingTimeAbbreviation, BST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: daylightSavingTimeAbbreviation Context triple: [Europe/London, daylightSavingTimeAbbreviation, BST]
-
A.
DSTAbbreviation
chosen
Indicates that one entity is the standard abbreviated form used to represent another entity related to daylight saving time.
-
B.
abbreviationStandardTime
Indicates that one entity is the standard-time abbreviation (e.g., non-daylight-saving time short form) for the other entity.
-
C.
UTCOffsetDaylightSavingTime
Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
-
D.
DSTStartRule
Indicates the rule or condition that determines when daylight saving time begins for a given time zone or region.
-
E.
DSTEndRule
Indicates the rule or condition that specifies when daylight saving time ends in a given timekeeping system.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25901a9188190b8f510bec8c8e7f2 |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2566ccc288190add5624ede96d82b |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.