Triple

T782133
Position Surface form Disambiguated ID Type / Status
Subject Chief of Staff of the Air Force E16519 entity
Predicate notInChainOfCommandOver P1432 FINISHED
Object combatant commands 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: combatant commands | Statement: [Chief of Staff of the Air Force, notInChainOfCommandOver, combatant commands]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notInChainOfCommandOver
Context triple: [Chief of Staff of the Air Force, notInChainOfCommandOver, combatant commands]
  • A. notCommanderOf chosen
    Indicates that a given entity does not hold a commanding or leadership role over another specified entity.
  • B. commandedTo
    Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
  • C. commandedIn
    Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
  • D. isCommandedIn
    Indicates that an entity is under the authority or control of another entity within a specific context, such as a mission, operation, or organizational structure.
  • E. commandedBy
    Indicates that one entity holds authoritative control or issues orders over another entity.
  • 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_69a4936ad1fc81908f190208059ccf78 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a90365648190ace53b0f0e87aa68 completed March 1, 2026, 9 p.m.
PD Predicate disambiguation batch_69a4a50bd23081908908235b8ec9201e completed March 1, 2026, 8:43 p.m.
Created at: March 1, 2026, 7:37 p.m.