Triple
T38333937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania XX |
E1037899
|
entity |
| Predicate | openingMatchWinner |
P194453
|
FINISHED |
| Object | John Cena |
—
|
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: John Cena | Statement: [WrestleMania XX, openingMatchWinner, John Cena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingMatchWinner Context triple: [WrestleMania XX, openingMatchWinner, John Cena]
-
A.
openingMatchResult
Indicates the outcome or result associated with the opening match in a series, tournament, or competition.
-
B.
openingMatch
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving another entity.
-
C.
openingMatchScore
Indicates the degree of similarity or compatibility between an opening (e.g., a position, role, or opportunity) and a given candidate or item, typically expressed as a numeric score.
-
D.
openingGameResult
Indicates the outcome or result of an entity’s opening game or initial match in a series or season.
-
E.
openingRace
Indicates that one race serves as the initial or first event in a sequence of races or a racing competition.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
| PDg | Predicate description generation | batch_69fd6f9a8bd881909983fe8f4cd0ba98 |
completed | May 8, 2026, 5:07 a.m. |
Created at: May 3, 2026, 4:30 p.m.