Triple
T34819981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 267 |
E1003742
|
entity |
| Predicate | coMainEventTitleOnTheLine |
P181518
|
FINISHED |
| Object | UFC Interim Bantamweight Championship |
—
|
NE NERFINISHED |
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: UFC Interim Bantamweight Championship | Statement: [UFC 267, coMainEventTitleOnTheLine, UFC Interim Bantamweight Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coMainEventTitleOnTheLine Context triple: [UFC 267, coMainEventTitleOnTheLine, UFC Interim Bantamweight Championship]
-
A.
mainEventTitleOnTheLine
Indicates that the primary event’s title is being prominently featured or emphasized as the key focus (e.g., “on the line”) in a given context.
-
B.
coMainEvent
Indicates that two or more events share equal primary status as the main featured events within the same program or occasion.
-
C.
mainEventTitle
Indicates the primary or official title assigned to an event within a given context.
-
D.
coMainEventTitleChange
Indicates a change in the title of a co-main event within a larger event or program.
-
E.
coMainEventWinner
Indicates that an entity is one of the winners of a shared or jointly headlined main event.
- F. None of above. chosen
Provenance (4 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77adce5dc81909c8d07ff1c0e9c93 |
completed | May 3, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77a39135081908ae22d2a23b44e74 |
completed | May 3, 2026, 4:39 p.m. |
Created at: May 3, 2026, 4 p.m.