Triple
T23165611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 2 |
E578703
|
entity |
| Predicate | tournamentFinalBout |
P79233
|
FINISHED |
| Object | Royce Gracie vs Patrick Smith |
—
|
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: Royce Gracie vs Patrick Smith | Statement: [UFC 2, tournamentFinalBout, Royce Gracie vs Patrick Smith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentFinalBout Context triple: [UFC 2, tournamentFinalBout, Royce Gracie vs Patrick Smith]
-
A.
finalTournamentStage
chosen
Indicates that an event or match represents the concluding or championship stage of a tournament.
-
B.
isFinalsOf
Indicates that one entity represents the final or concluding stage, round, or version of another entity.
-
C.
hasFinalTournament
Indicates that an entity is associated with a specific tournament that serves as its final or concluding competition.
-
D.
divisionFinalsMatchup
Indicates a competitive pairing between two entities in the final round of a division-level contest or tournament.
-
E.
semifinalMatchup
Indicates that two competitors or teams are paired to compete against each other in a semifinal round of a tournament or competition.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2bca4881909f6148d588948018 |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:03 p.m.