Triple
T25996656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Middleweight Championship |
E646503
|
entity |
| Predicate | isWonBy |
P20470
|
FINISHED |
| Object | defeating the reigning champion |
—
|
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: defeating the reigning champion | Statement: [World Middleweight Championship, isWonBy, defeating the reigning champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWonBy Context triple: [World Middleweight Championship, isWonBy, defeating the reigning champion]
-
A.
wonBy
chosen
Indicates that a contest, game, or competition is decided in favor of a particular participant or side.
-
B.
gameWinner
Indicates which participant or team has won a particular game or match.
-
C.
winnerState
Indicates the state or condition of an entity that has achieved victory or been declared the winner in a given context.
-
D.
ownedWinnerOf
Indicates that an entity owns or possesses the winner of a specified competition, contest, or event.
-
E.
winnerPlaysIn
Indicates that the entity identified as the winner of a contest or match participates in a subsequent game, round, or 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6056f481c81909fd23b04483b76a0 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:58 a.m.