Triple
T13221215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Football League ownership group |
E314756
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports ownership collective |
C19039
|
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 ownership collective Context triple: [National Football League ownership group, instanceOf, sports ownership collective]
-
A.
sports team collective
A sports team collective is a coordinated group of athletes, coaches, and supporting staff who work together under a shared identity to compete in organized sporting events and pursue common performance goals.
-
B.
sports organization collective
chosen
A sports organization collective is a coordinated group of sports entities—such as teams, clubs, leagues, or associations—that collaborate under shared governance, resources, or objectives to promote, manage, and develop athletic activities.
-
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-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.
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.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:18 p.m.