Triple
T16820238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saab‑Fairchild partnership |
E408867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace industry partnership |
C24683
|
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 industry partnership Context triple: [Saab‑Fairchild partnership, instanceOf, aerospace industry 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 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.
-
C.
aerospace industry trend
An aerospace industry trend is a recurring pattern or directional shift in technologies, markets, regulations, or business models that collectively shape the future development and competitiveness of the aerospace sector.
-
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.
defense industry joint venture
chosen
A defense industry joint venture is a collaborative business entity formed by two or more organizations to jointly develop, produce, or support military and security-related products or services, sharing resources, risks, and profits.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:23 a.m.