Triple
T2925028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kroenke Sports & Entertainment |
E78822
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports and entertainment holding company |
C3826
|
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: sports and entertainment holding company Context triple: [Kroenke Sports & Entertainment, instanceOf, sports and entertainment holding company]
-
A.
sports and entertainment company
chosen
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.
-
B.
sports management company
A sports management company is an organization that represents and supports athletes or sports entities by handling contracts, marketing, endorsements, career planning, and related business affairs.
-
C.
sports team owner
A sports team owner is an individual or entity that holds the legal and financial control of a professional or amateur sports franchise, overseeing its strategic direction, operations, and major business decisions.
-
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-owning family
A sports-owning family is a family whose members collectively own and control a professional sports franchise, often influencing its strategic, financial, and cultural direction across generations.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:55 p.m.