Triple

T328747
Position Surface form Disambiguated ID Type / Status
Subject Soviet 64th Army E6577 entity
Predicate militaryDoctrine P11476 FINISHED
Object Soviet deep operations doctrine 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: Soviet deep operations doctrine | Statement: [Soviet 64th Army, militaryDoctrine, Soviet deep operations doctrine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: militaryDoctrine
Context triple: [Soviet 64th Army, militaryDoctrine, Soviet deep operations doctrine]
  • A. militaryStrategy
    Indicates a relationship where an entity plans, directs, or is associated with the organized use of armed forces and tactics to achieve military or defense objectives.
  • B. militaryContext
    Indicates that the relationship or action occurs within a military setting, framework, or operational environment.
  • C. militaryTechnology
    Indicates that one entity is a type of military-related technology used for defense, combat, or warfare purposes.
  • D. militaryFunction
    Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
  • E. militaryMeasure
    Indicates a relationship where an entity undertakes, imposes, or is subject to a specific military-related action, policy, or operational measure.
  • F. None of above. chosen

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_69a2e7933d6c8190bb2592ad13286ef2 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eaad37b0819085beda2a491da9a8 completed Feb. 28, 2026, 1:16 p.m.
PD Predicate disambiguation batch_69a2e94aab1c8190b8654708c87eeb91 completed Feb. 28, 2026, 1:10 p.m.
PDg Predicate description generation batch_69a2ea09a5e881908b313cb37409a4f9 completed Feb. 28, 2026, 1:13 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.