Triple
T29037968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania 36 |
E737916
|
entity |
| Predicate | mainEventNight1Stipulation |
P108734
|
FINISHED |
| Object | Boneyard match |
—
|
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: Boneyard match | Statement: [WrestleMania 36, mainEventNight1Stipulation, Boneyard match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEventNight1Stipulation Context triple: [WrestleMania 36, mainEventNight1Stipulation, Boneyard match]
-
A.
night2MainEventStipulation
Indicates that the predicate specifies the rules or conditions (stipulation) governing the main event held on the second night of a multi-night event or show.
-
B.
mainEventNight1
Indicates the primary or most significant event occurring on the first night in a sequence or schedule.
-
C.
mainEventNight2
Indicates that an event occurs as the primary or featured event during the second night of a sequence or schedule.
-
D.
mainEventNight1MatchType
chosen
Indicates the specific type or stipulation of a match that takes place during the first night of the main event.
-
E.
mainEventNight2Outcome
Indicates the resulting state or consequence that occurs as a result of the second night's main event.
- 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_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 10 a.m.