Triple

T5430174
Position Surface form Disambiguated ID Type / Status
Subject Joint Unmanned Combat Air Systems E121465 entity
Predicate developedCapability P63710 FINISHED
Object long-endurance unmanned strike platforms 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: long-endurance unmanned strike platforms | Statement: [Joint Unmanned Combat Air Systems, developedCapability, long-endurance unmanned strike platforms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: developedCapability
Context triple: [Joint Unmanned Combat Air Systems, developedCapability, long-endurance unmanned strike platforms]
  • A. capabilityType
    Indicates the type or category of capability that an entity possesses or is associated with.
  • B. plannedCapability
    Indicates that an entity is intended or scheduled to possess or provide a particular capability in the future.
  • C. consideredCapability
    Indicates that something is regarded or evaluated as a potential capability of an entity.
  • D. associatedCapability
    Indicates that one entity has a related ability, function, or competence that is linked to or relevant for another entity.
  • E. usedCapability
    Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
  • F. None of above. chosen

Provenance (4 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_69bd463c65f0819082ee6483ab4b466a completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd8911a7348190ad9378a248190f07 completed March 20, 2026, 5:51 p.m.
PD Predicate disambiguation batch_69bd846b8bdc81909dcdc2a3084226f2 completed March 20, 2026, 5:31 p.m.
PDg Predicate description generation batch_69bd8910de688190aa0cd80627849a60 completed March 20, 2026, 5:51 p.m.
Created at: March 20, 2026, 2:06 p.m.