Triple
T26346543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Hardcore Championship |
E662789
|
entity |
| Predicate | unificationMatchWinner |
P160995
|
FINISHED |
| Object | Rob Van Dam |
—
|
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: Rob Van Dam | Statement: [WWE Hardcore Championship, unificationMatchWinner, Rob Van Dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unificationMatchWinner Context triple: [WWE Hardcore Championship, unificationMatchWinner, Rob Van Dam]
-
A.
featuredMatchWinner
Indicates that an entity is the winner of a highlighted or prominently featured match.
-
B.
finalMatchType
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
C.
determinedPennantWinnerFor
Indicates that one entity has been determined as the pennant-winning team for a particular league, season, or competition.
-
D.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
E.
divisionWinnerTeam2
Indicates that the second team is the winner of its division in a competition or league.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa7f0588190988ce7483ab7523d |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 26, 2026, 10:42 p.m.