Triple
T21986545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Ministry of Aviation Industry |
E542974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace industry authority |
C5661
|
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 industry authority Context triple: [Soviet Ministry of Aviation Industry, instanceOf, aerospace industry authority]
-
A.
aerospace executive
An aerospace executive is a high-level business leader responsible for guiding the strategic direction, operations, and financial performance of organizations involved in the design, manufacture, and support of aircraft, spacecraft, and related technologies.
-
B.
aerospace expert
An aerospace expert is a highly skilled professional with deep knowledge of aeronautics and astronautics who designs, analyzes, and optimizes aircraft, spacecraft, and related systems for performance, safety, and reliability.
-
C.
aerospace organization
chosen
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.
-
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.
aerospace industry trend
An aerospace industry trend is a recurring pattern or directional shift in technologies, markets, regulations, or business models that collectively shape the future development and competitiveness of the aerospace sector.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 8:04 p.m.