Triple
T29037982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania 36 |
E737916
|
entity |
| Predicate | originalUniversalTitleChallenger |
P40099
|
FINISHED |
| Object | Roman Reigns |
—
|
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: Roman Reigns | Statement: [WrestleMania 36, originalUniversalTitleChallenger, Roman Reigns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalUniversalTitleChallenger Context triple: [WrestleMania 36, originalUniversalTitleChallenger, Roman Reigns]
-
A.
challengerTitle
Indicates that an entity holds the status or designation of a challenger, typically in a competitive or contest-based context.
-
B.
challenger
chosen
Indicates that one entity is challenging or opposing another, typically by initiating a contest, dispute, or competitive confrontation.
-
C.
challengedForTitleAgainst
Indicates that one entity competed against another in a contest or match specifically for a title or championship.
-
D.
originalTitleName
Indicates that one entity is the original or primary title name associated with another entity.
-
E.
featuredChallenger
Indicates that an entity is highlighted or designated as a primary or special challenger in a given context or competition.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: April 28, 2026, 10 a.m.