Triple

T1894481
Position Surface form Disambiguated ID Type / Status
Subject I Airborne Corps E41946 entity
Predicate usesTacticalDoctrine P30685 FINISHED
Object airborne assault 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: airborne assault | Statement: [I Airborne Corps, usesTacticalDoctrine, airborne assault]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesTacticalDoctrine
Context triple: [I Airborne Corps, usesTacticalDoctrine, airborne assault]
  • A. militaryTacticsUsed chosen
    Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
  • B. militaryDoctrine
    Indicates that one entity embodies, follows, or defines the strategic military principles, tactics, and operational guidelines used by another entity.
  • C. 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.
  • D. warfareCapability
    Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
  • E. usedWarfareType
    Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
  • 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_69a8864b6de0819098d089f6a1b910a7 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb1497df08190ad90dd89f76208ca completed March 7, 2026, 5:02 a.m.
PD Predicate disambiguation batch_69abafe7e7e88190b58c0df59187c0c2 completed March 7, 2026, 4:56 a.m.
Created at: March 4, 2026, 7:34 p.m.