Triple
T22285630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Korsun–Cherkassy Pocket |
E550852
|
entity |
| Predicate | breakoutAttemptDate |
P147691
|
FINISHED |
| Object | 1944-02-16 |
—
|
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-02-16 | Statement: [Battle of the Korsun–Cherkassy Pocket, breakoutAttemptDate, 1944-02-16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breakoutAttemptDate Context triple: [Battle of the Korsun–Cherkassy Pocket, breakoutAttemptDate, 1944-02-16]
-
A.
triedAt
Indicates that an attempt to perform an action or achieve an outcome occurred at a specific time or place.
-
B.
attackDate
Indicates the calendar date on which an attack or assault event took place.
-
C.
ruptureDate
Indicates the date on which a rupture event (such as a break, burst, or failure) occurs in the relationship between entities.
-
D.
rescueAttemptNumber
Indicates the ordinal count of distinct attempts made to carry out a rescue in a given rescue situation or operation.
-
E.
wasTriedAt
Indicates that a legal case or judicial proceeding involving an entity took place at a specific court or location.
- 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.