Triple
T13212627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Champion |
E314531
|
entity |
| Predicate | defendsTitleIn |
P40107
|
FINISHED |
| Object | WWE pay-per-view events |
—
|
LITERAL FINISHED |
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 pay-per-view events | Statement: [WWE Champion, defendsTitleIn, WWE pay-per-view events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendsTitleIn Context triple: [WWE Champion, defendsTitleIn, WWE pay-per-view events]
-
A.
isTitleDefenseFor
chosen
Indicates that an event, match, or competition serves as the defending champion’s attempt to retain an existing title or championship.
-
B.
defendedTitleAgainst
Indicates that one entity successfully retained a title or championship by competing against and overcoming a specific opponent.
-
C.
titleDefendedBy
Indicates that a specific title or championship is actively defended or held against challengers by a particular entity.
-
D.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
E.
defendedAs
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9f0f148190a0698ef27573c885 |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:17 p.m.