Triple
T17638606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group W Satellite Communications |
E429164
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | television technology company division |
C39467
|
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: television technology company division Context triple: [Group W Satellite Communications, instanceOf, television technology company division]
-
A.
television broadcasting company division
A television broadcasting company division is an organizational unit within a broadcasting company responsible for managing specific channels, content genres, regional operations, or functional areas such as programming, production, or distribution.
-
B.
television broadcasting division
The television broadcasting division is the organizational unit responsible for planning, producing, scheduling, and transmitting television content to audiences across designated channels and platforms.
-
C.
television company
A television company is an organization that produces, acquires, schedules, and broadcasts television content to audiences through various distribution channels such as terrestrial, cable, satellite, or streaming platforms.
-
D.
television brand
A television brand is a company or label that designs, manufactures, and markets televisions, often distinguished by its technology, quality, features, and market positioning.
-
E.
television distribution company
A television distribution company is an organization that acquires, packages, and delivers TV content to broadcasters, streaming platforms, and other outlets across various regions and markets.
- F. None of above. chosen
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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 6 a.m.