Triple
T33213186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA management |
E850214
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | professional sports executive function |
C24024
|
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: professional sports executive function Context triple: [NBA management, instanceOf, professional sports executive function]
-
A.
combat sports executive
A combat sports executive is a business leader who oversees the strategic, financial, and operational aspects of combat sports organizations, including event promotion, athlete contracts, media rights, and regulatory compliance.
-
B.
professional movement
A professional movement is a collective, organized effort by members of a profession to advance shared goals such as standards, recognition, working conditions, or social impact within their field.
-
C.
professional athlete
A professional athlete is an individual who competes in organized sports at an elite level and earns income from their athletic performance, endorsements, or related activities.
-
D.
sports marketing executive
chosen
A sports marketing executive develops and oversees strategic marketing campaigns, partnerships, and brand initiatives that promote sports teams, events, or athletes to drive fan engagement and revenue growth.
-
E.
American football executive
An American football executive is a high-level professional responsible for overseeing the strategic, financial, and operational aspects of an American football organization, including player personnel decisions, coaching hires, and long-term team development.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:30 a.m.