Triple

T323793
Position Surface form Disambiguated ID Type / Status
Subject Soviet military officers E6469 entity
Predicate notableDoctrine P5485 FINISHED
Object deep operation 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: deep operation | Statement: [Soviet military officers, notableDoctrine, deep operation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableDoctrine
Context triple: [Soviet military officers, notableDoctrine, deep operation]
  • A. keyDoctrine
    Indicates that something is a central or foundational doctrine within a belief system, organization, or theoretical framework.
  • B. concernsDoctrine chosen
    Indicates that something is related or pertains specifically to a particular doctrine or set of doctrinal principles.
  • C. teachesDoctrine
    Indicates that one entity imparts, explains, or promotes a specific doctrine or set of beliefs to another entity.
  • D. stateDoctrine
    Indicates that a state or government officially endorses, promotes, or is guided by a particular doctrine, ideology, or set of principles.
  • E. deniesDoctrine
    Indicates that one entity rejects, opposes, or refuses to accept the truth or validity of a particular doctrine associated with another entity.
  • 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_69a2e7933d6c8190bb2592ad13286ef2 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eb1a37c08190b1380f6bf8513a37 completed Feb. 28, 2026, 1:18 p.m.
PD Predicate disambiguation batch_69a2e949364c8190bc2351f5413f5057 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.