Triple
T8266693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major League Baseball on ESPN |
E193318
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | television sports broadcasting franchise |
C12452
|
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 sports broadcasting franchise Context triple: [Major League Baseball on ESPN, instanceOf, television sports broadcasting franchise]
-
A.
regional sports network
A regional sports network is a television or streaming channel that primarily broadcasts live games, analysis, and related programming focused on professional, collegiate, or local sports teams within a specific geographic area.
-
B.
sports television broadcast
chosen
A sports television broadcast is a live or recorded video program that presents sporting events to viewers, combining game coverage, commentary, analysis, graphics, and replays.
-
C.
sports media rights package
A sports media rights package is a bundled set of licensed broadcasting, streaming, and distribution rights for specific sports events, leagues, or seasons, sold to media platforms for a defined term and territory.
-
D.
sports media division
A sports media division is an organizational unit responsible for creating, managing, and distributing sports-related content across various media platforms to engage audiences and support business objectives.
-
E.
sports television program block
A sports television program block is a scheduled segment of TV programming dedicated to broadcasting sports-related content, such as live games, highlights, analysis, and commentary, within a defined time period.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:50 p.m.