Triple
T14100145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snecma engineering division |
E339356
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace engineering organization unit |
C22434
|
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 engineering organization unit Context triple: [Snecma engineering division, instanceOf, aerospace engineering organization unit]
-
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 engineering subsystem
An aerospace engineering subsystem is a specialized, interrelated component or functional unit within an aerospace vehicle or system (such as propulsion, avionics, or thermal control) that performs a distinct set of engineering tasks to support overall mission objectives.
-
D.
military aviation maintenance organization
A military aviation maintenance organization is a structured unit responsible for inspecting, repairing, servicing, and ensuring the airworthiness and mission readiness of military aircraft and related systems.
-
E.
systems engineering organization
chosen
A systems engineering organization is a structured group that plans, designs, integrates, and manages complex systems across their life cycles to meet stakeholder needs within technical, cost, and schedule constraints.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:22 p.m.