Triple
T13358532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 100 |
E318758
|
entity |
| Predicate | roundOfHendersonBispingFinish |
P109203
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [UFC 100, roundOfHendersonBispingFinish, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundOfHendersonBispingFinish Context triple: [UFC 100, roundOfHendersonBispingFinish, 2]
-
A.
roundOfMainEventFinish
chosen
Indicates the specific round in which the main event concludes or is finished.
-
B.
roundOfKnockdown
Indicates the specific round in which a knockdown event occurs during a fight or match.
-
C.
reachedRound
Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
-
D.
finalRoundMargin
Indicates the point or score difference between competitors in the final round of a contest or competition.
-
E.
championshipOutcome
Indicates the result or final standing of a competitor or team in a championship event.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da62887e588190bd7241c720a112a2 |
completed | April 11, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.