Triple
T34926524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 280 |
E1007302
|
entity |
| Predicate | thirdMainCardBout |
P191038
|
FINISHED |
| Object | Petr Yan vs. Sean O'Malley |
—
|
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: Petr Yan vs. Sean O'Malley | Statement: [UFC 280, thirdMainCardBout, Petr Yan vs. Sean O'Malley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdMainCardBout Context triple: [UFC 280, thirdMainCardBout, Petr Yan vs. Sean O'Malley]
-
A.
thirdBoutSubtitle
Indicates the subtitle or descriptive text associated specifically with the third bout in a sequence of bouts or matches.
-
B.
thirdBoutTitleOnTheLine
Indicates that in the third bout of a series or event, a title is at stake for the competitors.
-
C.
thirdBoutResult
Indicates the outcome or result of the third bout in a sequence of competitive events or matches.
-
D.
thirdBoutDate
Indicates the date on which the third bout, match, or contest in a sequence takes place.
-
E.
thirdFightState
Indicates the condition or status of the entities involved during the third occurrence of a fight or combat interaction.
- 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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd866dd248190bff61c43bee93f54 |
completed | May 7, 2026, 6:22 p.m. |
Created at: May 3, 2026, 4 p.m.