Triple
T14204991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lavochkin design bureau |
E352065
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defense 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: defense design bureau Context triple: [Lavochkin design bureau, instanceOf, defense design bureau]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
defense company
A defense company is an organization that designs, develops, manufactures, and supports military and security-related products, technologies, and services for governments and authorized entities.
-
E.
bridge design bureau
A bridge design bureau is a specialized engineering organization responsible for planning, analyzing, and designing bridge structures to meet safety, functionality, and aesthetic requirements.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:05 a.m.