Triple
T32977752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kreminna |
E843712
|
entity |
| Predicate | post2022Status |
P175454
|
FINISHED |
| Object | occupied by Russian forces and their proxies |
—
|
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: occupied by Russian forces and their proxies | Statement: [Kreminna, post2022Status, occupied by Russian forces and their proxies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: post2022Status Context triple: [Kreminna, post2022Status, occupied by Russian forces and their proxies]
-
A.
post2020Status
Indicates the status or condition of an entity specifically in the period after the year 2020.
-
B.
post2000Status
Indicates whether a given entity’s status, condition, or classification applies specifically to the period after the year 2000.
-
C.
post2005Status
Indicates the status or condition of an entity specifically in the period after the year 2005.
-
D.
post2009Status
Indicates the status or condition of an entity specifically in the period after the year 2009.
-
E.
postBlipStatus
Indicates the action of publishing or updating a short status message (a "blip") to a stream or feed.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1da0c508190bbd87880d37890c5 |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: May 1, 2026, 1:22 a.m.