Triple
T29780941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XM2001 Crusader |
E756111
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army weapons program |
C10566
|
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. Army weapons program Context triple: [XM2001 Crusader, instanceOf, U.S. Army weapons program]
-
A.
U.S. Army aviation program
The U.S. Army aviation program encompasses the development, training, operation, and maintenance of rotary- and fixed-wing aircraft to provide air mobility, reconnaissance, attack, and support capabilities for Army missions.
-
B.
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.
-
C.
U.S. military ordnance
U.S. military ordnance encompasses the weapons, ammunition, explosives, and related equipment developed, procured, and used by the United States armed forces for combat and defense operations.
-
D.
military program category
A military program category is a classification grouping related defense initiatives, projects, or activities based on their purpose, function, or capability area within an armed forces structure.
-
E.
military program
chosen
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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:05 p.m.