Triple
T24959590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiev offensive (1920) |
E624568
|
entity |
| Predicate | withdrawalDateFromKyiv |
P12347
|
FINISHED |
| Object | 1920-06-10 |
—
|
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: 1920-06-10 | Statement: [Kiev offensive (1920), withdrawalDateFromKyiv, 1920-06-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withdrawalDateFromKyiv Context triple: [Kiev offensive (1920), withdrawalDateFromKyiv, 1920-06-10]
-
A.
withdrawalDate
chosen
Indicates the date on which a withdrawal action occurs or is recorded.
-
B.
withdrawalEnd
Indicates the point in time or condition at which a withdrawal process or right comes to an end.
-
C.
romanWithdrawalApproxDate
Indicates an approximate date when Roman forces or administration withdrew from a given place or region.
-
D.
withdrawnDuring
Indicates that something is removed, canceled, or taken back over the course of a specified time period or event.
-
E.
withdrawalAnnouncedBy
Indicates that an entity’s withdrawal (e.g., from an agreement, position, or situation) has been publicly announced or declared by a specified agent or source.
- F. None of above.
Provenance (3 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4242c447c8190bf7972390ac93814 |
completed | May 1, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:58 a.m.