Triple
T12022467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Perekop (1944) |
E286186
|
entity |
| Predicate | aimOfSide1 |
P61460
|
FINISHED |
| Object | Expel Axis forces from Crimea |
—
|
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: Expel Axis forces from Crimea | Statement: [Battle of Perekop (1944), aimOfSide1, Expel Axis forces from Crimea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfSide1 Context triple: [Battle of Perekop (1944), aimOfSide1, Expel Axis forces from Crimea]
-
A.
goalOfSide1
chosen
Indicates that the specified entity represents the objective or intended outcome pursued by the first side/party in a two-sided interaction or conflict.
-
B.
aimOfOtherSide
Indicates that one party’s goal or intended outcome is directed toward or defined in relation to the opposing or counterpart side in a relationship or interaction.
-
C.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
D.
aimOfAlliance
Indicates that a specified goal, purpose, or objective is the intended focus or motivation of an alliance between entities.
-
E.
onSide
Indicates that one entity is positioned along or adjacent to the side of another entity.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.