Triple
T17597936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omsk Time |
E428621
|
entity |
| Predicate | changeIn2011 |
P75870
|
FINISHED |
| Object | Russia abolished daylight saving time |
—
|
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: Russia abolished daylight saving time | Statement: [Omsk Time, changeIn2011, Russia abolished daylight saving time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changeIn2011 Context triple: [Omsk Time, changeIn2011, Russia abolished daylight saving time]
-
A.
statusAfter2011
chosen
Indicates the condition or state of an entity specifically in the period following the year 2011.
-
B.
post2020Change
Indicates a change, update, or event that occurred after the year 2020.
-
C.
notableChange
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
D.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
E.
constitutionalChangeFrom
Indicates a relationship where one constitutional state, framework, or arrangement is transformed or replaced by another, marking the source state from which the change originates.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469ecfb108190a9e7a5b380f8ab93 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.