Triple
T27879294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slammiversary |
E705042
|
entity |
| Predicate | hasMainPromotionBrand |
P197551
|
FINISHED |
| Object | Impact Wrestling main roster |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Impact Wrestling main roster | Statement: [Slammiversary, hasMainPromotionBrand, Impact Wrestling main roster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainPromotionBrand Context triple: [Slammiversary, hasMainPromotionBrand, Impact Wrestling main roster]
-
A.
hasMainPromotion
Indicates that an entity is associated with its primary or most prominent promotional offer or campaign.
-
B.
hasPromotionTarget
Indicates that an entity is the intended recipient, audience, or focus of a promotional activity or campaign.
-
C.
hasPromotionStyle
Indicates the manner or approach used to promote or market something in relation to another entity.
-
D.
hasPromotionName
Indicates that an entity is associated with a specific promotion identified by a given name.
-
E.
hasCoBrand
Indicates that two brands are jointly associated or partnered in offering a product, service, or marketing initiative.
- F. None of above. chosen
Provenance (4 batches)
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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
| PDg | Predicate description generation | batch_69fe9b013ec481908f89beddb9c4cd4e |
completed | May 9, 2026, 2:25 a.m. |
Created at: April 27, 2026, 6:29 p.m.