Triple
T5670211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Courland Pocket |
E124955
|
entity |
| Predicate | numberOfSovietTroops |
P6153
|
FINISHED |
| Object | several hundred thousand |
—
|
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: several hundred thousand | Statement: [Courland Pocket, numberOfSovietTroops, several hundred thousand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSovietTroops Context triple: [Courland Pocket, numberOfSovietTroops, several hundred thousand]
-
A.
numberOfTroopsInvolved
chosen
Indicates the quantity of military personnel participating in or assigned to a specific operation, event, or engagement.
-
B.
SovietFront
Indicates a military relationship where a unit, operation, or event is associated with or occurs on a Soviet military front (a major wartime operational formation).
-
C.
SovietEquipmentLosses
Indicates the extent or instances of military equipment lost by Soviet forces in a given conflict or period.
-
D.
numberOfSovietPOWsVictimsEstimate
Indicates an estimated count of victims who were Soviet prisoners of war.
-
E.
involvedUnitSoviet
Indicates that a Soviet military or organizational unit was involved in a particular event, operation, or action.
- 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.