Triple
T6080398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinclair Broadcast Group |
E135508
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | telecommunications conglomerate |
C12991
|
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: telecommunications conglomerate Context triple: [Sinclair Broadcast Group, instanceOf, telecommunications conglomerate]
-
A.
telecommunications company
A telecommunications company is an organization that provides communication services such as voice, data, and video transmission over wired or wireless networks to individuals and businesses.
-
B.
telecommunications organization
A telecommunications organization is an entity that provides communication services and infrastructure—such as voice, data, and internet connectivity—across distances using wired, wireless, or satellite networks.
-
C.
media and telecommunications conglomerate
chosen
A media and telecommunications conglomerate is a large corporate entity that owns and operates a diverse portfolio of media, entertainment, and communication businesses across multiple platforms and markets.
-
D.
telecommunications network
A telecommunications network is a system of interconnected nodes, transmission media, and protocols that enables the exchange of voice, data, and multimedia information between users and devices over distance.
-
E.
telecommunications magnate
A telecommunications magnate is a powerful and influential business leader who has amassed substantial wealth and control through ownership or dominance of major telecommunications companies and networks.
- 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:11 p.m.