Triple
T37881775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utva design bureau |
E944885
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aircraft design organization |
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: aircraft design organization Context triple: [Utva design bureau, instanceOf, aircraft design organization]
-
A.
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.
-
B.
aircraft design study
An aircraft design study is a systematic analysis and exploration of aircraft configurations, technologies, and performance parameters to determine feasible concepts that meet specified mission, safety, cost, and regulatory requirements.
-
C.
aeronautical company
An aeronautical company is an organization that designs, manufactures, tests, and maintains aircraft and related aerospace systems and technologies.
-
D.
aviation infrastructure organization
An aviation infrastructure organization is an entity responsible for planning, developing, operating, and maintaining the physical and technological systems that support air transportation, such as airports, air traffic control, and related facilities.
-
E.
aerospace engine design bureau
An aerospace engine design bureau is an organization that specializes in the research, design, development, and testing of propulsion systems for aircraft and spacecraft, integrating advanced engineering, materials science, and performance analysis.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.