Triple
T13092289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KSE |
E310490
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | entertainment holding company |
C32444
|
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: entertainment holding company Context triple: [KSE, instanceOf, entertainment holding company]
-
A.
cultural and entertainment company division
A cultural and entertainment company division is an organizational unit within a larger enterprise that develops, manages, and delivers cultural, artistic, and entertainment products or services to targeted audiences.
-
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 franchise company
A media franchise company is an organization that creates, owns, manages, and licenses interconnected entertainment properties (such as films, TV shows, games, and merchandise) under shared brands, characters, or story universes.
-
D.
sports and entertainment company
A sports and entertainment company is an organization that creates, manages, and promotes athletic competitions, live events, media content, and related experiences for audiences and fans.
-
E.
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.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
Created at: April 9, 2026, 9:03 p.m.