Triple
T35636437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rey Mysterio vs. Dominik Mysterio |
E1029732
|
entity |
| Predicate | majorEventMatchAt |
P42689
|
FINISHED |
| Object | WrestleMania 39 |
—
|
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: WrestleMania 39 | Statement: [Rey Mysterio vs. Dominik Mysterio, majorEventMatchAt, WrestleMania 39]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorEventMatchAt Context triple: [Rey Mysterio vs. Dominik Mysterio, majorEventMatchAt, WrestleMania 39]
-
A.
matchOf
chosen
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
B.
matchdayActivity
Indicates the specific activity, event, or engagement that takes place in connection with a particular match day.
-
C.
notableMatch
Indicates that there exists a particularly significant or noteworthy match or pairing between the related entities.
-
D.
notableMatchVenueFor
Indicates that a venue is notably associated with hosting a particular match or game.
-
E.
notableFootballEvent
Indicates an event in football that is distinguished by particular significance, impact, or memorability within the sport.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
Created at: May 3, 2026, 4:05 p.m.