Triple
T22285629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Korsun–Cherkassy Pocket |
E550852
|
entity |
| Predicate | pocketFormedOn |
P147690
|
FINISHED |
| Object | 1944-01-28 |
—
|
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: 1944-01-28 | Statement: [Battle of the Korsun–Cherkassy Pocket, pocketFormedOn, 1944-01-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pocketFormedOn Context triple: [Battle of the Korsun–Cherkassy Pocket, pocketFormedOn, 1944-01-28]
-
A.
pouch
Indicates that one entity is contained or stored within the pouch or pocket of another entity.
-
B.
isFormedFor
Indicates that something is created, established, or brought into existence for a particular purpose, function, or beneficiary.
-
C.
hasPocketType
Indicates the specific style or configuration of pocket associated with an item or garment.
-
D.
pouchType
Indicates the specific kind or category of pouch associated with an entity.
-
E.
potentialForm
Indicates that an action is expressed in its potential form, meaning the subject has the ability or possibility to perform that action.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15606948c81909ebaa5ea106d2b7a |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:40 p.m.