Triple
T31653435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Dodson |
E807795
|
entity |
| Predicate | divisionOnTheUltimateFighter |
P172606
|
FINISHED |
| Object | bantamweight |
—
|
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 | Statement: [John Dodson, divisionOnTheUltimateFighter, bantamweight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionOnTheUltimateFighter Context triple: [John Dodson, divisionOnTheUltimateFighter, bantamweight]
-
A.
wonTheUltimateFighterAs
Indicates that an individual won a season of The Ultimate Fighter competition while competing in a specified weight class or role.
-
B.
divisionIChampionship
Indicates that an entity has won or holds a Division I championship title in a given sport or competition.
-
C.
divisionTitleAtStake
Indicates that a particular division title is being contested or can be won in the referenced event or matchup.
-
D.
divisionRivalry
Indicates a competitive or adversarial relationship between entities that belong to the same division or subgroup within a larger organization or system.
-
E.
divisionChampionship
Indicates that an entity has won a championship title within a specific competitive division or group.
- 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_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 30, 2026, 10:54 p.m.