Triple
T13062559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhail Gurevich |
E329234
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | co-founder of aircraft design bureau |
C2329
|
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: co-founder of aircraft design bureau Context triple: [Mikhail Gurevich, instanceOf, co-founder of aircraft design bureau]
-
A.
aircraft designer
chosen
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.
-
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.
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.
-
D.
pioneer of military aviation
A pioneer of military aviation is an early innovator or leader who significantly advanced the development, tactics, technology, or strategic use of aircraft in armed conflict.
-
E.
Soviet Air Defense Forces commander
A Soviet Air Defense Forces commander was a high-ranking military officer responsible for planning, directing, and coordinating the detection, interception, and destruction of hostile aerial threats within the airspace of the Soviet Union and its allies.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:59 p.m.