Triple
T34247358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Všestary |
E878632
|
entity |
| Predicate | hasLocalTimeConvention |
P58643
|
FINISHED |
| Object | CET/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: CET/CEST | Statement: [Všestary, hasLocalTimeConvention, CET/CEST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalTimeConvention Context triple: [Všestary, hasLocalTimeConvention, CET/CEST]
-
A.
hasLocalizedTimeRules
chosen
Indicates that an entity applies specific time-related rules or conventions that are tailored to a particular locale or region.
-
B.
observesLocalTimeFor
Indicates that one entity follows or uses the local time standard that is defined for another entity (such as a place or region).
-
C.
isStandardTimeFor
Indicates that a specified time zone or region is currently observing its standard (non-daylight-saving) time.
-
D.
startDateConvention
Indicates the rule or method used to determine the effective start date of a period, contract, or calculation.
-
E.
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.
- 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 1, 2026, 1:56 a.m.