Triple

T9959504
Position Surface form Disambiguated ID Type / Status
Subject AJP-3 Allied Joint Doctrine for the Conduct of Operations E195529 entity
Predicate levelOfWarfare P81790 FINISHED
Object operational level 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: operational level | Statement: [AJP-3 Allied Joint Doctrine for the Conduct of Operations, levelOfWarfare, operational level]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: levelOfWarfare
Context triple: [AJP-3 Allied Joint Doctrine for the Conduct of Operations, levelOfWarfare, operational level]
  • A. levelOfWar chosen
    Indicates the specific intensity or scale of military conflict at which an operation, action, or relationship is occurring (e.g., tactical, operational, strategic).
  • B. warfareType
    Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
  • C. fieldOfOperation
    Indicates the domain, area, or scope within which an entity operates or carries out its primary activities.
  • D. armedConflictLevel
    Indicates the intensity or severity of ongoing or potential armed conflict between parties.
  • E. warfareCapability
    Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
  • 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_69ca82eaaa008190a54fa1a9f954b9ad completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb6d08fdc8190a77b9c97830035bc completed April 2, 2026, 12:22 a.m.
PD Predicate disambiguation batch_69cd1d9ae19c819099fb3635e57c79be completed April 1, 2026, 1:28 p.m.
Created at: March 30, 2026, 8:46 p.m.