Triple
T6784206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikoyan design bureau |
E155759
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aircraft design bureau |
C10690
|
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: aircraft design bureau Context triple: [Mikoyan design bureau, instanceOf, aircraft design bureau]
-
A.
rocket design bureau
A rocket design bureau is an organization that specializes in the research, engineering, and development of rocket systems and related aerospace technologies.
-
B.
Soviet design bureau
A Soviet design bureau was a state-controlled, specialized engineering and research organization responsible for conceiving, developing, and prototyping advanced military and industrial technologies within the centrally planned Soviet system.
-
C.
aircraft designer
An aircraft designer is a professional who conceptualizes, plans, and develops the structure, systems, and performance characteristics of airplanes and other flying vehicles to meet safety, efficiency, and mission requirements.
-
D.
Soviet aircraft
Soviet aircraft are military and civilian airplanes and helicopters designed, produced, or operated by the Soviet Union, reflecting its technological, strategic, and industrial priorities from 1922 to 1991.
-
E.
design bureau
chosen
A design bureau is an organization or department that specializes in planning, developing, and refining product, graphic, or architectural designs, often providing creative and technical solutions for clients or internal projects.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:14 p.m.