Triple
T34804047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 257 |
E1003299
|
entity |
| Predicate | resultMainEventWinner |
P6361
|
FINISHED |
| Object | Dustin Poirier |
—
|
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: Dustin Poirier | Statement: [UFC 257, resultMainEventWinner, Dustin Poirier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultMainEventWinner Context triple: [UFC 257, resultMainEventWinner, Dustin Poirier]
-
A.
coMainEventWinner
Indicates that an entity is one of the winners of a shared or jointly headlined main event.
-
B.
mainWinner
chosen
Indicates that one entity is the primary or overall winner in a competition, contest, or comparative outcome relative to others.
-
C.
leaderOfMainWinner
Indicates that an entity serves as the primary leader of the entity that is the main winner in a given context or event.
-
D.
featuredMatchWinner
Indicates that an entity is the winner of a highlighted or prominently featured match.
-
E.
winnerFinalsResult
Indicates the outcome or result achieved by the winner in the finals of a competition or series.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 3:59 p.m.