Triple
T34921971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pšurnovice |
E1007164
|
entity |
| Predicate | usesDSTAbbreviation |
P2161
|
FINISHED |
| Object | CEST |
—
|
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: CEST | Statement: [Pšurnovice, usesDSTAbbreviation, CEST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDSTAbbreviation Context triple: [Pšurnovice, usesDSTAbbreviation, CEST]
-
A.
DSTAbbreviation
chosen
Indicates that one entity is the standard abbreviated form used to represent another entity related to daylight saving time.
-
B.
usesDSTNotationChange
Indicates that a system or context applies a change in notation or representation when switching between standard time and daylight saving time.
-
C.
hasDSTOfCountry
Indicates that a country observes a particular daylight saving time (DST) scheme or rule.
-
D.
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.
-
E.
DSTAlternativePreviouslyUsedUTCOffset
Indicates that a daylight saving time alternative has, at some point in the past, used a specific UTC offset.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.