Triple
T18454249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europe/Stockholm |
E450861
|
entity |
| Predicate | dstStartRuleEU |
P108476
|
FINISHED |
| Object | last Sunday in March at 01:00 UTC |
—
|
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: last Sunday in March at 01:00 UTC | Statement: [Europe/Stockholm, dstStartRuleEU, last Sunday in March at 01:00 UTC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dstStartRuleEU Context triple: [Europe/Stockholm, dstStartRuleEU, last Sunday in March at 01:00 UTC]
-
A.
followsEuropeanDSTRules
chosen
Indicates that the subject adheres to European Daylight Saving Time rules for adjusting clocks and timekeeping.
-
B.
usesEuropeanUnionDSTRules
Indicates that the action or process is governed by, or conforms to, the European Union’s Digital Services Act (DSA) rules and requirements.
-
C.
dstRuleRegion
Indicates that a rule applies specifically to, or is associated with, a particular destination region.
-
D.
startTimeOfRuleInHanover
Indicates the specific time at which a particular rule or regulation becomes effective or applicable within Hanover.
-
E.
startsInCountry
Indicates that an entity’s starting point or origin location is situated within a specified country.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5264b200c8190be2e79ca5ea0b082 |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.