Triple
T11509459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weapon System 107A-1 |
E272870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Air Force development program |
C18113
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: U.S. Air Force development program Context triple: [Weapon System 107A-1, instanceOf, U.S. Air Force development program]
-
A.
United States Air Force project
chosen
A United States Air Force project is an organized, time-bound initiative undertaken by the USAF to research, develop, test, or implement capabilities, systems, or operations in support of its strategic and tactical missions.
-
B.
military program
A military program is an organized set of defense-related activities, projects, or initiatives designed to develop, maintain, or enhance a nation's armed forces capabilities and readiness.
-
C.
U.S. Army program executive office
A U.S. Army program executive office is an organizational entity responsible for managing the life cycle of specific categories of Army acquisition programs, from development and procurement through sustainment and modernization.
-
D.
rocket development program
A rocket development program is an organized, multi-phase effort to design, build, test, and refine launch vehicles to meet specific performance, safety, and mission objectives.
-
E.
F-35 program office
The F-35 program office is the organizational entity responsible for managing, coordinating, and overseeing all aspects of the F-35 Joint Strike Fighter’s development, production, sustainment, and integration across participating services and partner nations.
- F. None of above.
Provenance (1 batch)
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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:36 p.m.