Triple
T34804052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 257 |
E1003299
|
entity |
| Predicate | resultCoMainEventLoser |
P151182
|
FINISHED |
| Object | Dan Hooker |
—
|
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: Dan Hooker | Statement: [UFC 257, resultCoMainEventLoser, Dan Hooker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultCoMainEventLoser Context triple: [UFC 257, resultCoMainEventLoser, Dan Hooker]
-
A.
coMainEventLoser
chosen
Indicates that the subject is the competitor who lost in the co-main event of a competition or fight card.
-
B.
mainEventLoser
Indicates that the subject entity is the loser of the primary or main event in a given context.
-
C.
coMainEventWinner
Indicates that an entity is one of the winners of a shared or jointly headlined main event.
-
D.
finalBoutLoser
Indicates that an entity is the competitor who lost in the final bout of a match, tournament, or competition.
-
E.
mainEventPreviousMeetingLoser
Indicates that the referenced entity is the loser of the previous meeting between the participants in the main event.
- 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_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 3, 2026, 3:59 p.m.