Triple

T20988222
Position Surface form Disambiguated ID Type / Status
Subject Belarusian theatre of operations E516947 entity
Predicate frontLine P2502 FINISHED
Object Soviet Central Front sector 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: Soviet Central Front sector | Statement: [Belarusian theatre of operations, frontLine, Soviet Central Front sector]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Soviet Central Front sector
Context triple: [Belarusian theatre of operations, frontLine, Soviet Central Front sector]
  • A. Bryansk sector
    The Bryansk sector was a key area of military operations on the Eastern Front during World War II, centered around the strategically important city and region of Bryansk in western Russia.
  • B. Belgorod sector
    The Belgorod sector was a World War II Eastern Front operational area around the city of Belgorod, notable as a focal point of German and Soviet military actions including parts of the Battle of Kursk.
  • C. Leningrad sector
    The Leningrad sector was a key portion of the Eastern Front around the besieged city of Leningrad during World War II, where intense and prolonged fighting took place between German and Soviet forces.
  • D. Soviet Reserve Front
    The Soviet Reserve Front was a major Red Army formation in World War II that served as a strategic reserve and played a key role in the defense of Moscow in 1941.
  • E. Soviet Western Front
    The Soviet Western Front was a major Red Army operational command during the Russian Civil War and Polish–Soviet War, responsible for conducting large-scale offensives against Poland and other western adversaries.
  • 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: Soviet Central Front sector
Target entity description: The Soviet Central Front sector was a key portion of the Eastern Front in Belarus where Soviet forces engaged German troops in major World War II operations.
  • A. Bryansk sector
    The Bryansk sector was a key area of military operations on the Eastern Front during World War II, centered around the strategically important city and region of Bryansk in western Russia.
  • B. Belgorod sector
    The Belgorod sector was a World War II Eastern Front operational area around the city of Belgorod, notable as a focal point of German and Soviet military actions including parts of the Battle of Kursk.
  • C. Leningrad sector
    The Leningrad sector was a key portion of the Eastern Front around the besieged city of Leningrad during World War II, where intense and prolonged fighting took place between German and Soviet forces.
  • D. Soviet Reserve Front
    The Soviet Reserve Front was a major Red Army formation in World War II that served as a strategic reserve and played a key role in the defense of Moscow in 1941.
  • E. Soviet Western Front
    The Soviet Western Front was a major Red Army operational command during the Russian Civil War and Polish–Soviet War, responsible for conducting large-scale offensives against Poland and other western adversaries.
  • 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_69e0b4ffac148190bbade9f0eceb660b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fbe5208c8190b8b843b3778589d3 completed April 21, 2026, 4:24 a.m.
Created at: April 16, 2026, 1:49 p.m.