Triple
T21588271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khamzat Chimaev |
E532709
|
entity |
| Predicate | wonPerformanceOfTheNightBonuses |
P128987
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Khamzat Chimaev, wonPerformanceOfTheNightBonuses, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonPerformanceOfTheNightBonuses Context triple: [Khamzat Chimaev, wonPerformanceOfTheNightBonuses, yes]
-
A.
winningPerformer
Indicates that the referenced performer is the one who achieved victory or first place in a particular competition, event, or contest.
-
B.
bestRockPerformanceWinner
Indicates that an entity is the winner of an award for best rock music performance.
-
C.
fightOfTheNightRecipients
Indicates that the related entities are recipients of a "Fight of the Night" award for a particular combat sports event.
-
D.
bingoBonus
Indicates that an entity receives or is associated with a bonus specifically awarded in the context of a bingo game or bingo-related activity.
-
E.
hasWonBonus
chosen
Indicates that an entity has received or been awarded a bonus, typically as a result of meeting certain conditions or achieving specific performance.
- 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb621ab88190a33a943424ffb306 |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:31 p.m.