Triple
T30719235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Backlash 2023 |
E782105
|
entity |
| Predicate | challengerInvolved |
P40099
|
FINISHED |
| Object | Zelina Vega |
—
|
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: Zelina Vega | Statement: [WWE Backlash 2023, challengerInvolved, Zelina Vega]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: challengerInvolved Context triple: [WWE Backlash 2023, challengerInvolved, Zelina Vega]
-
A.
challenger
chosen
Indicates that one entity is challenging or opposing another, typically by initiating a contest, dispute, or competitive confrontation.
-
B.
challengerSyndicate
Indicates a relationship where an entity acts as a challenger or rival within, or in opposition to, a particular syndicate or organized group.
-
C.
challengerParty
Indicates the political party that is opposing or seeking to unseat an incumbent or dominant party in a given contest or election.
-
D.
challengerStatus
Indicates the role or condition of an entity as a challenger in a competitive or adversarial context.
-
E.
laterChallengedBy
Indicates that an earlier claim, decision, or position was subsequently questioned, disputed, or opposed by another party.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c583438819093b812f11327eb60 |
completed | May 2, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:36 p.m.