Triple
T27879179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impact World Championship |
E705040
|
entity |
| Predicate | formerPromotionName |
P171438
|
FINISHED |
| Object | Total Nonstop Action Wrestling |
—
|
NE NERFINISHED |
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: Total Nonstop Action Wrestling | Statement: [Impact World Championship, formerPromotionName, Total Nonstop Action Wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerPromotionName Context triple: [Impact World Championship, formerPromotionName, Total Nonstop Action Wrestling]
-
A.
originalPromotion
Indicates that one entity is the initial or primary promotion from which another promotion, offer, or campaign is derived or related.
-
B.
promotedFrom
Indicates that an entity has advanced to a new position, role, or status from a specified prior one.
-
C.
promotionFormerName
chosen
Indicates that an entity previously operated or was known under a different promotion name before adopting its current one.
-
D.
finalPromotion
Indicates that an entity has received its ultimate or last promotion in a sequence of possible advancements.
-
E.
formerName
Indicates that an entity was previously known by a different name in the past.
- F. None of above.
Provenance (3 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_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 27, 2026, 6:29 p.m.