Triple
T28568883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing (video and marketing department) |
E722759
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corporate communications unit |
C39822
|
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: corporate communications unit Context triple: [Boeing (video and marketing department), instanceOf, corporate communications unit]
-
A.
public relations department
chosen
A public relations department is an organizational unit responsible for managing a company’s communication and relationships with its various publics to build and maintain a positive image and reputation.
-
B.
communications unit
A communications unit is a modular component responsible for managing, formatting, and transmitting information between systems, devices, or subsystems using defined communication protocols.
-
C.
communications agency
A communications agency is a professional service firm that develops and executes strategic messaging, branding, and media outreach to help organizations effectively engage and influence their target audiences.
-
D.
media and communications company
A media and communications company is an organization that creates, distributes, and manages content and messaging across various channels to inform, entertain, and connect audiences.
-
E.
military public affairs unit
A military public affairs unit is an organizational entity responsible for managing communication between the armed forces and the public, including media relations, community engagement, and information dissemination to support operational objectives and maintain public trust.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 4:08 a.m.