Triple
T35905694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC Welterweight Championship |
E1038465
|
entity |
| Predicate | isFiveRoundFightsForTitle |
P179175
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [UFC Welterweight Championship, isFiveRoundFightsForTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFiveRoundFightsForTitle Context triple: [UFC Welterweight Championship, isFiveRoundFightsForTitle, true]
-
A.
isWorldChampionshipFight
Indicates that a given fight is officially recognized as a world championship bout for a title in its sport.
-
B.
isTitleFight
Indicates that a competitive match or bout is officially designated as being for a championship title.
-
C.
roundOfChampionship
Indicates the specific stage or round within a championship competition in which an event, match, or result takes place.
-
D.
typicalRoundsForTitleBouts
chosen
Indicates the usual or standard number of rounds scheduled for championship (title) fights.
-
E.
thirdFightRounds
Indicates the number of rounds that occurred in the third fight of a series or sequence of fights.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa6f167481908a174f615299e151 |
completed | May 3, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:07 p.m.