Triple
T18424591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing–Saab |
E442103
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace partnership |
C8844
|
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: aerospace partnership Context triple: [Boeing–Saab, instanceOf, aerospace partnership]
-
A.
aerospace organization
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.
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.
-
C.
aerospace hub
An aerospace hub is a centralized facility or region where aerospace research, manufacturing, testing, and logistics activities are concentrated to support the development and operation of aircraft and spacecraft.
-
D.
aerospace program
An aerospace program is an organized initiative or series of projects focused on the research, development, testing, and operation of aircraft, spacecraft, and related technologies to achieve specific scientific, commercial, or defense objectives.
-
E.
strategic partnership
chosen
A strategic partnership is a long-term, collaborative relationship between two or more independent organizations that align resources, capabilities, and objectives to achieve mutually beneficial competitive advantages they could not easily attain alone.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:47 a.m.