Triple
T22917749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 46 |
E568777
|
entity |
| Predicate | rematchBout |
P63572
|
FINISHED |
| Object | Frank Mir vs. Wes Sims |
—
|
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: Frank Mir vs. Wes Sims | Statement: [UFC 46, rematchBout, Frank Mir vs. Wes Sims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rematchBout Context triple: [UFC 46, rematchBout, Frank Mir vs. Wes Sims]
-
A.
wasRematchOf
chosen
Indicates that an event or contest is a subsequent encounter between the same parties, held as a repeat of a previous matchup.
-
B.
rematchDate
Indicates the date on which a subsequent or repeat contest between the same parties is scheduled or took place.
-
C.
isRematchOfFinal
Indicates that a match is a subsequent encounter replaying the same opponents and stakes as a previous final match.
-
D.
secondFight
Indicates that an entity engages in a second instance of a fight or combat interaction with another entity.
-
E.
otherBoutsIncluded
Indicates that one bout or contest encompasses, contains, or includes one or more other bouts within it.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1807b254c8190bb84596dcacaa35e |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.