Triple
T5405956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Białystok–Minsk |
E120892
|
entity |
| Predicate | SovietPrisonersTaken |
P6764
|
FINISHED |
| Object | about 300000 |
—
|
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: about 300000 | Statement: [Battle of Białystok–Minsk, SovietPrisonersTaken, about 300000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SovietPrisonersTaken Context triple: [Battle of Białystok–Minsk, SovietPrisonersTaken, about 300000]
-
A.
treatmentOfSovietPOWs
Indicates how individuals, groups, or authorities behaved toward, managed, or dealt with Soviet prisoners of war.
-
B.
prisonersOfWar
chosen
Indicates a relationship where certain individuals are held in custody by an enemy during an armed conflict as prisoners of war.
-
C.
numberOfSovietPOWsVictimsEstimate
Indicates an estimated count of victims who were Soviet prisoners of war.
-
D.
recapturedByDuringWWII
Indicates that an entity was taken back or regained by another entity specifically during the period of World War II.
-
E.
capturedInWar
Indicates that one entity was taken prisoner or seized by another entity as a result of armed conflict or wartime actions.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87924c588190beb4a1be27f8d11b |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.