Triple
T17050532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamond Baseball Holdings |
E413682
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | baseball team ownership group |
C671
|
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: baseball team ownership group Context triple: [Diamond Baseball Holdings, instanceOf, baseball team ownership group]
-
A.
Major League Baseball owner
A Major League Baseball owner is an individual or entity that holds a controlling financial stake in an MLB franchise and oversees its strategic, business, and operational decisions.
-
B.
sports team owner
chosen
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.
-
C.
stakeholders in Major League Baseball
Stakeholders in Major League Baseball are the individuals and groups—such as team owners, players, league officials, broadcasters, sponsors, local communities, and fans—who have a financial, professional, or personal interest in the operation, governance, and outcomes of the league.
-
D.
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.
-
E.
organizational unit of Major League Baseball
An organizational unit of Major League Baseball is a formal structural division—such as a league, division, team, or affiliated entity—established to manage competition, governance, and operations within the MLB system.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:34 a.m.