Triple
T21702015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurland Kessel |
E535680
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Fourth Battle of Courland |
—
|
NE NERFINISHED |
How this triple was built (3 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: Fourth Battle of Courland | Statement: [Kurland Kessel, hasPart, Fourth Battle of Courland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fourth Battle of Courland Context triple: [Kurland Kessel, hasPart, Fourth Battle of Courland]
-
A.
Third Battle of Courland
The Third Battle of Courland was a late-World War II engagement on the Courland Peninsula in which encircled German forces resisted repeated Soviet offensives as part of the broader Courland Pocket fighting.
-
B.
First Battle of Courland
The First Battle of Courland was a World War II engagement on the Eastern Front in which German and Soviet forces clashed in the Courland region of Latvia, contributing to the encirclement known as the Courland Pocket.
-
C.
Battle of Königsberg
The Battle of Königsberg was a World War II engagement in early 1945 in which Soviet forces besieged and captured the heavily fortified East Prussian city of Königsberg from Nazi Germany.
-
D.
Battle of Koknese
The Battle of Koknese was a significant engagement during the Polish–Swedish conflicts in the early 17th century, notable for the Polish–Lithuanian Commonwealth’s effective use of cavalry against Swedish forces.
-
E.
Courland Pocket
The Courland Pocket was a World War II encircled area in western Latvia where German forces were cut off by the Soviet Red Army and continued to resist until the war’s end in Europe.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Fourth Battle of Courland Target entity description: The Fourth Battle of Courland was a late-World War II engagement on the Courland Peninsula in which encircled German forces resisted repeated Soviet offensives as the Red Army pushed toward final victory in the Baltic region.
-
A.
Third Battle of Courland
The Third Battle of Courland was a late-World War II engagement on the Courland Peninsula in which encircled German forces resisted repeated Soviet offensives as part of the broader Courland Pocket fighting.
-
B.
First Battle of Courland
The First Battle of Courland was a World War II engagement on the Eastern Front in which German and Soviet forces clashed in the Courland region of Latvia, contributing to the encirclement known as the Courland Pocket.
-
C.
Battle of Königsberg
The Battle of Königsberg was a World War II engagement in early 1945 in which Soviet forces besieged and captured the heavily fortified East Prussian city of Königsberg from Nazi Germany.
-
D.
Battle of Koknese
The Battle of Koknese was a significant engagement during the Polish–Swedish conflicts in the early 17th century, notable for the Polish–Lithuanian Commonwealth’s effective use of cavalry against Swedish forces.
-
E.
Courland Pocket
The Courland Pocket was a World War II encircled area in western Latvia where German forces were cut off by the Soviet Red Army and continued to resist until the war’s end in Europe.
- F. None of above. chosen
Provenance (2 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b802e008190a68ec62b98512794 |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 16, 2026, 6:45 p.m.