Triple
T3411063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania 29 |
E71893
|
entity |
| Predicate | preShowMatch |
P23679
|
FINISHED |
| Object | The Miz vs. Wade Barrett |
—
|
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: The Miz vs. Wade Barrett | Statement: [WrestleMania 29, preShowMatch, The Miz vs. Wade Barrett]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preShowMatch Context triple: [WrestleMania 29, preShowMatch, The Miz vs. Wade Barrett]
-
A.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
B.
openingMatch
chosen
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving another entity.
-
C.
preAttackCondition
Indicates the circumstances or requirements that must be satisfied before an attack can be initiated.
-
D.
preparesFor
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
E.
appearsBefore
Indicates that one entity occurs, is positioned, or is presented earlier in an ordered sequence than another entity.
- 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9094b2881909262e58a470ed9d0 |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.