Triple
T22253642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Communication Systems |
E550042
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | L3Harris Technologies division |
C1871
|
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: L3Harris Technologies division Context triple: [Communication Systems, instanceOf, L3Harris Technologies division]
-
A.
Collins Aerospace division
A Collins Aerospace division is an organizational unit within Collins Aerospace responsible for specific product lines, technologies, or market segments in the aerospace and defense industry.
-
B.
Boeing division
A Boeing division is an organizational unit within The Boeing Company responsible for specific product lines, services, or business functions such as commercial airplanes, defense systems, or global services.
-
C.
defense contractor division
chosen
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.
-
D.
NASA division
A NASA division is an organizational unit within NASA responsible for managing specific programs, research areas, or operational functions to support the agency’s overall space and aeronautics mission.
-
E.
F-35 program office
The F-35 program office is the organizational entity responsible for managing, coordinating, and overseeing all aspects of the F-35 Joint Strike Fighter’s development, production, sustainment, and integration across participating services and partner nations.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:39 p.m.