Triple
T2728569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evander Holyfield |
E60253
|
entity |
| Predicate | becameUndisputedChampionInDivision |
P10278
|
FINISHED |
| Object | cruiserweight |
—
|
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: cruiserweight | Statement: [Evander Holyfield, becameUndisputedChampionInDivision, cruiserweight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameUndisputedChampionInDivision Context triple: [Evander Holyfield, becameUndisputedChampionInDivision, cruiserweight]
-
A.
defendingChampion
Indicates that an entity currently holds a title or championship and is defending it against challengers.
-
B.
wonChampionshipAgainst
Indicates that one competitor secured a championship title by defeating another specific opponent.
-
C.
wonDivisionTitle
chosen
Indicates that an entity secured first place in its competitive division, earning the division championship title.
-
D.
championedBy
Indicates that an entity is actively supported, promoted, or advocated for by another entity.
-
E.
championshipFor
Indicates that a championship event or title is held, awarded, or designated for a particular competition, season, or category.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaeaee388190a21e7fa0b8f83546 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.