Triple
T23165923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamaru Usman |
E578709
|
entity |
| Predicate | preUFCBackground |
P151177
|
FINISHED |
| Object | collegiate wrestling |
—
|
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: collegiate wrestling | Statement: [Kamaru Usman, preUFCBackground, collegiate wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preUFCBackground Context triple: [Kamaru Usman, preUFCBackground, collegiate wrestling]
-
A.
UFCDebutResult
Indicates the outcome of a fighter’s first bout in the UFC, specifying how that debut fight concluded.
-
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.
preFightHype
Indicates the promotional buildup, media buzz, and public excitement generated in anticipation of a fight or competitive matchup.
-
E.
roleInUFC
Indicates the specific capacity or position an entity holds within the context of the Ultimate Fighting Championship (UFC), such as fighter, referee, coach, or official.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2bca4881909f6148d588948018 |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b75e2708190ba48875e36f983bc |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:03 p.m.