Triple
T923137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russo-Ukrainian War |
E19925
|
entity |
| Predicate | escalationDate |
P21572
|
FINISHED |
| Object | 24 February 2022 |
—
|
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: 24 February 2022 | Statement: [Russo-Ukrainian War, escalationDate, 24 February 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escalationDate Context triple: [Russo-Ukrainian War, escalationDate, 24 February 2022]
-
A.
attackDate
Indicates the calendar date on which an attack or assault event took place.
-
B.
uprisingDate
Indicates the date on which an uprising or rebellion occurred or began.
-
C.
firstRaisedAt
Indicates the initial time or context at which an issue, topic, or matter was first brought up or introduced.
-
D.
immediateCauseDate
Indicates the specific date on which an event or condition directly caused another event or outcome to occur.
-
E.
dateOfSubmission
Indicates the specific date on which something (such as a document, application, or assignment) was formally submitted.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b314f6fc81908a3ccc2e741e3c2b |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b295b02481908e5f53bfcb83cc94 |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b30efd2c8190b780a6dee086d0aa |
completed | March 1, 2026, 9:43 p.m. |
Created at: March 1, 2026, 7:40 p.m.