Triple
T13358530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 100 |
E318758
|
entity |
| Predicate | resultHendersonBisping |
P56461
|
FINISHED |
| Object | Dan Henderson defeated Michael Bisping by KO |
—
|
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: Dan Henderson defeated Michael Bisping by KO | Statement: [UFC 100, resultHendersonBisping, Dan Henderson defeated Michael Bisping by KO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultHendersonBisping Context triple: [UFC 100, resultHendersonBisping, Dan Henderson defeated Michael Bisping by KO]
-
A.
championshipOutcome
Indicates the result or final standing of a competitor or team in a championship event.
-
B.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
C.
resultOfMatch
chosen
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
D.
secondRoundWinner
Indicates that the subject is the winner of the second round in a multi-round competition, contest, or process.
-
E.
subsequentChampionshipResult
Indicates the outcome or result of a championship that occurs immediately after a referenced earlier championship.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da62887e588190bd7241c720a112a2 |
completed | April 11, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.