Triple
T35628444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elimination Chamber 2019 |
E1029518
|
entity |
| Predicate | womenTagTitlesWonBy |
P134176
|
FINISHED |
| Object | Bayley and Sasha Banks |
—
|
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: Bayley and Sasha Banks | Statement: [Elimination Chamber 2019, womenTagTitlesWonBy, Bayley and Sasha Banks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: womenTagTitlesWonBy Context triple: [Elimination Chamber 2019, womenTagTitlesWonBy, Bayley and Sasha Banks]
-
A.
womenPastChampion
chosen
Indicates that the subject has previously won a championship title in a women's competition or event.
-
B.
notableFemaleWinner
Indicates that the subject is a female who has achieved a notable or distinguished victory in the specified context.
-
C.
recordWinners
Indicates that an entity documents or stores information about the winners of a particular event, contest, or competition.
-
D.
majorTitleWon
Indicates that an entity has won a significant or top-level title, championship, or major award in a given domain.
-
E.
womenAllAroundChampion
Indicates that women are present surrounding or on all sides of the champion.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:05 p.m.