Triple
T23917638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cody Rhodes |
E602125
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | professional wrestling executive |
C32656
|
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 wrestling executive Context triple: [Cody Rhodes, instanceOf, professional wrestling executive]
-
A.
professional wrestling promoter
A professional wrestling promoter is an individual or organization responsible for organizing, marketing, and financing wrestling events, managing talent, and crafting storylines to attract and entertain audiences.
-
B.
professional wrestling authority figure
A professional wrestling authority figure is an on-screen character, such as a promoter, general manager, or commissioner, who is portrayed as having the power to make matches, enforce rules, and influence storylines within a wrestling promotion.
-
C.
professional wrestling booker
chosen
A professional wrestling booker is the person responsible for planning match outcomes, storylines, and character directions to shape the overall narrative and business strategy of a wrestling promotion.
-
D.
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.
-
E.
professional wrestling promotion
A professional wrestling promotion is an organization that produces, markets, and presents scripted wrestling events and storylines using contracted performers for live audiences and broadcast media.
- 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 8:40 p.m.