Triple
T35790852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Aerospace Threat Identification Program |
E1034687
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. government defense program |
C60757
|
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. government defense program Context triple: [Advanced Aerospace Threat Identification Program, instanceOf, U.S. government defense program]
-
A.
U.S. Department of Defense research program
chosen
A U.S. Department of Defense research program is a government-funded initiative that investigates, develops, and tests advanced technologies and methodologies to support national security and military capabilities.
-
B.
U.S. Navy program
A U.S. Navy program is an organized, formally managed initiative that develops, acquires, sustains, or improves naval capabilities, systems, or operations to support the Navy’s strategic and operational objectives.
-
C.
United States government program
A United States government program is an organized set of activities, services, or regulations funded and administered by federal agencies to achieve specific public policy goals or address national needs.
-
D.
United States Air Force project
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.
-
E.
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.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.