Triple

T9688133
Position Surface form Disambiguated ID Type / Status
Subject Air Force Global Strike Command E234462 entity
Predicate nickname P55 FINISHED
Object AFGSC E814809 NE 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: AFGSC | Statement: [Air Force Global Strike Command, nickname, AFGSC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: AFGSC
Context triple: [Air Force Global Strike Command, nickname, AFGSC]
  • A. AFGSC chosen
    AFGSC is a major command of the United States Air Force responsible for the nation’s strategic bomber and intercontinental ballistic missile forces.
  • B. AFSC
    AFSC is a major U.S. Air Force logistics and sustainment organization responsible for depot maintenance, supply chain management, and readiness support for air and space systems.
  • C. AFSC
    AFSC is a Quaker-founded social justice organization known for its peace, humanitarian, and advocacy work in the United States and internationally.
  • D. AFSOC
    AFSOC is the U.S. Air Force’s major command responsible for organizing, training, and equipping airmen for global special operations missions.
  • E. AFNWC
    AFNWC is a U.S. Air Force organization responsible for the lifecycle management, sustainment, and modernization of the service’s nuclear weapons systems and related infrastructure.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca84ca73208190957a900c8543bdcc completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9d019d40819095059a4d6167900a completed April 1, 2026, 10:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69d19f76aca481909692b29cac3c3dc3 completed April 4, 2026, 11:32 p.m.
Created at: March 30, 2026, 8:17 p.m.