Triple
T24790568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cold War military aviation programs |
E620239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace development initiative |
C38555
|
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: aerospace development initiative Context triple: [Cold War military aviation programs, instanceOf, aerospace development initiative]
-
A.
aerospace program
chosen
An aerospace program is an organized initiative or series of projects focused on the research, development, testing, and operation of aircraft, spacecraft, and related technologies to achieve specific scientific, commercial, or defense objectives.
-
B.
aerospace organization
An aerospace organization is an entity that researches, designs, manufactures, operates, or supports aircraft, spacecraft, and related systems and technologies for commercial, governmental, or defense purposes.
-
C.
space technology development program
A space technology development program is an organized initiative that researches, designs, tests, and matures advanced space-related technologies to enable or enhance future space missions and capabilities.
-
D.
aerospace corporation
An aerospace corporation is a large-scale enterprise that designs, manufactures, and services aircraft, spacecraft, and related systems and technologies for commercial, military, and space applications.
-
E.
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.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:47 a.m.