Triple
T12440239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krasnoyarsk Time |
E297249
|
entity |
| Predicate | followsRussianTimeReform |
P104940
|
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: [Krasnoyarsk Time, followsRussianTimeReform, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsRussianTimeReform Context triple: [Krasnoyarsk Time, followsRussianTimeReform, 2014]
-
A.
DSTAbolishedInRussia
Indicates that the subject entity was officially abolished, discontinued, or ceased to exist within the territory of Russia.
-
B.
isSummerTimeVariantOf
Indicates that one temporal or time-related entity is the daylight-saving (summer time) version of another standard-time entity.
-
C.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
D.
regionBeforeReform
Indicates that a region is defined or considered as it existed prior to a specific reform or reorganization.
-
E.
timePeriodOfInitialRussianControl
Indicates the time span during which Russia first held control or authority over a given entity or territory.
- 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_69d6ada166c48190b902972cd2408fa3 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d94df652cc8190a1d2d685fa87cf98 |
completed | April 10, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:55 p.m.