Triple
T15812164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaliningrad Time |
E383380
|
entity |
| Predicate | timeChangePolicyStableSince |
P120173
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Kaliningrad Time, timeChangePolicyStableSince, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeChangePolicyStableSince Context triple: [Kaliningrad Time, timeChangePolicyStableSince, 2014]
-
A.
timeZoneChange
Indicates a change in the time zone associated with an entity, such as shifting from one time offset or region-based time standard to another.
-
B.
DSTOffsetChange
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
C.
timeZoneState
Indicates that one entity is a state or region associated with the time zone of another entity.
-
D.
DSTChangeReason
Indicates the reason or cause for a change in daylight saving time status or rules.
-
E.
isFixedOffsetSince
Indicates that one entity consistently occurs or is positioned at a constant, unchanging offset in time or value relative to another reference entity.
- F. None of above. chosen
Provenance (4 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b52bbb888190b226567e84ced7e9 |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e00e48d49c819081afccb02f9cf18b |
completed | April 15, 2026, 10:16 p.m. |
Created at: April 10, 2026, 4:49 a.m.