Triple
T35805341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruthless Aggression promo |
E1035088
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | professional wrestling promo |
C32704
|
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 promo Context triple: [Ruthless Aggression promo, instanceOf, professional wrestling promo]
-
A.
professional wrestling segment
chosen
A professional wrestling segment is a scripted, non-wrestling portion of a wrestling show—such as interviews, promos, skits, or in-ring confrontations—designed to advance storylines, develop characters, and engage the audience.
-
B.
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.
-
C.
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.
-
D.
professional wrestling valet
A professional wrestling valet is a performer who accompanies and supports a wrestler to the ring, enhancing their presentation, character, and storylines through managerial, promotional, or dramatic involvement.
-
E.
professional wrestling announcer
A professional wrestling announcer is a broadcast personality who narrates matches, provides context and storytelling, and heightens the drama and excitement of wrestling events for the audience.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.