Triple
T37884874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeastern Conference marching bands |
E944969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports-related musical organization group |
C65723
|
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-related musical organization group Context triple: [Southeastern Conference marching bands, instanceOf, sports-related musical organization group]
-
A.
sports organization collective
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.
-
B.
sports entertainment group
A sports entertainment group is an organization that creates, manages, and promotes live and media-based sports-related events and content to engage and entertain audiences.
-
C.
segregated sports organization
A segregated sports organization is an athletic governing body or club that separates participants, teams, or competitions along lines such as race, gender, or other social categories, enforcing or perpetuating unequal access and opportunities in sport.
-
D.
sports team
A sports team is an organized group of players who cooperate under shared rules and strategies to compete against other groups in a particular sport.
-
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. 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.