Triple
T30719234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Backlash 2023 |
E782105
|
entity |
| Predicate | championInvolved |
P171596
|
FINISHED |
| Object | Rhea Ripley |
—
|
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: Rhea Ripley | Statement: [WWE Backlash 2023, championInvolved, Rhea Ripley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championInvolved Context triple: [WWE Backlash 2023, championInvolved, Rhea Ripley]
-
A.
championOf
Indicates that one entity serves as the primary defender, advocate, or leading supporter of another entity, often working to promote or protect its interests.
-
B.
champion
Indicates that one entity has won a competition or contest and holds the top position or title over others.
-
C.
championedBy
Indicates that an entity is actively supported, promoted, or advocated for by another entity.
-
D.
championWins
Indicates that a champion emerges victorious in a competition, match, or contest.
-
E.
championPairs
Indicates a relationship where two entities are linked as a champion pair, typically representing partners or counterparts that jointly hold or share a champion status in some context.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 8:36 p.m.