Triple
T52656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raytheon Company |
E1034
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace and defense company |
C136
|
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 and defense company Context triple: [Raytheon Company, instanceOf, aerospace and defense company]
-
A.
manufacturing company
chosen
A manufacturing company is an organization that transforms raw materials or components into finished goods through industrial processes, machinery, and labor for sale to other businesses or consumers.
-
B.
defense organization
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
-
C.
engineering firm
An engineering firm is a business organization that provides professional engineering services—such as design, analysis, consulting, and project management—to plan, develop, and implement technical solutions for clients in various industries.
-
D.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
E.
federally owned corporation
A federally owned corporation is a government-established legal entity that operates commercial or public service activities on behalf of the federal government while retaining a distinct corporate structure.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.