Triple
T9029972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harris Controls Division |
E216143
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of Harris Corporation |
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: division of Harris Corporation Context triple: [Harris Controls Division, instanceOf, division of Harris Corporation]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
division of JPMorgan Chase
A division of JPMorgan Chase is an organizational unit within the global financial services firm that focuses on a specific set of products, services, or markets under the broader corporate structure.
-
E.
defense contractor business unit
A defense contractor business unit is an organizational division within a defense company that focuses on developing, producing, and supporting specific military or security-related products, services, or programs for government and allied customers.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:08 p.m.