Triple
T38312662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 90 |
E1033734
|
entity |
| Predicate | mainEventTitleBout |
P127213
|
FINISHED |
| Object | UFC Middleweight Championship bout |
—
|
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 Middleweight Championship bout | Statement: [UFC 90, mainEventTitleBout, UFC Middleweight Championship bout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEventTitleBout Context triple: [UFC 90, mainEventTitleBout, UFC Middleweight Championship bout]
-
A.
mainEventTitle
Indicates the primary or official title assigned to an event within a given context.
-
B.
mainEventTitleOnTheLine
chosen
Indicates that the primary event’s title is being prominently featured or emphasized as the key focus (e.g., “on the line”) in a given context.
-
C.
titleUnificationBout
Indicates a competitive match or event in which separate titles or championships are contested with the aim of combining them into a single unified title.
-
D.
coMainEventBoutType
Indicates the type or category of the bout designated as the co-main event within a combat sports or similar event card.
-
E.
coMainEventTitleOnTheLine
Indicates that a title is being contested or defended in a co-main event matchup.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 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:30 p.m.