Triple
T35679629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 82 |
E1030967
|
entity |
| Predicate | knockoutOfTheNightWinner |
P113383
|
FINISHED |
| Object | Chris Leben |
—
|
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: Chris Leben | Statement: [UFC 82, knockoutOfTheNightWinner, Chris Leben]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knockoutOfTheNightWinner Context triple: [UFC 82, knockoutOfTheNightWinner, Chris Leben]
-
A.
winningPerformer
Indicates that the referenced performer is the one who achieved victory or first place in a particular competition, event, or contest.
-
B.
coMainEventWinner
Indicates that an entity is one of the winners of a shared or jointly headlined main event.
-
C.
winnerCharacter
Indicates that one entity is the character who wins or is victorious in a given event, contest, or situation involving another entity.
-
D.
nightSeriesWinner
chosen
Indicates that one entity is the winner of a particular night’s series or session in a recurring competition or event.
-
E.
winnerNickname
Indicates the nickname used to refer to the entity that has won a particular contest, event, or competition.
- 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79fe8ce1481908c66234d2be16d9d |
completed | May 3, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.