Triple

T4243196
Position Surface form Disambiguated ID Type / Status
Subject Joint Functional Component Commands E95463 entity
Predicate hasComponent P35 FINISHED
Object Joint Functional Component Command for Integrated Missile Defense
The Joint Functional Component Command for Integrated Missile Defense was a U.S. Strategic Command subcomponent responsible for planning, integrating, and coordinating global missile defense operations across the military services and combatant commands.
E95463 NE FINISHED

How this triple was built (4 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: Joint Functional Component Command for Integrated Missile Defense | Statement: [Joint Functional Component Commands, hasComponent, Joint Functional Component Command for Integrated Missile Defense]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Joint Functional Component Command for Integrated Missile Defense
Context triple: [Joint Functional Component Commands, hasComponent, Joint Functional Component Command for Integrated Missile Defense]
  • A. Joint Functional Component Command for Network Warfare
    The Joint Functional Component Command for Network Warfare was a U.S. military command responsible for planning and conducting offensive and defensive cyberspace operations across the Department of Defense.
  • B. Command and Control, Battle Management, and Communications (C2BMC) system
    The Command and Control, Battle Management, and Communications (C2BMC) system is a U.S. missile defense network that integrates sensors, weapons, and command centers to provide coordinated tracking, decision-making, and engagement of ballistic missile threats.
  • C. Missiles and Fire Control
    Missiles and Fire Control is a major Lockheed Martin business unit specializing in advanced missile systems, fire control solutions, and related defense technologies for military and aerospace applications.
  • D. Joint Functional Component Commands
    Joint Functional Component Commands are specialized subordinate commands within U.S. Strategic Command that focus on distinct mission areas such as space, global strike, missile defense, and intelligence to support unified strategic operations.
  • E. Battle Management Command, Control and Communications
    Battle Management Command, Control and Communications is a U.S. Space Force component focused on integrating and directing space operations through advanced command, control, and communications systems.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Joint Functional Component Command for Integrated Missile Defense
Triple: [Joint Functional Component Commands, hasComponent, Joint Functional Component Command for Integrated Missile Defense]
Generated description
The Joint Functional Component Command for Integrated Missile Defense was a U.S. Strategic Command subcomponent responsible for planning, integrating, and coordinating global missile defense operations across the military services and combatant commands.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Joint Functional Component Command for Integrated Missile Defense
Target entity description: The Joint Functional Component Command for Integrated Missile Defense was a U.S. Strategic Command subcomponent responsible for planning, integrating, and coordinating global missile defense operations across the military services and combatant commands.
  • A. Joint Functional Component Command for Network Warfare
    The Joint Functional Component Command for Network Warfare was a U.S. military command responsible for planning and conducting offensive and defensive cyberspace operations across the Department of Defense.
  • B. Command and Control, Battle Management, and Communications (C2BMC) system
    The Command and Control, Battle Management, and Communications (C2BMC) system is a U.S. missile defense network that integrates sensors, weapons, and command centers to provide coordinated tracking, decision-making, and engagement of ballistic missile threats.
  • C. Missiles and Fire Control
    Missiles and Fire Control is a major Lockheed Martin business unit specializing in advanced missile systems, fire control solutions, and related defense technologies for military and aerospace applications.
  • D. Joint Functional Component Commands chosen
    Joint Functional Component Commands are specialized subordinate commands within U.S. Strategic Command that focus on distinct mission areas such as space, global strike, missile defense, and intelligence to support unified strategic operations.
  • E. Battle Management Command, Control and Communications
    Battle Management Command, Control and Communications is a U.S. Space Force component focused on integrating and directing space operations through advanced command, control, and communications systems.
  • F. None of above.

Provenance (5 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_69b3453d91548190b4d4ef8fe52aa2ac completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34e8a676c8190ac2cb59e62613dd9 completed March 12, 2026, 11:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5b77ce4d48190ba24e3ef8c9ceb8d completed March 14, 2026, 7:31 p.m.
NEDg Description generation batch_69b5bb7b11e08190abe931711bc7811d completed March 14, 2026, 7:48 p.m.
NED2 Entity disambiguation (via description) batch_69b5bbda0cec819092b4f6dd0c8257c3 completed March 14, 2026, 7:49 p.m.
Created at: March 12, 2026, 11:05 p.m.