Triple
T35805420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batista vs Triple H |
E1035089
|
entity |
| Predicate | thirdMajorMatchEvent |
P191038
|
FINISHED |
| Object | Vengeance 2005 |
—
|
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: Vengeance 2005 | Statement: [Batista vs Triple H, thirdMajorMatchEvent, Vengeance 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdMajorMatchEvent Context triple: [Batista vs Triple H, thirdMajorMatchEvent, Vengeance 2005]
-
A.
hasThirdPlaceMatch
Indicates that a competition or tournament includes a specific match played to determine the third-place finisher between the losing semifinalists or equivalent contenders.
-
B.
isThirdMLSChampionshipMatch
Indicates that the match is the third championship (final) game in the history of Major League Soccer.
-
C.
thirdPlaceMatchScore
Indicates the score recorded in a match that determines the third-place finisher in a competition or tournament.
-
D.
thirdMainCardBout
chosen
Indicates a bout or match that is scheduled as the third main card fight in an event’s lineup.
-
E.
decisiveMatchOf
Indicates that one entity is a match for another in a way that determines or strongly influences a final outcome or decision.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:06 p.m.