Triple
T38415191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glover Teixeira |
E901582
|
entity |
| Predicate | wonUFCTitleEvent |
P44164
|
FINISHED |
| Object | UFC 267 |
—
|
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: UFC 267 | Statement: [Glover Teixeira, wonUFCTitleEvent, UFC 267]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonUFCTitleEvent Context triple: [Glover Teixeira, wonUFCTitleEvent, UFC 267]
-
A.
UFCChampionship
chosen
Indicates that an entity holds or has held a championship title in the Ultimate Fighting Championship (UFC) organization.
-
B.
eventChallengedForUFCWelterweightTitle
Indicates that an event involved a fighter challenging for the UFC Welterweight Championship title.
-
C.
wonTheUltimateFighterAs
Indicates that an individual won a season of The Ultimate Fighter competition while competing in a specified weight class or role.
-
D.
wonInternationalTitle
Indicates that an entity has achieved victory in a competition or event that is recognized at an international level, earning an international title.
-
E.
inauguralTitleFightWinner
Indicates the entity that won the very first title fight for a given championship or division.
- 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.