Triple
T18163909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Focke-Wulf design bureau |
E434839
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aeronautical engineering office |
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: aeronautical engineering office Context triple: [Focke-Wulf design bureau, instanceOf, aeronautical engineering office]
-
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.
aeronautical engineering community
A group of professionals, researchers, students, and enthusiasts who share knowledge, collaborate, and advance the field of aeronautical engineering and aircraft-related technologies.
-
C.
air engineering squadron
An air engineering squadron is a military unit responsible for the maintenance, repair, testing, and technical support of aircraft and related aerospace systems to ensure their operational readiness and safety.
-
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 engineer
An aerospace engineer is a professional who designs, develops, tests, and improves aircraft, spacecraft, satellites, and related systems to ensure safe, efficient, and reliable flight within and beyond Earth’s atmosphere.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:30 a.m.