Triple
T23684580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 239 |
E585127
|
entity |
| Predicate | coMainEventChallenger |
P145609
|
FINISHED |
| Object | Holly Holm |
—
|
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: Holly Holm | Statement: [UFC 239, coMainEventChallenger, Holly Holm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coMainEventChallenger Context triple: [UFC 239, coMainEventChallenger, Holly Holm]
-
A.
coMainEventWinner
Indicates that an entity is one of the winners of a shared or jointly headlined main event.
-
B.
coMainEvent
Indicates that two or more events share equal primary status as the main featured events within the same program or occasion.
-
C.
featuredChallenger
chosen
Indicates that an entity is highlighted or designated as a primary or special challenger in a given context or competition.
-
D.
coMainEventLoser
Indicates that the subject is the competitor who lost in the co-main event of a competition or fight card.
-
E.
majorChallenger
Indicates that one entity is a primary competitor or leading rival to another in a given context or domain.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4fb26c88190a6776e4dfd10d54c |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.