Triple
T25001346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Great American Bash |
E625726
|
entity |
| Predicate | successorPromotion |
P161630
|
FINISHED |
| Object | World Championship 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: World Championship Wrestling | Statement: [The Great American Bash, successorPromotion, World Championship Wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorPromotion Context triple: [The Great American Bash, successorPromotion, World Championship Wrestling]
-
A.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
-
B.
successorAct
Indicates that one action or event directly follows and replaces another in a sequence or process.
-
C.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
D.
successorPolicy
Indicates that one policy follows or replaces another policy in a sequence or hierarchy.
-
E.
successorInPractice
Indicates that one entity has taken over the role, position, or function of another in actual practice, even if not formally or officially designated as its successor.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 18, 2026, 6:04 a.m.