Triple

T31154442
Position Surface form Disambiguated ID Type / Status
Subject Army Co-operation Command E794162 entity
Predicate airPowerCategory P17955 FINISHED
Object tactical air force precursor 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: tactical air force precursor | Statement: [Army Co-operation Command, airPowerCategory, tactical air force precursor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: airPowerCategory
Context triple: [Army Co-operation Command, airPowerCategory, tactical air force precursor]
  • A. airPower
    Indicates the extent to which one entity can project, control, or influence force through the use of aircraft and other aerial capabilities over another entity or area.
  • B. airPowerUsedBy
    Indicates that a particular actor employs or deploys air power (such as aircraft or aerial operations) as part of its activities or capabilities.
  • C. typicalEquipmentPowered
    Indicates that one entity is commonly powered or operated by another entity as its usual source of power.
  • D. hardwareCategory
    Indicates that an item belongs to or is classified under a specific hardware category or type.
  • E. airGroupType chosen
    Indicates the classification or category of an air group based on its role, composition, or operational function.
  • 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_69f224d41bb48190a5621cd1485e3a30 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6df450014819099d118e5c2d697fa completed May 3, 2026, 5:38 a.m.
PD Predicate disambiguation batch_69f6de07836481908785cde9c511920b completed May 3, 2026, 5:32 a.m.
Created at: April 29, 2026, 9:06 p.m.