Triple

T4056258
Position Surface form Disambiguated ID Type / Status
Subject Soviet deep operations doctrine E84700 entity
Predicate appliedInConflict P49719 FINISHED
Object Eastern Front of World War II E277 NE FINISHED

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: Eastern Front of World War II | Statement: [Soviet deep operations doctrine, appliedInConflict, Eastern Front of World War II]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eastern Front of World War II
Context triple: [Soviet deep operations doctrine, appliedInConflict, Eastern Front of World War II]
  • A. Northern Front of World War II
    The Northern Front of World War II was the Arctic and sub-Arctic theater where German, Finnish, Soviet, and later Allied forces fought over Scandinavia, the Arctic Ocean, and northern Soviet territories, heavily influenced by extreme climate and strategic control of sea routes and resources.
  • B. Soviet-German Front
    The Soviet-German Front was the vast and brutal World War II battlefield between Nazi Germany and the Soviet Union, marked by some of the largest and deadliest military operations in history.
  • C. Defense of the Eastern Front
    Defense of the Eastern Front refers to the German military’s large-scale defensive operations against the advancing Soviet forces on the Eastern Front during World War II.
  • D. Eastern Front chosen
    The Eastern Front was the vast and brutal theater of World War II where Nazi Germany and its allies fought the Soviet Union, marked by immense casualties, pivotal battles, and decisive turning points in the war.
  • E. Eastern Front
    The Eastern Front was a major World War I theater of war stretching from the Baltic to the Black Sea, where the Russian Empire fought the Central Powers in large-scale, mobile campaigns.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliedInConflict
Context triple: [Soviet deep operations doctrine, appliedInConflict, Eastern Front of World War II]
  • A. appliesToConflictWith
    Indicates that one element’s scope, rules, or effects are relevant to a conflict involving another element, defining how that element is implicated in or governed by the conflict.
  • B. implementedDuringConflict chosen
    Indicates that an action, policy, or measure was carried out while an active conflict or war was ongoing.
  • C. conflictWith
    Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
  • D. appliedBecauseOf
    Indicates that one entity is applied, used, or enacted as a consequence or result of another specified cause or condition.
  • E. reportedConflict
    Indicates that one party has formally reported the existence of a conflict involving another party or situation.
  • F. None of above.

Provenance (4 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_69aed933bec881909edfa28ebb69c634 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefbad953c81909d7b42fae5db9f25 completed March 9, 2026, 4:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5629e75e88190935ae3e7db8eb12f completed March 14, 2026, 1:29 p.m.
PD Predicate disambiguation batch_69aef90249e4819095e9e043bc4aa9a6 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:38 p.m.