Triple
T35905695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC Welterweight Championship |
E1038465
|
entity |
| Predicate | standardTitleFightRounds |
P179175
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [UFC Welterweight Championship, standardTitleFightRounds, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardTitleFightRounds Context triple: [UFC Welterweight Championship, standardTitleFightRounds, 5]
-
A.
typicalRoundsForTitleBouts
chosen
Indicates the usual or standard number of rounds scheduled for championship (title) fights.
-
B.
numberOfTournamentFights
Indicates the total count of fights that occurred within a specific tournament.
-
C.
titleFightsConsistOf
Indicates that a set of title fights is composed of, or made up from, specific individual fights.
-
D.
inauguralTitleFightRound
Indicates the specific round in which an inaugural (first-ever) title fight takes place or is decided.
-
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_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:07 p.m.