Triple

T1565451
Position Surface form Disambiguated ID Type / Status
Subject Air Force Gallant Unit Citation E33421 entity
Predicate combatRequirement P7256 FINISHED
Object yes 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: yes | Statement: [Air Force Gallant Unit Citation, combatRequirement, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: combatRequirement
Context triple: [Air Force Gallant Unit Citation, combatRequirement, yes]
  • A. requiresSkill
    Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
  • B. rosterRequirement
    Indicates that one entity specifies or imposes a required composition, number, or type of participants that must be included in another entity’s roster.
  • C. weaponCapability
    Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
  • D. militaryCharacteristic chosen
    Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or context.
  • E. safetyRequirement
    Indicates that one entity specifies or imposes conditions, standards, or measures necessary to ensure the safety of another entity or activity.
  • 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_69a885f11b048190935025a035302715 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a90fccd4b48190a44012888a00af7f completed March 5, 2026, 5:08 a.m.
PD Predicate disambiguation batch_69a907b872f0819096b3df6ad502c63e completed March 5, 2026, 4:34 a.m.
Created at: March 4, 2026, 7:27 p.m.