Triple
T26346142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RVD |
E662780
|
entity |
| Predicate | wonTitleByCashingIn |
P160431
|
FINISHED |
| Object | WWE Championship |
—
|
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: WWE Championship | Statement: [RVD, wonTitleByCashingIn, WWE Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonTitleByCashingIn Context triple: [RVD, wonTitleByCashingIn, WWE Championship]
-
A.
usesWinningsFor
Indicates that an entity allocates or spends its winnings or prize money for a particular purpose or beneficiary.
-
B.
wonTitleWith
Indicates that an entity secured a specific title, award, or championship while being associated with or representing another entity (such as a team, organization, or group).
-
C.
winnerReceives
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
-
D.
wonTitleFrom
Indicates that one entity obtained a title or championship by defeating or surpassing another specific entity who previously held it.
-
E.
winnerMake
Indicates that one entity causes or brings about another entity becoming the winner in a contest, competition, or selection process.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa718188190a3f4d76db2cdf670 |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 10:42 p.m.