Triple
T25259166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avionics Division |
E633256
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace electronics division |
C44839
|
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 electronics division Context triple: [Avionics Division, instanceOf, aerospace electronics division]
-
A.
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.
-
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.
avionics system
An avionics system is an integrated collection of electronic hardware and software on an aircraft that manages navigation, communication, monitoring, and control functions to ensure safe and efficient flight operations.
-
D.
aerospace and defense organization unit
chosen
An aerospace and defense organization unit is a structured division within a larger aerospace and defense entity responsible for managing specific functions, projects, or capabilities related to the development, production, or support of aerospace and defense systems.
-
E.
defense contractor division
A defense contractor division is an organizational unit within a defense company responsible for developing, producing, and supporting specific military or security-related products, services, or programs for government and allied clients.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:13 p.m.