Triple
T13246800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania 39 |
E315425
|
entity |
| Predicate | featuredMatchOutcome |
P51199
|
FINISHED |
| Object | Rhea Ripley defeated Charlotte Flair |
—
|
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: Rhea Ripley defeated Charlotte Flair | Statement: [WrestleMania 39, featuredMatchOutcome, Rhea Ripley defeated Charlotte Flair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredMatchOutcome Context triple: [WrestleMania 39, featuredMatchOutcome, Rhea Ripley defeated Charlotte Flair]
-
A.
featuredMatchWinner
chosen
Indicates that an entity is the winner of a highlighted or prominently featured match.
-
B.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
C.
featuredMatchLoser
Indicates that an entity is the participant who lost in a designated featured match.
-
D.
featuredMatchType
Indicates the specific category or kind of match that is highlighted or given special prominence.
-
E.
finalMatchDecidedBy
Indicates that the outcome of a final match is determined by a specific method, event, or deciding factor.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d5c09f88190bb1566a6d8c073a6 |
completed | April 10, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69d98bcca7d88190a3e68e99ed3a29e6 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.