Triple
T35291110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Felsberg |
E1019227
|
entity |
| Predicate | likelyTimeZoneDST |
P90348
|
FINISHED |
| Object | Central European Summer Time |
—
|
NE NERFINISHED |
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: Central European Summer Time | Statement: [Felsberg, likelyTimeZoneDST, Central European Summer Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyTimeZoneDST Context triple: [Felsberg, likelyTimeZoneDST, Central European Summer Time]
-
A.
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.
-
B.
DSTRegion
chosen
Indicates that a location or entity is associated with a time zone region that observes daylight saving time (DST).
-
C.
DSTPolicy
Indicates a relationship where a timekeeping system follows a specific daylight saving time policy, defining how and when clocks are adjusted seasonally.
-
D.
DSTObservedInCountry
Indicates that daylight saving time (DST) is implemented or observed within a given country.
-
E.
hasDSTOfCountry
Indicates that a country observes a particular daylight saving time (DST) scheme or rule.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.