Triple
T34804048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 257 |
E1003299
|
entity |
| Predicate | resultMainEventLoser |
P51198
|
FINISHED |
| Object | Conor McGregor |
—
|
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: Conor McGregor | Statement: [UFC 257, resultMainEventLoser, Conor McGregor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultMainEventLoser Context triple: [UFC 257, resultMainEventLoser, Conor McGregor]
-
A.
mainEventLoser
chosen
Indicates that the subject entity is the loser of the primary or main event in a given context.
-
B.
coMainEventLoser
Indicates that the subject is the competitor who lost in the co-main event of a competition or fight card.
-
C.
finalBoutLoser
Indicates that an entity is the competitor who lost in the final bout of a match, tournament, or competition.
-
D.
featuredMatchLoser
Indicates that an entity is the participant who lost in a designated featured match.
-
E.
semifinalLoser
Indicates that an entity lost in a semifinal round of a competition or tournament.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 3, 2026, 3:59 p.m.