Triple
T35636558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Backlash 2016 |
E1029735
|
entity |
| Predicate | womenTitleMatchType |
P184437
|
FINISHED |
| Object | six-pack elimination challenge |
—
|
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: six-pack elimination challenge | Statement: [WWE Backlash 2016, womenTitleMatchType, six-pack elimination challenge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: womenTitleMatchType Context triple: [WWE Backlash 2016, womenTitleMatchType, six-pack elimination challenge]
-
A.
hasWomenTagOrTriosLikeTitle
Indicates that the item’s title suggests it involves women or trio-related content, based on specific tags or title patterns.
-
B.
worldTitleMatch
Indicates that the title of a world matches a specified or expected title.
-
C.
hasFemaleTitleCharacter
Indicates that the subject work includes at least one female character whose title or role is explicitly referenced in its title.
-
D.
womenSystemTopDivision
Indicates that the subject competes in the highest-level division of a women’s sports league or system.
-
E.
titleHolderSex
Indicates the biological or identified sex of the person who holds a particular title.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: May 3, 2026, 4:05 p.m.