Triple
T31653436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Dodson |
E807795
|
entity |
| Predicate | wonTheUltimateFighterAs |
P172066
|
FINISHED |
| Object | bantamweight winner |
—
|
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: bantamweight winner | Statement: [John Dodson, wonTheUltimateFighterAs, bantamweight winner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonTheUltimateFighterAs Context triple: [John Dodson, wonTheUltimateFighterAs, bantamweight winner]
-
A.
producedUFCChampion
Indicates that one entity (such as a gym, team, or country) has been the origin or training base of an individual who became a UFC champion.
-
B.
successorInUFCPromotion
Indicates that one entity directly follows another as the next promotion event or stage within the UFC organization.
-
C.
UFCChampionship
Indicates that an entity holds or has held a championship title in the Ultimate Fighting Championship (UFC) organization.
-
D.
wonChampionshipAgainst
Indicates that one competitor secured a championship title by defeating another specific opponent.
-
E.
UFCDebutYear
Indicates the year in which an entity first appeared or made its debut in the UFC.
- F. None of above. chosen
Provenance (4 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a95b77688190a24eabe11d5fa989 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:54 p.m.