Triple
T33189871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bertelsmann |
E849572
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | media and services conglomerate |
C33856
|
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: media and services conglomerate Context triple: [Bertelsmann, instanceOf, media and services conglomerate]
-
A.
media and telecommunications conglomerate
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.
-
B.
multimedia company
A multimedia company is an organization that creates, produces, and distributes content across multiple media formats—such as video, audio, text, and interactive platforms—to inform, entertain, or engage audiences.
-
C.
media and communications company
chosen
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.
-
D.
leisure and entertainment company
A leisure and entertainment company is an organization that creates, manages, and delivers recreational, cultural, and amusement experiences to consumers through venues, events, media, or activities designed for enjoyment and relaxation.
-
E.
media and hospitality company
A media and hospitality company is an organization that creates, distributes, and monetizes content while simultaneously providing lodging, dining, and experiential services to consumers.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:29 a.m.